How it works

Each record drafts the next.

Sixteen pipelines carry a project from the RFP to as-built. Each reads the approved records before it and writes drafts for the step after. Nothing becomes a record until a person accepts it.

P2 · P3 · Detailing and quality

Ambiguity is flagged before sign-off.

P2 turns a high-level requirement into detailed ones, with fields, formulas and use cases. P3 reads the set and flags wording two people could read two ways, with a rewrite to accept or dismiss.

P5 · Meeting extraction

A decision flags what it changes.

P5 reads workshop notes and pulls out the decisions, the actions and the records they touch. When a decision changes later, every record linked to it is flagged for review.

P6 · Project Q&A

Every answer cites its record.

Anyone on the team can ask a question in plain words. P6 answers from the project’s own records, cites each one, and reads only what the person asking is allowed to read.

P9 · Test scripts

Test scripts from the use cases.

P9 writes FAT scripts from the use case, the requirement and the wireframe. Each expected result points to the record it proves, so a failed step raises an issue against the right requirement.

P16 · Change requests · R2

A change request from the scope check.

In R2, P16 turns an out-of-scope verdict into a change request: what was asked, the clauses that exclude it, the effort and the price at your rate card. It stays a draft until the project manager sends it.

MVP · Define and control

What the MVP has to prove.

The MVP covers the front half of delivery, from intake through tests, plus scope control and the portal. Capture, guides and as-built detection follow in R2. These are its targets, to be measured with design partners.