How to Manage Drawing Revisions
Revision control is one of the most common causes of coordination friction. The issue is rarely just the revision letter; it is whether the team can trust what changed and what actions depend on it.
By Coorda
Start with the live set
Good practice starts with plain structure. Use concise drawing titles, reliable revision fields, agreed statuses and named owners. Keep the source drawing attached to each RFI, issue, decision or comment. Do not let responses disappear into email if they change the project record. Make superseded drawings easy to find without letting them look current. These habits are simple, but they are hard to maintain in a spreadsheet once a project becomes busy.
The most important point is that drawing coordination is not only a design activity. It is a project control activity. Teams need to know which drawings are current, what has changed, what has been reviewed, what questions are open and what information has been issued. When those records sit in separate folders, trackers and email chains, the team can still work, but every decision carries more friction. A drawing-led platform gives the team a clearer route from source information to action, then from action to controlled output.
Keep history without creating confusion
The most important point is that drawing coordination is not only a design activity. It is a project control activity. Teams need to know which drawings are current, what has changed, what has been reviewed, what questions are open and what information has been issued. When those records sit in separate folders, trackers and email chains, the team can still work, but every decision carries more friction. A drawing-led platform gives the team a clearer route from source information to action, then from action to controlled output.
Good practice starts with plain structure. Use concise drawing titles, reliable revision fields, agreed statuses and named owners. Keep the source drawing attached to each RFI, issue, decision or comment. Do not let responses disappear into email if they change the project record. Make superseded drawings easy to find without letting them look current. These habits are simple, but they are hard to maintain in a spreadsheet once a project becomes busy.
Connect revisions to actions
Coorda is built around that practical reality. The product starts from the live drawing set, keeps revisions and register data visible, and lets project teams create RFIs, decisions, issue sheets and actions from the same coordination record. It is designed for UK M&E consultants, building services engineers, contractors and project managers who need a clearer way to manage technical project information.
Good practice starts with plain structure. Use concise drawing titles, reliable revision fields, agreed statuses and named owners. Keep the source drawing attached to each RFI, issue, decision or comment. Do not let responses disappear into email if they change the project record. Make superseded drawings easy to find without letting them look current. These habits are simple, but they are hard to maintain in a spreadsheet once a project becomes busy.
Applying this in Coorda
The practical test for any coordination process is whether someone can return to the record later and understand what happened. A project manager should be able to see which drawing revision was current, what review comments were raised, which RFIs remained open, which decisions changed the design and what information was issued to the wider team. Without that chain, the project may still move forward, but the evidence becomes harder to defend.
Coorda is designed to keep that chain visible. Drawing register data, revision control, RFI management, issue sheet software and building services coordination workflows are treated as connected parts of the same project record. That matters for M&E consultants and contractors because technical questions rarely stay in one place. A drawing review can become an RFI, the RFI response can become a design decision, and the decision can affect the next issue pack.
The aim is not to add another admin layer. It is to reduce the amount of retyping, checking and searching that happens when teams rely on disconnected spreadsheets, folders and email threads. When the project is busy, concise structure is what makes the record usable: clear anchors, current information, visible history and direct routes into the next action.
For public buyers comparing tools, this is also the difference between a generic collaboration space and drawing coordination software. The valuable system is the one that reflects how building services projects actually behave: drawings change, questions need answers, decisions need reasons, and issue information needs a traceable source. Coorda keeps those links close so the team can work from a clearer shared understanding.
