AirOrchestra
AirOrchestra · a Torspan product
AirOrchestra — How it worksSay it once. It lands everywhere it belongs.
Your crew writes to AirOrchestra in the app's messenger the way they already text — a sentence, a photo, a question — from the phone in their pocket. It reads what they sent against the job's documents: the drawings, the cut sheets, the dispatch. It writes the pre-task plan and the daily report, files each photo to the job it came from, and answers a question from the sheet it read, naming the sheet and the revision. Where nobody said something, the line is blank and says so. The reading and the writing are done by AI. The checking is done by a person: nothing counts as the record until a person at Torspan has read it.
01 Nothing is invented. A fact in the record came from a person or a document. The machine does not fill a gap with something plausible.
The whole thing, in three moves
A man says what happened. It repeats back what it took him to mean. Then it writes the records that sentence contained. That is the product. Everything below this is detail.
Twelve seconds of talking at the gang box. Nobody picked a job from a list, nobody chose a hazard from a dropdown, and nobody typed a name.
Invented crew, invented job, invented building. Real records belong to the companies that made them, and those don't go on a website.
It tells you what it heard, before it writes anything
Every reply starts the same way: one plain paragraph saying what it took you to mean. That paragraph comes back before a single record is filed.
It is not politeness. It is the receipt. If it heard the wrong level, the wrong man, the wrong job — you say so in the same conversation, in your own words, and the correction lands in the same turn. No screen to go find. No record to open and edit.
There is no reply YES to confirm. A confirmation step is a form with extra steps.
The message you sent is kept exactly as you sent it, in the language you sent it in. The record points back at it. When a man says a week later that the record is wrong, the argument is about what he said on Tuesday — not about what the software decided.
One way in. Six places it can land.
There is one way into this system and it is a message. Typed, or dictated with the phone's own keyboard, or up to ten photos, in English or Spanish or Russian, badly punctuated, with a glove on. What comes out the other side is not one document. It is every record that sentence contained.
| What lands | What comes out of it | Who reaches for it |
|---|---|---|
| Messages | The record of what was said, verbatim, in the language it was written in, with who said it | Everybody on the job |
| Documents | The drawings, cut sheets and dispatch, read — and named, by sheet, when they have not been | The man on the lift with a question |
| Photos | The photo under the right job, with the date and the man on it | Anybody who has to show what was there before it got covered |
| Safety paperwork | The pre-task plan for the jobsite, with the crew on it, and each man's acknowledgment with a time on it | The foreman at 6:40, the owner in November |
| The daily report | One current write-up of the day, rewritten in full each time it learns more | The GC, the owner, the file |
| Answers off the prints | The answer with the sheet, the revision and the date under it — or the name of the sheet it hasn't read | The crew |
Nothing on this list is a separate app, a separate login, or a separate thing to remember. They are lanes the same message runs into.
One sentence usually lands in more than one of these at once. "North corridor's topped out, we started the shaft, and the drywall crew's in the mechanical room Monday." That is the day's account and the crew line on Monday's pre-task plan, out of seventeen words on the walk to the truck.
A day, start to close
Invented crew, invented job, invented building. This is the shape of the machine over ten hours.
| Time | The man does this | The record does this |
|---|---|---|
| 6:10 | Talks for twelve seconds at the gang box. | The pre-task plan. Crew on the job. |
| 6:14 | Four men read a poster and tap once. | Four acknowledgments, each with a name and a time on it. |
| 7:22 | The newest man on the crew shoots two photos of the hangers he just set: "north corridor, first six done." | Both land under Riverbend Building 2, dated today, with his name and his words on them. Nobody tagged anything. |
| 9:05 | A man on a lift, thumb-types: "what's the drop size on the north side" | The answer comes back with the sheet under it — M-402, Rev C, dated, sheet note 4. He never came down the ladder. |
| 3:20 | Seventeen words on the walk to the truck. | The day written up whole. |
| 3:24 | Reads one paragraph. Puts the phone in his pocket. | That paragraph is the receipt. If it's wrong he says so and it's fixed before he's out of the parking lot. |
Nothing in that day required anyone to open a form, start a timer, or write a report.
When it can't tell, it files nothing
This is the part that decides whether the rest is worth anything.
A photo arrives with no words on it, and the man was on two jobs that day. The words say the shaft; the schedule says the other building. Two sheets disagree about the same detail. A machine that guesses well is still a machine that guesses, and a record with a good guess in it is a record you cannot hand anybody.
So it doesn't. It files the photo nowhere, names both jobs, and says so. It answers with both sheets and their revisions instead of picking the likelier one. And when nobody described a day at all, the day stays empty and says so — it does not write work continued over a silence.
The gap is the feature. A record you can hand to somebody is one where the blanks are real blanks.
Then it leaves the field
The crew's half of this ends when a man puts his phone in his pocket. The office's half starts on its own.
The day is written up once and rewritten in full every time it learns something new — not appended to, not stacked into three fragments that argue with each other. Tell it more at noon and again at four and what you have at five is one current account of the day, with the photos and the answered questions folded into it.
The answer to how does the office get the day is a PDF, not a login. It is made from what the crew said, and it opens without AirOrchestra.
The whole job comes out as a PDF — the days, the photos, the pre-task plans and who acknowledged them, the questions and their answers. That is the thing you forward when somebody asks, and the thing that makes them stop asking. It is made when somebody asks for it.
The office side gets its own page, including the parts it stays out of — no accounting, no invoicing, no job costing. → The daily report
What nobody has to do
Most field software fails in the same place, and it is not where the vendor thinks. It fails at the moment it asks the crew to do new work so the office gets a better report. Under a deadline, a man goes back to the fastest thing he knows — a text to the foreman, or a note on the dash — and the record fills up with holes.
So the list of what this asks the crew to learn is empty, and here it is in full.
Nobody has to be talked into using it, which means nobody has to be the one doing the talking into.
- No form. Not an easy form, not a short form, not a smart form. None.
- No tagging. Not photos, not jobs, not people, not dates.
- No timer to start and no shift to clock into.
- No second app to open. The messenger is the app. He is already in it.
- No training day. If a man can send a text to his foreman, he is done learning this.
- No English required. Write it in the language you think in. The record keeps your words as you wrote them.
What it won't do
- It does not record. No calls, no site walks, no background listening. Every word in the record is something a person chose to write or say into it.
- It does not write a day nobody described. Not from movement, not from app activity, not overnight, not ever.
- It does not sign in anybody's name, and it does not decide. Where it is not sure, it leaves the line blank and asks. A person's name goes on a document when the person puts it there.
- It does not know your job from the outside. It knows what your crew said and what is in your documents. Where neither one covers it, it says so instead of reasoning around the gap.
The complete list, including the things people wish it did. → What it won't do
What it says when there's nothing to say
The exact words on the screen when a day is empty, a photo can't be placed, or a sheet hasn't been read. These are product strings, not marketing.
| Where | What it says |
|---|---|
| Day with nothing reported | Nobody described this day. It's blank until somebody does. |
| Photo it couldn't place | Not filed. Two jobs named — pick one or ask him. |
| Question asked about an unread sheet | M-403 is on this job but I haven't read it. That's the one your question is about. |
| Job with no documents at all | This job has no documents in it yet. I'm not going to answer from anywhere else. |
| A message it couldn't follow | I couldn't follow that one — say it again another way. |
See it work.
Start with the most ordinary thing it makes, and the one your office will test first. → The daily report
All of that assumes it actually read your prints. When it hasn't read the sheet your question is about, it says so and names the sheet. → What it says when it hasn't read the sheet