Torspan
AirOrchestra · a Torspan product
AirOrchestra — for foremenYour night ends when you shut the truck door.
You said one sentence on the walk to the truck. That closed the hours for four men, wrote the day up, put tomorrow's plan on tomorrow, and put the lift return on Friday. There is nothing waiting for you at nine o'clock.
08 It shows you the bubble. You call it. An instrument does not overrule the man holding it.
Before the ceiling closes.
The GC is closing the corridor ceiling on Friday. Five things are still open above it. Two of them are open because a question got asked twice and nobody ever came back — and an absence is not something you can look up.
| Item | Where it is | Waiting on |
|---|---|---|
| Condensate trap, FCU-14Your own message, Mon 4:06 PM | Room 412 — set, levelled, trap off | The invert at the tie-in. Asked twice, no answer |
| VAV-22 inlet sizeRFI, day three | East corridor — tap not cut | The engineer. Ball in his court |
| Trunk, C-8 to C-11M-501 Rev C, detail 4 | East corridor — hung to C-8 | Nobody. This one is yours |
| Pressure class, corridor trunkM-601 Rev B and Rev C | Two revisions, both in the job | Somebody to say which sheet is current |
| Access door, FSD-L4.6Not on M-402, not on M-501 | Stack 14 — nobody drew it | Nobody. This one is yours too |
Three of these five came off paper. One is a sentence you said. One is on this list because nothing came back.
5 open
2 crew
3 waiting on somebody else
Both are his own words, character for character. Nothing came back in any thread on this job.
Same trunk, same line on the same schedule, two revisions in the job. What the numbers are matters less than the fact that they differ and nothing on the job says which one governs.
Declaring which sheet is current from the field is on our year. Until then the machine asks, and the record keeps the name of whoever answers.
It can run the leakage arithmetic — that formula is public. It declines, because the input would be a guess. A machine that can compute and chooses not to is worth more to you at 2:12 on a Wednesday than one that always has a number.
Invented crew, invented job, invented building — Ray D., Marco A., Dee W., Tomas R., RIVERBEND Building 2. Real records belong to the companies that made them, and those don't go on a website.
Ordering tonight.
One sentence on the walk to the truck, and five records have to be held at once before a single line can be written: what is already staged on the job, what the submittal came back at, what the drawing still says, what came off last week's truck, and which of two vendors he means.
One soft limit and one hard limit on the same piece of paper. That is engineered behaviour, not a machine being careful.
A receipt that stops mid-page does not become a whole delivery because the part you can read adds up. What is on the paper is eight, so the record says eight.
The channel line reads 10 because Ray said 10, in the message above, at 3:53. It does not read 10 because the machine thought 40 was too many. That distinction is the whole product.
Invented crew, invented job, invented building.
Six more he asks.
The line under each one isn't the answer. It's what has to be held at once before there is an answer.
who has no plan today
Who worked, from time entries, against who has a form, from safety forms. Two record sets that never meet.
we good on 12 inch for monday
Ordered, delivered, installed, held and Monday's plan — five records by four men on five days.
did the office ever answer my rfi on the vav inlet
Ball-in-court and days open, computed on the server rather than off anybody's calendar.
whats on m601 rev c that isnt on rev b for the corridor
Two revisions of one schedule, compared line by line — not revision to revision.
did dee or marco ever put eyes on the l5 stage
Whether a question relayed into another man's thread ever came back.
what did i promise casey in june that i havent got in writing
Eight weeks of his own messages, against every RFI, ASI and bulletin on the job.
You've been handed an app before.
You know how it went. Somebody in the office picked it. It asked your men to do something extra so the office could have a report. For two weeks they did it. Then a Thursday got tight, and men do what's fastest when a Thursday gets tight — they texted you, or wrote it on the back of a cut sheet. The reports went half empty, the office decided the field wasn't cooperating, and the conversation that followed was about you.
That chain breaks in one place, and it isn't training.
The crew is not asked to do anything it wasn't doing already. A man says what he did, the way he'd say it to you. That's the whole ask, and it's an ask he's been answering for twenty years.
There is no form. Not a short form, not a smart form — none. No cost code to pick off a list, no dropdown, no required field, no timer to start, no shift to clock into, no tagging step, no second app to open. Nothing on the crew's phone has a submit button on it.
Which means there is nothing here for you to enforce. That is not a promise about how easy it is. It's a description of what's missing.
The ninety seconds.
This is the whole rollout. You say it once, at the gang box, Monday morning. It's written to be said out loud by a man holding a coffee, and it's short enough that you won't have to look at your phone while you say it.
Take it and change it. It's yours.
Starting Monday we've got a new thing on our phones. Here's all of it.
End of the day, tell it what you did. Same way you'd tell me. "Eight hours, north corridor, got six hangers set." That's it. That's your time.
Pictures go to it instead of the group text. It puts them on the right job with the date on them. You don't tag anything.
You need something off the print — a size, a detail — ask it. It gives you the sheet and the revision it came off. If it hasn't read that sheet, it says so instead of making something up.
Anything you'd normally walk over and ask me, ask it. It puts it on my list with your name and your words, and I answer it.
It doesn't know where you are. No GPS, no map, no clocking in. There's no score on anybody and no list of who did more.
Write it in whatever language you write in.
And if you'd rather just tell me and let me put it in — do that. That still works.
That's it. Nothing to fill out.
New app starting Monday — it's just messaging. End of the day tell it your hours and what you got done, same as you'd text me. Photos go there instead of here. Need something off the print, ask it. No GPS, no score, nothing to fill out. Any language. Questions, ask me.
Nobody has to sign in during that ninety seconds. Nobody has to download anything while you're standing there. If a man has a question, it's the one you'd expect — so what happens if I forget — and the answer is the next section.
The man who doesn't say anything.
He will. Somebody's phone dies, somebody's kid is sick, somebody just goes home. Here is exactly what happens, because this is the part that decides whether you end up being the enforcer anyway.
His day stays blank. No hours are invented for him. Nothing is averaged from Tuesday. A day nobody described is a day with nothing in it, and the app says that in plain words instead of quietly filling it.
The blank is on your week, not on his record. You see the gap where the hours would be. He doesn't get a warning, a flag, a strike, or a red cell. There is nothing to appeal because there is nothing against him.
Nobody upstairs is told. No report goes out saying who's behind. No adoption number exists. The office sees the records that exist; it is not handed a list of the men who were quiet.
You can close it in one sentence. "Tomas had eight yesterday." That's another man's hours — you can give them, out loud, and the entry will say it came from you.
Or leave it. A gap you know about is not a problem. A guessed number is. The record is more useful to you empty and honest than full and wrong, because the day somebody argues about an hour, the only thing worth having is what a man actually said.
There is no mechanism in this product for it to nag your crew, and no mechanism for it to report on them to anybody. That isn't a setting you turn off. It was never built.
The morning, before the lift goes up.
Twelve seconds at the gang box — the job, the level, who's with you, what you're hanging, what equipment, what else is going on around you. What comes back is a pre-task plan for every man on the crew, one per man, each with his own name on it and the whole crew listed, and each one signed by the man it belongs to with a time on it.
You are not writing it at 6:55 while you're also trying to get a lift moved. You're describing the day, which you were going to do anyway, standing in front of the men you were going to describe it to.
The document, at the size it prints, and the four sentences it came out of → Safety paperwork
Another man's hours.
You can give them, out loud, in one sentence, for the whole crew at once. There are rules on it, and the rules are what make the entry worth anything later.
You name him. The man has to be named in your own words — "six for Tomas" — and the name is matched against your stored message on the server before anything is written. It won't fill in a man you didn't mention.
It has to be a man you can report for. Somebody else's hand on somebody else's crew is refused, by name, in the reply. It doesn't half-write it and tell you later.
The entry carries your sentence. Every row says who submitted it, when, and the exact words it came from. Including yours.
Saying it twice changes nothing. Re-send the same message, correct yourself, sweep the whole week on Friday — no duplicate hours. The row is keyed to the message it came from.
"Same as yesterday" is allowed. It resolves it against yesterday's row and repeats the number back to you before it writes, so you can catch it in the same breath.
The day a man disputes an hour, the entry shows his own words or yours, with the time on it. The argument is between two people about what was said — not between a man and a piece of software about what it decided.
What's in an hours record and how long it's kept → Hours
What you open in the truck.
One screen. It's already assembled when you get to it, because it was assembled out of what your crew said during the day. You did not build it and you can't be behind on it.
Dispatched: Ray D., Marco A., Dee W., Tomas R.
North corridor supply duct, level 3. Boom lift. Hot work at the shaft after lunch.
Published yesterday 3:41 PM
| Man | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| Ray D. | 8.0 | 9.5 | – | 8.0 | – |
| Marco A. | 8.0 | 9.5 | – | 8.0 | – |
| Dee W. | 8.0 | 8.0 | – | 8.0 | – |
| Tomas R. | 8.0 | — nothing said | – | 6.0 | – |
Nobody said anything about Wednesday at all, and nobody said anything about Tomas on Tuesday. You can say it for them, or leave it blank. Friday hasn't happened yet.
If one is unsigned the row reads Not signed yet · made 6:43 AM and nothing else. No red, no exclamation, no count of misses.
Nothing goes out on its own.
AHU-3 set · VAV-22 hung.
Forward only. A hold is a proposal with somebody's name on it, never a state the app entered by itself.
North corridor supply duct topped out on level 3; the shaft was started after lunch. Four hands on site. Two photos and one answered question are in the day. The lift goes back Friday.
Rewritten whole every time it learns something, not stacked in fragments.
Everything on that screen came from a sentence somebody sent. There is no field on it you have to complete, and nothing on it turns a colour to make you deal with it.
Blank because it's blank. Not because it's loading, and not because somebody forgot to look.
Invented crew, invented job, invented building.
The question that used to be a phone call.
A man on a lift needs a drop size. Two things can happen now. He asks the app and gets the answer with the sheet number, the revision and the date it came off — no call, no climbing down. Or the question is genuinely yours, and it lands on your list with his name and his exact words on it, and you answer it at lunch from your phone.
M-402 · Rev C · issued Jun 11 · sheet note 4 · Riverbend Bldg 2. If it hadn't read that sheet it would say so instead of answering.
Answered by Ray D., 12:58 PM. It never writes as him and it never signs as him.
He gets your answer back in his own thread. It arrives in the app's own voice, saying you're the one who said it. It never writes as you and it never signs as you. Nothing goes out over your name that you didn't say.
What an answer looks like, and what it says when it hasn't read the sheet → Answers off the prints
Invented crew, invented job, invented building. Real records belong to the companies that made them, and those don't go on a website.
What the office can see about you.
You're going to be the one holding this thing, so here is what it reports.
| The office sees | The office does not get |
|---|---|
| The hours, with who submitted each one — including the ones you submitted | Any number about you. There is no per-man figure and no per-crew figure in this product |
| The day's account, the photos, the plans and who signed them | Any ranking of foremen, crews, or jobs against each other |
| The questions and how long they sat open | A location, a route, a map, or a time you arrived anywhere |
| The week's hours as a file, pulled when somebody asks for it — a weekly pack, and anything that leaves on a schedule, are on our year | An adoption report, a usage percentage, or a list of who didn't post |
The first column exists on purpose, and it's the same rule that protects you: every line says where it came from. When somebody in November asks what happened on level 3 on the 14th, the answer has your men's own words attached to it, with times. You are not reconstructing a Tuesday from memory in front of a GC.
What it won't do.
- It doesn't assign work, build a schedule, or tell you where to put anybody. Running the crew is not a thing it has an opinion about.
- It doesn't score your men and it doesn't score you. No ranking, no leaderboard, no productivity number, no adoption percentage.
- It doesn't know where anyone is. No GPS, no geofence, no clock-in radius, no idle detection.
- It never creates hours on its own. Not from a schedule, not from a pattern, not overnight.
- It doesn't approve hours, sign a plan, or send an order. It drafts and it hands it to a person.
- It doesn't listen. No calls recorded, no background transcription, no site walk picked up because a phone was in a pocket. Every word in the record is something a person chose to say into it.
- It doesn't invent a day. Where nobody said it, it's blank — and it says so.
The full list, and what's live today → What it won't do
What comes off your week.
- The daily at nine at night, after a twelve-hour day.
- Friday afternoon reconstructing Tuesday out of a text thread and four men's memories.
- Re-typing your crew's hours into the office's system, or photographing a legal pad and hoping.
- The pre-task pad at 6:55 with one hand while you're on the phone about a lift.
- Digging for the photo of the hangers on the north corridor from October.
- The forty-five minute call explaining a time card to somebody who wasn't there.
None of that is your trade. It's the second shift that got attached to it.
What the last rollout actually cost you.
The real cost of the last rollout wasn't the hour it added to your night. It was that it turned you into the guy who nags his crew about an app. You spend something every time you do that, and it comes out of the same account you need on Monday when you ask four men to stay two more hours in a hot mechanical room.
There is nothing here to nag anybody about. You get your standing back, and you go back to being the man who runs the job.
See it work.
The page your crew should read before Monday, written for them and not about them → For crews
The document that shows up at the gang box, at the size it prints → Safety paperwork