Draft for Tamir's review. Not published.
The framework sets the ceiling, and the order sets what you get
Framework defaults are written for the framework as a whole. Ask what it fixes and what it leaves to the order. Then require deliverables, acceptance tests, payment milestones, named staff, and data and exit terms specific to this system.
Keep maintenance separate from optional new capabilities. Check whether declining an upgrade removes access to existing functions, and which future obligations the first signature already triggers. Treat free discovery bundled with implementation the same way: you should stay free to act on what it finds.
Keep one party accountable
In a consortium, map each service outcome to the party accepting responsibility. Test how the members would handle a failure that crosses their boundaries, and check what happens if a partner leaves.
When a framework holder proposes to deliver through a subcontractor you never evaluated, keep the holder fully liable in writing. Get approval rights over the subcontractor and its key staff, and make data, security and confidentiality terms apply to it. Evaluate the subcontractor as if it were bidding.
Depending on your seat
If you sit on the approving committee, ask procurement counsel to confirm that the order's own terms fit the framework's rules. Then review acceptance evidence at each milestone before payment.
If you run the program and the winning bidder asks to change liability terms or replace evaluated staff, compare the request with the tender commitment. Identify the risk it shifts to you. Procurement and counsel decide the permitted process, and schedule pressure is no authority to change the award.
What to check before you decide
- Ask what the framework fixes and what it leaves to the order.
- Require deliverables, acceptance tests, payment milestones and named staff in the order itself.
- Require data ownership and exit terms specific to this system.
- Separate essential maintenance from optional new capabilities and future purchases.
- Map each service outcome to the single party that accepts responsibility for it.
- Keep the framework holder fully liable for subcontracted work, with approval rights over the subcontractor.
- Compare any change requested after award with the commitments the evaluation relied on.
Questions people ask
Approving a large order under a government framework with mostly default terms, what should the committee require?
Require the order to define what the framework leaves open: deliverables and acceptance, named staff, milestones and payments, data and exit for this system, and the body's rights on delay. The framework sets the ceiling; the order sets what you get. It depends on what the framework specifies and on the system's criticality.
Should a municipal contract make future feature requests mandatory purchases?
Keep future capability decisions separate from the initial commitment. Signing depends on mandatory updates, compatibility, purchasing options, and terms verified with procurement and legal owners.
Should we choose a supplier consortium without one accountable service owner?
Evaluate the accountable service arrangement alongside each partner's capability. Selection depends on enforceable ownership, subcontractor boundaries, and continuity if a consortium member withdraws.
Should we accept free discovery bundled with a municipal implementation contract?
Separate learning from a commitment that prevents acting on what is learned. The decision depends on exit freedom, usable findings, and procurement conditions checked by the responsible owners.
What should we do when a winning public bidder changes important contract terms?
Assess the business impact and obtain a procurement and legal view on the permitted response. It depends on the actual tender, the materiality of the change, and the authorised decision process.
Framework holder wants to deliver our order through an unevaluated subcontractor, what should we require?
Keep the framework holder fully responsible in writing, get approval rights over the subcontractor and its key staff, and make sure data, security and confidentiality terms flow down. Evaluate the subcontractor as if it were bidding. It depends on what the framework allows on subcontracting and on how critical the subcontracted work is.
What should we assess when a winning technology bidder changes key personnel?
Compare the proposed replacement capability with the commitments on which the award relied. Available responses depend on the tender and contract, and procurement and legal owners must determine the permitted process.
How I can help with this decision
- Ask or talk (Free)
- I give my view on the gaps framework orders and public contracts usually leave, and what to require before you approve.
- Review (Pay if it was worth it)
- I write an independent review of the order, bid or requested change against the framework and the system's needs. I recommend terms to add, conditions for approval or grounds to refuse.
- Retain (When it makes sense)
- I stay available at each milestone to review acceptance evidence and the supplier's staffing against the agreed conditions.