The PMC Firm / Module 04
Proposal → work order → project
One reference from first proposal to provisioned project: revisions under the same number, acceptance against a work order, and the project created from the scope that was actually accepted.
- Business development
- Partner
- Delivery lead
For a firm. The gap between what was sold and what gets delivered opens in the handover from proposal to project team. Provisioning the project from the accepted scope closes it: the modules, the deliverable catalogue and the fee stages are the ones the client signed.
What it holds
Proposal with revisions under one reference
R0, R1, R2 under the same proposal number, each issued and superseded rather than replaced — so a client cannot accept a version you have withdrawn.
Acceptance against a work order
Acceptance requires the client's work order logged as an inward document with their own reference — the commercial fact, not a verbal go-ahead.
Project provisioned from the accepted scope
One work order creates one project, with modules pre-curated, the deliverable catalogue seeded and the fee stages set. A duplicate attempt is refused.
One thread, end to end
The enquiry, proposal, revisions, work order and project sit on one timeline, so the reason a fee was set the way it was remains findable two years later.
The flow
- 01Enquiry logged; proposal drafted and issued with a reference.
- 02Revised as R1 under the same reference; the prior version supersedes.
- 03Client work order logged inward; proposal accepted against it.
- 04Project created from the acceptance, modules already curated.
What it will not allow
- Accepting a superseded proposal version
- Acceptance with no work order logged
- Two projects from one work order