Every major project mobilisation on a Tier 1 civils or engineering firm starts with the same document. The Project Management Plan. Twenty sections give or take, four hundred paragraphs, six hundred citations back to the bid, the contract, the client's own conditions, the firm's method statements, and the standards the delivery is being held to. A senior PM assembles it. A commercial lead reviews it. A legal reviewer reads the risk and change-control sections. An HSE lead reads sections eleven and twelve. The delivery partner stamps it.
Two weeks. Every project.
The two weeks is not the writing. The two weeks is the sourcing. Every claim in section §04.3 has to trace back to a specific bid clause. Every deliverable in section §07.2 has to trace back to a contract obligation. Every risk in section §14 has to reference the risk workshop it was raised in. When a reviewer asks "where did this number come from", the PM has to be able to open the source.
The document is not a document. It is a treaty. It binds the bid the firm won to the delivery the firm just promised. And it binds every sub-plan the delivery generates to a single canonical statement of scope, cost, programme, quality, risk, and change control.
Why the twenty sections have to be cited
A PMP with an uncited paragraph in section §12.1 is a PMP with a claim about the HSE method that has no source. When the delivery hits a moment where the client asks "how were you planning to handle X", and the PM opens the plan, and the plan says something plausible but nobody knows where the plausible sentence came from, the plan has failed its job. It was supposed to be a treaty. It became fiction.
This is the failure mode that commercial document-drafting AIs walk straight into. They produce a fluent, well-structured, twenty-section PMP that reads correctly. Roughly a third of the paragraphs are actually in the source. Another third are plausible and not. Another third are correct but sourced from documents the PM would not have used if he had been asked. The delivery lead's review time goes up because now she has to verify sources for every paragraph rather than judge the content of paragraphs the PM already sourced.
Provenant is built to fail differently. Where the source is silent, Provenant flags the gap in the section it should occupy. Where the source is ambiguous, Provenant cites both candidates and asks the reviewer to choose. Where the source is unambiguous, Provenant writes the paragraph with the citation attached to every sentence.
The delivery lead's review is now the review of a document with every sentence sourced. The forensic work goes away.
Twenty sections, one order of review
The other thing the delivery lead cares about is that the sections were reviewed in the right order.
The scope section (§03) is reviewed first because everything else depends on it. The programme section (§05) is reviewed next because the risk register and the resource plan need the programme baseline. The commercial section (§08) is reviewed by the commercial lead once §03 and §05 are locked. The legal reviewer reads §14 and §17 after the commercial lead has stamped §08 because the risk allocation and the change control both rest on commercial decisions. The HSE lead reads §11 and §12 after the technical scope is locked. The delivery lead reads the whole plan last.
This is not a nicety. It is how the PMP actually gets stamped in a large firm. If §14 gets reviewed before §08, the legal reviewer is reading against an unfinalised commercial position and will flag things that the commercial reviewer would have already resolved. If §03 gets reopened after §14 is stamped, the whole downstream chain has to be reviewed again.
Provenant carries this order on the document type. When a PMP is drafted, the review workflow is not "everyone reviews the document at once". It is the ordered sequence above, with each reviewer only allowed to see sections that have cleared the prior stage. The commercial lead does not see §14 until §08 clears. The legal reviewer does not see §17 until §14 clears. The delivery lead does not see anything until the seven upstream reviewers have all stamped.
This is not enforced by an email chain. It is enforced server-side. The document cannot be exported for the delivery lead's signature until the sequence completes. The sequence itself is auditable; the log records who stamped which section at what time and against which cited evidence.
Twenty sections drafted in minutes
When the senior PM runs a new project through Provenant on mobilisation day, the following happens.
The bid, the contract, the client's conditions document, and the firm's method statement library go in as source documents. Provenant reads them and extracts the clauses that will be cited into the PMP. Each clause gets a stable identifier that survives re-run, so a citation to CL a20b35 is the same citation on the third read as it was on the first.
The PMP's twenty sections generate section by section. Each paragraph is drafted from cited clauses in the source. Where two source documents disagree, Provenant surfaces both. Where a section requires a value that the source does not contain, Provenant flags the gap.
The senior PM reviews the draft. This is where the two weeks becomes an afternoon. The PM is reading a document where every sentence has a source and every gap has an owner. The review is judgement, not sourcing.
The ordered sign-off begins. The scope reviewer reads §03. The programme reviewer reads §05 once §03 clears. The commercial lead reads §08 once §05 clears. The legal reviewer reads §14 and §17 once §08 clears. The HSE lead reads §11 and §12 once the technical sections are locked. Each reviewer can downgrade a section from pass to hold. Only the delivery lead can convert the final hold into a pass, and only by explicitly accepting each departure on the record.
The plan that comes out the other side is not longer than the manual version. It is not more readable. It is more defensible. Every sentence has a source. Every gap has an owner. Every acceptance has a signature. The delivery lead reads it, stamps it, and it goes to the client.
The document is the treaty
The reason to invest in this is not the time saved during mobilisation, though that is real. The reason is that six months into delivery, when the client asks a question about a commitment in section §12.1, the PM can open the plan and click through to the exact clause in the exact source document that produced that commitment. When the answer to "where did this come from" is a click instead of a reconstruction, the client's confidence in the delivery is a different confidence.
The PMP was always supposed to be a treaty. Provenant is what makes a treaty stamped by four reviewers in an ordered chain, defensible sentence-by-sentence, and shipped in an afternoon.
Send us your firm's PMP template and the bid and contract from your next mobilisation. We will draft the plan in a live call and show you every citation in place.