One inspection grammar across every QDIP application.
- 01Situation
- 02Alternatives
- 03Evaluation
- 04Risk / uncertainty
- 05Recommendation
- 06Evidence
- 07Trace
Scenario context
Teams must be assigned across communities over a planning horizon while demand, availability and movement costs compete for limited capacity.
Which daily team allocation best covers weighted demand while respecting availability and operational constraints?
Tests whether QDIP finds a feasible allocation with measurable demand coverage and operational trade-offs compared with the baseline.
- • Communities and demand by day/service
- • Teams, capabilities and availability
- • Current allocation / optional baseline
- • Team availability and eligibility
- • Planning horizon
- • Movement/reassignment limits and business priorities
- • Imported data is validated before use; synthetic demo inputs are explicitly marked as demo data.
Mobile team allocation plan
QDIP helps decide where to send mobile teams so more priority needs are covered with the resources already available.
5 teams · 5 communities · 320 demand units · 5 days
Responsible Citizens · synthetic
Can the same teams cover more priority demand?
QDIP accounts for needs, team skills, current locations, location availability and movement across the full planning horizon.
Unlike a spreadsheet, QDIP evaluates consequences across the full horizon: where a team ends today changes what is feasible tomorrow.