Architecture drawing register workflow

A drawing register is useful only when every sheet has one reference, one current status, and one visible owner. Beech keeps those together so updates do not drift across spreadsheets and chat.

Start with stable references

Define section codes and sequence ranges first. Use one reference pattern for the whole project so revision history stays attached to each drawing over time.

Track progress with review context

A sheet is not really done until review outcomes are recorded. Link review state to each drawing so leadership can distinguish in-progress, waiting review, and approved sheets.

Surface blocked sheets early

Model dependencies and consultant waits directly against drawings. Weekly planning then shows where downstream work is blocked before deadlines slip.