Torspan
AirOrchestra — What it does

Nobody tags anything. Every photo is still on the right job.

A man shoots the hangers he just set and sends them the way he would have texted them to you. They land under that job, with the date, his name, and his own words on them. When his words and the schedule disagree about which job it is, nothing gets filed — it names both and asks.

Two photos, one sentence, and nothing in between.

He sent this at 7:22 in the morning, standing on a lift. Nobody opened anything afterward.

No folder was picked. No tag was applied. No job was chosen off a list. The filing step is the sentence he was going to send anyway.

Invented crew, invented job. Nothing on this page is a real person, a real jobsite, or a real building. Every picture tile on this page is a flat block, on purpose — no jobsite photograph appears anywhere on this site.

What it does

  • It puts the job on the photo. From the job he named in his own words, or from the day's dispatch when he named none. His words beat the schedule, because the schedule is what somebody planned and the sentence is what happened.
  • It puts the day on the photo — the day it was shot, not the minute it finished uploading. A picture taken Friday in a mechanical room with no bars is still a Friday picture when it lands Monday.
  • It keeps his words as the caption, word for word, marked as his. Nothing gets written in a man's voice that he did not write.
  • It files nothing to a guess. Two possible jobs and no way to tell means the photo waits, unfiled, with the question sitting in front of the man who knows.

How it works

Seven steps, in the order they happen on the job — not in the order the software does them.

01

He shoots it inside the app.

The job and the day are the ones he is on. There is no project to select first, which is the step every other product calls “quick.”

02

He sends it, with words or without.

Up to ten on a message. HEIC off an iPhone, JPEG, PNG, WebP. Words are better and nobody is required to write any.

03

His words become the caption.

The exact substring of what he sent, pulled out of the stored message rather than written about it. Marked as his, permanently, so nothing can put a sentence in his mouth later.

04

The job gets attached.

One clear jobsite named in his own words wins outright. No job named and one job on the day's dispatch — that one. No job named and two jobs on his day — see the next section, because that is the part that matters.

05

Words in the next message are labelled as what they are.

He sends the picture, then thirty seconds later types “that's the shaft wall.” That second message is attached as a timing match and shown as one — near in time, not spoken about this photo. A caption is a quote or it is empty. It is never a good guess wearing quote marks.

06

A description gets written for search, and it is labelled as machine-written.

So that typing hangers north corridor finds this morning six months from now. It sits below his caption in a lighter weight with the word described on it. The two are never merged into one voice, and the machine's line never becomes the caption.

07

No signal, no problem.

Photos shot in a mechanical room queue on the phone and go up when there are bars, keeping the minute they were taken. Nothing is lost and nothing gets re-dated to whenever the truck reached the highway.

There is no tagging step, so there is nothing to be behind on. A photo either arrives filed, or it arrives as a question.

When it can't tell which job

This is the section that decides whether the rest of the page is worth anything.

A man was on two jobs Thursday. He sends a picture at 2:41 with five words on it, and the five words point at one job while the day's dispatch points at the other. Every product in this category has an answer for that moment and the answer is always the same: pick the likelier one and file it, quietly, because a filed photo looks better on a screen than an unfiled one.

Here it does not get filed. Both jobs get named, and the question goes to the one person who can settle it in four seconds — the man who took it — in the thread he is already in.

Tomas R. · his own thread · 2:41 PM
Tomas R. · 2:41 PM north riser done, second floor

unfiled

AirOrchestraWhich job is this one — Riverbend Bldg 2 or Meridian West? It's not filed until you say.
Riverbend Bldg 2 Meridian West

Two answers on the screen and neither one chosen. That is not a bug in the demo. No red, no warning triangle, no badge with a count on it — invented crew, invented jobs.

He answers with one tap and it is filed with his answer on it — job, date, person, and the fact that he is the one who said so. If he is on a ladder and does not answer, the photo stays unfiled and shows up on the foreman's review list the same way, with both jobs still named. Nothing gets decided by a clock running out.

An unfiled photo is a question with a picture attached. A wrongly filed photo is the same thing, except nobody ever finds out.

Everything that comes back as a question instead of a filing, in one place. → How it works

The words it actually uses

The strings out of the product, not a friendlier version written for a website. This is what a man reads on a phone when something can't be placed.

