RTW OS
GAITIQ · governed return-to-work operations
RTW OS
Return-to-work execution that aligns claims, assessment evidence, milestones, and escalation.
RTW OS turns assessment evidence, claim posture, employer readiness, milestones, escalation, and governed recovery pathways into one operating surface.
RTW OS
GAITIQ · governed return-to-work operations
The problem
RTW programs lose momentum when claims, clinical assessment, employer coordination, milestones, and escalations are split across disconnected tools with no shared evidence frame.
You coordinate sensitive return-to-work journeys across claims and clinical teams.
Employers, insurers, and providers need one governed view of readiness and milestones.
You must show regulators and partners that evidence and audit are first-class.
Why businesses choose RTW OS
Governed RTW coordination
Claims, clinical, and employer teams share milestones and escalation posture.
Evidence you can present
Keep assessment, plan, and milestone context tied to each decision.
Safety for sensitive work
Boundaries for clinical and claims decisions stay explicit and visible.
RTW OS complements Finance OS and Growth Command Center by treating claims and recovery journeys as first-class operating work.
Connects to
- Claim posture
- Assessment evidence
- Employer readiness
- Plan milestones
- Escalation pathways
How it works
- 1Claim
- 2Assessment
- 3Readiness
- 4Plan
- 5Milestone
- 6Escalation
Readiness cockpit
Show return-to-work posture, employer capability, worker readiness, and escalation pressure in one governed dashboard.
Evidence pathway
Attach assessment, claim, plan, milestone, and employer context without collapsing unknowns into false certainty.
Coordinated recovery
Route sensitive RTW work through clear review paths so teams can coordinate without hidden automation.
Evidence posture
Logged-out preview only; tenant evidence loads after sign-in.
Outcome
Operators can understand readiness, spot blockers, coordinate next steps, and keep sensitive RTW decisions inside governed review paths.
Signal source
Claim + assessment postureRTW recommendations explain source quality, readiness, and missing evidence.
Policy state
Review boundedNo clinical, claims, employer, or recovery-plan mutation is exposed from public story pages.
Audit source
RTW evidence spinePlans, milestones, and escalations remain traceable as the runtime matures.
- Role-safe evidence
- Clinical and claims boundaries
- Approval visibility
- Audit-ready recovery plans
Evidence rail
Open the console to inspect tenant-scoped evidence for RTW OS.
Open evidence in console →Related agents
Kinematics engine
Product story →Kinematics engine
Converts pose frames into stride, cadence, symmetry, confidence, and calibration-aware diagnostics without placeholder scoring shortcuts.
Marketing OS (MERCURY module surface)
Product story →
Marketing OS (MERCURY module surface)
Primary operator workspace for governed marketing operations; MERCURY domain agent manifests in integration topology.
Sales OS (AUCTOR module surface)
Product story →
Sales OS (AUCTOR module surface)
Primary operator workspace for governed sales and pipeline intelligence; AUCTOR domain agent manifests in integration topology.
Operator console (Next.js)
Agent profile →
Operator console (Next.js)
Primary control-plane experience for pilots and demos; uses cookie-based JWT to `/api/v1/*` (see `apps/web/middleware.ts`).
Growth Command Center
Product story →
Growth Command Center
Single pane for demand-to-revenue posture when one or both commercial modules are active.
API ingress & identity boundary
Agent profile →
API ingress & identity boundary
Single controlled ingress for the TypeScript kernel; aligns with API-first posture.