PROFESSIONAL WORK · Reporting & operations
Placement lifecycle report
A weekly email briefing on upcoming starts, active work, and endings, built from actual scheduled shifts.
BuiltProductionDocumented October 6, 2026
My contribution
Built lifecycle reconciliation, report generation, delivery fencing, and a separate delivery-health check.
Tools
Python · Scheduling data · Bullhorn · Microsoft Graph · Durable ledger
How it works
- Read scheduling and placement context and reject stale inputs.
- Reconcile actual shifts into upcoming starts, first days/weeks, active work, endings, and review items.
- Freeze the HTML report and persist a send intent.
- Send through Microsoft Graph and record delivery state.
Decisions that mattered
Assignments are not actual shifts
Lifecycle classification checks scheduled work rather than assuming a placement date proves activity.
Freshness is a delivery gate
A stale source stops report delivery instead of producing a confident-looking briefing from old inputs.
A scheduler retry should not resend
Durable send intent and duplicate-send fencing protect delivery. A local-time guard handles daylight-saving behavior for the Monday schedule.
Monitor the report separately
A dedicated health check can detect a missed or uncertain delivery without depending on the report run to announce its own failure.
Results
Records from October 5–6, 2026 document the live weekly workflow and its operational validation.
Scope & limits
The workflow only reads records and sends the briefing; it doesn’t change placements or schedules.