Head office writes the standard. Every site runs it.
You decide what gets checked, what each answer sets off, when it is due at every site, and who sees which sites. The people on the floor get a phone that already knows.
Decide what an answer does before anyone gives it.
For every answer, head office sets what follows: stop the run, raise a finding, propose a work order, ask for proof. The inspector doesn’t have to know the rule. The phone does.
Weekly fire safetyQuestion 6Choice
Does the fire door close and latch on its own?
Pick an answer to see what it sets off.
On the inspector’s phoneA minor finding is raised with a photo, and the inspector gets a line of guidance. The run goes on.
- Halt inspectionOff
- Raise findingOnMinor: “Fire door does not close on its own”
- Propose work orderOff
- Require photosOnNo photo, no sign-off.
- Require noteOff
- Show next-step guidanceOn“Report it at the morning briefing.”
Eight kinds of question, each with its own rules
CheckboxChoiceNumberTemperatureRatingTextDate and timePhoto and video count
A temperature can be out of range, a question can appear only after a certain answer, and a reference document from your library can sit beside the question that needs it. The editor is laid out for a wide screen; the inspector’s side works on any phone.
Change the standard without pulling the floor out from under anyone.
Edit a draft, preview it as the phone will show it, read the diff and publish. A published version never changes. An inspection already under way finishes on the version it started with.
Weekly fire safetyv3 to v4
- AddedDoes the fire door close and latch on its own?
- ChangedExtinguisher pressure in the green: now requires a photo
- ChangedEscape route clear: “Partly” now raises a major finding, was minor
- RemovedExit signage lit, moved to the emergency lighting program
Nørrebro started on v3 at 06:58. It finishes on v3; the next run uses v4.
Every Monday at 07:00. Their 07:00.
One recurring schedule, resolved in each site’s own time zone. Nobody in London opens at six because head office is in Aarhus.
Weekly fire safetyMonday 2 NovemberPreview before saving
- Aarhus HavnCopenhagen time07:0006:00 UTCSara Holm
- Malmö TriangelnStockholm time07:0006:00 UTCPool: Malmö morning
- London Kings CrossLondon time07:0007:00 UTCPool: London crew
- Helsinki KamppiHelsinki time07:0005:00 UTCAino Virta
- + 304 more sites, each at its own 07:00
- Aimed, not copied
- Point one schedule at every site, a facility group, a facility type or a hand-picked list. See the coming runs before you save.
- The weeks ahead
- A horizon shows how many inspections fall on each day, so a busy Monday shows before it arrives.
- One calendar, many schedules
- Bind schedules to a shared calendar, so a change to it reaches all of them.
- A person or a pool
- Assign a named inspector, or a pool that anyone in it can claim from. A crew can share one run.
- Edit or halt
- Change a schedule going forward, or halt it while a site is closed.
Nobody sees a site until you say so.
Access starts closed. Arrange your sites in facility groups, nested however your organization actually runs, and grant a manager a group. Work assigned to someone directly is theirs to see without a grant.
Teams decide who does the work, never who sees a site. Putting Mette on the weekend team gives her runs to claim, not a single extra site.
- Nordbrød (demo organization)
- Denmark
- JyllandGranted
- Aarhus HavnVia Jylland
- Aalborg VestreVia Jylland
- Vejle TorvVia Jylland
- + 142 more sitesVia Jylland
- Sjælland
- NørrebroNot visible
- Roskilde BymidteOnly her assigned run
- JyllandGranted
- Abroad
- Sweden and Finland
- Malmö TriangelnNot visible
- Helsinki KamppiNot visible
- United Kingdom
- London Kings CrossNot visible
- Sweden and Finland
- + 157 more sites in other groupsNot visible
Six roles. Then fine-tune any one person: grant a permission, or take one away.
- Owner
- The account itself, and everything below.
- Admin
- Every site, every setting, the standards.
- Manager
- The sites they are granted, and their teams’ work there.
- Inspector
- The work assigned to them, and the sites they are granted.
- Translator
- Programs to translate. No sites, no records.
- Viewer
- Reads what they are granted. Changes nothing.
Nothing overdue goes quiet. Nothing we do goes unseen.
Deadlines that climb
For each severity you set how long a finding or work order may stay open, and when it turns due soon. Once it is overdue, it climbs.
- Level 1The manager of whoever has the workWhen the deadline passes, at once or after a grace you set.
- Level 2One level upEach time nobody acts within the wait you set, counted in the site’s opening hours.
- Level 3Every owner and adminThe last level. Nothing overdue goes quiet.
No manager covers the site? It goes to the escalation contact you name.
When we help, you see it.
If Fortia staff open your account to help, it is a session that lasts one hour, and every action in it is logged. Each session is listed for you under Account, Support access.
Fortia SupportTue 13 Oct10:02 – 11:02
2 changesEnded when the hour ran out
Demo entry
Your own team’s changes are in the audit log under Reports: who changed what and when, exported to CSV.
Also set from head office: a cost above which a work order waits for approval, in your currency; work orders with subtasks and planned maintenance; and parent and child organizations for a group that runs more than one business.
One standard. Every site. Your call.
Fortia is in early access. Send us one of your checklists and we’ll show it to you as a program, with its consequences written in.