Handovers / daily work and exceptional tools
Shift continuity and advanced handover tools
Subject overview and one combined journal
Handovers opens on By day / subject. Subjects use the existing saved department plus subject/vessel/site label. Select the same group to navigate its operational days, read published shifts or resume your own private notes. Current roster changes do not relabel earlier records. My shift still offers assigned-day cards, automatic periods and cross-date saved-note continuation.
Daily / shift creation puts the department, subject, shift pattern, full period and named/department recipients together, then Write handover opens the normal reason-free editor. It creates your own personal handover; it does not assign authorship to another person. People & shifts manages the separate recurring roster for authorised leads, with a return to retained creation choices. Manual irregular periods and other handover types remain available.
Export N published handovers to PDF compiles all current permitted publications in the selected subject/date range, with a clickable chronological index. Private wording is excluded even for the author. Historical revisions, visitor/drawn signatures and attachment bytes remain in their existing separate views/exports. Counts refer to publications, not crew attendance or task completion. Changed evidence or access refuses the old selection rather than releasing a partial report. See Handovers Help for scope and limits.
Use My shift for everyday notes. Keep source preparation, revision review and recipient analysis separate from normal saving.
The everyday route
Handovers → My shift → Edit notes → Save & close saves a personal private draft. Finish handover saves the current notes and first publication atomically. Ordinary assigned-daily creation, editing, saving and first finish need no typed reason or confirmation checkbox. Automatic actor/time/action/version and change history remain attributable.
A lead assigns people to a department’s reusable shift pattern once. Two 12-hour shifts are the default; existing automatic overnight periods, other patterns and time-basis labels remain. Several people on one shift have separate authorship and private drafts. There is no shared live text editor, automatic crew-wide draft access or automatic incoming signature.
Opening or moving to the next operational day creates nothing. The device’s Today can differ from the operational day of a night shift. Current assignments are not a historic roster. Changes to setup cannot rewrite previous records. Every finished handover still has its exact saved author, dates, location and audience.
Saved notes and changed shift setups
Continue saved notes on My shift gives direct access to this department’s private daily drafts across dates and sites. It is independent of the viewed operational day. Continue my notes retrieves the saved record again and keeps its original dates, audience and identity. It does not create another draft or substitute today’s setup. The most recently saved draft is shown first, with older drafts in an expandable list.
The day’s permitted publications are grouped by exact saved period, time basis and site. Other saved handovers holds records that differ from current shift proposals. A changed site, renamed shift or missing reusable setup does not hide earlier work or rewrite its content. Current assignments are separate from saved authorship. A missing published handover is not proof of missing private work or an incomplete crew.
Refreshing clears the previous draft and day snapshots before reading again. Interrupted or invalid responses do not leave old actions available. Opening a saved draft rechecks ownership and create permission; the existing save/finish conflict and unchanged-request retry remain unchanged.
Previous-shift reference and access
The simple notes screen offers accessible publications ending at this shift start in the same stated time basis. Choose the author when more than one matches. An existing linked previous revision stays pinned; missing or revoked access does not substitute a newer version. Reading only displays saved public wording. It does not copy sections, acknowledge receipt or assert that old work occurred again.
Your own saved drafts across dates in the selected department are directly available in Continue saved notes. The broader cross-department list remains under More handover tools → Your saved daily drafts. Other people’s private drafts never appear simply because they share a department or shift. Existing current and historical-publication access rules still apply, including current department membership and each revision’s saved audience.
Manual daily continuation
For irregular periods or deliberately selected historical sources, the older department/day board and Start daily handover / Start next shift remain under More handover tools. They retain explicit period/source review and their existing creation rules. The selected publication, not whichever author published last, determines the predecessor. A carried section is labelled as earlier published wording, not new work. Once its personal daily draft exists, Edit my notes opens the simpler note-save path; Advanced draft editor remains available for deliberate metadata/audience changes.
Prepare from previous
Use More actions → Prepare from previous for a separate ungrouped private copy, commonly a full-hitch handover. It is not needed to start a normal assigned shift. The existing guide is Sources & title → Sections & order → Review & create.
Select up to twelve accessible active published handovers, then explicitly choose sections and their copy order. No sections are selected automatically. Read exact publication displays the chosen saved version, never an author’s newer private draft. Changing sources or hiding the reference invalidates delayed reads. A newer source publication must be deliberately reselected and reviewed.
The hub combines only selected historical wording. Blank sections add no text; overlong combinations are rejected rather than truncated. A reason and explicit confirmation remain for this exceptional reviewed copy operation. A successful copy has its own private identity and blank period, location and audience; no publication, acknowledgements or signatures are inherited. Later source changes do not overwrite it. Review is not creation.
Published revisions and incoming acknowledgement
Incoming publications under More handover tools shows accessible active publications by other authors across dates. Pending/acknowledged filters describe your account’s acknowledgement state, not unread messages or compulsory signatures. View-only access can allow reading without signing.
The publication reader shows all seven note sections and exact full periods. Reload retains the displayed revision. A newer revision is opened explicitly. Revision history compares chosen earlier/later publications, including text added/cleared and selected audience identities. It never compares another author’s private draft. Two separately authorised reads are not an atomic live snapshot; mismatched states are refused.
Incoming acknowledgement remains a separate personal reviewed action. Reading, comparing or finishing the outgoing handover does not record it. The hub rechecks current revision and permissions. Lost-response retry retains the same request; it must not be replaced with a new signature request on somebody else’s behalf.
Corrections after issue
To correct a finished handover, the author starts a private revision through the saved-record tools. Ordinary note changes can be saved using the simple editor. Reissuing still uses the separate saved-draft publication review and an explicit change summary. The old publication and its acknowledgements are not rewritten; the new revision has its own evidence. Archiving/withdrawing and other exceptional lifecycle changes retain their existing reason and confirmation rules.
Recipient evidence
Authors can use Current recipients on the exact current publication. Search and status/source filters apply to current eligible accounts. People selected by name and department are deduplicated. Unavailable named selections, inactive departments and retained acknowledgements outside the current eligible list are separate evidence, not replacement recipients. Saved acknowledgement names/times are distinguished from current account details.
Recipient counts are not proof of delivery, reading, shift attendance, required signatures or crew completion. Refresh checks the same publication and clears the old snapshot. A newer publication needs an explicit saved-record reload. No automatic reminders or permission changes are added.
Save state and project boundaries
Unsent notes, reasons and source choices are memory-only until the relevant explicit save. This is not offline autosave. A conflict preserves the newer hub state; an uncertain result retains the same in-tab retry. Save/Finish do not mark Tasks complete, approve equipment or sign for incoming users. Preserve unfinished browser work during updates.
These instructions describe the hosted browser interface. They do not update a native vessel installation, enable vessel/cloud synchronisation, establish independent backup recovery acceptance or change guest/admin login behaviour. UI31’s subtle project-active indicator reports recent account connection presence. It is not a shift roster, attendance evidence or a signature; this update leaves it unchanged.
Files follow their saved publication
The simple daily editor can save optional photos/files together with notes. Each publication retains exact immutable file references. The incoming reader, previous-shift reference and acknowledgement review may open those files using current access. Reading is not acknowledgement, and two people assigned to a shift do not share private drafts. New correction files remain private until reissue; old published files remain available to their authorised readers.
Revision comparison counts describe notes/audience, not file-content differences. Open each complete revision to inspect its attachment list. Prepare from previous copies selected wording only, not file bytes. A PDF lists the publication attachments but does not package them. After using attachments, keep UI33 or later; see Handovers Help for size, format, transfer and rollback boundaries.