v0.7.0 — 2026-09-19 · Open Jobs gets a calendar Open Jobs opens on a week of nights you can click. Every night shows its jobs colored by where they stand: scheduled, on site, waiting for review, couldn't finish, missed, done. Click a night to see only that night. Click an empty night to schedule one with the date already filled in. WEEK / MONTH flips the same calendar to a month for planning ahead; the arrows move a week or a month; TODAY comes back. Under the calendar, one row of counts replaces the stacked lists: Review, Couldn't finish, Findings, Tonight, Missed, Unscheduled. The page shows what needs you; click a count to see just that list. Coming up is gone from the list because the calendar is where you see it. A job whose night couldn't finish no longer shows a second time under Unscheduled. Today is now the date on your wall, not the date in London: after 8 PM Eastern the office no longer skips ahead a day.

v0.6.1 — 2026-09-19 · finding photos Findings carry any number of photos (record shape 3.1.5, linked by finding). The night view and the findings report show all of them.

v0.6.0 — 2026-09-19 · step 2.4, review, approve, print On a closed night: Service report, Findings report (when there are findings), FDNY cleaning checklist (when the night was flagged). Each is draft → approved → sent. The service report's outgoing narrative is edited on the document; the technician's original stays on the record. Findings are their own document; marking it sent writes a client-notified entry on every finding and sets a two-week follow-up. The FDNY form shows every box with where it came from — the technician's taps, the ticked list, derived from the record, or yours — and cannot be approved with a box empty. Print renders the same HTML as the preview, letterhead from the new Company card under Data & Version. The wall (§6) is a function, reportData: times, money, instructions and the log never reach a page.

v0.5.4 — 2026-09-19 · Jonathan's review of the hosted build Job Search: ten per page, sorted most recent first in every view, the column is Date. Open Jobs: the "Open, nothing scheduled" rows had landed above the Tonight rows (a bug) — order fixed; past nights that were scheduled but never checked in are now their own block instead of inflating Tonight. Job Setup refuses a new work order whose WO number already exists and jumps to the existing one — that is how night two gets added.

v0.5.3 — 2026-09-19 · certifications A technician can carry any number of other certifications — name, number, expiry — alongside the FDNY C of F. Record shape 3.1.4.

v0.5.2 — 2026-09-19 · first hosted build Live at closeout.360aor.com. DEMO DATA chip in the sidebar whenever the store is the demo set. Links to the field app and the start page.

v0.5.1 — 2026-09-18 · the list is the work A task line can carry a note the technician sees under it, and the FDNY box picker gained All standard steps — one line on the phone answers every routine box. The demo quarterly template is six lines instead of fifteen.

v0.5.0 — 2026-09-18 · forms pop out; technicians; plain names Customer, Site and Technician forms now open as a dialog over the full-width list — wide, scrollable, SAVE / CANCEL / DELETE. Customer gained billing address, AP email, terms, PO-required, notes and its own contact list. New Technicians screen: name, role, kind, phone, email, employer, C of F number and expiry, active. A technician on past nights is marked inactive rather than deleted. Names say what they are: Open Jobs, Job Search, Job Setup, Customers, Sites, Technicians, Job Templates. Open Jobs also lists jobs with nothing scheduled and a one-click SCHEDULE A NIGHT. Record shape 3.1.3.

v0.4.0 — 2026-09-18 · step 2.3b, records Customers (name, kind, main contact, phone, email, billing notes, their sites), Sites now editable (address, how to get in, contacts with roles and phones, site notes, and the equipment that lives there — hood, fan, make, model, serial, manufacturer's job number), and Jobs with search across everything Ray would remember: site, customer, address, WO, technician, what the technician wrote, findings, equipment. Open / Completed / All. A customer or site with jobs cannot be deleted.

v0.3.0 — 2026-09-18 · step 2.2, Ray's morning The screen the desktop opens to. Exceptions first: close-outs waiting for review (tasks, pairs, findings, FDNY at a glance), nights that couldn't finish with the technician's reason and a one-click schedule the next night, findings open with whether the client has been told. Then tonight and the week. Successful work is silent. Clicking a night lays it out for the office — times, instructions, the list with counts, before and after side by side, the six FDNY answers, what he said, findings — read-only, with MARK REVIEWED so the queue clears. The Jobs table opens the latest night. Approve and print is step 2.4 on this same screen.

v0.2.0 — 2026-09-16 · step 2.3, set up a night Ray's setup, one page, four cards: the site (remembered, with its contacts and how to get in, or new), the job (a new work order or another night on an existing one — "I need another day" becomes night two here), the night (date, window, lead, crew, his instructions to the technician, whether the FDNY checklist applies), and the list and photos — started from a template, edited freely, saved back as a template for next time. A Templates screen keeps the library: a kind of night written once; editing it changes future nights, never past ones. Everything saved is validated against the record shape before it is written. Record shape 3.1.2.

v0.1.0 — 2026-09-19 · step 2.1, the office shell First file of the desktop app. Sidebar and main panel; the same store module as the phone, embedded verbatim; the same storage key, so in one browser the office reads what the phone wrote — the loop demonstrates without a server. Read-only Jobs and Sites tables prove it. Morning (2.2) and Set up a night (2.3) are placeholders. Backup, import, demo and erase share the phone's two-tap safety.