Lane
Hand back packets, not dock invoices.
Onboard baseline, hand back in the same vessel zones, export a compare packet when the trip ends. One job · proof-of-condition operators can file with brokers and card processors.
Who this is for
Bareboat & multi-vessel operators
Deposit holds, guest return, broker files. M1 · Berth Charter is live.
Day-rental & boat clubs
Platform claims are not your archive. Same baseline → return discipline on the roadmap.
Haul & layup yards
Interchange and seasonal in/out packets · skins planned after charter revenue path.
Operator path
Onboard (check-in baseline) → Hand back (guest return) → Packet (compare PDF). Same flow on charter, rental, haul, and layup skins · vessel zones and labels change; the packet shape does not.
What Berth covers
Onboard baseline, hand back compare, haul interchange, and seasonal layup in/out. Timestamped photos, tags, and PDFs for deposit holds and broker files.
Out of scope
Navigation, marina slip billing, maintenance ERP, USCG licensing, and certified survey. Berth documents condition at hand back; it does not replace those stacks.
Berth skins
| Phase | Skin | Use case | Status |
|---|---|---|---|
| M1 | bt_charter | Bareboat check-in · guest return · compare PDF | Live |
| M2 | bt_rental | Peer rental · platform-adjacent holds | Roadmap |
| M3 | bt_haul | Transport captain interchange | Roadmap |
| M4 | bt_layup | Winter layup in/out | Roadmap |
| M5–M8 | yard · service · marina · slip | Adjacent ops (not billing-first) | Planned |
Start reading (by job)
- Castoff discipline · Why baseline beats a camera roll, No return without baseline
- Release the hold · Release with a packet, Deposit chronology
- Know the lane · Marina software vs handback packet, Platform claim vs your archive