Post-Tender Negotiation (PTN): How to Prepare, Respond, and Protect Your Score

Post-tender negotiation isn’t a second competition. It’s due diligence. Commissioners use PTN to confirm feasibility, align assumptions, and document any clarifications before award. This guide shows how to prepare, respond, and finish with a clean, award-ready record.

Handled well, PTN reinforces the strengths that won you marks. Handled poorly, it can introduce doubt. The key is to approach it using clear bid writing principles and a disciplined tender strategy — so your clarifications align perfectly with what was scored and preserve auditability.

A strong clarification process usually begins with understanding the right way to handle clarification requests after a tender so responses stay accurate, controlled, and relevant.

🎯 What PTN Is (and Isn’t)

Is: A structured clarification after evaluation to confirm deliverability, risks, assumptions, and value for money. Notes are recorded and can form part of the contract clarification schedule.

Isn’t: A chance to introduce a new model, materially change price, or dilute commitments that affected scoring. Commissioners must preserve fairness, equal treatment, and audit trails.

Think of PTN as a stability check: the commissioner is asking, “Does this bid still stand up under light pressure?” Your job is to show calm control.


🧭 The PTN Objectives (Commissioner Lens)

  • Feasibility: Can the service start on time with safe staffing and systems?
  • Assumptions: Are casemix, geography, volumes, and TUPE understood?
  • Risk: Are workforce, TUPE, digital/IG, medication, safeguarding, and escalation risks owned with mitigations?
  • Value: Does the financial model remain viable, lawful, and within scope?
  • Clarity: Are ambiguities resolved in writing for contract signature?

Every PTN question fits one of these five lenses. Answer through them, and you’ll stay aligned.


📦 Build a 6-Page PTN Pack (Reusable)

Keep it short, visual, and structured. Aim for six pages that demonstrate control without overwhelming the panel:

  1. Summary & Assumptions (1 page): service description, volumes, geography, response times, inclusion/exclusion criteria; list key assumptions (TUPE headcount, travel zones, night cover model).
  2. Mobilisation Timeline (1 page): 0–8 week roadmap, gateways at Weeks 2 and 4, mock-run, go-live checklist, named owners.
  3. Workforce & Safer Staffing (1 page): recruitment pipeline/TUPE plan, skill mix, supervision cadence, relief pool, escalation on-call model.
  4. Governance & Safety (1 page): incident loop, audit cadence, safeguarding timescales, NI oversight and reporting rhythm.
  5. Digital & IG (½ page): DSPT status, role-based access, incident logging, action tracker sampling and verification.
  6. Finance & Sensitivities (1½ pages): price basis, wage/inflation assumptions, travel/training inputs, scenario deltas (±10–20% volume), trigger points and mitigation.

Optional appendices: risk register (1 page), rota sample, training matrix snapshot, example dashboard.

The aim is reassurance, not reinvention.


🧱 Answer PTN Using the Four-Line Scaffold

Maintain the same leadership tone that scored well in your tender:

  1. Behaviour: “We run weekly practice reviews; actions logged same day.”
  2. Owners & cadence: “NI chairs monthly governance; safeguarding decisions within 48–72 hours.”
  3. Evidence: “Q2 documentation compliance 96% (84% Q1); 100% incident triage within 72 hours last quarter.”
  4. Assurance: “Re-audit confirmed; themes shared in supervision and monthly ‘what we learned’ brief.”

This pattern signals continuity between what you wrote and what you’re now clarifying.


📋 Typical PTN Topics (and Model Responses)

1) Mobilisation Readiness

Question: “What gives confidence you can start safely in Week 1?”

Response: “Daily huddles in Weeks 1–2; weekly Mobilisation Board chaired by the Registered Manager; gateways at Weeks 2 and 4; mock-run before go-live. Week-6 re-audit confirms documentation and staffing stability. One-page dashboard shared weekly.”

2) Workforce & TUPE

Question: “How will you manage unknown TUPE volumes?”

Response: “We modelled ±20% TUPE variance. A 10% relief pool is ring-fenced; mentors embedded in rota. If volumes exceed baseline, agency sampling and observation increase temporarily until sign-off and induction are complete.”

3) PBS & Enablement

Question: “How early will enablement be visible?”

Response: “Visual schedules and graded exposure begin Week 2; enablement outcomes reviewed monthly. Two recent packages moved 2:1→1:1 within eight weeks, verified by observation and PBS review.”

4) Safeguarding

Question: “How do you ensure timely decisions?”

Response: “Same-day alert; decision within 48–72 hours; quarterly sampling; safeguarding reflection in monthly supervision. Escalation card embedded in induction.”

5) Digital & IG

Question: “What proves IG in practice?”

