By Friday afternoon somebody is scrolling two hundred shots deciding which ones the customer is allowed to see, and nobody can remember any more which pour those forms belong to.

A customer reads every photo as news about their build, and a crew only shoots freely when they know nobody outside will see the mess. The two piles do different jobs — one is a story you are telling, the other is evidence you may need — so they are kept apart end to end, and internal is the default: nothing reaches the customer that was not put there on purpose.

A gloved thumb in full sun sends the six-a.m. mud shot to the customer, and the reassurance call happens before the pour is even finished.

A crew lead needs to shoot without worrying he'll embarrass the company. Colour, weight and wording all differ, and both targets are sized for a work glove rather than a desk mouse. Two buttons rather than one toggle, because a toggle has a state you can misread in sunlight and two labelled buttons have no state at all — and the upload route refuses any photo whose destination is not literally one of the two, so a missing field can never quietly mean customer.

Three hundred pictures in a camera roll and no way to say which of the four jobs on the go this footing belongs to.

Nobody on a ladder wants a filing job, and a photo that files itself is one that actually gets taken. The confirmation names the checkpoint and shows the shots riding along with it, so the last look happens before the tick is committed rather than a week later — and one more photo can go on right there, which is exactly when the missing one gets noticed. On the crew's phone the job and the stage come from the shift he is clocked into; if he is on two jobs with no shift open the upload is refused with "clock in first", because a refusal is a better answer than a guess about which site he is standing on.

Documenting a pour takes twenty shots and the crew quits at four, because every frame throws them back to a screen before they can take the next one.

A crew that can document a pour without breaking stride will actually do it. Review and retake happen inside the camera, so one more shot costs one more tap instead of a round trip through a form. They land on the checkpoint row rather than in a job-wide album, which means a burst dropped on the wrong row is visibly on the wrong row — and every tile carries its own delete, so fixing it is one tap too.

The out-of-plumb post gets mentioned on a call at six, and by Monday nobody remembers which post.

The man who saw the problem is the best person to point at it, and the best moment is while he is still standing in front of it. When he can say it on the photo, the office understands the first time and he feels his judgement counted — fewer callbacks, fewer wrong fixes.

The back line of that property has no bars, the upload dies without saying so, and the shots that would have proved the pad was right sit on a phone nobody thinks to check.

A crew trusts a tool that tells the truth about what happened to their work. So nothing fails quietly: a walk-round waits on the phone with its count showing until the signal comes back, and a single shot that can't go says so in plain words. A queue you can see is honest; one you can't is how a crew believes a photo is filed when it isn't. When a file does have to shrink, resolution is cut before quality — a barn photo is mostly sky and concrete, which is exactly where compression shows.

The photo that would settle the dispute exists, but it's one of thirty thousand and nobody can say which job it's under.

A photo you can't find might as well not exist, and people stop taking photos they never see again. Filing by job and stage — the way a builder already thinks — means the office actually goes back to the record, and the crew sees their photos being used.

The customer's whole sense of how their build is going comes from what they could see from the road and what a neighbour guessed.

Customers relax when what they see is chosen and clean — it reads as a builder in control. The customer's page asks for photos on this job marked customer, and that is the whole of the rule — no second filter, no hidden flag, no per-photo permission list to keep in step. One column decides it, so the guarantee still holds in a year when somebody builds a screen nobody has thought of yet.

Every Friday brings the same call asking whether anything actually moved this week, and answering it properly costs half an hour you were going to spend quoting.

A customer who can watch the building go up stops worrying, and a customer who stops worrying stops calling. Ordering by stage rather than by upload time is the decision, and it costs something: a shot sent up two days late from a phone that had no signal lands where the work was instead of at the top of the feed, so nothing announces itself as new. In exchange a stage nobody photographed is visibly empty — which is the honest answer, and usually the useful one.

Six months on, somebody asks what the rebar looked like before the pour and all you have is your word for it.

Proof that costs no extra effort is proof that actually gets taken. The ask sits on the tick rather than on the photo, because the tick is the only moment the thing is still visible — afterwards the rebar is under six inches of concrete. The shot stays on the internal side with the time it was taken sitting on it, so the record accumulates as a by-product of the work instead of being one somebody has to sit down and produce.

Three weeks after the wet spell the customer wants to know why their build slipped, and all you have is your memory of how bad the approach was that morning.

People accept a delay they can see the reason for; they resent one they only hear about. A delay with no evidence beside it is only your side of the story, so the photo hangs off the delay record itself and the first promised date is kept next to the new one. The customer sees the reason and the date move together instead of hearing about the slip on its own.

The one clean shot of the finished gable sits in the job file where the customer will never see it, while Tuesday's mud is in the gallery where they will.

Being able to change a sharing decision later takes the pressure off getting it perfect on site. Everything added in this section is customer-visible by construction, and internal proof shots live on the checkpoint rows instead — so there is no per-photo switch to misread and no way for a shot to change sides after the fact. Taking one back deletes the file rather than hiding it: a photo you decided the customer should not have has no business surviving as a link somebody could still open, and the price of that is that removal is permanent.

The walkthrough video and the plan set the customer keeps asking about are stuck in your outbox, too big to send, so the answer to their question turns into another phone call.

Customers feel listened to when they can show you rather than describe it. What a customer sends goes straight to storage on a signed upload rather than through the app, which is the only reason a fifty-megabyte walkthrough survives the trip at all — the old path through the server died at about four and a half. Over the ceiling the refusal names the ceiling in megabytes, and it comes before the upload starts rather than at the end of it, so nobody watches a bar crawl to ninety for nothing.

Six months on, two men each swear they photographed that footing, and the file holds one picture with nothing on it but a date.

Crews want the credit for good work, and owners want to know who to ask. Who took it is stamped from the authenticated caller on the way in and only on the way in, so a photo pushed to the customer's side a month later is never re-credited to whoever pushed it — attribution is set once, at capture, or it is not attribution. His name is kept next to his id because crews churn and a credit that resolves to nobody is worse than no credit, and the location is recorded against the row rather than left buried in a file the customer might download.

You ring the yard in October about six panels that never came off the July truck, and the whole call is your word against the driver's.

A yard settles faster when the evidence is in front of them and nobody has to argue. The photographs ride inside the claim itself rather than as numbered links — nobody at a lumber yard clicks "1 2 3" in an email — and only the lines that went wrong travel with them, because a four-hundred-row order with ten bad lines buried in it is an order that gets ignored. The evidence is stored on the claim, not just sent in the mail, so it is still under that order and that supplier's name a year later; the cost is a cap of six images inline, because a mail a yard's server bounces proves nothing at all.

The dispute lands on the one stage that ran three weeks long, and that is also the one stage with two photographs on it.

An owner sleeps better knowing where the record is thin before it matters. The count sits in stage analytics beside how long that stage ran and how many days it lost, because those turn out to be the same question asked twice — a stage nobody documented is usually a stage nobody was watching. Counting is all it does: no target, no nag, because a number that scolds a crew gets fed pictures of the sky.