DeliverDrawing review
Three marks moved between these two issues.
Switch between them and find them. Take as long as you like.
Drawing review
Three marks moved. Nobody remembers which
Issue ASwitch between the issues. Three of these forty-eight marks are different — see whether you can find them.
The computed delta, as text
- Row 2, column 3Changed between issue A and issue B.
- Row 3, column 4Changed between issue A and issue B.
- Row 4, column 5Changed between issue A and issue B.
Review output stays attached to the drawing set and the project. The field above is a diagram of a sheet, not a drawing — no sheet, revision, project or date is real.
You were looking at it the whole time.
The delta is computed from the two issues rather than remembered, so what changed is a fact. A finding raised against it becomes an item somebody owns.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- Drawing sets, revisions and review inside the project: a comparison workspace for revisions, review checklists, and findings recorded against the drawings themselves.
- Who it is for
- Practices whose quality review currently happens as red pen on a printed set, or as comments in a PDF that never rejoin the project record.
- What is different
- Review output stays attached to the drawing set and the project. The revision delta is computed rather than remembered, so what changed between issues is a fact rather than a recollection.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Drawings belong to the Project Pod, findings can become issues, and Mudo Connect can keep the drawing register in step with the Archicad model.
Part of Deliver.
Verified against the Mudo application on .
Review is a practice asset, not an event
The value of internal review is cumulative. What one reviewer catches should be what the practice checks for next time.
That only happens if the findings live somewhere durable. Red pen on a printed set and comments in a downloaded PDF both fail the same way: the knowledge leaves with the file.
What changed between revisions
The most common question in review is also the most tedious to answer by eye: what is different from the last issue.
Mudo computes it. Comparing two revisions is a view rather than an exercise, which changes how often it is actually done.
Attached to the set, not to a person
Drawings belong to sets, sets are issued, and issues have dates that the programme and the deliverables register depend on. Keeping review inside that structure is what stops it becoming a parallel process with its own filing.
Common questions
What does drawing review software do for an architecture practice?
It makes internal review a recorded, repeatable process rather than a personal one. Revisions can be compared, a checklist can be worked through, and the findings stay attached to the drawing set, so the next reviewer sees what the last one found.
Can I compare drawing revisions?
Yes. There is a comparison workspace for revisions and a revision delta view, so the difference between two issues of a drawing is shown rather than reconstructed by eye.
What happens to review findings?
They are recorded against the drawings and stay in the project. Because the registers live in the same Pod, a finding that needs tracking does not have to be retyped somewhere else to be actioned.
Stop trying to remember what changed.
Free for solo practices: one user, two projects, no card.