Cost Audit Bridge

Original released schedule cost vs current — attribution of every dollar of movement

Cloud connected · no rows yet · Import CSVsSource: Forecast· as of
Last refreshed
Next refresh ()
Viewing: Pay Period 22 Dec – 4 Jan · All rosters
Original released
Baseline at release
Total movement
Net change since release
Final amount
Current schedule cost
Resource swap shifts
Shifts with employee change

Bucket attribution

Where the movement came from, by SCHADS-aware bucket

Reconciliation OK
Resource change
$0.00
Employee swap delta
OT impact
$0.00
OT1.5 + OT2 above ordinary
Unallocated fill
$0.00
Open shifts at pool median
Sleepover change
$0.00
Award 25.7 deduction
Manual adjustment
$0.00
Residual movement
Identity check
Holds
Movement = Final − Original

Per-roster bridge

Sorted by total movement · 0 rosters in scope

No bridge data for this period.

How the bridge is calculated

Movement attribution methodology

  • Original release — baseline shift cost at release
  • Resource change — cost delta when expected employee differs from actual employee. Real Salesforce baseline (Cost Difference) used where available (4,305 shifts); 10% proxy fallback for unmatched edge cases (416 shifts).
  • OT impact — incremental cost from OT1.5 + OT2 hours above ordinary
  • Unallocated fill — Open Shifts not yet assigned, costed at the roster median pool rate
  • Sleepover change — sleepover hour deduction (Award 25.7)
  • Manual adjustment — residual movement not captured above

Per UFC Pay Cost Engine Requirements v0.4 §15. Salesforce baseline ingested from Cashflow Per Appointment Detailed.csv (Phase 4.A complete). Identity holds at 99.56%. Remaining 0.44% leak from OT-delta clamping when OT cost > shift_total.