User guide

A trip: before, during and after

On this page: The life of a trip · Plan a trip · The next-trip card · Prepare · Start a trip · While you are out · For assistants · Positions · End trip · Log a trip · Engine hours on a trip · The trip page · Tell someone · Edit, Cancel and Restore · Places and people

A trip is one sail, from planning it to writing it up. This chapter follows a trip through its life, and covers the two kinds of record a trip leans on: places and people.

The life of a trip

A trip has four statuses. Each changes only through the action named for it; no form has a Status field.

StatusHow a trip gets thereWhat you can do next
PlannedPlan a tripPrepare it, Start a trip, Edit, Cancel trip
UnderwayStart a tripAdd to log, Something's wrong, End trip, Cancel trip
CompletedEnd trip, or Log a trip for one already overEdit, add engine hours, record a problem afterwards
CancelledCancel tripRestore trip (it comes back as planned)

The Logbook page has Start a trip, Log a trip and Plan a trip. The Record menu in the top bar and the "Record something" row on Today offer Start a trip and Log a trip until a trip is underway; during a trip they offer Add to log, Something's wrong, Add a reading and Add a document instead.

Plan a trip

Plan a trip asks only what planning needs.

Save trip makes a planned trip and opens its page. The title is made for you: "Hankø → Son · 4 Oct 2026" when From and To differ, else "Trip · 4 Oct 2026". The year is always in it, because a title is stored and read in later years.

The planned time is on the boat's clock, the time zone in Boat details. A trip planned for 4 October on a phone in another time zone is still on 4 October where the boat is, and Today and Start a trip read the day there.

The next-trip card

Today shows a Next trip card for the earliest planned trip whose day, on the boat's clock, is today or within the next 7 days. It is not shown while a trip is underway.

The card shows the title, the day ("Today" or "Monday 5 Oct"), the route when the title does not say it, and the preparation summary (below). Open trip opens the trip's page; on the trip's day the card also has Start trip. A trip with no date, or whose day has passed, is not on the card and is started from its own page.

The card is not a Today fact, because a trip being prepared is not something wrong with the boat. It reports counts and never says the trip or the boat is ready.

Prepare

A planned or underway trip's page has a Prepare section.

On a completed or cancelled trip the section is Prepared: only what was started or made, nothing to start, and nothing at all when nothing was.

Start a trip

Start a trip says you are leaving now.

Start trip saves without waiting for the position, then shows Today.

One trip underway at a time, on one device. The form says "You're already out on <title>. End it first." Two devices offline can each start one; after sync both are underway, and either can be ended from its own page.

While you are out

Today's Trip in progress card says "Out since 14:30" and has End trip. After 24 hours it asks "Still out on <title>?" instead, and cannot be dismissed. With a departure checklist on the boat, the card links to it.

Add to log writes an entry in the trip's log.

A new entry is saved as an Observation. Editing an entry offers Observation, Weather and Note; an older entry of another kind (Departure, Arrival, Position, Engine hours) keeps it.

Something's wrong asks What's wrong?, High priority and the position. It saves a problem (High when ticked, else Medium) and a log entry at that moment and position pointing at it. What happens to the problem afterwards is in Work: plans, jobs and problems.

For assistants

