Civic Tender Milestone Payment and Value for Money Pricing Specification
Develop a milestone-linked, performance-contingent pricing specification for public outcome contracts.
Use this template when responding to municipal, state, or civic innovation tenders where vendor compensation is tied to deliverables, public milestones, retainage, and Value for Money (VfM) performance benchmarks.
Role: Lead Commercial Finance Director specializing in municipal tenders, civic innovation, and public outcome contracts.
Context
- Contracting Authority: {{contracting_authority}}
- Maximum Budget Allocation: {{total_award_ceiling}}
- Critical Delivery Phases: {{key_program_milestones}}
- Compliance & Assurance Standard: {{statutory_compliance_standards}}
- Milestone Retainage Requirement: {{retention_holdback_rate}}
- Financial Contingency Allocation: {{risk_contingency_buffer}}
Task
Draft a performance-based milestone pricing and cash flow specification that maps deliverables to auditable payout criteria, retainage releases, and Value for Money (VfM) indicators for {{contracting_authority}} within {{total_award_ceiling}}.
Method
- Break down {{key_program_milestones}} into discrete, verifiable deliverable packages with measurable completion gates.
- Apportion {{total_award_ceiling}} across milestones based on weighted resource intensity and risk.
- Integrate {{retention_holdback_rate}} withholding terms to create clear escrow and final acceptance release terms.
- Map {{statutory_compliance_standards}} to mandatory evidence artifacts required prior to invoice sign-off.
- Allocate {{risk_contingency_buffer}} into a transparent change-order reserve mechanism with clear invocation criteria.
- Build a Value for Money (VfM) scoring index showing civic return on public expenditure.
- Establish remedy and liquidated damage penalty tables for milestone delays or non-conformance.
Constraints
- MUST keep the cumulative milestone values plus contingency strictly at or below {{total_award_ceiling}}.
- MUST NOT authorize milestone payouts without explicit, objective proof-of-delivery criteria.
- MUST separate core deliverable value from the {{risk_contingency_buffer}} line item.
- Limit output strictly to the four designated spec sections.
Output format
Generate the specification organized into four sections:
- Milestone Payment Schedule (table containing Milestone ID, Deliverable Name, Weight %, Net Billing Amount, Retainage Withheld, Net Payable)
- Deliverable Verification & Payout Criteria (detailed validation criteria for each milestone)
- Retainage Release and Performance Penalty Terms (explicit rules for final release and delay deductions)
- Value for Money (VfM) Public Benefit Justification (250-word fiscal stewardship statement)
Self-review
- Ensure the sum of all milestone Net Billing Amounts plus {{risk_contingency_buffer}} precisely matches {{total_award_ceiling}}.
- Verify that the retainage percentage in the table mathematically reflects {{retention_holdback_rate}}.
- Confirm every milestone references compliance with {{statutory_compliance_standards}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.