Field mode (offline)
Use the schedule on a site with no signal. Keep a project's activities, last calculated dates and three-week lookahead on your phone, record progress offline, and sync it as one new version when signal returns, with every conflict put to you.
On this page
Field mode is the schedule for the superintendent on a site with no signal: a basement, a steel deck, a rural job. You can read the activities and their last calculated dates, check the three-week lookahead, and record progress. When signal comes back, your updates sync as one new version through the same save, calculation and history as the Planner.
Open it from Schedule › Field mode. It runs in the phone’s browser; there’s no app to install.
Who can use it
| You have | You get |
|---|---|
| Schedule view | The three-week lookahead, online and offline. |
| Schedule admin (the Planner’s level) | The lookahead, plus the activity cards with their last calculated dates, and progress capture. |
Field mode never shows more than you can open online. Every sync is authorized again on the server, as any Planner save is.
Keep a project on the device
- Open Field mode while you have signal. The page loads the lookahead and, if you’re a Schedule admin, the saved plan with its last calculation and the layout the Planner opens with: your default, the project default or Classic Schedule.
- Tick Keep available offline on this device. The schedule, its lookahead and your layout are stored in this browser for this project.
- Go to site. Without signal, the page opens from the stored copy and says Offline: data from … with the time the server produced it.
The activity list applies your layout’s filters, as the touch view does. The projects you keep are listed on the page, each with a Remove button.
What it stores
- The plan: activity rows and their calculated dates, as the Planner loads them (Schedule admins only).
- The lookahead: the activities in the three weeks from the day you stored it, and the linked items you’re allowed to open.
- Your start layout.
- Your queued field updates, until they sync.
It doesn’t store drawings, documents, the pages of linked items, other tools, passwords or sign-in tokens.
Record progress offline
Tap an activity to open its update sheet, the same one the touch view uses:
- Mark started or Mark finished.
- Set percent complete.
- Adjust remaining duration.
Each change is queued on the device with the time you made it. The status strip always shows how many field updates are waiting to sync, and Undo drops the last one. A project with queued updates stays on the device even if you didn’t keep it offline, so a reload never loses unsynced work.
Only actual start, actual finish, remaining duration and percent complete can be queued. Field mode refuses anything else on the device, and the server refuses it again on sync. Dates aren’t recalculated on the phone: cards keep the last calculation, marked as out of date, until a sync recalculates the plan.
Sync
Field mode syncs when the phone comes back online, when you open the page, and when you tap Sync now. The net change of your queued updates goes up as one save against the version you stored. It takes the Planner’s path: the version check, the calculation, a new version with its change summary, and an entry in the change feed. The new version records you as its author, that it came from field mode, how many updates it holds and when the first and last were captured.
Conflicts
If someone saved a newer version while you were offline, field mode loads it and replays your updates on top of it.
- A field the other save didn’t touch merges without asking.
- A field both of you changed to different values is listed with was, yours and saved. You choose Keep my field update or Keep the saved value for every one before Apply and sync is enabled. Nothing is resolved for you.
- An update to an activity the newer version removed can only be dropped. Restoring an activity is a Planner decision.
- Decide later keeps your queue on the device, and the next sync asks again.
Security and data at rest
- Per user and per project. Each copy is keyed to you and the project, and every read checks that it’s yours.
- Lost access. If a refresh finds you can no longer open the schedule, the project’s copy and its queue are deleted from the device. If you lost Schedule admin, the plan copy and the queue are deleted and the page tells you how many updates were removed.
- Sign out clears it. Signing out deletes every field mode copy and cache in that browser. If updates haven’t synced, you’re asked first.
- Another user clears it. When a different user opens any project page in the same browser, the previous user’s field data, including any unsynced queue, is deleted. Sync before you hand a device over.
- An expired session doesn’t clear the copy by itself. It stays until you sign out or another user opens a project page.
- The offline page. To open without signal, the browser keeps a copy of the field mode page and the app’s build files. That page holds the app’s frame (your name, the project name and navigation), not plan data. It never keeps API responses or any other tool’s pages.
- Private browsing or blocked storage. Nothing can be kept, so updates last only until the page closes, and the page says so.
Turn it off
- One project: untick Keep available offline on this device, or tap Remove in the list. Remove is available once the project’s updates have synced.
- Everything on a device: sign out, or clear the site’s data in the browser settings.
- For a whole deployment: build the app with
NEXT_PUBLIC_SCHEDULE_FIELD_OFFLINE=off. Field mode then works online only and removes its offline page. Updates already queued on a device are kept until they sync.
Limits
- It’s not an offline Planner. You can’t add activities, change logic, constraints or original durations offline, and dates aren’t recalculated until you sync.
- Open it online first. A project you never opened in field mode on that device isn’t available offline.
- The lookahead is fixed to the three weeks from the day you stored it, and linked items open only online.
- After an app update, a page opened from the offline copy may not be able to sync. The status strip then offers Reload to sync; your queue is safe on the device.
- One device’s queue is its own. Updates captured on a phone sync only from that phone.
- The Planner’s touch view stays online only.
Mistake: Keeping a project offline only once you are on site
In the app: Open Field mode and tick Keep available offline while you still have signal.
Mistake: Handing your phone or tablet to a colleague with updates still queued
In the app: Sync first. When another user opens a project page in that browser, your unsynced updates are deleted.
Mistake: Tapping Keep the saved value for every conflict to get it over with
In the app: Read each one. The saved value came from someone else's later save; your field update is what you saw on site.
Related
Keep exploring
Related across os.construction
- GlossaryField Mode (Offline Sync)A way to keep a schedule on a phone, record progress on site without signal, and sync the updates as one new version when the connection returns.
- DocsSchedule: CPM planning, field tasks and the look-aheadPlan the project in a native critical path Planner or bring in a P6 or Microsoft Project file, then publish reviewed dates to the field task list your team reads as a list, 3-week look-ahead, calendar and Gantt.
- DocsThe schedule on a phone or tablet: touch viewUse the Planner's touch view on a phone or tablet. Read activities as cards or a pinch-and-pan Gantt that follows your layout's timescale, bars, baselines, filters and progress line, mark work started or finished, set percent complete and remaining duration, then save and recalculate.
- GlossaryChange FeedA running, newest-first list of what happened to a shared record, such as a schedule's saves, calculations, baselines, imports and discussion, with who did it and what changed.
- BlogSchedule of values vs budget: billing lines and cost codes are not the same thingThe schedule of values splits the contract price into lines the owner pays against. The budget splits expected cost into cost codes the contractor manages against. Here is how they differ, why they shouldn't be the same list, how to map one to the other, a worked example and the mistakes that hide over-billing.
- BlogHow to track labor productivity: units installed against hours spentHours spent only tell you how much labor budget is gone. To know whether the crew is keeping up, compare the hours with the quantity installed: earned hours from the budget unit rate, a productivity index, and a forecast of hours to finish. Here is the method by cost code, with a six-week conduit example and three ways to forecast the rest.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →