Built for the Employer-Side RTW Workflow

When a physician form arrives, the first step is capturing restrictions accurately without re-keying them for every downstream document. Transitional Duty Manager supports WA Activity Prescription Form (APF), TX DWC-073, and a generic work-status fallback — each with structured fields that map directly to the O*NET matching engine and all generated documents.

• Single intake record links to every downstream artifact
• WA APF and TX DWC-073 field layouts rendered dynamically on form type selection
• File upload zone for scanned form storage (Supabase Storage)
• Restriction expiry date tracked with 14-day advance alert

Captured restrictions are matched against your site-scoped employer task bank using O*NET 30.3 physical demands and abilities data. The engine returns a ranked list of safe duties with the restriction↔demand rationale recorded for each match — showing exactly why each task is compliant or conflicted.

Every match output is stored with the input restrictions, full ranked result set, human selection, and recorded rationale — retained for a minimum of 3 years for AI-disclosure compliance per Colorado SB 26-189 (effective January 1, 2027), Illinois 2026, and California ADS 2025.

• Ranks compliant duties from your own task bank — not a generic job database
• Explainable output: shows restriction↔demand comparison for every result
• Human selection is required — never auto-assigned (BR-001)
• Analyst role can prepare a recommended selection for coordinator confirmation
• Match output immutably logged with actor identity and O*NET dataset version

The task bank is the matching engine's input dataset and your program's long-term institutional memory. At onboarding, the task bank is seeded with O*NET-derived starter templates for your selected industry (manufacturing, construction, healthcare, or logistics). You edit and extend your own copy — it stays yours across every insurer and every renewal cycle.

• Site-scoped — tasks at one location are not visible to other locations
• Seeded from O*NET 30.3 data for four target NAICS sectors
• Onboarding is complete only when at least one task is accepted or edited
• The populated task bank survives coordinator turnover and carrier changes

Includes information from O*NET 30.3, used under CC BY 4.0. O*NET® is a trademark of USDOL/ETA.

Generate a WA Employer's Job Description Form (Light Duty/Transitional designation) pre-filled from the confirmed O*NET duty selection, restriction record, and employer task bank data. State-form fidelity is maintained as a configurable template — form version and effective date tracked in the admin registry.

• Pre-fills from confirmed human duty selection — no manual re-entry
• State form version tracked with generation timestamp
• "Not legal or medical advice" disclaimer in every document footer
• Multi-Site and Partner tiers: custom branding, no watermark

Generate the physician approval packet from case data and track the physician's response — status, date, and treating provider identity — before the offer is issued. Then generate the written modified-duty offer and capture the worker's acceptance or refusal with timestamp, method, and representative identity.

• Approval status, date, and provider name stored per case
• Offer cannot advance without a recorded physician approval status
• Acceptance or refusal captured with timestamp and method (verbal/written/email)
• 5-business-day offer non-response alert fires automatically
• Refusal documentation stored and surfaced in the audit trail

Restriction windows expire. Assignments last too long without review. Transitional Duty Manager tracks both — alerting you 14 days before restriction expiry and flagging cases that exceed your configured max-duration threshold (default 90 days). The flag notifies and requires documented disposition — it never auto-terminates an assignment.

• 14-day restriction-expiry in-app and email alert
• Physician re-approval pending >7 days alert
• Max-duration flag (default 90 days) — configurable per case
• Case disposition documented by coordinator before closure
• All alert events logged in the audit trail

Track approved days and wages using approved-dates-only logic — only dates within the active restriction window, with physician approval in force, and with the approved light-duty job assigned are eligible. When the case is ready, the pre-filled My L&I-ready reimbursement packet is assembled from stored case data.

• Program rules: 50% of base wages, $25,000 cap, 120-workday cap (injuries on/after Jan 1, 2025) — stored as configurable data rows, never hard-coded
• Excluded days flagged with reason (off-restriction, pre-approval, post-closure)
• In-app alert when approved days are logged but no packet has been filed
• TX DWC-008 and OR EAIP modules available on Multi-Site tier

Every document generated, sent, approved, accepted, refused, or edited is logged with actor identity and timestamp. The audit log is append-only — no edit, no delete — and is retained for a minimum of 3 years from case closure. Exportable as CSV for carrier audits and L&I reviews.

• Covers: case creation, restriction intake, match run, human selection with rationale, physician approval, offer generation, acceptance/refusal, day log entries, reimbursement export, case closure
• Retained ≥3 years (AI-disclosure compliance + WC statute of limitations alignment)
• Exported CSV includes action type, actor, timestamp, and document reference

Site supervisors see assignment limits and approved duty names — never restriction diagnoses, APF field data, or physician form content. Medical data separation is enforced at the database layer (Supabase RLS), not merely the UI layer — it cannot be bypassed by API calls.

• Five-role model: Admin / RTW Coordinator+HR Manager / Analyst / Site Supervisor (Viewer) / Platform Admin (Rovaryn)