Field operations platform with job scheduling and site documentation

A services contractor running crews across many active job sites had no single record of where anyone was scheduled, who had moved an appointment, or where a job's paperwork had gone. Site visits got rescheduled repeatedly with no way to answer who changed a booking and when — the question a customer or manager would actually ask. Plans, bids, permits and before-and-after photographs were scattered across personal phones and email, missing exactly when they were needed on site, and field expense receipts arrived late and unattributed. The team needed something that worked from a phone in a vehicle between sites, not a web app for the office.

Modelled every scheduling action as an immutable event rather than an editable field: creating a booking writes an entry, moving it writes another, and every entry carries the acting user and a server-assigned timestamp rather than the device clock. That produces a plain-language history — scheduled by whom for when, then rescheduled by whom for when — readable directly in the app.

For a business with no appetite to run infrastructure, the whole thing was built on managed services rather than a bespoke API tier: the app authenticates against a managed identity provider and reads and writes a hosted document database and object storage directly, with a single serverless function for notification dispatch. The data model is built around the queries the calendar actually makes — a purpose-built date key alongside the true timestamp so month and week views run as indexed range queries — and each appointment's absolute moment is kept separate from its local calendar day so scheduling stays correct across device time zones. Documents and photographs are filed into categories (plans, bids, permits, photos) at the moment of capture, with per-user, reversible archiving so one person tidying their list never disturbs anyone else's.

Field crews and coordinators now work from one shared calendar of site visits instead of a schedule assembled from calls, texts and a spreadsheet, and every booking and reschedule is permanently attributed and timestamped, so disputed appointments have an actual answer. Job documentation — plans, bids, permits and photographs — is filed by category at the moment it's captured rather than scattered across personal devices, and field expense receipts are attributed to whoever submitted them. The business runs on managed cloud services with no server to provision, patch or monitor.

Something holding you back?

New build, rebuild, or adding AI to what you already have — I'll take a look and give you an honest perspective.