Your jobs, on this device
This sets up the site card only. The programme is generated from Plans once you upload the consent set.
Private jobs live only in this browser's storage. Nothing is uploaded anywhere unless you turn on "Share with team" for a job, or use the Ask assistant (see Privacy in More).
Upload the documents that size your programme
Plans get attached to a specific site.
This scans the text printed on your plans — floor area, window/door labels, cladding/roofing notes, storey count — and builds a programme from proven high-end stage durations, scaled by those few values. It's a fast, structured starting point, not a deep analysis of the drawings: it can't read design complexity, junctions or detailing the way you can. Treat every result as a draft, then shape it with your own edits, the Materials & finishes factors, and Notes to reflect the real build.
Upload the engineer's drawings (PS1, specific design, foundation/bracing details). This reads the printed text the same way as building plans, stores it separately, and cross-checks it against your building plans — flagging things like storey mismatches or specific-design references so inconsistencies surface early. Always confirm against the stamped engineering documents.
Your build sequence, at a glance
Tap a bar for its stage name and dates. The amber ring marks today.
The order stages happen in, independent of how long each one takes. A hold point sits on the line between stages that need council/engineer/subtrade sign-off before the next one starts.
A clean, branded timeline to share with your client. It mirrors your real build stages and picks up any calendar entries you've tagged to run alongside a stage, and refreshes every time you open it — so you can reissue an updated version any time.
Tip: "Upload a photo" lets you pick any image from your device — a current site photo is perfect for showing the client where the build's at. You can change or remove it anytime.
Photos are kept per job.
Notes are kept per job.
Finishes that add time. Tick which apply to this build — relevant stages stretch to suit.
Factors are starting estimates from typical NZ high-end work — edit any to match your real numbers. As you complete builds, the app can refine them from your actuals.
The code you enter when you open the app.
Your only real safety net. Everything lives on this device.
A snapshot of how you're using the app and what it's learned. Copy it and send it over for review.
Build tick-lists by supplier, then copy & send to your team.
Orders are kept per job.
Tap Task in a note's expanded editor to have it show up here — with or without a date.
Team management needs a signed-in admin account.
Your account isn't set up as an admin yet.
Ask what's on, what's blocking a stage, or ask for a change — e.g. "what have I got booked next week?", "book the concreter Tuesday for 2 days", or "push framing back 3 days, the truss supplier is delayed."
Pick a stage, then use your browser's print (or "save as PDF").
Every job you create is private by default and stored only in this browser, on this device — nothing is uploaded anywhere just by using Library, Plans, Timeline, Chart, Subtrades, Snags or Print.
Share with team. Adding a team member (More → Share with team) prepares a read-only copy of the stage breakdown scoped to the stages you choose. Members can only tick off tasks they've been sent — they can't change durations, dates, or anything else. The copy is written to the shared store, so treat it as visible to anyone with the link; only add client-identifying jobs for people you trust.
Ask assistant. Sending a message in Ask transmits that job's current data — name, address, stage list, subtrades, snags — to Anthropic's API to generate a reply. This is the only feature in the app that sends data off this device, whether or not the job is shared.
This device. Anyone with access to this browser can open any private job stored here — there's no login. If this device is shared, consider that when leaving client details in job names or addresses.
Site photos. Photos added to the Site diary are compressed and stored as part of the job data (privately, unless shared) — not uploaded to any separate photo service.