AirOrchestra
AirOrchestra · a Torspan product
AirOrchestra — The daily reportThe daily report is already written.
It is made out of what the crew already said, on the day it was said. The GC gets the days as a PDF, with the photos in them, pulled when somebody asks. Nobody has to have an account here, nobody has anything to learn, and nobody keys a week off a photo of a legal pad.
09 The records are yours and they leave with you. Any day, whole, in files that open without us.
What it does
- It writes the day up once and keeps it current. One account of Thursday, not a nine o'clock note, a noon note and a four o'clock note for somebody to reconcile in November.
- It puts each day in a PDF per job — what the crew said got done, the photos, the pre-task plans and who acknowledged them, the questions and their answers. Pulled when somebody asks for it.
- A person at Torspan reads it before it counts. If a line does not trace to something the crew said, it comes out before your office sees it.
- It leaves the quiet days quiet. A day nobody described comes out blank and named as blank. Silence does not turn into “work continued.”
How it works
Three steps, in the order they happen on the job.
The crew says the day, the way it already does.
Typed with a thumb, or dictated into the phone's own keyboard. Nobody opens a report. There is no report to open.
The account gets written, and rewritten.
The first thing anybody says about a day starts it. Everything said afterward rewrites the whole thing, so what exists at any minute is one current account — with that day's work, that day's photos and that day's answered questions folded in where they belong.
A person at Torspan reads it.
Before the report counts, somebody here reads it against what the crew said. What does not trace comes out.
Nowhere in those three steps does a person open a screen and fill it in. Everything after step 1 happens to a record that already exists because somebody talked.
The day gets rewritten, not added to
This is the part that behaves differently from what an office expects, so it is worth a paragraph rather than a bullet.
Most systems accumulate. You get an entry from nine in the morning, another from noon, another at quitting time, and by Friday somebody has three partial versions of Wednesday and the job of deciding which one is true. A record that accumulates is a record somebody reconciles later, and later is always somebody in an office with less information than the man who was there.
Here the account is rewritten whole every time it changes. Tell it more at noon and you do not get a second paragraph appended under the first — you get Wednesday, rewritten, as it now stands. What the office opens on Friday is one story, current as of the last thing anybody said.
Two men remembering it differently is not a conflict to resolve. If Marco says the north corridor topped out and Dee says it did not, the account carries both, with a name on each. It does not average them, it does not pick the one that came in last, and it does not quietly drop one. Two attributed sentences is an honest Wednesday. One smoothed-over sentence is a guess with nobody's name on it.
See the two earlier versions See what changed
North corridor. Marco A. reported it topped out at 2:15. Dee W. reported two joints still open at the corridor end at 3:02. Both are below, in their own words.
Shaft started at the second-floor landing. The AHU-3 curb is clear and the opening is framed.
FCU-14 rough-in on the east side is waiting on the revision to M-501. The boom lift stays through Friday.
MARCO A., 2:15 PM
“north corridor's topped out”
DEE W., 3:02 PM
“still two joints open at the corridor end”
Both lines are in the report. Neither one was chosen over the other by anything that was not standing there. Invented crew, invented job, invented sheet number.
Three versions of Wednesday is not a record. It is three people's Wednesdays and a job for whoever has to pick one.
When the GC has his own system
On plenty of jobs the GC runs Procore, or Autodesk Build, or Fieldwire, and the sub's daily report is expected to be typed into it. That is the reader's life and it is worth answering plainly instead of pretending it away.
Nothing here writes into any of them. There is no push, no sync, and no plugin.
What changes is what the person doing the typing is working from. Right now he is working from memory, four days late, at nine at night, and what he produces is the reason a GC's daily log for a sub is usually three lines long. With this, the day is already written, with the photos already on the right day and the men's own words already on the work. Whoever pastes it into the GC's system is reading, not remembering — and the version that goes into the GC's system says the same thing as the version in your own file, which is the part that matters the week somebody pulls both.
And your copy is yours. A record that lives only inside the GC's account is a record you stop having on the day the job closes out and your access goes away. This one is on your side of the line, whole, for as long as you keep it.
Who owns the record, and what happens if the company stops. → Your records
What it says when there's nothing to send
The words the product actually uses. Not a friendlier version written for a website.
| Where | What it says |
|---|---|
| A day in the week nobody described | Wed, Aug 12 — nothing reported. Blank. |
| Correction after a file was sent | That file was made Aug 15, 6:40 AM. Making a new one — the old one stays as it was. |
| Two men describing the same day differently | Two accounts of Thursday. Both are in the report, with names on them. |
| A whole week with nothing reported | Nothing was reported this week. There's no report to make. |
| Report pulled while documents are still being read | Three documents on this job haven't been read yet. They're not in this report. |
| Export requested for a job the person can't see | That job isn't yours to pull. |
Every one of those is the alternative to a file that looks complete and isn't.
What it won't do
It is not accounting. No invoicing, no AP, no AR, no general ledger, no WIP, no over/under billing, no payment applications, no checks.
No job costing and no estimating. It writes down what happened. What it cost, and whether the job is making money, is the office's system and the office's job.
No scheduling, no project management, no submittal log. It does not run the job. It writes down what happened on it.
No connector to any accounting or payroll system. Keep whatever you run the office on; this is the jobsite's paperwork.
No certified payroll, no intents and affidavits, no prevailing wage determinations, no fringe calculations, no OSHA log. Those are filings with rules of their own and they are not made here.
No labor productivity report about a man. No utilization, no units per hour, no ranking of crews, no profitability by person. There is no screen that puts two men's numbers side by side.
No live dashboard. Nothing here is built to be left open on a monitor in an office so somebody can watch a jobsite all afternoon.
The complete list, including the things people wish it did. → What it won't do
What it takes off Friday
Not the craft. The second shift after the real one, and the office's version of the same shift.
- The Sunday-night daily log, written from memory four days late, by a man who has been awake since four-thirty five days running.
- The office keying a week off a photo of a legal pad, and calling three people to ask what a word says.
- The forty-five-minute phone call in October to reconstruct a Tuesday in August, which produces an answer nobody would want to defend.
- The GC's Thursday email — who was on level 3 on the 13th, what did you find, do you have a photo — answered by forwarding something that already exists.
- The second entry. The foreman writes the day in one system and somebody in an office writes the same day again in another one. That is the task this page exists to delete.
How long it has to last
The file is not finished when the job is finished. Somebody comes back for it, and it is usually somebody with a lawyer, years after the last man left the building.
| What the rule says | Where it says it | What that means for a report you pull |
|---|---|---|
| Contractors shall make records available “3 years after final payment” | FAR 4.703(a)(1) | On federal work, the report made in August 2026 can be asked for well into 2030 |
| “Each contractor, subcontractor, or employer shall keep accurate payroll records for three years from the date of acceptance of the public works project by the contract awarding agency” | WAC 296-127-320 | On public work in Washington, for example, the clock starts at acceptance, not at the payroll date — which is usually much later than people assume |
What is kept here: the files that were made and their as-of stamps, the account each one was made from, and the messages the lines came out of. Not a summary of them. The actual sentences, with the men's names and the minutes on them.
And all of it comes out any day, whole, in files that open without this software — which is the point of the whole arrangement and is written out in full one page over.
This is not a compliance product and it does not certify anything. It states the standard, states what the record contains, and states how long it is kept. Whether a business meets a rule is between that business, its lawyer and the agency asking. → Your records
See it work.
Everything on this page was made on a phone, by men who never opened a report screen. → The app
The office's next question is what it costs. The shape of that is on the page, and the figure comes in writing when you ask. → What it costs