Compliance Register

Strategy session - the register is born

Engineers run the strategy discussion exactly as they do today. The AI reads the session and proposes a structured register - every item labelled AI inferred, pending human review. Nothing is decided by the AI.

Foundry Lane Warehouse Conversion · CE-2026-0417 · session recorded 22 May 2026 · D. Okafor (PD), P. Sharma (PM), T. Reeves (Engineer)

Bring the session in: simulated · Stage 1 intake

Stage 1 runs on the transcript you already produce. The approved capture door is agreed in the sprint, inside your Australian boundary.

Structured register

0 items · 0 performance solutions

AI inferred - pending human review

pre-computed demo run - same screen flow, no live call in the demo

Review 15 items →

PM review - humans own the judgement

Every item classified with the consultancy's own taxonomy and anchored to the transcript - click any timestamp to see the exact source line. Rows with incomplete evidence rise to the top and block the write until a human decides.

0

items

0

AI-classified

0

need a human decision

0

confirmed

0%

Item type · provenance	NCC ref	Description	Proposed strategy / action	Source	PM ✓

0 of 15 reviewed
Confirm unlocks when the 3 “needs a human” rows are resolved.

(in production, writes to your monday.com board)

Open the register →

Performance Solutions Register - Project Director view

The single source of truth, seven weeks later (today, 14 Jul). Statuses moved as the project advanced through PBDB. Every change carries who, when and why - the record that today lives in heads, comments and email threads. The register supports the director's duty of review - it never replaces it.

Signature exposure - across your book (synthetic)

On a good day this screen shows nothing. 0 endorsements · 0 current · 0 standing on changed ground

Project	PS	Signed → now	Origin of change	Stage
Foundry Lane Conversion	PS-004	9 m comparative → 14 m full evacuation	brigade-directed FRV response · AI-proposed · engineer confirms	PBDB → FER
Harbour Mill Redevelopment (sample)	PS-011	smoke exhaust 5 ACH → 6 ACH proposed	internal refinement	FER drafting
Kensington Goods Depot (sample)	PS-002	Type A assumption → Type B confirmed	DtS reconciliation	FSCS review

Caught 7 weeks before lodgement. Today a change like this surfaces in the director's final read, ~2 days before delivery - the rework scramble you described.

Generate the draft →

Stage 4 · roadmap preview

Documents - one approved change becomes a first draft

Turn one approved change into a first-draft document - in your Word format - with checks that flag unapproved number or clause changes. Always Word, always reviewable, never auto-issued.

✓ FSCS issued · 28 May

✓ PBDB v1 issued to FRV · 12 Jun

⚠ PBDB v2 - CHANGED brigade response · 08 Jul

● FER §7.4 drafting now

☐ FIR checklist auto-derived from the approved FER (Stage 5, coming)

Format profiles per brigade: FRNSW strict · FRV flexible (roadmap).

Input · provenance

Generating from:

PS Register entry - the approved change

PS-004 · Extended exit travel distance
9 m → 14 mcomparative RSET/ASET → full evacuation modelling

Review outcome recorded by D. Okafor · 13 Jul

PBDB v2 - brigade response, ingested as input

FRV response received 08 Jul: travel distance revised to 14 m; full evacuation modelling required. This is the document the engineering team reformats by hand today - PBDB in, FER language out.

The AI drafts only changes already approved in the register - it never invents an edit. ← the change the brigade forced, in the PS Register

Generate

The draft - native Word tracked changes Runs after Generate - the draft lands here as a real Word page.

Fire Engineering Report (FER) - Draft (extract)
Project: Foundry Lane - Warehouse Conversion, 42–48 Wreckyn Street, North Melbourne VIC
Project ref: CE-2026-0417 · NCC edition: NCC 2022, Volume One (BCA), Victoria · Report status: DRAFT - for internal review · Extract: Section 7.4 (PS-004)

7.4.4 Analysis

A comparative required-safe-egress-time versus available-safe-egress-time (RSET vs ASET) assessmentfull building-wide evacuation model - an agent-based evacuation simulation (Pathfinder) run against the PS-001 CFD tenability results for both the daytime office and the peak evening assembly configurations - was then carried out for the affected zone underas the Verification Method under A2G2(2)(b).

Parameter	Value	Basis / source
Max. travel distance to single point of choice (proposed)	9 14 m	Architectural set, extended path (PS-004)
Overall travel distance to required exit	38 m	Path to retained east stair - unchanged

Table 7.4-A - PS-004 travel distance and egress summary (office zone, daytime profile)

