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.
MVP · Define and control
R2 · Capture, document and iterate
Every output is a draft · cited, 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.
Detailed by P2 from SOW §3.2.4
Forecast at completion recalculates when a change order posts.
With field fac_amount · a formula · use case UC-CM-06
Ambiguous · flagged by P3
“A change order” does not say whether a pending change order counts toward FAC.
Suggested rewrite
Forecast at completion recalculates when an approved change order posts.
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.
FAC includes pending COs only after approval.
Settled 12 Sep · Extracted by P5 from the workshop notes
- Changes
- REQ-CM-014 · the trigger for FAC
- Field
fac_amount· calculated- Formula
FAC = Actuals + ETC + Approved CO value
Linked records
REQ-CM-014 UC-CM-06 TS-CM-06
Reopen D-031 and all three are 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.
Tomás Albrecht
Does FAC include pending change orders?
Answer · P6
No. A change order counts toward forecast at completion only once it is approved. D-031 settled this on 12 Sep, and REQ-CM-014 recalculates FAC when an approved change order posts.
Answered from the records Tomás can read · 2 cited
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.
Drafted by P9 from UC-CM-06 · REQ-CM-014
Precondition
A WBS line on the Cost Breakdown Grid with actuals and ETC, and one change order raised against it.
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.
Portfolio dashboard rolls up costs across EUR, GBP and NOK.
Raised by Jonas Becker · workshop, 29 Sep
- Scope check
- Out of scope
- Excluded by
- SOW §3.4.1 SOW §5.2
- Module
- Portfolio Reporting
- Route
- Chargeable · a change order on approval
- Estimate
- 6 days · EUR 9,600 at the rate card
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.
In the MVP
Intake, requirements, wireframes, tests, scope, decisions, issues, mapping, versioning, the customer portal.
In R2
Screenshot robot, guides and training, agile mode, as-built detection, SSO, Jira and Azure DevOps sync, an API.
Measured with design partners before launch