Orientation Compliance
Cross-checked against Field Scheduling's live bookings — every currently-scheduled resource should have a logged Orientation on that project dated on or before their first day, the same "site access gated on induction" rule HammerTech enforces. Nothing here blocks scheduling; it's a heads-up list.
| Resource | Type | Project | First Scheduled Day | Status |
|---|
Safety Log
Site observations, incidents & injuries, inspections, orientations, toolbox talks and permits — one log, same as HammerTech's Report module. Click a column header to sort, or a status pill to advance it.
| ID ▾ | Type ▾ | Project ▾ | Date ▾ | Resource ▾ | Title ▾ | Severity ▾ | Status ▾ |
|---|
About this test build. Safety records live in their own shared Cloudflare KV store (a Pages Function at
/api/safety), separate from Field Scheduling's /api/schedule store — the two never collide. Orientation Compliance reads Field Scheduling's live bookings (read-only) to cross-check who's actually on site; project and resource lists (34 real Acumatica projects, 69 employees, 252 vendors/subcontractors) are the same live-pulled data as Field Scheduling. Only the 14 currently Active projects are offered when logging a new record — Completed jobs stay fully viewable for any record that already references them.
Modeled on HammerTech's Mobilize / Coordinate / Report structure. This is a working test/prototype, not the system of record — real OSHA-recordable incidents still need to go through Cadence's actual safety reporting process. This endpoint is not yet gated behind Cloudflare Access, so treat it as internal-link-only for now, not public.