7.4.5 Conclusion

…the maximum travel distance to a single point of choice for the affected office zone shall be 9 14 metres, and this Performance Solution demonstrates compliance with Performance Requirements DP4, DP6 and EP2.2 to a level of safety at least equivalent to the Deemed-to-Satisfy Provision D2D5.

Reviewing

Aivy Drafting Assistant

Updated per PBDB v2 brigade response: exit travel distance revised 9m to 14m; justification method changed to full evacuation modelling per NCC D2 Performance Requirements. Numeric check passed for the approved inputs.

✓ Accept✕ Reject

the engineer decides - in Word

Open in Word ⬇ the same file, as native Word tracked changes - this preview mirrors it exactly

By hand, this redline is half a day to a full day of team time. The AI drafts it in seconds; your engineer reviews and signs. Capacity back to engineers, not replacing judgement.

The check - deterministic number check Runs automatically after every draft.

Find the precedent - search the library →

Stage 3 · design preview · sample data

⌕ Precedent Library - find the justification, not just the document

SharePoint and Copilot find you a document; this finds you a justification, and tells you whether the brigade recorded an objection.

Restricted sites are excluded - not searched, not counted.

Access follows your project permissions, granted site-by-site by your IT.

see how ▸

No generated answer in the query path - it returns source documents. Any tagging or embeddings run inside the approved AU boundary, on ISSUED reports only. Search quality is measured on your golden set before Stage 3 is billed.

Stage 6 · QA & review dashboard · design preview

▦ Overview - the whole book at a glance

The GM and directors' view: what was captured, what is waiting on a human, and what needs a director's attention - across every live project. In production this is your monday.com QA dashboard, fed by the register. Synthetic data.

MC M. Calder · General Manager · full visibility

Week of 14 Jul 2026 · mirrors to monday.com - simulated in this demo

312

Active projects

9

Strategy sessions captured this week

14

Items awaiting PM review

3

PS changes flagged to a director

6

Documents in draft

7

Registers written this week

Needs your attention

PS-004 · Foundry Lane - brigade-directed change, awaiting the director's review outcome.
flagged 08 Jul · D. Okafor notified

Foundry Lane - 3 items need a human decision before the register can be written.
P. Sharma (PM)

Harbour Mill Redevelopment - PS-011 internal refinement pending PD endorsement.
FER drafting

Kensington Goods Depot - FSCS review complete, no objection recorded.
on track

Live projects - status

Project	Stage	Open PS	Pending reviews	Flags
Foundry Lane Conversion	PBDB → FER	6	3	● 1
Harbour Mill Redevelopment	FER drafting	4	0	● 1
Kensington Goods Depot	FSCS review	5	1	-
Riverside Woolstore (VIC)	PBDB → FRV	3	0	-
Collins Street Podium	FER issued	7	0	-

Showing 5 of 312 · one row per live project · click-through opens the project register in the live product.

Open a flagged project →

Strategy session - the register is born

Structured register

Session readback - confirmed before anything is written

Performance solutions (4 firm · 2 potential)

Open questions (3)

No owner yet (2)

Also captured

PM review - humans own the judgement

Performance Solutions Register - Project Director view

Signature exposure - across your book (synthetic)

Documents - one approved change becomes a first draft

Generating from:

PS Register entry - the approved change

PBDB v2 - brigade response, ingested as input

7.4.4 Analysis

7.4.5 Conclusion

This draft - PASS

Planted fault - CAUGHT

⌕ Precedent Library - find the justification, not just the document

▦ Overview - the whole book at a glance

Needs your attention

Live projects - status

Strategy session - the register is born

Structured register

Session readback - confirmed before anything is written

Performance solutions (4 firm · 2 potential)

Open questions (3)

No owner yet (2)

Also captured

PM review - humans own the judgement

Performance Solutions Register - Project Director view

Signature exposure - across your book (synthetic)

Documents - one approved change becomes a first draft

Generating from:

PS Register entry - the approved change

PBDB v2 - brigade response, ingested as input

7.4.4 Analysis

7.4.5 Conclusion

This draft - PASS

Planted fault - CAUGHT

⌕ Precedent Library - find the justification, not just the document

▦ Overview - the whole book at a glance

Needs your attention

Live projects - status

Source in transcript

Audit record - what did the human approve, and where did it come from?

PS-004 - what changed since you signed DP4, EP2.2 · D2D5

Endorsed snapshot - 28 May, D. Okafor

Current - after FRV response, 08 Jul