Quick answer
Every request must become a registered object with an author, responsible user, status, due date and link to the relevant model, element or document. Conversation remains useful, but it must not be the only place where the decision exists.
What the team sees
A request is sent in chat, a decision is made during a meeting, a file is attached to email and the deadline is stored in a spreadsheet. A week later the team cannot prove which decision is current, who owns the action or what model context was discussed.
Why it keeps happening
Communication channels are being used as the system of record. Messages, tasks, approvals, documents and BIM objects have no shared identity, status model or responsibility chain.
A controlled way to solve it
- Register each request once and give it a stable identifier.
- Capture the model, element, view or document context automatically.
- Assign a responsible person, status and due date.
- Keep approvals and changes in the same history as the discussion.
- Show the same current state to designers, BIM coordinators and managers.
Expected result
The team sees who requested what, who is responsible, what has been approved, what is late and which model context is affected. Decisions remain traceable after people, chats and files change.
Related RS-Systems solution
Revit.Messenger
Chats, requests, tasks, approvals and BIM context in one Revit workspace.
Revit.Messenger →
Revit CDE
A controlled project environment for BIM communication, documents, decisions, tasks and project intelligence.
Revit CDE →Questions and answers
Why is a normal group chat not enough?
A chat is chronological, while project control needs objects with status, responsibility, due dates and evidence links.
Should every message become a task?
No. Only messages that require an action, decision, approval or formal response need a controlled status.