Handling delays or missed changes
If a watch change happens later than planned, you can record that as a delay. This tells WatchKeeper that the handover boundary has moved and lets the app recompute the next watch timing from the updated schedule state. That is usually the best option when the crew still intends to follow the same schedule, just a little later than expected.
If a change was missed entirely, start by checking who is actually on watch now and what the crew wants the next correct state to be. In some cases, a delay is enough. In others, you may need a swap, pause, or another targeted adjustment. The best approach is usually the smallest change that matches what really happened onboard.
WatchKeeper stores these updates as schedule overrides rather than rewriting the base trip. That matters because it keeps the original plan intact while still allowing the live watch state to reflect reality. It also helps the app recover correctly after a restart, since the current state is rebuilt from the saved schedule, the recorded changes, and the current time.
Common Situations
- A handoff happened late but the rotation should continue.
- The next crew member did not arrive on time.
- An alarm was missed and the schedule needs to catch up.
- The crew wants to delay the next change rather than rebuild the trip.
Best Practices
- Record the smallest change that matches the real situation.
- Use a delay when the schedule is only running late.
- Check the current and next watch after making an adjustment.
- Confirm the crew understands whether the updated timing should continue forward.
Delays and missed changes are normal on real passages. The goal is not to keep the schedule perfect on paper. The goal is to keep it clear, recoverable, and trustworthy for the crew in the moment.