A hand with your field notebook.

Choose the demonstration or your team

Today, Field, Wells, Tanks and Handover let you explore a fictional field and a local demo notebook. Open the Team workspace to work with your own asset register and manually entered team records. The 3D scene remains a demonstration; it is not a map of the assets you add to a team. The app does not monitor or control real equipment.

Sign in and join your team

Use the same named account in the phone app and web Team workspace. Verify your email before opening shared records. A team owner creates an invitation for your email and shares its ID with you; enter that ID while signed in with the matching email. Creating an invitation does not automatically send an email.

An owner or supervisor can add your wells and tanks, choose units and set limits. Observations can contain a measurement, a note or both. A collection ticket records the collected volume; it does not calculate the remaining tank inventory.

Capture a ticket and prepare a report

In Team, use Record for an observation or collection ticket, Tickets to find saved collections, and Reports to prepare an export. More contains issues, handovers and setup. To try the workflow without an account, open the fictional ticket sample; its changes stay in that browser.

Take or choose a clear photo of one ticket, then read the text or enter the fields manually. Text recognition needs a connection to download the scanner on first use and works best with clear printed English. Compare every suggested value with the image, choose the correct tank and explicit unit, and confirm the details before saving. On the phone, the ticket date represents the selected local day; the web form also accepts the local collection time. A compressed photo is retained with the record; keep the original if needed.

In Reports, choose the period and record type, then select, reorder and rename columns. Check the preview before downloading or sharing a CSV. The web also offers a printable report. By default, only records confirmed at the last refresh are included. If you include pending records, their sync status remains in the export. CSV exports do not attach photos or connect to accounting software.

A record is pending or did not save

Wait for the local save confirmation before leaving a form. Pending sync means the change is saved on that device but is not yet confirmed for the team. Reconnect, open the team and use Sync / refresh team or Sync now. Confirmed records can be read by teammates using the same workspace.

A failed record stays on its original device for retry. If an issue or asset changed on another device, review the current record and your conflicting draft before discarding the draft and making a new edit. Do not uninstall or clear storage while records remain unconfirmed. Export cached records if you need a separate copy.

If the local demo reports a storage problem, use Retry storage before submitting again. If saved records cannot be read, the app preserves them rather than replacing them. Contact us with the error text before removing app data.

Prepare and receive a handover

In Team, confirm pending field records first, then choose the handover period. Capture requires an online refresh and includes confirmed observations and collection tickets observed in that period, plus unresolved issues known at capture. Saved contents stay fixed; records entered later need a supplemental handover. Acknowledging receipt records who read it and when. It does not close the outstanding issues.

The separate mobile demo also has saved handovers and a native Share handover action. Sharing sends a copy to your chosen destination; it does not synchronize the demo notebook into a Team workspace.

Manage access or delete your account

Open account settings on the web or Account settings in the mobile Team workspace. The deletion flow asks for your current password and an explicit confirmation. If you own a team with other active members, transfer ownership to another active member first. Teams where you are the only active member close and become inaccessible; their records remain stored.

Deleting your account removes your sign-in and active team access, and clears that device’s cached team records and unconfirmed drafts. Historical operational records and author names remain in the team record; copies on other devices and exported files are not recalled. See what is retained before confirming. If you cannot access your account, use Reset password or contact hello@westcode.io for help.

A team owner can remove another member’s access, revoke an unused invitation or transfer ownership. Other members can leave a team after confirming pending work. Removing access is separate from deleting an account.

Report a problem

Include whether you were in the demo or Team workspace, the screen, the steps that led to the problem and the error message. Remove confidential information from screenshots. We cannot retrieve a demo notebook or pending draft that existed only on a device after its storage has been removed. Do not send passwords or complete field archives by email. You can also contact the studio about a field pilot.

WellRelay privacy · About the demonstration