When NHS Procurement Gets Local: How to Win Place-Based Frameworks Under ICSs

October 26, 2025

Integrated Care Systems (ICSs) are reshaping NHS procurement — shifting influence to local “place” decision-making and rewarding providers that can evidence partnership, prevention, and population impact. If you want a practical foundation for writing scorable NHS answers, start with our bid writing principles and then apply a whole-bid approach using our tender strategy.

🌍 What “place-based” really means in an ICS tender

In ICS procurement, “place-based” is not a slogan. It is a commissioning logic: services are expected to fit local pathways, link to neighbourhood partners, and show how delivery improves system outcomes (flow, prevention, inequalities), not just contract KPIs. Practically, this means your bid must read like it was written for the local system — with clear integration routes, governance arrangements, and evidence that you understand how care is organised across primary care, community services, local authority partners, and the VCSE sector.

⚖️ The new ICS scoring themes

Most ICS and place-based tenders score variations of the same pillars. Build your response plan so every major answer clearly maps to at least one of these:

Integration and partnerships: co-designed pathways, shared MDT working, and agreed escalation routes.
Prevention and early intervention: reducing deterioration, avoidable attendances, and preventable admissions.
Equity and inclusion: targeted approaches that narrow gaps in access and outcomes.
Digital and data readiness: information governance, secure sharing, and outcome tracking.
Value and outcomes: measurable improvement delivered efficiently and sustainably.

The key shift is that “quality” is increasingly judged by system contribution, not just internal process maturity.

🧭 Step 1: Start with the ICS strategy, then write to the question

Before drafting, read the ICS strategy and Joint Forward Plan (and any place plans or neighbourhood priorities). Pull out the repeated terms and outcome measures (for example: admission avoidance, frailty, long-term conditions, urgent care flow, prevention, inequalities). Then reflect that language in your answers — not by copying slogans, but by showing how your delivery model operationalises those aims.

Commissioner expectation: evaluators want to see explicit alignment to their priorities and pathways, with credible measures they can monitor. If your narrative doesn’t reference system goals, it will feel generic even if your service is strong.

📈 Step 2: Translate partnership into day-to-day delivery

Partnership claims only score when they become operational. Describe mechanisms that make integration real:

Referral and triage: who receives referrals, how decisions are made, what “same day” means operationally, and how you prevent duplication.
MDT working: which roles attend, cadence (weekly/fortnightly), how actions are recorded, and how disagreements are escalated.
Shared care planning: how care plans align to agreed pathways, and how updates are communicated across teams.
Place governance: how you participate in place meetings, provide dashboards, and respond to performance themes.

Regulator / inspector expectation (e.g., CQC): integration must not weaken accountability. Show clear clinical/quality ownership, safe escalation, and oversight that remains robust even when delivery is distributed across partners.

💬 Step 3: Prove outcomes using an “activity → output → outcome” chain

ICS panels typically score higher when the logic is explicit and evidenced. Use this chain in your main answers and case examples:

Activity: what you do (for example, rapid response assessment and short-term support).
Output: immediate measurable result (for example, response within X hours; discharge supported within Y days).
Outcome: system benefit (for example, reduced delayed discharge, fewer readmissions, improved flow).

Include time-bound measures where possible (last quarter, rolling 3 months, year-to-date) and state how you verify the data (audit sample, dashboard source, governance review).

🏗️ Step 4: Build assurance into every answer

ICS tenders weight assurance because risk is shared across the system. Make your controls easy to see:

Governance: named lead accountability, meeting cadence, action logs with owners and deadlines.
Incident learning: how incidents/near misses are reviewed, themes tracked, and improvements re-audited.
Safeguarding: thresholds, same-day escalation routes, Making Safeguarding Personal practice, and learning loops from safeguarding outcomes.
IG and data: role-based access, training compliance, reporting routes, and how you prevent and respond to breaches.

A strong bid shows “control” not through policy lists, but through routines: review, act, verify, learn.

🧱 Step 5: Use local operational examples that demonstrate system fit

Use short, structured examples that show context, approach, day-to-day detail, and evidence of change. Here are three patterns that score well in ICS tenders:

Example A: Place-based admission avoidance

Context: rising urgent care demand in a neighbourhood with high frailty and multiple long-term conditions. Support approach: same-day triage and rapid response visits with agreed escalation thresholds. Day-to-day delivery detail: a single point of access logs referrals, assigns a named lead, updates the shared action tracker, and completes a follow-up call within 24 hours to confirm stability. How change is evidenced: response-time compliance and avoidance outcomes are reviewed weekly, with a monthly thematic review to confirm learning and consistency.

Example B: Integrated discharge support and flow

Context: delayed discharge pressures with variable handover quality. Support approach: standardised discharge handover checklist and a “first 72 hours” safety protocol. Day-to-day delivery detail: staff confirm medication availability, red flags, and escalation routes before the first visit; any gaps trigger a same-day liaison call and documented risk controls. How change is evidenced: missed-handover issues are tracked as a theme; improvements are verified by sampling cases at governance and re-checking adherence in the next audit cycle.

Example C: Inequalities and inclusive access

Context: underserved communities experiencing barriers to access and engagement. Support approach: targeted outreach with accessible information and proactive follow-up. Day-to-day delivery detail: appointments are offered in flexible formats, communication needs are recorded and reviewed, and staff use agreed interpretation/accessible-format processes. How change is evidenced: access and satisfaction data are segmented (where available), themes are reviewed in place governance, and actions are tracked to closure with owners and timescales.

🧮 Step 6: Present value in system terms

In ICS tenders, value is not just price. It is credible contribution to system efficiency and outcomes. Keep value statements grounded:

Flow value: fewer delays and smoother transitions reduce pressure on beds and urgent care services.
Quality value: fewer incidents and better consistency reduce rework and safeguarding risk.
Experience value: faster access and clearer coordination improve trust and satisfaction.

Link each value claim to the assurance mechanism that keeps it real (dashboard, audit cycle, governance cadence).

🔧 Common pitfalls (and quick fixes)

❌ Generic partnership claims without structures. ✔ Add cadence, roles, escalation routes, and how actions are tracked.
❌ Activities without outcomes. ✔ Use the activity → output → outcome chain with time-bound measures.
❌ Equity as a paragraph, not a plan. ✔ Describe targeted delivery and how you monitor access and experience.
❌ Assurance hidden in policies. ✔ Show operational routines: review, act, verify, learn.

🚀 How to prepare before the next ICS tender window

Build a small library of place-relevant examples in a consistent structure (context, approach, delivery detail, evidence).
Align your dashboards and audit cycles to the outcomes the ICS cares about (flow, prevention, inequalities, safety).
Write method statements that show how integration works operationally, not just “we work in partnership.”
Stress-test your bid for scannability: headings that mirror criteria, proof points visible, and verification lines included.