A start date slips. Nine households move. Thirty-seven stay put.

DecisionOS re-plans only what a change touches, shows the rule behind every move, and returns the same plan for the same inputs every time.

Alder Court redevelopmentBuilding C relocation plan
Plan v14In effect
Plan in placePlan
Schedule changeChange
Impact checkImpact
Re-planRe-plan
Check and approveApprove
Paused while you look
No open changes. Plan v14 was approved Feb 12.
Building C construction start slips 2 weeksMar 9 → Mar 23 Read from the construction schedule
0households re-assigned
46keep their unit
46/ 56temporary units in use
0rule violations

    Same inputs, same plan.

    Plan v14 was approved by the Relocation Manager. Its cost was inside the manager's limit.
    Added moving cost in v15$0
    Manager limit $10,000
    Relocation Managercan approve to $10,000
    Director of Developmentnot needed

    Simulation summary: a relocation plan places 46 households in 56 temporary units across four sites. Building C's construction start slips two weeks, which would leave nine households in Hollis Street units past the end of that lease. The engine re-assigns only those nine households to vacant units at other sites, each for a stated rule: bedroom size, accessible unit, notice period or school district. Thirty-seven households keep their unit, there are zero rule violations, and because the added moving cost of $14,200 is over the Relocation Manager's $10,000 limit, the new plan is sent to the Director of Development for approval.

    Illustrative data. Alder Court, its sites and its households are fictional.