Open coordination workload
Count tasks derived from the same referral, home-care and pathway sources used by Transitions.
New care-coordination range
Local product demonstratorMeridian Neighbourhood Capacity
Compare open coordination tasks with locally entered team-capacity assumptions and make unconfigured workload visible.
See the work. Test the assumptions.
Capacity gives service managers a transparent starting point for discussing distribution of coordination work. It answers how many open tasks sit with an owner or team and how that raw count compares with a locally entered weekly capacity assumption. It keeps the assumption visible instead of presenting an unexplained resource recommendation.
What the AI does. What people decide.
The actual assistance
No generative model or autonomous workforce planner is used in this workspace. It groups open coordination tasks by owner or team and compares those counts with values entered by the service. Its role within the wider AI platform is to make downstream operational workload visible; it does not optimise staffing or make a clinical allocation.
Human ownership
Operational planning context only. Local assumptions must be validated with the team; apparent spare capacity is not proof that a service can accept more clinical demand.
Features in the current workspace.
Owner and team view
Summarise where open work sits, including owners or queues that are not yet configured.
Local weekly assumptions
Enter a team label and a weekly task-capacity value that the service is prepared to review.
Saved configuration
Add assumptions and explicitly save capacity settings so the comparison is repeatable.
Over-capacity visibility
Show where the current count is above the recorded assumption, without treating the threshold as a recommendation.
Unconfigured teams
Distinguish absent capacity information from a configured zero or a team with no work.
Source refresh
Refresh the workload against current coordination state rather than relying on a static image of the queue.
Transparent interpretation
Keep the raw-count basis visible: task complexity, clinical acuity, staff hours and time per task are not included.
From first input to a reviewed next step.
- 01
Load open work
Read coordination tasks from the existing local workflow state.
- 02
Group ownership
Count items by the recorded owner or team.
- 03
Enter assumptions
The service supplies weekly task capacity.
- 04
Compare
Show the task count against the saved assumption.
- 05
Review context
A person considers complexity, hours and missing work before acting.
How the product works.
| Area | Mechanism and scope |
|---|---|
| Aggregation | The neighbourhood capacity endpoint performs deterministic task grouping and count comparisons. |
| Configuration | Capacity assumptions are stored with update time and actor information in the configured application store. |
| Meaning of a count | One task is one coordination item. A count is not weighted by expected duration or care need. |
| Planning limits | There is no automatic rota generation, workforce optimisation or clinical staffing recommendation. |
Product evidence and source notes
Content checked against the v25.2.0 source and visible local workspace on 30 October 2026. This is a product description and interface inspection, not an end-to-end deployment or clinical validation.
routes/neighbourhood_ops.py, capacity and configure_capacity; static/neighbourhood-ops.js
Review assurance scopeQuestions about Neighbourhood Capacity.
Is this an AI staffing recommendation?
No. It is a visible comparison of raw task counts and locally entered assumptions.
Does it include every piece of team workload?
Only work represented by the configured source workflows is counted. Offline work and other systems can make the view incomplete.