Platform

Every injury case, its restrictions and who is watching it

Return to work fails in the gaps - a certificate that expired, a duty nobody adjusted, a review that slipped. One register holds the case, the current capacity and the next date that matters.

Replaces
Case spreadsheets, email, filing
Tracks
Cases, capacity, providers, claims
Alerts on
Expiring certificates and reviews
Live in
24 hours from your export

What does return-to-work and injury case management software need to do?

Return-to-work management has to hold three things together: the injury case, the capacity currently certified by a treating doctor, and the suitable duties assigned against that capacity. Cases fail in the gaps between them - an expired certificate, a restriction nobody re-read, a review date that slipped. Frontline keeps all three as linked registers with the next date that matters surfaced to the person who has to act, and restricts medical detail to the people with a reason to see it.

  • Certificate expiry and review dates raised before they lapse, not after
  • Suitable duties matched to the capacity actually certified
  • Cases linked back to the incident that caused them
  • Role-based access - a supervisor sees the duties, not the diagnosis

The problem

The cost is in the days nobody was tracking

Nobody loses a return-to-work case deliberately. It slips because the certificate sat in an inbox and the restriction nobody re-read was still in force.

Injury case management is coordination work: a treating doctor issues a certificate with restrictions, a supervisor has to find suitable duties, a review date lands three weeks out, and a claim runs alongside it on a different timeline. Miss one handover and someone is either off work longer than they need to be, or back on a task their certificate does not permit.

Most teams run this from a spreadsheet and a calendar reminder, which works right up until the coordinator is on leave.

  • The current certificate and its restrictions, on the case
  • Suitable duties matched to the capacity actually certified
  • Every upcoming review and expiry surfaced before it lapses

What it does

Three linked registers, one dashboard

Injury cases

One record per case from first report to closure, carrying the mechanism, body part, treatment, days lost and current status.

Capacity and duties

The restrictions on the current certificate, and the suitable duties assigned against them - so a supervisor can see what this person can do today.

Treating providers

Doctors, physios and rehab providers on the case, with the correspondence and certificates attached where the case can see them.

Dates that bite

Certificate expiry, review dates and planned upgrades all raise before they land, to the person who has to act.

Linked back to the incident

The case hangs off the incident that caused it, so injury data and the risk it evidences stay connected instead of living in separate systems.

Confidentiality by design

Medical detail is restricted to the people with a reason to see it. A supervisor sees the duties; they do not see the diagnosis.

How a case runs

From the incident to case closed

  1. The incident is reported

    Captured from the field on a phone. If it involves an injury, a case opens off the back of it rather than being re-entered somewhere else.

  2. The certificate sets the capacity

    Restrictions and review date go on the case. The expiry is now a date the system is watching, not one a coordinator has to remember.

  3. Duties are matched and assigned

    Suitable duties are selected against the certified capacity and assigned to a supervisor, with the restriction visible to them.

  4. Reviews step the capacity up

    Each review updates the capacity and the plan. The history stays on the case, which is what an insurer or a regulator asks for.

  5. The case closes with a record

    Days lost, cost and outcome land on the record - and roll into the injury metrics your board already looks at.

Included

What you get on day one

  • Your open cases imported with their current restrictions
  • Certificate and review expiry alerts to named owners
  • Suitable duties register matched to certified capacity
  • Provider directory with correspondence attached to the case
  • Role-based access so medical detail stays restricted
  • Days-lost and injury-severity metrics from live case data
  • Full case history for insurer and regulator requests
  • Cases linked back to the incidents that caused them

Questions we get asked

Who can see medical information?

Only the people you grant it to. Access is role-based and set per field, so a site supervisor sees the duties and restrictions they have to manage without seeing the diagnosis behind them.

Does it replace our claims system?

No, and it shouldn't. The insurer's claims system is the system of record for the claim. Frontline is where the case, the capacity, the duties and the evidence live - the operational side the claims system never covers well.

Does it work across jurisdictions?

The case fields, certificate types and review cadences are configured, so states or countries with different schemes can run side by side in one account.

See it running on your own data.

Tell us what you run today. When your spot comes up you are looking at your own register, your own incidents and your own sites, not a canned demo environment.

  • We take a few teams at a time
  • Works with your existing exports
  • No IT project