Block contracts and bundled payments are used to simplify commissioning and stabilize budgets. Instead of paying per unit of activity, systems allocate a fixed payment to cover a defined population or pathway over a set period.
These models sit alongside Commissioner Expectations & System Priorities and interact closely with Funding, Rates & Payment Models, shaping how providers plan delivery and manage risk.
Their effectiveness depends on wider system design, explored further in the Commissioning, Funding & System Design Knowledge Hub, where funding structures, accountability, and operational reality are aligned.
Poorly calibrated block models transfer demand and complexity risk onto providers, leading to access pressure, workforce strain, and declining service quality.
Why Block and Bundled Models Are Used
Commissioners use block contracts to create financial predictability. Budgets are fixed, and providers are expected to manage delivery within agreed funding levels.
Bundled payments extend this approach by grouping multiple services into a single payment. This reduces transactional complexity but increases reliance on accurate planning assumptions.
How Block and Bundled Payments Work in Practice
Funding is agreed upfront based on expected demand, complexity, and service scope. Providers are responsible for managing staffing, access, and quality within that envelope.
Performance is monitored through activity, outcomes, and access measures. However, payment does not automatically adjust when demand or complexity changes.
Operational Example 1: Managing Demand Volatility Within Fixed Funding
Step 1: Commissioners define expected demand levels and record assumptions within contract schedules and demand modelling documentation.
Step 2: Providers track referral volumes and record real-time demand within intake and case management systems.
Step 3: Operational leads compare actual demand against assumptions and record variance within performance dashboards.
Step 4: Governance teams escalate sustained variance and record actions within contract review and escalation logs.
Required fields must include: demand forecasts, actual referral volumes, response times, and staffing capacity data.
Cannot proceed without: accurate and current demand data linked to service delivery.
Auditable validation must confirm: demand pressures are identified and acted on before service quality declines.
This process ensures that demand changes are visible and managed. Without it, providers absorb increased pressure without adjustment. Early warning signs include longer response times and staff overload. Escalation is led by operational and commissioning teams to trigger review mechanisms.
Demand management is audited through referral data, performance reports, and service metrics. Reviews occur monthly, with escalation triggered by sustained variance from agreed levels.
Operational Example 2: Managing Complexity Creep Over Time
Step 1: Intake teams assess referral complexity and record risk levels and support needs within case management systems.
Step 2: Providers track changes in case mix and record trends within service delivery and workforce reports.
Step 3: Quality teams review complexity data and record findings within governance and audit reports.
Step 4: Commissioners and providers review complexity trends and record re-basing discussions within contract review documentation.
Required fields must include: complexity indicators, acuity levels, case mix trends, and workforce impact data.
Cannot proceed without: consistent measurement of complexity across all referrals.
Auditable validation must confirm: funding assumptions remain aligned with actual service user needs.
This process prevents providers from absorbing increasing complexity without recognition. Without it, staff burnout rises and service quality declines. Early warning signs include rising caseload intensity and reduced staff retention. Escalation is led by quality and commissioning teams.
Complexity trends are audited through case records, workforce data, and performance reviews. Reviews occur quarterly, with escalation triggered by sustained increases in acuity.
Operational Example 3: Protecting Access Under Fixed Payment Models
Step 1: Referral teams log all incoming requests and record acceptance decisions within intake systems.
Step 2: Service managers review acceptance rates and record trends within performance dashboards.
Step 3: Governance teams monitor access patterns and record potential restrictions within audit reports.
Step 4: Commissioners review access data and record findings within contract monitoring and safeguarding reviews.
Required fields must include: referral numbers, acceptance rates, waiting times, and rejection reasons.
Cannot proceed without: transparent recording of all referral decisions.
Auditable validation must confirm: access is not being restricted due to financial pressure.
This process ensures that access remains fair and safe. Without it, providers may limit intake to manage costs. Early warning signs include rising rejection rates and longer waiting lists. Escalation is led by safeguarding and commissioning teams to protect access.
Access patterns are audited through referral logs, waiting time data, and service reviews. Reviews occur monthly, with escalation triggered by changes in access patterns.
System and Funder Expectations
Federal and state systems expect block models to deliver stable, accessible services. Fixed funding does not reduce accountability for access, safety, or quality.
Commissioners require evidence that providers are managing demand, maintaining workforce stability, and delivering consistent outcomes within agreed funding. Where this is not demonstrated, intervention is expected.
Regulatory Expectations
Regulators expect clear evidence that services remain safe and accessible under fixed payment models. Providers must show that financial constraints do not compromise care quality.
Inspection readiness depends on documented links between funding, staffing, and service delivery. Records must demonstrate that risks are identified, managed, and escalated appropriately.
Conclusion
Block contracts and bundled payments offer predictability and reduce administrative complexity. They allow systems to plan services at scale and reduce transactional burden.
However, they also concentrate risk. Demand volatility, rising complexity, and access pressure must be actively managed through strong governance and transparent data.
Effective models depend on realistic assumptions, clear escalation mechanisms, and regular review. Providers must be able to evidence how funding aligns with real service delivery and changing needs.
Consistency is maintained through monitoring demand, tracking complexity, and auditing access. Evidence comes from referral data, workforce metrics, and service performance reports.
Without these controls, block models create hidden pressure that undermines delivery. With them, they can support stable, accountable, and sustainable community-based care systems.