WhereWhat it says
Photo that can't be placed, in his own threadWhich job is this one — Riverbend Bldg 2 or Meridian West? It's not filed until you say.
The same photo, on the foreman's review listNot filed. Two jobs named — pick one or ask him.
Photo with no words, one job on the scheduleFiled under Riverbend Bldg 2, Aug 14. Say the word if that's wrong.
Photo with no words, no job on his dayNothing on the schedule for you Thursday. Which job was this?
Photo out of the camera roll, day not obviousThat one wasn't shot today. What day was it?
Photo of a drawing or a printed sheetIs that a document or a photo? A document goes with the job's prints.
Waiting on signalWaiting for signal. It'll go up with the time you took it.
Same photo sent twiceAlready have that one — nothing added.
A job with no photos yetNo photos on this job yet.
His own photos, none yetNothing yet.
Search with no resultNothing matching that. Try what's in the picture — “hangers,” “north corridor.”
A photo he deleted, where a report referenced itDeleted by the man who took it, Aug 18.
Caption he changedCaption changed by Tomas R., Aug 15. The first one is still on it.
Unfiled photo, label under the thumbnailunfiled

A question is not a failure. It is the alternative to a job name nobody said.

What's on the photo

Every photo, every time. This is the block a controller screenshots.

FieldWhat it holds
ImageThe photo as he shot it, full size, unedited
TakenThe date and minute it was taken
JobThe job it's filed under
Filed fromHow that job was decided — his words, or the day's dispatch
PersonWho took it and sent it
His captionHis own words, word for word, marked as his
DescribedA machine-written line, marked as machine-written, for search
MessageThe message it arrived in, kept whole
NearbyWords from an adjacent message, labelled a timing match, never a caption
HistoryEvery caption change, with who made it and when
One photo, opened
Nothing is printed over the picture. No corner stamp, no logo, no coordinates.
TakenAug 14, 7:22 AM
JobRiverbend Bldg 2
Filed fromhis words
PersonTomas R.
MessageAug 14, 7:22 AM · 2 photos
Nearby“that's the shaft wall” — timing match, not a caption
His caption

“north corridor, first six done” — his words

Described

Overhead hangers set in a corridor ceiling, rod and band, six in a run. described

Two lines, two voices, never merged. The machine's line is for search and never becomes the caption.

Nothing is printed over the picture. No date burned into the corner, no company logo, no coordinates stamped across a man's work in a font nobody picked. The attribution lives on the record, where it can be opened, checked, and traced back to the message it came from. A stamp cannot be asked where it got the job name. This one can.

The original is the original. What comes out of an export is the file he shot, not a re-encoded copy with a band across the bottom. Mark-ups and notes, when somebody adds them, are kept beside the photo rather than baked into it.

How the job got decided is on the record too. Not a confidence score, not a percentage — one of two plain values: his words, or the day's dispatch. Six months from now that line is the difference between a photo you can hand somebody and a photo you have to explain.

It's covered up now. The photo isn't.

Every job buries most of its own work. Hangers go behind drywall, welds go behind insulation, and the sleeve somebody swears was never there gets poured into a deck.

What is left, three or six years on, is whatever somebody happened to photograph and whoever still remembers where they put it.

Usually that is a phone. The picture exists — it is in a camera roll among four thousand others, on a device that belongs to a man who left the company in the spring.

Here it is on the job, under the date, with the name of the man who took it, and it is findable by what is in it.

Riverbend Bldg 2 · Photos
what's in the picture Everyone ▾ All dates ▾

Aug 14 · Thu

Tomas R. “north corridor, first six done”
Tomas R. “north corridor, first six done”
Marco A. “FCU-14 set, hangers doubled”
Dee W. “shaft wall before it gets closed”

Aug 13 · Wed

Ray D. “VAV-22 rough-in, above the grid”
Tomas R. “AHU-3 curb, before the roofers”
Marco A. “sleeve in the deck, north end”

Export this job

Sorted by the day the work happened, not the day somebody got around to uploading it. Invented crew, invented job; the tiles are flat blocks, not photographs.

Search finds it by what is in it.

Type hangers north corridor and the morning of the fourteenth comes back, because a description was written when the photo landed and it has been sitting there ever since, waiting to be useful once.

The record travels.

A job's photos come out as files, in a folder per day, with a sidecar file carrying the attribution — job, date, person, his caption, the message it came from. It opens on any computer, with or without an account here, forever.

