iPhone & iPad · Private beta
Faster than paper, so it actually gets done.
iChecks runs professional checklists on iPhone and iPad and keeps a record of what was actually done. It works entirely offline, with no account and no server.
TestFlight, by invitation. Free during the beta.
Immediate Primary Actions
Damage Assessment and Control
The problem
A checklist that isn't used protects no one.
Paper checklists carry enough friction that professionals come to see them as wasted time, and stop. The printout gets left on the desk. The pen doesn't work. Filing the sheet afterwards is a chore nobody does, so it never gets scanned and never gets found again.
The digital tools that replaced them mostly solve the auditor's problem — forms, scoring, compliance dashboards — and they are heavy, slow to open and priced per seat. None of them is what you reach for on a wet deck at 03:00.
The phone is already in your pocket and never runs out of ink. iChecks makes running a checklist quicker than the paper version, and captures the proof as a byproduct rather than as extra work.
Built for the field moment
Not for the audit desk.
-
Every tick is saved the instant you make it
Not on finish, not on a timer. A run survives a force-quit, a flat battery, or a phone dropped in a bilge — and it resumes exactly where it stopped, hours or days later.
-
Opens straight into the run
No sign-in screen, no loading spinner, no sync on launch. Tap a checklist and the first item is under your thumb.
-
Built for gloves
The whole row is the target, not the tick box — 56 points tall, with item text that wraps instead of truncating at large Dynamic Type sizes.
-
Your checklists are plain files
Markdown with a small header. Write them in the app or in any text editor, import and export through the share sheet, keep them in version control if you want to. Nothing is trapped in a proprietary format.
-
A record of what was actually done
Completed runs go to History with their timestamps and the time zone they were captured in, plus any comment you left on an item you could not tick.
-
Nothing leaves the device
No account, no server, no analytics, no advertising — and in this version, no networking code of its own at all. Your checklists and your runs are yours.
Night mode
Red-biased, down to the body text.
A dark theme is not a night theme. Under a dark-adapted eye, cool grey text sits close to the peak of scotopic sensitivity — so blue-grey body copy does more damage to your night vision than any accent colour, simply because it covers far more of the screen.
So Night has no cool neutrals at all: every background, every rule and every shade of text is red-biased. It runs on one hue, because at low light the eye stops telling hues apart long before it stops resolving detail — urgency is carried by saturation and by the container instead. The tick's checkmark inverts to a dark knockout rather than glowing white.
It is never selected for you. Night is a mode you choose, on the run screen, when you need it.
- Single hue — coral, no second accent to discriminate.
- Warm neutrals — every one red-dominant, R > G > B.
- Dark knockout — the checkmark stops being the brightest thing on screen.
- No status bar — iOS has no warm clock, and nothing up there matters mid-procedure.
- Light and Dark meet WCAG AA — Night deliberately trades contrast ratio for preserved dark adaptation, which is why it is opt-in.
Use the switcher on the run screen above to see all three.
The file format
A checklist is a text file you own.
Every checklist is Markdown with a short header. Edit it in the app, or in whatever editor you already use. Share one as a file, and the person who receives it can read it without iChecks installed.
An item is written the way a professional says it out loud — the thing, then
the response verb. Speed — REDUCED TO MINIMUM. On screen the item
sits left, the verb sits right, and the row is what you tap.
---
ichecks: 1
title: Flooding
vertical: yacht
emergency: true
---
Immediate response to flooding.
## Immediate Primary Actions
- [ ] Master — CALLED
- [ ] Chief Engineer — CALLED
- [ ] Guests and crew — MUSTERED
- [ ] Speed — REDUCED TO MINIMUM
- [ ] Bilge pump via OWS — STARTEDSomething to start from
43 superyacht checklists, included.
Seamanship and engineering procedures, written to be replaced: edit them, delete them, or import your own on day one.
- 19 Emergency Flooding · Man overboard · Abandon ship
- 12 Bridge Pre-departure · Bridge handover · Heavy weather
- 12 Engineering Bunkering · Watchkeeping in port · Dry dock entry
They are examples written by the developer, not approved procedures — see the note at the foot of this page.
Who it's for
Small crews where "who did this, and when?" matters.
- Yacht crews Captain or officer writes them; the crew runs them on deck.
- Flight ops Ops manager and private pilots, pre-flight through shutdown.
- Maintenance shops Shop lead and mechanics, per job and per machine.
- Kitchens and food shops Opening and closing checks, cleaning, delivery logs.
- Inspection teams Repeatable safety rounds where the record is the point.
The two roles are usually the same person — you write the checklist somewhere quiet, and you run it somewhere busy. iChecks is built so the solo path never pays for the team features.
Price
Free while it's in beta.
There is no purchase surface in the app at all right now, and nothing to subscribe to. When iChecks reaches the App Store there will be a one-off price for a single professional and a flat monthly price for a crew — per team, not per seat. Those numbers are not set yet, and they will be published here before anyone is asked to pay one.
Try it on a day you'd have used paper.
That is the whole test. Builds go out through TestFlight by invitation — send an email and you'll get one, along with what changed in it.
What iChecks is not
iChecks is not a substitute for the operator’s approved or certified procedures. It runs checklists that you or your operator have written; nothing in it is approved by any authority, and where an official procedure exists, that one governs.