Say it once. It lands everywhere it belongs.
One message from the job becomes the hours, the photo filed to the right job, the pre-task plan, tomorrow's plan, the material order and the question on your list — and nobody opened a form, because there isn't one.
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 sheet numbers — on this page and every screen below it. Nothing here is a real jobsite, a real person or a real building.
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 hours are wrong, the argument is about what he said on Tuesday — not about what the software decided.
One way in. Ten places it can land.
There is one way into this system and it is a message. Text, or hold the button and talk, 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 |
|---|---|---|
| Hours | Time entries — person, date, job, hours — each carrying the sentence it came from | The office, on Friday |
| 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, one per man, and each man's acknowledgement with a time on it | The foreman at 6:40, the owner in November |
| Day plans | Tomorrow's plan, published to tomorrow, with the job's weather on it | The crew, before they leave the house |
| Work reports | Discrete installed items, located — the thing you count | The PM |
| The day's account | One current write-up of the day, rewritten in full each time it learns more | The GC, the owner, the file |
| Questions for the foreman | An item on his list with the man's name and his exact words, and a status | The foreman, at lunch |
| Materials and deliveries | A draft order — job, item, quantity, vendor, needed-by — waiting for a person to send it | Whoever orders |
| Equipment progress | Forward status on a unit. It cannot walk one backwards, and it cannot put one on hold | The PM, the super |
| A word to another man | Carried into his own thread, in the app's voice, never signed as you | 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 three or four of these at once. "Eight for me, Marco and Dee, six for Tomas — he left at one. North corridor's topped out, we started the shaft. Lift goes back Friday." That is four time entries, the day's account, and Friday's plan, out of twenty-two words on the walk to the truck.
A day, start to close
Invented crew, invented job. This is the shape of the machine over ten hours.
| Time | The man does this | The record does this |
|---|---|---|
| 4:58 | Phone buzzes once. He doesn't touch it. | Tomorrow's plan, published yesterday when Marco said the lift was booked, is now today's plan. Weather for the job is on it. |
| 5:30 | Opens the app in the truck, one hand, coffee in the other. | Today: who's dispatched, what's planned, three questions still open from Friday, two deliveries due, the sheets that changed since Friday. |
| 6:10 | Talks for twelve seconds at the gang box. | Four pre-task plans, one per man. Day plan. Crew on the job. |
| 6:14 | Four men read a poster and tap once. | Four acknowledgements, each with a name and a time on it. |
| 7:22 | Apprentice 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 | Journeyman 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. |
| 11:40 | "Need 40 more 24-gauge hangers by Thursday, north side." | A draft order, filled in, sitting there waiting for a person to send it. |
| 12:30 | Apprentice: "ask Ray if we're tying into the existing at the shaft." | On the foreman's list, with his name and his exact words. Answered from a phone at lunch; the answer goes back into the apprentice's own thread. |
| 2:15 | "AHU-3 is set, VAV-22 and FCU-14 hung." | Equipment progress moves forward. It does not move back, and nothing goes on hold without a person saying so. |
| 3:20 | Twenty-two words on the walk to the truck. | Four time entries. The day written up whole. Friday's lift return published to Friday. |
| 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. |
| 4:00 | The office does not call anybody. | The week's hours are in a file shaped the way the bookkeeper keys them. |
| 9:40 pm | Nobody is awake. | Every document that came in today gets read tonight and is searchable in the morning. Anything it couldn't resolve is sitting in one list, waiting to be asked about. |
Nothing in that day required anyone to open a form, start a timer, pick a cost code, or write a report.
When it can't tell, it files nothing
This is the part worth reading twice, because it 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 puts one item in front of a person who knows. 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.
Frame drawn, not a photo
Ask him
Two answers on the screen and neither one chosen. That is not a bug in the demo. Both job names are invented, like everything else on this page.
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 work items, the photos and the answered questions folded into it.
The hours come out as a file: person, date, job, hours, the cost code if one was recorded, the sentence each entry came from, and who submitted it. Columns get set once by whoever keys them and then never move again. Weekly, by mail from the app, or pulled off a desktop whenever somebody wants it.
The answer to how do the hours get into my system is a file, not a connector. The file is named, the columns are yours, and it opens without AirOrchestra.
Once a week the whole job comes out as one PDF — the days, the work items, the photos, the safety plans and who signed them, the questions and their answers, the hours. That is the thing you forward when somebody asks, and the thing that makes them stop asking.
| Person | Date | Job | Hours | Cost code | Source | Submitted by |
|---|---|---|---|---|---|---|
| Ray D. | 2026-08-12 | Riverbend Bldg 2 | 8.0 | — | "Full day for all four on level 3, north corridor…" | Ray D. |
| Marco A. | 2026-08-12 | Riverbend Bldg 2 | 8.0 | — | "Full day for all four on level 3, north corridor…" | Ray D. |
| Dee W. | 2026-08-12 | Riverbend Bldg 2 | 8.0 | — | "Full day for all four on level 3, north corridor…" | Ray D. |
| Tomas R. | 2026-08-12 | Riverbend Bldg 2 | 8.0 | — | "Full day for all four on level 3, north corridor…" | Ray D. |
| Ray D. | 2026-08-13 | Riverbend Bldg 2 | 8.0 | SM-100 | "8 for me, Marco and Dee. 6 for Tomas, he left at 1…" | Ray D. |
| Marco A. | 2026-08-13 | Riverbend Bldg 2 | 8.0 | SM-100 | "8 for me, Marco and Dee. 6 for Tomas, he left at 1…" | Ray D. |
| Dee W. | 2026-08-13 | Riverbend Bldg 2 | 8.0 | SM-100 | "8 for me, Marco and Dee. 6 for Tomas, he left at 1…" | Ray D. |
| Tomas R. | 2026-08-13 | Riverbend Bldg 2 | 6.0 | SM-100 | "…6 for Tomas, he left at 1." | Ray D. |
The column on the right is the sentence the row came from. It is in the file, not just on the screen. Invented crew, invented job, invented cost code.
The office side gets its own page, including the parts it stays out of — no accounting, no invoicing, no job costing. → Reports and the office
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 cost code to pick. No dropdown, no job list to scroll, no required field.
- 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 create hours. Not from movement, not from app activity, not overnight, not ever. A man's pay is not a machine's guess.
- It does not sign, approve, or send. It drafts the order and waits. It proposes the hold and waits. 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. |
| Foreman's week, hours missing for a man — shown as a gap, never as a zero | Tomas — no hours submitted Tue, Wed. |
| Photo it couldn't place | Not filed. Two jobs named — pick one or ask him. |
| Question asked about an unread sheet | M-402 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. |
| Voice it couldn't make out | I couldn't make that out — say it again, or type it. |
| Review list, empty | Nothing waiting. Everything that came in today landed somewhere. |
See it work.
Start with the most ordinary thing it makes, and the one your office will test first. → Hours
All of that assumes it actually read your prints. It publishes which ones it has and which ones it hasn't, by sheet number, on your job. → What it's read