What Cor Pathway 360 does

The page follows the work in the order it actually happens: the field record, the office view, then the auditor's file. First, one record from start to finish.

One record, start to finish

1. A foreman fills in a field level hazard assessment at the tailgate, in a yard with no signal. It saves on the phone.
2. One hazard on the card needs fixing. The foreman opens a corrective action with a photo, assigns it to the shop lead, and sets it due Friday.
3. The phone syncs on the drive back. The office sees the assessment and the open action that same afternoon.
4. The shop lead closes the action with a photo and a signature.
5. The assessment and the closed action are filed against the audit elements they prove. Nobody retypes it. Nobody rebuilds a binder.

In the field

Offline first, on the crew's own phones. Installed as an app from the browser, no app store account needed. Submissions, photos and signatures queue on the device and sync when signal returns. A crew with no bars fills out an FLHA the normal way and it uploads on the drive back.

Forms you control. Build your own, with conditional logic so a question appears only when it is relevant. A long inspection form stays short for the person holding the phone.

Signatures and photos as evidence. Captured at the point of work with the time and the person attached, which is what makes them worth something in an audit rather than just a picture in a folder.

Hazard assessment, both kinds

Auditors care about the difference between these two, and a surprising number of programs blur them.

Formal hazard assessments are the documented, reviewed assessments of the tasks your company performs, with controls assigned and a review history. They are a program level document.

Field level hazard assessments (FLHAs) are what the crew completes at the site, for today, for these conditions, before the work starts.

Both live in the system, and the field level cards reference the formal assessment they came from, which is exactly the link an auditor looks for. There is more detail on the hazard assessment page.

Incidents and near misses, reported from the site

Reported from the site. Incidents and near misses are reported on the phone where the work happened, with photos, while the detail is still accurate rather than reconstructed on Monday.

In the office

Corrective actions that close properly. Every action is assigned to a named person with a date, and tracked through to sign off. This is the part of the audit that catches most companies. Finding the hazard is half of it. An auditor will ask what you did about it, who did it, when, and how you know it worked.

Which tickets expire, and when you find out

Who holds which ticket, and what expires when. First aid, tickets, licences, competency sign offs and site specific orientations.

The practical value is the warning before the problem: knowing in advance that a worker's ticket expires next month, rather than finding out when a prime contractor turns them away at the gate.

Equipment, and where a defect goes after you find it

Pre use inspections, defect reports, and service history attached to the piece of equipment rather than living in a separate maintenance spreadsheet. A defect found during a pre use inspection becomes a maintenance record without anybody retyping it. That is the per unit vehicle file NSC Standard 11 expects you to keep, built as a by product of the work instead of assembled the week before an audit.

Service work orders

For contractors whose safety program and service work are the same operation: work orders, scheduling and completion records in the same system as the safety documentation, so a technician does one set of paperwork instead of two.

For the audit

This is the difference between a form app and an audit system.

Evidence is tied to your certifying partner's audit elements while it is being collected, not reassembled from four systems the week before the auditor arrives. When the audit comes, the evidence is already organized the way the auditor thinks about it.

Requirements differ between certifying partners, and the number and naming of elements differ between partners and standards. So the mapping is done for your partner specifically, during the program build. See the COR guide for what that involves, or the documents auditors ask for.

If you run regulated vehicles

For companies running regulated vehicles.

Daily trip inspections, pre trip and post trip, completed in the cab, following the same walk-around order a driver uses on the circle check. Defect reporting that routes to whoever fixes it. Driver files kept with the same expiry tracking as everything else. Vehicle certifications such as CVIP inspections tracked to their expiry date, so a decal never lapses on a unit already out on the road.

If you are a new carrier, none of this is groundwork you get to do later. Alberta will not issue you a Safety Fitness Certificate until you confirm you have written safety and maintenance programs, which makes the program a condition of getting on the road rather than something an auditor raises three years in.

If you do not run vehicles, turn the module off and none of it appears in your navigation.

What it does not do

Worth saying plainly.

• No worker chat. Deliberately. Your crew already has a group text and a safety app is not the place to compete with it.
• No payroll, no invoicing and no accounting. It records the work. It does not bill for it.
• No estimating or bidding.
• No AuditSoft integration today.
• No dedicated 24/7 support desk. It is a small company. The SiteDocs comparison sets out the full list of what you give up.

The technical shape of it

Next.js and Supabase Postgres, installed as a progressive web app, offline queue in the browser's own storage. Multi tenant with row level security across 83 tables, which for a self hosted deployment means one company in the database: yours.

The self host page has the requirements, the licence in plain language, and the GitHub repository.