AirOrchestra · a Torspan product
AirOrchestra — Safety paperworkThe foreman describes the day's work the way he'd describe it to his crew. What comes back is the pre-task plan for that work — the hazards he named, the actions that go with them, the tools, the crew listed, and each man's own acknowledgment with a time on it.
02 An empty screen is an honest screen. If nobody said what happened, the day stays blank and the app says so.
The GC closed the corridor for a pour at 11:52. The morning's plan describes work nobody is doing any more — and it is the only evidence of the morning, so it does not get touched.
Updated today's pre-task plan for RIVERBEND Building 2 — task: roof access door, exhaust chute. 1 plan on file for 08/18/26.
One plan, one job, one day. The record now says four men spent Tuesday on a roof. If somebody gets hurt in that corridor at 9:30, the only document for the day describes work nobody was doing — and the man who signed it is the one holding it.
Two plans, one day, two tasks — the afternoon plan went out when Ray said go at 12:04. One man has not tapped, and the screen says which one.
It can tell you who worked a day with no plan on record. It cannot tell you whether the plan that exists was any good.
Best practices is blank because nobody said one, and that blank is worth more than a printed line nobody meant. The morning's plan is still on the record with 6:04 on it, unedited.
Invented crew, invented job, invented building. Real records belong to the companies that made them, and those don't go on a website.
The foreman says what the work is, who's on it, and what else is going on around them. That's it — no field to land in, no hazard to pick off a list, no job to scroll to. The job and the date come off the day's dispatch, so nothing gets asked for that's already known.
Every man on the crew is named on the plan, and every man acknowledges it himself. An acknowledgment belongs to a person, not to a crew, so nobody taps for anybody.
The hazards on it are the ones that were named or that follow from the work described — hot work brings the fire watch, a basket brings the lanyard, a trade overhead brings the hard hat line. Nothing gets added because a template had a row for it.
Each man reads the plan and taps once. That tap is the acknowledgment, and it goes on the record with his name and the minute it happened.
Written in the order it happens on the job, not in the order the software does things.
6:41 — He describes the day. Standing at the gang box, one hand on a coffee. Typed with a thumb or dictated into the phone's own keyboard, in whatever language he thinks in, badly punctuated, with a glove on.
6:41 — It reads the day back to him. One plain paragraph, before anything is filed: the job, the level, the men, the work, the equipment, and what else is around them. If it heard the wrong level or the wrong man, he says so in the same conversation and the correction lands in the same turn.
6:42 — The plan renders. Same six sections every time, same layout every time, one page. A PDF goes into the job's file at the same moment.
6:43 — The poster goes on the box. Printed, or held up on a phone, or open on the iPad on the tailgate.
6:47 to 6:52 — Four men tap. Name and time on each one. Not a typed signature, not an initial in a box, not a sheet that gets carried around all day and put in a truck door.
All day — nothing gets silently rewritten. Work changes at noon, a new plan comes out for the new task and the old one stays exactly as it was, with its own acknowledgments on it.
Nothing below was typed into a form. The sentences are the whole input. The document is the whole output, at the size it prints.
4 sentences · 36 words
One plan, off one description, with the whole crew listed on it. Each man's own acknowledgment goes on it when he taps.
Best practices reads Not stated on this plan because Ray did not state one. A section nobody spoke to prints the line saying nobody spoke to it — on every plan, every day, including this one.
Invented crew, invented job, invented building.
| What happens | What the record does |
|---|---|
| Two jobs in one day | Two plans. Each with its own job, its own crew and its own acknowledgments. |
| A man shows up at ten | He is added to the plan when he's named — with his own acknowledgment at 10:15. It is not slipped in with a 6:43 on it. |
| The work changes after lunch | A new plan for the new task. The morning's plan stays on the record, unedited. |
| The same description sent twice | One plan. Not two. |
| Somebody says something that contradicts the dispatch | It names both and asks. It does not quietly pick the one it likes. |
3 of 4 acknowledged · you haven't yet
Acknowledged 6:52 AM · Aug 13
The count of who hasn't tapped is on the foreman's screen. It is not on anybody's scorecard, and it does not exist as a number about a man anywhere in the product.
Invented crew, invented job, invented building.
Most pre-task plans are a photocopy of a photocopy — eight-point type, a grid of boxes, and a signature line. Men sign them at the truck without reading them, and everybody involved knows it.
So this one is built to be read standing up, at arm's length, in a corridor with the lights not on yet. Six cards, big type, one page, the same six every single day so a man's eye knows where to go. The worst thing that can happen is in the largest type on the page, on its own, in red — because that is the line that changes what somebody does in the next ten minutes.
Hazards, actions and tools are tiles with a drawn icon on each one. A man who reads badly, or reads English badly, still gets the harness, the barricade and the fire watch off the picture. A plan that only works if you can read a paragraph is a plan that was written for a filing cabinet.
Before a plan counts, a person at Torspan reads it against what the foreman said and what the drawings and cut sheets say: every hazard on it traces to something said or something on a sheet, and no line stands in a man's name that he did not say. What does not trace is taken out before it counts. It comes out as a second version with a time on it; the plan the crew acknowledged stays as they acknowledged it.
If an icon is missing from the library, the plan does not render with a gap in it. It fails, loudly, and somebody fixes it before a crew ever sees it.
The plan prints on one page and binds flat in a book. The PDF is the same document as the poster — not a stripped-down version of it, not a data export with the design taken off. What went on the gang box in August is what comes out of the file in February.
This is the part that decides whether any of the rest is worth having.
A machine that fills in the missing morning produces a safety file with no holes in it — and a safety file with no holes in it, made by a machine, is worth exactly nothing to the man who has to stand behind it. Every plan in it is a guess wearing a date.
So when nobody described the day, no plan gets made. The day stays empty, and the empty day is put in front of somebody, by name, with the job and the date on it.
Ask it directly to write up a day that's already gone and it will, off the pattern of the days around it. That plan is marked in the record as patterned rather than reported — a field in the database, and the screen says so. The paper does not, on purpose: a filled-in plan prints identical to one written at the gang box, so nobody is handed a document with two classes of page in it. Every one of them can be found and pulled in a single pass. It never does this on its own — not overnight, not to make a screen look finished, not ever.
Nobody described this day. No plan was made.
Messages and photos came in on those days, so somebody was on that job. That is the whole test, and it is why a missing plan cannot hide.
Invented crew, invented jobs, invented dates.
One plan, opened up. This is the block the office asks about and the block that matters in November.
Invented crew, invented job, invented file name.
The Source line is the whole argument. It is the foreman's own sentence, stored exactly as he sent it, in the language he sent it in — and the plan points back at it. Six months from now the conversation is about what a man actually said on a Tuesday morning, not about what a piece of software decided he meant.
Nothing on the job is deleted when the job closes. The plans, the acknowledgments and the sentences underneath them come out any day you want them, as PDFs and as a file that opens without AirOrchestra. → Your records
The complete list, including the things people ask for and won't get. → What it won't do
Washington already requires a written accident prevention program, and crew-leader safety meetings at the start of a job and every week after that, with the attendance and the subjects written down and the minutes held a year. Federal rule requires that each man be instructed in recognizing and avoiding the hazards of the work he is doing.
This makes the pre-task plan out of what the crew already said, keeps it for the life of the job and after it, and hands it over any day you ask. It does not certify anything, and no software can.
OSHA maximum penalties assessed after Jan 15, 2026: $16,550 per serious violation · $16,550 per day for failure to abate · $165,514 per willful or repeated violation. Source: osha.gov/penalties.
The exact words on the screen when a day is empty, a man taps late, or a plan was reconstructed. These are product strings, not marketing.
| Where | What it says |
|---|---|
| Day nobody described at all | Nobody described this day. No plan was made. |
| Plan made, not everyone has tapped — shown as a gap, never as a zero | 3 of 4 acknowledged · Dee W. hasn't yet |
| Man added after the morning batch | Dee W. joined at 10:15. He was added to the plan then. |
| Plan the system was asked to reconstruct | Patterned from Aug 11. Not reported. |
| Job with no safety documents at all | No safety documents on this job yet. |
| Description too thin to make a plan from | Not enough here to make a plan — what's the work, and who's on it? |
| Acknowledgment confirmed | Acknowledged 6:52 AM · Aug 13 |
| Missing-plan list, empty | Every day with work reported on it has a plan. |
Invented crew, invented job, invented building. Real records belong to the companies that made them, and those don't go on a website.
The exact words a foreman can say to six guys on Monday morning, written out so he doesn't have to invent them. → For foremen
Who can see a plan, how long it's kept, how all of it comes back out, and what happens to the file if Torspan stops. → Your records
AirOrchestra