Your boat and the cloud — sending her up, bringing her down, and checking
Signing in does not send your boat by itself. This is the one-time send, the pull onto a second device, and the check that tells you in numbers whether her record is whole.
Linking your account to the boat is not the same as sending her. On the first phone that carries her, that link is a tap: Account offers "Put <her name> in the cloud", and signing in alone no longer puts her up. It still does not send her record.
The reason is worth a sentence, because it explains something that would otherwise look broken. theONE keeps a queue of everything you change, and that queue started the day the app did. Records you entered before you ever signed in were never in it — so signing in sends a queue that knows nothing about them. Your account ends up linked to a boat with no history, and nothing anywhere reports a problem, because nothing has gone wrong.
Send this boat’s record is the fix, and you do it once for each boat: a second boat on this device, or a new boat started after one was lost, has her own, and her row says Not yet until her records have gone. Account → Send this boat’s record. It shows you the count before it does anything: so many systems, so many service records, so many hour readings. Read it, then decide.
What goes up: systems, service records, hour readings, work orders, issues, observations, tasks and playbook runs; the boat's own details; incidents, safety equipment, float plan contacts and man-overboard pins; vendors, their people and work sessions; storage, inventory and saved routes; jots and notes; documents and manuals; and bills, fuel entries, and crew and guest cards. Bills reach only the owner, captain and manager; fuel entries reach them and the crew, whose phones receive no price or receipt; a crew or guest card reaches those three and the person it is about. Files follow on their own.
What stays on this device: trips and passage tracks recorded before today, playbooks (they travel whenever you change them), and the Boat IT vault. Those are listed on the screen too, with the reason for each, so nothing goes missing later without your having been told about it first.
Queued is not the same as delivered, and the screen says so. When it finishes, your records are in the queue. They travel as signal allows. Nothing is lost if you lose service halfway — and if you close the app in the middle of it, it picks up where it stopped rather than starting again.
Bringing her down onto another device. Sign in on the second phone or iPad with the same account and it takes the boat's identity. Then Account → Bring her down pulls her record onto it. It counts: so many records before, so many after, so many came down. Run it again any time — a second run over the same record simply says there was nothing new.
If it stops part-way — you lose signal, you get signed out — it says so, and says why. It will not tell you it finished when it did not. What arrived is on the device and the rest is still in the cloud, waiting for the next run.
What it will mention when it applies, so that nothing reads as something going missing: records removed from this device because they were deleted on another one; older edits held because a newer edit of the same record is here; entries written by a NEWER version of theONE than the one you are running, counted and named — safe in her record, and updating shows them; and entries that could not be read at all, which were skipped and are listed on Sync Health. On a device whose person is not the owner, captain or manager, bills, documents and other people's crew and guest cards do not come down at all — they are kept for those three — and the counts leave them out; a crew member's device brings the fuel log down without prices or receipts, and a vendor's or a guest's brings none of it.
Steps
-
Sign in first
Menu (☰) → Settings → Account. The send only appears once your account is linked to this boat — there is nowhere to send her otherwise.
-
Read the count, then send
The row says "Not yet" until you do it, and "Sent" afterwards. Tap it, read what it will send and what it will not, then Send the record.
-
Who is offered it
Only her owner, and only on the phone that carried her before she was in the cloud. A captain's, manager's, crew member's or vendor's phone does not show the row, and neither does a phone that took her down from the cloud — a second phone, or this one after a reinstall: everything on it came from her record already, and sending it back would only repeat it.
-
Watch the queue go down, if you like
After it finishes, "Still to send" counts down as records land. That number comes from the queue itself — it is what is actually left, not what we intended to send. If the queue empties while a change the cloud refused sits set aside in Sync Health, the sheet says so instead of saying every record has gone up.
-
You do not have to wait
Leave the screen, close the app, go and start the engines. It keeps going, and it resumes if it is interrupted.
-
On your second device
Sign in there with the same account and it takes the boat down. Anything on that second device that the boat has never seen is not merged into her — you are asked first.
-
Ask whether it is all up, any time
Account → “Is it all up?”. It asks the cloud how far your boat’s record runs and compares that with this device, then answers in numbers you can check for yourself. It changes nothing — it only reports. Worth running before you hand the phone to a surveyor. Changes set aside on Sync Health count as still to go up: it never says Everything is up while one is waiting there. On her owner's phone — the one that carried her before the cloud did — the records Send this boat's record has not sent yet count too, so it says Still going up until that send has run.
-
If it says it cannot tell
That is an honest answer, not a fault — no signal, signed out, not linked to a boat yet, or linked to a different boat from the one on this device. It never guesses, and it never shows you an old answer dressed up as a new one. Nothing on this device changes either way.
-
Bring her down on a second device
Sign in there with the same account, then Account → “Bring her down”. It reports what arrived by counting, not by claiming. Safe to run as often as you like.
-
If it stops part-way
It tells you why — no signal, signed out, more waiting than one run brings. Nothing is lost: what came down is on the device, the rest is still in the cloud. Run it again when you have service.
-
If it mentions held or unreadable entries
Held means an older edit of a record that already has a newer one here — the newer one stands. Unreadable means a newer version of theONE wrote them; they are safe and an update will show them. Neither is data loss. Entries it says could not be read at all are different: they were skipped, an update will not show them, and Menu (☰) → Settings → Sync Health lists them so you can ask for them again.
Related
- Where your data lives — and the one thing that does leaveUntil you sign in, everything you enter stays on this device. Your position goes out to fetch weather, tides and charts, and to Apple to name the place you are. Here is exactly what leaves, and when.
- The one question we asked you — usage and crash reportstheONE asked once whether you would share anonymous usage and crash reports. Here is exactly what each one does, what it can never see, and how to change your mind.