If you are an assistant connected to LazyJack, these are the rules for trips.

  1. A trip that is over is one call. voyage_complete carries the trip, its readings and its defects together; do not create the readings or the problems separately first. For a trip that is planned or underway, voyage_complete with its id ends it.
  2. Engine hours are readings. They go in readings (or reading_record with the trip's voyageId), never in an entry's text or the trip's notes. A reading may not be lower than the latest accepted one; read reading_list first and tell the owner if their number is lower.
  3. Something found wrong on a trip is a problem (defect_create with the trip's id and, when known, the equipment), not a log entry alone and never a change to the equipment's status.
  4. A position is only what the owner gave. Never guess coordinates from a place name; waypoint_list has the saved places and their positions. A place the owner names that is not saved is created only after asking.
  5. People are records. crew_list first; a name that is not there is a new person, and the owner is asked before one is added.
  6. Tell someone is the owner's. You may read a float plan and remind the owner of an Expected back that has passed; you do not file or close one unless asked.
  7. Never say the trip or the boat is ready. Report what Prepare shows: which checklists are done or not started, what the kit is missing, what is in Do first.

Positions

Start a trip, End trip, Add to log and Something's wrong ask the position with one control and four choices.

ChoiceWhere the position comes fromCan the phone replace it later?
Use my locationThe phone's location serviceYes, by a more accurate fix from the same request
Saved placeYour places: home first, then favourites, then nearest (or by name)No
Pick on mapA pin you place and dragNo
Enter coordinatesText such as "59° 54.1′ N, 10° 44.6′ E" or "59.9, 10.74"No

Saving never waits for the position. A form saved before the phone has a good fix saves with what it has, possibly nothing, and the app keeps asking. When a better fix arrives the record is updated: "Position added." or "Position updated.".

A position near a saved place shows the place's name. Near is within 300 m; a phone fix counts only when it is accurate to 300 m or better, while typed coordinates, map pins and places are exact. The name is worked out when shown, never stored.

Save as place is offered when no place is within 300 m and you did not choose one. It asks a name, Favourite and Home, and the place is made when the form is saved (with no name, none is). From Start a trip or End trip it also becomes the trip's From or To.

LimitValue
A position is "at" a place within300 m
A phone fix is matched to a place only if accurate to300 m or better
The phone is asked for at most15 seconds
The request stops early at a fix accurate to50 m

The map

Pick on map opens a map with sea marks under the four choices. Tap to place the pin; drag it to move it. It opens on the position already chosen, else the phone's, else the home place, else the last position logged, else the whole world. A pin behaves exactly like typed coordinates.

The map needs a connection. With no map tiles loaded, offline or after 5 seconds, it is covered by "Map unavailable offline", offering Use my location and Saved place. A pin already placed stays chosen.

While the boat has no home place, the map offers Set as home marina: it fills Save as place with "Home marina" and Home ticked, and nothing is made until you save. Not now hides it for the session.

When location does not work

What you seeWhat it meansWhat to do
Getting position…, or "· improving…"The phone is looking, or has a rough fixSave when you like; the position follows
No position fix yet. You can still save.15 seconds passed with no fixSave, or choose another way
Your position is not available right now.The phone could not get a fixSave, or choose another way
Location is turned off for this app…Location permission was refusedAllow it in the browser or phone settings; each form asks again
This browser cannot share its position here…No secure connection, or no location in this browserUse a saved place, the map or coordinates

End trip

End trip, on Today's trip card and the trip's page, wraps up a trip that is underway.

End trip saves and opens the trip's page.

Log a trip

Log a trip records a trip already over, in one form and one change. Date cannot be after today. Left at and Back at are optional, and a departure time is kept only with a return time. It goes from and back to the home place, with Change for From and To. Who came picks people, Engine hours and Anything wrong? work as in End trip, and Notes is optional. Save trip opens the new trip's page.

Engine hours on a trip

Engine hours typed on a trip are readings, the same ones Boat care and Today show; the rules are in How LazyJack thinks. The trip decides when each is dated.

Where the hours are typedThe reading is dated
End tripAt Back at
Log a tripAt Back at, else the end of that day on the boat's clock, never later than now
Add to logAt the entry's time
Add engine hours, on the trip pageAt the trip's end, never later than now

Add to log checks the value at once: not lower than the reading before that time, not higher than a reading taken later, not for a time still to come. With hours and no text, only the reading is saved and the button says Save hours.

A wrong reading is corrected, not edited. A reading's row on the trip page opens Correct engine hours; the old value stays in the history as voided. Hours an older entry or trip carries from before readings are shown as a note, never as a reading.

The trip page

The header has the title, one line with the date, route, duration and "Aboard: …", and the main action: Start a trip when planned, End trip when underway. The pencil is Edit; More holds Cancel trip or Restore trip, and Archive or Delete. A From or To that is a saved place links to it. Below, in order:

Tell someone

Tell someone records who ashore knows you are out and when you expect to be back, on a planned or underway trip. It asks Contact name and Contact phone (optional), Expected back (required) and a Note; File saves it. LazyJack sends nothing to the contact: telling them is yours to do. A filed one has Change and Mark arrived.

Once Expected back has passed without Mark arrived, the trip page says "Overdue" and Today lists it under Do first. Ending the trip does not mark it arrived; press Mark arrived when you are back.

Edit, Cancel and Restore

Edit trip changes the title, Who's aboard, Started, Ended, From and To, with Weather and Notes behind More details. It has no status and no engine hours.

Cancel trip, for a planned trip or one underway, is in the More menu of the trip page and of its row on the Trips list. It asks first; the trip stays in the logbook as Cancelled, with its log. Restore trip brings it back as planned. Archive and Delete follow the usual rules; deleting a trip deletes its log.

Places and people

A place is a saved position with a name, made mostly with Save as place. The Places page has no navigation item; How LazyJack thinks lists its ways in, among them "Manage places…" at the end of every place list.

A person is someone who sails with you: Name, Role, Phone, Email, PLB / EPIRB id, PFD aboard and Notes, on the People page under Logbook. A name typed into a trip form becomes a person when the form is saved.

A place or a person that a trip which is not archived still uses cannot be deleted.

Not in this chapter

The ideas behind the app: How LazyJack thinks. Setting up the engine and its meter: Setting up the boat and engine. Problems and jobs after the trip: Work: plans, jobs and problems. Kits: Inventory and To buy. Attaching documents: Documents and papers. Changes refused at sync: Troubleshooting sync. Logging a trip through an assistant: Assistants.

This chapter as Markdown · llms.txt