Verity for architects
An architect’s capacity is the licensed signature, not the studio. Verity shows what is queued against it, what is issued, and what is still waiting on someone else.
Verity runs the practice. Drawing tools stay where they are.
Verity / Practice
LiveLive projects
14
Awaiting your review
23
Waiting on others
9
Superseded drawings in use
4
Needs attention
Illustrative figures. Verity shows your own practice in this shape.
How the business runs
An architect practising alone or with a small studio has a capacity problem that does not look like other capacity problems. Drafting can be delegated and coordination can be delegated, but review, seal and issue cannot: every drawing and every statutory submission carries one registered name, and twenty-three items queued against that name is the practice’s actual throughput limit regardless of how many people are drawing.
The second characteristic is revision control with consequences. A drawing issued and then superseded does not stop existing — it is on a site, in a contractor’s folder, being built from. Four superseded drawings still in use is not an administrative untidiness, it is work being built to the wrong information.
The third is dependency on other people. Architectural projects pause on client decisions, consultant inputs and authority responses, and while they are paused the architect is still carrying the project without progressing it. Nine paused projects is nine open commitments producing nothing.
The fourth is that the architect is legally exposed by what was issued and when. Correspondence, instructions and issue history are the record that matters years later.
Verity holds the review queue, the issue and revision history, the dependencies on others, and the correspondence that evidences them.
What Verity calls these things
What gets in the way
The difficulties of practising as an architect come from personal responsibility that cannot be delegated.
Everything queues behind one reviewer
Drafting scales, review does not, and the queue is invisible until something is late.
In Verity The review queue is a visible list with age and project, so the constraint is managed.
Superseded drawings stay in circulation
A revision is issued and the old sheet is still on site being built from.
In Verity Issue and acknowledgement are recorded per recipient, so superseded sheets in use are visible.
Projects pause on other people
Client decisions, consultant inputs and authority responses stall work with no owner chasing them.
In Verity Every dependency has a holder, an age and a chase, so paused work is not silent.
Verbal instructions become disputes
A change agreed on site is built and later contested with nothing written.
In Verity Instructions are recorded against the project and confirmed in writing from the same record.
Small variations are absorbed unbilled
Additional drawings and revisions requested outside scope are done and never invoiced.
In Verity Additional work is captured against the project as it is requested, with a fee position.
Old projects have to be reconstructed
A query years later requires finding what was issued, when, and to whom.
In Verity Issue history, correspondence and approvals stay attached to the project permanently.
The complete system
One system across review, issue, dependency and correspondence.
Workflows
Items requiring the architect’s review form one queue with project, stage, age and urgency, and issue is a recorded step.
Why it matters here Review is the practice’s actual capacity and it needs to be visible as a queue.
In practice Twenty-three items queued on one signature this week.
Records
Each drawing carries its revision, issue date, recipients and acknowledgement, with superseded versions marked.
Why it matters here What was issued, when and to whom is the record that matters during construction and afterwards.
In practice Four superseded drawings still in use on site.
Work
Each project is structured by stage with the drawings, approvals and fee position attached.
Why it matters here An architect’s work is staged and the practice needs to know which stage each project actually sits in.
In practice Fourteen live projects across six stages.
Relationships
Each party carries the projects they touch, what is outstanding from them and how long it has been outstanding.
Why it matters here Most paused work is waiting on someone outside the practice.
In practice Consultant inputs outstanding on three submissions.
Communication
Instructions, confirmations and project conversation attach to the project and the drawing they concern.
Why it matters here A verbal change becomes a written record from the same place it was discussed.
In practice A site instruction confirmed in writing against the drawing it changed.
People
Studio capacity is modelled separately from review capacity, with work attributed to both.
Why it matters here Adding a draughtsperson increases drawing output and not review output.
In practice Drafting capacity against review throughput.
Orders
Fee stages, additional drawings and revisions outside scope carry a fee position and an invoicing state.
Why it matters here Additional work absorbed unbilled is the most common loss in a small practice.
In practice Additional revisions requested against fee recorded.
Reports and analytics
Review queue age, dependency ageing, issue history, additional work and fee recovery come from the records.
Why it matters here The practice is limited by one queue and leaks through unbilled work, and both are measurable.
In practice Average age of items in the review queue.
Verity AI
Verity AI answers from your own project, drawing, issue and correspondence records, respects permissions, and can create assigned follow-ups.
Why it matters here The questions that matter are about what is queued and what is waiting on someone else.
In practice "What is waiting on consultants?" returns the list with age and chase assigned.
Control
One permission model and one audit trail, with approvals and submissions carried as reportable states.
Why it matters here Personal registration means personal liability, and the record is the defence.
In practice Submission and approval history retained per project.
Locations
Site visits, observations and photographs attach to the project and the drawing they relate to.
Why it matters here What was observed on site is evidence tied to a date.
In practice Site visit observations recorded against the drawing revision current at the time.
Work in motion
These already happen. Recorded, the queue and the liability record manage themselves.
Recording recipients is what makes a superseded drawing in use detectable.
A paused project with no owner chasing it stays paused.
Conditions attached to an approval are obligations that need to travel forward.
The written confirmation is generated from the same record as the instruction.
A query years later is answered from the archive rather than reconstructed.
Verity AI
Verity AI reads the same project, drawing, issue and correspondence records the practice creates as it works. It answers from your own practice, respects permissions, and can turn an answer into a chase or a confirmation.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the practice’s own records at the point the condition is met.
When
An item sits in the review queue beyond a threshold
When
A revision is issued
When
A dependency ages past a threshold
When
An instruction is recorded outside scope
When
An approval carries conditions
What you can understand
Throughput, dependency and fee recovery from working records.
Verity records the practice’s operations. Drawing and modelling tools continue as they are.
One system, different ways of seeing it
Everyone works from the same records.
Architect
What needs me, and what is waiting on someone else?
Review queue by age, dependencies outstanding, submissions and conditions, fee position.
Project assistant
What is moving and what is stuck?
Drawing status, issue and acknowledgement, chases outstanding, project stages.
Draughtsperson
What am I drawing and to which revision?
Assigned drawings, current revisions, markups from review, issue deadlines.
Practice administration
What can be invoiced?
Stage completion, additional work recorded, invoices raised and outstanding, project archive.
Where it is used
Everything requiring the registered signature in one list with age and project, so the practice’s real constraint is visible rather than discovered at a deadline.
Revisions with recipients and acknowledgement, so a superseded sheet still being built from is detectable rather than assumed away.
Client decisions, consultant inputs and authority responses with holders and ageing, so paused projects are chased rather than forgotten.
Site and verbal instructions captured against the project and confirmed in writing from the same record.
Revisions and drawings requested outside scope recorded as they happen with a fee position attached.
Issue history, correspondence, approvals and conditions retained against the project for queries years later.
Plain-language questions across projects, drawings, dependencies and fees, with chases raised in the same step.
Getting there
Drawing and modelling tools continue and are mapped during implementation. Projects, stages, drawing registers with revision and issue history, clients, consultants, correspondence and fee positions are brought across.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own project, drawing, issue and correspondence records: what is queued on your review and how old it is, which superseded drawings are still with recipients, what is outstanding from consultants, which projects are paused on a client. Each answer can become a chase or a written confirmation.
No. Drawing and modelling tools continue as they are. Verity holds the practice around them — projects, stages, drawing registers, issue history, dependencies, correspondence and fees.
Because drafting can be delegated and the registered signature cannot. Adding drawing capacity increases what arrives for review without increasing what leaves the practice, so the queue against that signature is the throughput limit.
Issue records who received which revision and whether they acknowledged it. When a revision is issued the prior one is marked superseded and its recipients are listed, so a sheet still in use on site is visible rather than assumed replaced.
Outstanding items are recorded against the holder with the date they were requested, so ageing is visible and chases are assigned rather than remembered.
Additional drawings and revisions outside scope are recorded against the project as they are requested, with a fee position, which is what makes them invoiceable rather than absorbed.
Issue history, correspondence, approvals and conditions stay attached to the project after it closes and remain searchable, which is what a query years later actually needs.
About four weeks: discovery and mapping of stages, drawing register conventions and fee structure, configuration, migration of live projects and archives, then an ongoing operations partnership.
It is the practice’s real capacity. Tell us how work reaches you for review today.