Drawing revision control for architecture studios

Revision control should answer three questions quickly: what changed, who approved it, and whether it is ready to issue.

Keep revisions on the same drawing thread

Avoid creating unrelated task records for each revision. Keep revision history attached to one drawing reference so previous approvals and dependencies remain visible.

Pair revision updates with review outcomes

When a reviewer requests changes, the drawing should return to work status until a new approval is captured. This avoids accidental issue of unapproved updates.

Use issue-ready markers

Mark sheets as issue-ready only after dependencies and review requirements are met. This keeps release packages trustworthy for clients and consultants.