v3.6.0 — 2026-09-19 · check out; photos on findings CHECK OUT — LEAVING SITE stamps the time (and location) the moment he leaves, whether or not the record is finished; the card reads Left site — not closed and he can still finish and close from the truck. Close-out and can't-finish keep an existing check-out instead of overwriting it. A finding takes any number of photos, before it is saved and after (+ photo on the card), each linked to the finding in the record (3.1.5).

v3.5.2 — 2026-09-19 · pick your name, every time it matters If the phone had no names when you entered and names arrive later (demo loaded, or the office set you up), the picker comes up once. SWITCH TECHNICIAN under Data & Version. Record shape 3.1.4.

v3.5.1 — 2026-09-19 · first hosted build Live at closeout.360aor.com. A DEMO DATA chip shows in the top bar whenever the store on this device is the demo set, so nobody mistakes it for a real night. Links to the start page and the office app from the splash and the top bar.

v3.5.0 — 2026-09-18 · step 1.7, what the transcript said Sign in: pick your name once; it stays until you log out; My Jobs shows your nights first with a one-tap Show all. FOUND SOMETHING: damage, a leak, a dead motor — one line, which unit (from the site's equipment) or where, how urgent, a photo — sent to the office as its own report, never mixed into the before/after. Every visit, every type, now requires a before and an after of the work area; the slot is added at check-in if the office didn't list one. The type of call shows on the job card. A line the technician adds himself can take a count.

v3.4.0 — 2026-09-18 · the list is the work The quarterly list was fifteen ticks because every fire-department box had become a line. Wrong — the same mistake as the twenty-nine questions. The list is now the actual work, five or six lines, and the routine steps every cleaning includes are one line: Standard FDNY steps. One tick answers all of those boxes. Exceptions are what the three questions and the narrative are for. A progress line sits above the list.

v3.3.2 — 2026-09-18 · record shape 3.1.3 Store module updated with the office's customer fields (billing, contacts). No change on the phone.

v3.3.1 — 2026-09-16 · from the office A visit now shows what Ray wrote for it — how he wants it done, what to bring — and who else is on the crew tonight, in a card above CHECK IN. Record shape 3.1.2 (templates, instructions, crew). Demo data carries the office's template library.

v3.3.0 — 2026-09-16 · the form belongs to the office v3.2.0 put twenty-nine fire-department questions on the technician's phone. That was the paper process with chips. Reversed. The technician answers only what he alone can see — fans running, power locked out, how bad the grease, leaks, spots he couldn't reach, wires in the ducts — six questions, seven taps, three at check-in and three before he goes. The rest of the form is either the work list (each office-loaded task silently answers its box when ticked), office knowledge (last cleaning, hoods, subcontractors), or derived from the record. The office completes and prints the form on the desktop. Direction: desktop → mobile, admin → technician.

v3.2.1 — 2026-09-16 · job list for the technician; desktop view The job card now answers the technician's three questions and nothing else: where, what, when — Tonight · 22:00 in orange, Night 2 of 3 when a job spans nights, the work order number small at the right. The office's trade categories are gone from this screen; they belong to the office. On a wide screen the app draws at phone width, so the desktop shows what the phone shows. Fixed: the checklist chips shared a class name with the job-card tags and stretched them (error #6).

v3.2.0 — 2026-09-16 · step 1.4b, the FDNY checklist woven in The fire department cleaning checklist (26 items) is not a screen. When the office marks a night as needing it, the pre-cleaning questions appear right after check-in, the FDNY work items sit under the work list, and the post-cleaning questions sit above close-out. Every answer is a tap; the few boxes that need a number or a word get a field. Where the record already knows the answer — last cleaning at this site, hoods on record, panels installed tonight, pairs of photos — it is offered as a suggestion the technician confirms, never written for him. Close-out will not pass with a question unanswered. The answers live in a draft document the office prints and sends. Record shape 3.1.1: `visits.formsRequired`, `people.cofNumber/cofExpires`.

v3.1.0 — 2026-09-15 · step 1.4, the active visit The screen the technician lives on. CHECK IN stamps the time and, when the phone allows it, the location. The work list: tap to tick, a count where the office asked for one, and ADD for anything done that was not on the list — marked as his, not the office's. Photos: Before slots come from the office; the After is taken from its Before so the pair is made by the app, never by memory; extra photos are welcome and never block. What you did, in his own words, saved as he types. CLOSE OUT runs the gate and lists exactly what is missing; on a cleaning or repair visit every required Before needs its After, on a diagnostic visit Afters are optional. CAN'T FINISH TONIGHT asks why and marks the visit for review — "I need another day" becomes a record, not a text. Photo capture, orientation and compression ported from v2.5.5 unchanged.

v3.0.4 — 2026-09-15 · no browser pop-ups Load demo, erase, and import no longer use the browser's confirm box — some webviews and app previews swallow it silently and the button looks dead. Destructive actions are now a two-tap: the button turns red and says what it is about to do; tap it again within six seconds to do it. Found on Jonathan's phone.

v3.0.3 — 2026-09-15 · step 1.3, My Jobs → visits The first screens with real data. My Jobs lists open work orders by their next visit, closed ones below. A job opens to the site, its contacts (tap to call), the scope of work, and its visits in order — one night or five, on one record. Tapping a visit lands on the 1.4 placeholder. Demo data loader added under Data & Version: two jobs, one of them a three-visit diagnostic-then-repair with a finding and a pair of photos, so the list can be judged before the office app exists.

v3.0.2-shell — 2026-09-15 · wordmark fix The top-bar wordmark showed a gap between Close and Out — the same flex-row spacing bug v2.5.2 fixed, reintroduced in the port. The wordmark is one element again.

v3.0.1-shell — 2026-09-15 · light by default The app opens in light mode. Off-white surfaces, charcoal type, safety-orange actions — the same palette as the printed report. Dark mode is still there under Data & Version and the choice persists. The splash keeps its charcoal, because it is the mark, not a theme.

v3.0.0-shell — 2026-09-15 · step 1.2, the shell First file of the v3 field app. Store module 3.1.0 embedded verbatim (one implementation, D16). Boots a fresh store, migrates a v2.6.0 store, upgrades a 3.0.1 store, each behind its own backup. Survives a refresh. No external resources, so it works with no signal once opened. Backup export and import run through the same boot path as a live store, so an imported v2.6.0 file is migrated, not trusted. No job screens yet — 1.3 is My Jobs → visits.