
Revision control: how to never lose a project correction
A correction asked for in Tuesday's meeting. Another one by WhatsApp, at eleven at night. A third one scribbled in pen on a print that stayed on someone's desk. Two weeks later the new version of the project goes out, and one of them is not there. Nobody notices until construction.
Corrections get lost less through carelessness than through the lack of a method. This guide shows a simple way to record, assign and check every change, from the request to the revised sheet.
Where corrections get lost
- In scattered channels. Meeting, phone, email, message: each request ends up in a different place.
- Without an owner. Everyone heard the correction, and each person thought someone else would do it.
- Without a check. The window was fixed, but the dimension next to it disappeared along the way.
- Without a history. Nobody can say what changed between R01 and R02.
A four-step method
1. Mark the correction at the exact spot on the sheet
A correction has to say where and what. “Enlarge the bedroom window on Elevation 02” leaves no doubt; “check the window” does. Mark each correction on the sheet itself, at the spot that changes, and treat each mark as a separate item. Ten corrections in a single comment become a list nobody finishes.

2. Give each item an assignee and a due date
A correction without an assignee is a correction nobody will make. Say who fixes it and by when, even in a small studio. That way the person knows what is theirs, and you know what is missing without having to ask.
3. Fix it and record the new revision
The corrected sheet gets a new revision number, in the file name and in the title block's table, with the date and a short description of what changed. The previous version is not deleted: it is the proof of what applied before.
4. Compare the new version with the previous one
Before sending, compare the two versions and look beyond the corrected spot. Changing a window can affect the plan, the sections, the window schedule and the quantities. Only mark the correction as resolved after this check.
Client requests: record them before you draw
Many corrections come from a client request, and those requests deserve special care:
- Write down every request, with the date and who asked, even the ones that come by phone or during a site visit.
- Confirm in writing what will change and whether the change affects the timeline or the fees. If the contract sets a number of change rounds, this is the moment to say which one the request falls into.
- Record the decisions. What was approved or declined, and when. Nobody needs to argue later about what was already decided.
One round at a time
Instead of correcting bit by bit as requests arrive, group the corrections into rounds. A round starts with all the items marked, ends when they are all resolved and checked, and produces a single new revision. Fewer versions going around, less chance of the site getting the wrong one.
A correction is only done when someone has checked the new version, not when someone said they did it.
How to do it in Arcture
In Arcture, you open the PDF in “Files” and click “Start review”. Each mark on the sheet (pin, text, arrow, rectangle, circle, freehand or highlight) becomes an item with an assignee and a due date, and the progress of every item is in the project's “Reviews” tab. The corrected sheet comes in with “Upload new version”, and “Compare versions” shows the two side by side, overlaid or with a swipe, pointing out the areas that changed.
On the client's side, deliveries go through the portal, where they approve or request changes. Requests stay under “Requests”, including those that came by phone or WhatsApp, and what was approved or declined stays under “Decisions”. See a review from start to finish.




