How to Make an Architecture Stage Report Clients Actually Read

An architecture stage report gets read when it opens with the decision the client has to make and supports that decision in the pages that follow. Most stage reports do the reverse: they open with the design story, bury the ask on page 14, and reach the client as a long attachment that waits in an inbox for a week.

TL;DR: The RIBA Plan of Work 2020 asks for a stage report at the end of Stage 2 (Concept Design) and Stage 3 (Spatial Coordination), and the client signs it off before the next stage starts. Put the decision on page one, then what changed since the brief, the design in images, cost and programme, risks, and what you need next. AI can draft the wording from your meeting notes. DocsAura, an AI document design tool, takes the finished DOCX or PDF and returns a designed page in about two minutes, so the report looks like the studio that wrote it.

What an Architecture Stage Report Has to Do

The RIBA Plan of Work 2020 defines the stage report as a report produced at the end of Stage 2 (Concept Design) and Stage 3 (Spatial Coordination) to capture decision making during the stage and record the outcome of the design process as reviewed by the client. It also contains the project strategies and other useful project information, and the client signs it off at the end of the stage.[^1]

That definition gives the report one job: to let a client say yes, no, or "change this first." The client is not reading for the pleasure of the design story, because they lived through it in the meetings. They are reading to decide whether to release the next stage of fees and work.

Guidance from the Designing Buildings wiki lists what an end-of-stage report should do: identify any divergence between the project and the brief, budget or programme, identify risks, highlight the decisions required from the client, and explain the procedure for the next stage. It also says these reports should be concise and should not repeat information that already exists elsewhere.[^2]

Read together, those points describe a decision document, and the layout should treat it as one.

The Order a Client Reads It In

A client with a busy week reads the first page and skims the rest, so the first page carries the weight. This order works for a Stage 2 or Stage 3 report from a studio of any size:

1. The decision requested. One sentence: "We are asking you to approve the concept design and instruct us to proceed to Stage 3." Add the date you need the answer by.
2. What changed since the brief. A short list. If the client asked for a fourth bedroom and the plot took it away, this is where they see it first, in plain words.
3. The design, in images. Plans, sections, precedent images and renders carry this part. Keep the captions short and put one idea on each page.
4. Cost and programme. The latest figures from your cost consultant, compared with the last agreed figures. The movement against the last figure is the number the client acts on.
5. Risks and open questions. Planning, site conditions, lead times, anything that could move the budget or the dates.
6. Next stage. What happens after sign-off, what you need from the client, and when.

Everything else, such as full drawing sets, specification notes and consultant reports, sits in an appendix or a separate file. The report points to it and stops repeating it.

Where AI Helps With a Stage Report, and Where the Judgement Stays Yours

A stage report has two layers, the same way a fee proposal does.

The first layer is judgement: what the design decision is, what the cost movement means, which risk matters. That belongs to the architect and the cost consultant. AI has no access to the site, the planning officer's comments or the conversation in the last review meeting.

The second layer is the writing around those judgements. This is where a general AI chat tool saves real time:

• turning your meeting notes into a clean "what changed since the brief" list
• drafting the one-sentence decision request and the next-stage summary
• rewriting a dense design narrative into short captions
• checking that the report answers each question the client raised in the review

Give the tool your notes and the figures you already have, and read every line it returns against the project. Cost figures and dates come from you and your consultants, and the report should carry only figures a person has checked. The same split between judgement and wording runs through How to Use AI to Write an Architecture Fee Proposal, and it is worth keeping client names and addresses out of any tool you have not vetted.

What We Found Reading 10 Guides to the RIBA Stages

We read ten public guides to the RIBA Plan of Work stages, from practice websites, a software vendor and a construction wiki, and checked by keyword search what each says about the report that closes a stage. Three of the ten name the stage report or the concept design report. Two mention client sign-off. Nine mention cost or budget and six mention risk somewhere in their stage descriptions. None describes the decisions a client must make at the end of the stage, and none says anything about how the report itself should be laid out. Stage reports are well defined and rarely explained as documents someone has to read. (An eleventh page loaded without readable text and was left out.)

Laying Out the Report Without Losing an Evening

A stage report usually closes a busy stretch of design work, and the layout tends to be the last thing built, late in the day, in Word or a slide file. The studio can typeset a beautiful report; it lacks the hours. The pitch here is time, not taste.

DocsAura, an AI document design tool, is built for that last step. It takes the DOCX or PDF your studio already wrote and returns a designed HTML page in about two minutes: a clear page-one decision block, sections with visual hierarchy, tables for cost and programme that read cleanly. You open the result in the editor, click any text to change it, and export it as a PDF or share it as a link. The drawing sets, renders and cost figures stay yours. DocsAura does not draw, model or connect to Revit, ArchiCAD or AutoCAD. It changes how the finished report looks.

For studios that already send client reports, the routine is the same one applied to a stage boundary: write the content, check the numbers, then let the tool handle the page.

A Stage Report Checklist Before You Send It

Run through these before the report leaves the studio:

• The decision and the response date sit on page one.
• Every change since the brief appears in the "what changed" list, with the reason.
• Cost and programme show movement against the last agreed figures.
• Each risk has an owner or a next step.
• Appendices carry the detail, and the body carries the argument.
• The next stage is described in terms of what the client receives.

A report that passes this list is short enough to read in one sitting, and it gives the client what they need to sign.

Try It on One Report You Already Wrote

Pick the last stage report in your project folder, or the one due this month. Drop it into DocsAura, the AI document design tool, and see what comes back in about two minutes. There is nothing to install, no template to build and no new system to keep next to your drawing software. If the result suits the studio, use it. If a section needs adjusting, edit it in the editor and export.

[^1]: RIBA, "RIBA Plan of Work 2020," definition of Stage Report, as quoted in "Stage report for design and construction," Designing Buildings Wiki, designingbuildings.co.uk. [^2]: "Stage report for design and construction," Designing Buildings Wiki, designingbuildings.co.uk.