Drawings workflow
A revision costs money when a change nobody owns turns up on site. PlanOps compares every revision as it arrives and keeps each change as a record until it’s dealt with.
The complete run
A new issue lands from the designer. The drawing number and revision are read from the sheet and it is filed against the drawing it revises, so the set always knows which issue is current.
Every revision is compared with the previous issue as it arrives, and any two revisions of a drawing can be compared on request - P04 against P06, say - not only the latest pair.
Every difference found is written to the project as a change: what moved, where on the sheet in words, how much it matters and whether it is likely to cost something. Re-running a comparison refreshes a change rather than duplicating it.
From the change itself: mark it seen, ask the engineer by raising an RFI, give it to someone as a task, or flag it to commercial. The RFI or task stays linked to the change that caused it.
A change carries the packages its drawing is linked to, so the subcontractor whose RAMS and programme rest on that sheet can be told. Where the project assesses quantities, the quantity changes are recorded as well.
A drawing change register - by issue or by package - is generated, versioned, printed and exported like any other project register, with the issue named by its sheets, sender and date and a count of what is still open.
Two ways to compare
Free · one sheet
Go to drawingcomparison.co.uk and upload two revisions of one sheet. No account is needed.
Full workflow · every revision
Reference
What P01, C01, S2 and the A codes mean under the UK National Annex and what superseded means on site.
What to check when a revision arrives, before anyone builds to it. Free to print and use.
The manual method, what overlay and automated comparison miss and how to read a result.