Response: “DSPT ‘Standards Met’; role-based access; incident logs sampled monthly; action tracker flags overdue items; governance verifies closures and re-tests controls.”

6) Finance & Value

Question: “What if travel inflation rises mid-year?”

Response: “Base price includes X pence/mile and Y% inflation. If fuel indices exceed Y% for Z months, we propose review under the variation mechanism; first mitigations are route clustering and rota optimisation.”


🧮 Pricing in PTN: What’s In-Scope?

PTN can tighten assumptions and arithmetic but must not create a materially different offer.

Generally acceptable:

  • Clarifying TUPE headcount or mileage bands.
  • Correcting arithmetic errors with a clear audit trail.
  • Confirming scenario pricing already permitted in the ITT.

Usually out of scope:

  • New service models.
  • Material rate changes.
  • Introducing new dependencies not priced originally.

If in doubt, protect fairness and say so explicitly.


🧠 Bring a PTN-Specific Risk Register

Prepare a concise one-page register with: risk, trigger, owner, mitigation, and escalation.

  • Workforce spike: trigger = sickness > X%; mitigation = relief pool + on-call escalation.
  • PBS drift: trigger = incident trend; mitigation = observation + targeted supervision + re-audit.
  • Digital delay: trigger = access credentials pending; mitigation = paper backup + 48-hour secure backfill.
  • Medication error cluster: trigger = 2 similar incidents; mitigation = themed audit + double-sign check + supervision review.

This shows you expect risk — and manage it.


🧩 Governance & Assurance Signals in PTN

  • Weekly incident, audit and feedback review; actions logged to closure.
  • Monthly governance chaired by NI; themed learning distributed.
  • Supervision used as competence verification, not conversation alone.
  • Quarterly thematic deep dive with re-audit confirmation.

PTN is where governance becomes tangible.


📈 Social Value & Partnerships (Stay Measurable)

If PTN touches social value, keep commitments countable and governed:

  • Two volunteer placements per quarter.
  • 5% social enterprise spend, reported quarterly.
  • Quarterly community engagement hours logged and reviewed.

Link each commitment to oversight so it reads operational, not aspirational.


🗣️ Useful PTN Scripts

On scope boundaries: “To remain within the ITT scope and fairness requirements, our clarification relates to assumptions and arithmetic only; the model and offer remain as tendered.”

On uncertain TUPE: “Our price is based on X FTEs. We’ve modelled ±20% variance; relief pool and mentor rota maintain safety until induction and sign-off are complete.”

On inflation: “Year one includes Y%. If indices exceed this for Z months, we propose review under the contract mechanism; initial mitigations focus on rota optimisation.”

On data readiness: “Role-based access live at go-live; dashboards active by Week 2; governance samples closures monthly.”


📋 PTN Meeting Logistics (Small Things, Big Signals)

  • Team: Registered Manager, Mobilisation Lead, Finance/Commercial, Quality Lead; NI introduced if present.
  • Deck: 6 pages + concise appendix; one-page mobilisation handout.
  • Agenda discipline: Follow commissioner structure; recap clarified points before closing.
  • Record: Confirm how notes will be shared; correct inaccuracies immediately in writing.

🧮 Finance & VFM: Speak in Inputs

Arrive with the underlying spreadsheet and know the core drivers:

  • Pay: base rates, enhancements, on-costs.
  • Non-pay: travel, training, digital licences, equipment.
  • Overheads & margin: inclusions, risk allowances, sensitivity triggers.

Commissioners trust traceable arithmetic more than narrative reassurance.


🧠 Legal & Compliance Guardrails

  • Avoid material change.
  • Protect confidentiality.
  • Review and confirm clarification notes promptly.

PTN is documented. Treat every answer as contract-adjacent.


📘 Before / After — PTN Rewrite

Before: “We will mobilise quickly with our experienced team.”

After: “Daily huddles Weeks 1–2; weekly Mobilisation Board; gateways at Weeks 2 and 4; mock-run before go-live; Week-6 re-audit; weekly dashboard shared with commissioner.”


🧭 10-Point PTN Self-Check (Target ≥17/20)

  1. Opener shows behaviour (not adjectives)
  2. Owners named; cadence visible
  3. Assumptions listed and in scope
  4. Mobilisation timeline with gateways
  5. Workforce/TUPE mitigation explained
  6. Safeguarding timescales stated
  7. Evidence anchored (time/source/place)
  8. Finance inputs traceable; sensitivities shown
  9. IG/traceability present
  10. Clarifications captured with agreed next steps

🚀 Close Strong (and Quiet)

End PTN with calm assurance:

“We’ve confirmed assumptions A–C, gateways at Weeks 2 and 4, and the TUPE mitigation path. Our offer remains as tendered. We’ll return written clarifications within two working days.”