And they are already in the paperwork.

The day's write-up carries the day's photos. The week's pack carries the week's. Nobody assembles a photo report at nine on a Sunday night, because the report was written as the days happened.

Whose photo it is

Worth being blunt about, because a man who is unsure what happens to his pictures sends fewer of them, and a thin record is a useless one.

  • The job's photos belong to the job, and everybody on it can see them. That is the point. A picture nobody can find is the same as a picture nobody took.
  • He deletes his own, any time. No approval, no reason, no window that closes after a day. If it shows up in a report that already went out, the report says the man who took it deleted it. It does not quietly show a hole.
  • He can fix his own caption, and the first one stays on the record underneath, with the time he changed it. Two captions is a record. One that quietly changed is a problem.
  • Nothing is counted about him. No photo count, no ranking of who sends the most, no activity number, no comparison to another hand. There is no screen in this product that puts two men's numbers next to each other.
  • A face in the frame is just a face. Nothing is run against it, matched to anybody, or stored as anything other than part of the picture.
Caption history · one photo

“north corridor, first six done”

Tomas R. · Aug 14, 7:22 AM · his first caption, still on it

“north corridor, first six hung — the last two are on M-501”

Caption changed by Tomas R., Aug 15. The first one is still on it.

Two captions is a record. One that quietly changed is a problem.

Where a report referenced a deleted photo

Deleted by the man who took it, Aug 18.

The report says so where the picture was. It does not close the gap and pretend the day looked like that.

The camera does not work for the office. It works for whoever has to prove what was behind the wall.

What it won't do

No face recognition. Not for attribution, not for search, not for a head count. Ever.

No location out of the image. GPS written into a photo by a phone is not read, not used to decide a job, and not kept. It is stripped out of anything this product renders or hands over — a disclosure control, not an optimization. The job comes from a man's words or from the day's dispatch, both of which a person can argue with.

No stamp burned into the picture. No date corner, no watermark, no coordinates printed across the work. The attribution goes on the record, not on the image.

No progress percentage read off a photograph. No quality score, no automatic defect detection, no “80% complete” derived from pixels. A picture of a man's work does not become a judgment of the man.

No inspection sign-off. It does not approve, does not close a punch item, and does not decide whether what is in the picture is right.

It is not a camera roll backup. It files what a man sends into a job record. It does not reach into his phone and take the rest.

The complete list, including the things people wish it did. → What it won't do

What it takes off the day

Not the craft. The second shift after the real one.

  • The camera roll with four thousand pictures and no order, on a phone that belongs to a man who may not work here in a year.
  • The group text where the shot of the hangers is now nine hundred messages back, under two lunch orders and a photo of somebody's truck.
  • The night the foreman spends dragging photos into folders so that somebody in the office can find them — which is a filing job handed to the most expensive man on the crew.
  • The end-of-job scramble for “do we have a picture of that before it got covered,” which is a question about luck, asked at the worst possible time.
  • The email to the office with the subject line “photos” and eleven attachments named IMG_4471 through IMG_4482.

How long it's kept

The work gets covered up in a week. The question about it can arrive years later. Here is how long that window actually is in this state, and what stays on file for it.

What the rule saysWhere it says itWhat's kept here
A claim arising out of construction of an improvement upon real property must accrue “within six years after substantial completion of construction, or during the period within six years after the termination of the services” RCW 4.16.310 The photo, its date, its job and the man who took it
An action upon a contract in writing must be commenced within six years RCW 4.16.040 The message each photo arrived in, kept with it
Wage and hour records — the other half of the same day — kept at least three years 29 CFR 516.5 · WAC 296-128-020 On Hours, with the sentence each entry came from

Six years is longer than most phones last, longer than most men stay, and considerably longer than anybody's memory of a Thursday in August. Nothing here is deleted on a schedule, and everything here comes out whole any day you ask for it.

This is not a compliance product and it does not certify anything. It states the standard, states what the record holds, and states how long it is kept. Whether a business meets a rule is between that business, its lawyer, and whoever is asking. → Your records

See it work.

See it work See what it costs

The photos don't sit in a gallery waiting to be assembled — they're already in the day's write-up and the week's pack. → Reports and the office

All of this depends on a man sending a picture without wondering what gets done with it. Here is what is not collected about him, in writing, before price. → For crews