The Design Office
AI scope-of-work preparation
A first draft of every sub-consultant appointment — scope, deliverables by stage, review checkpoints and exclusions — written against your own deliverable catalogue. A principal edits and issues it. Nothing is appointed by an agent: the draft is staged for review, and importing it is what creates the deliverables the project is tracked against.
What it drafts
Discipline scope narrative
Services included, services excluded, interfaces with other consultants, and the design responsibility boundary — in the register your practice already writes in.
Deliverable schedule by stage
Drawing sets, calculations, reports and models due at each design stage, with suitability expected at issue — proposed against your own deliverable catalogue, so an accepted item becomes the very row module 02 tracks against.
Review checkpoints and code references
Hold points where your review is required before the consultant proceeds, with the applicable code clauses cited — each labelled as a requirement or a recommendation, never blended.
Omission check against your library
A list of catalogue deliverables the draft leaves out, computed from the catalogue itself rather than written by the agent — the part a principal should read first.
How the drafting is bounded
- Draft-only. The agent writes to a staged draft. It cannot issue, appoint or notify.
- Named reviewer. A person accepts each item; the acceptance and every rejection are recorded against them.
- Server-bound. The agent proposes titles; the platform decides which catalogue requirement each one is, and re-checks that on every read.
- No dates, no money. A draft carries a relative offset, never a calendar date, and carries no fee anywhere — both are refused by name.
- Metered. Every request is recorded in your agent usage ledger.