Offshore oil & gas · Client prototype
Two weeks,
from a meeting
to a platform.
A compliance client asked what we could do for the people on their rigs. We showed them a working system a fortnight later. This page is really about how fast we can build.
Why we built it
They make compliance software for offshore oil and gas, and everything they had solved was about equipment — valves, sensors, shutdown devices, the things that get tested and logged. The people were the gap. Every crew member on a platform carries a stack of certifications with expiry dates, and somebody has to know, today, which ones are about to lapse, who needs a class booked, and who is not allowed on the next crew change. They asked to see a demo of that. So the real question was never whether we understood offshore compliance. It was how much we could stand up before the next meeting.
What we decided to do
Not a clickable picture of a product. A working one.
Anyone can put screenshots in a slide. We built both halves of the real thing — what the compliance officer sees and what a crew member sees — sharing one engine and one set of real regulatory data, running on the actual calendar. Every date in it is computed from today, so it never goes stale.
A prototype on real data and an invented crew. Nothing you do leaves your browser.
By the numbers
Measured from the codebase
- Officer app
- 6 screens
- Crew app
- 8 screens
- Requirements
- 20, each with a real
citation and interval - Crew & positions
- 12 people, 12 positions,
31 assignment rules - Devices modelled
- 28 across 4 areas
- API RP 14C codes
- 13, each with its own
test procedure - Question bank
- 43 across 3 topics
- Built with
- React 19, Vite, TypeScript
- Runs on
- Cloudflare Workers,
D1 database, R2 storage - Every date
- Computed from today
- Lines of code
- about 55,000
Every number is measured from the codebase. The officer and crew apps keep their state in the browser — nothing you do leaves your device. The chart reader is the one part with a live database behind it.
- 14days, meeting to demo
- 14screens across two apps
- 2people in the studio
What's inside
Two apps for two different jobs, built on one engine, plus a reader for the safety charts the whole thing depends on. The officer sees the whole platform; the crew member sees only their own record and their own areas.
- The officer's side
- 01The facility calendarWorking, in the demo
- 02The rosterWorking, in the demo
- 03The inbox and the confirm loopWorking, in the demo
- 04Tests — one test, the whole crewWorking, in the demo
- 05SAM, the assistantWorking, in the demo
- 06Equipment — the two clocksWorking, in the demo
- The crew member's side
- 07The front doorWorking, in the demo
- 08Your own calendarWorking, in the demo
- 09RoundsWorking, in the demo
- 10MessagesWorking, in the demo
- The chart reader
- 11Reading a SAFE chartWorking, partly shown
The officer's side
One person responsible for twelve people and twenty-eight devices on a platform in the Gulf. Six screens.
01
The facility calendar
Working · in the demo
Every coloured chip is one person's certification, on the day it expires.
02
The roster
Working · in the demo
Every crew member ranked worst-first, each with a full record: what their position requires, when they last did it, when it's due.
03
The inbox and the confirm loop
Working · in the demo
A thread with each crew member; when someone reports a certification done, the officer confirms it in one tap and the record updates.
04
Tests — one test, the whole crew
Working · in the demo
A module to build a test once from a bank of written questions and send it to the whole crew on one day.
05
SAM, the assistant
Working · in the demo
An assistant that answers six standing questions, like "who hasn't booked?", straight from the compliance engine — not a language model.
06
Equipment — the two clocks
Working · in the demo
All 28 safety devices, sorted by how late their test is against the calendar interval and the hard ceiling, with the regulation cited.
The crew member's side
The same engine, seen by one person who wants to know: am I clear this month, and what do I have to do today? Eight screens; four worth walking.
07
The front door
Working · in the demo
A short sign-up where the crew member says when they last completed each requirement, and their calendar is built from the answers.
08
Your own calendar
Working · in the demo
The crew member's own certifications on a month, week or day view — red until a class is booked, blue once it is.
09
Rounds
Working · in the demo
Walks the crew member device by device in the order they'd walk the platform, takes each reading and flags a failed one on the spot.
10
Messages
Working · in the demo
The crew member's thread with the compliance officer: book a class in one tap, mark a certification done, see it confirmed.
The chart reader
Everything on the equipment side depends on knowing which safety devices a platform actually has.
11
Reading a SAFE chart
Working · partly shown
Upload a safety chart as a PDF; a model reads the device entries, and a person confirms or corrects every value before it counts.
What to look for
It opens on a month of a whole platform's crew. Every chip is one person's certification on the day it expires. Colour is urgency, icon is kind.
Then open Equipment and tap the red row at the top. It is past its six-week test ceiling, and the record cites the regulation.
Then Tests: the Lockout / Tagout check, 3 of 12 taken. Open the builder.
Then open the crew member's side and see the same platform from one person's seat.
A prototype built for a client, on a development URL. Never released. The client is not named here; the platform, the operator and all twelve crew members are invented.
NextSelvático