Recovery release 1.33.1 / step 6 of 6

Design logbooks in the browser

New empty structures, separate from saved operational evidence.

Use a named account with Build and import logbook designs permission. Open Setup & builders, Logbook designer, or Logs > Design logbook. Administrators have this capability automatically, but administrator status is not required. Search the saved logbook library or include archived structures. Selecting a saved book is read-only; it does not open entry history or alter fields, evidence, assignments or access. Record daily work in the operational Logs workspace.

Four clear steps

Select New logbook. Choose Vessel operations, Activity only, Issues & activity, Weather & SVP or Blank custom logbook. Presets use the native log definitions. Next, enter a descriptive Name & purpose. Changing a previously applied starting point requires confirmation before replacing unsaved sections; the name and purpose stay.

In Sections & fields, select one section and one field at a time. Add a standard or custom section, rename, remove or reorder it. Add fields using Text, Number, Date, Time or Dropdown; set a unit/label and whether every entry requires it. Dropdown choices must be distinct, one per line. Keep 1–25 sections with 1–40 fields each, subject to the request-size limit. Field IDs stay stable through renaming and reordering in this unsaved design; technical identifiers are available in collapsed details. On a phone, use the compact selected-field selector instead of a long expanded list.

Review, then deliberately create

Continue sends a read-only review of the exact design to the hub. In Review & create, inspect all section names, types, units and requirements. The confirmation starts unticked. Only Create reviewed logbook saves one new empty project logbook. Back returns to editing and invalidates the review and confirmation. There is no published-template revision or background draft saving for a logbook design.

Keep old definitions and evidence intact

Saved structures are fixed. This feature does not edit an existing logbook, copy entries, corrections, source documents, reference pictures, issue assignments or vessel grants. The new book uses the existing project-log access rules. The browser Setup & builders import for .ajlogs creates definitions only; operational entries, history, references and media remain excluded. Original-workbook import and offset-table setup remain advanced/native tools. Units are descriptive labels, not conversions or operating limits. The operational entry workflow still supplies event time, author identity, notes, corrections and personal issue acknowledgements. Reviewing or creating a design never acknowledges an issue or approves an operation.

Online editing and uncertain results

The designer is NOT an offline draft. Unsaved text exists only in the current tab. Background rendering preserves it, but closing or reloading discards it; changing account/project clears it. Navigation is guarded while editing. Save controls lock while waiting. After a lost response, keep the editor open and use Retry unchanged request. The same committed request returns the same logbook, not a duplicate. A different request is a new action. Receipt metadata does not contain the design text and cannot reconstruct a closed form. Check saved Logs before making a new creation after uncertainty.

Navigation polish

Browser and Fleet sidebars now have consistent horizontal icon slots, left-aligned labels, compact row spacing and a clear selected edge/background, including on narrow screens. Native Admin also uses explicit left alignment and smaller group headings. The sidebar still scrolls independently and is never automatically replaced by a dropdown merely because the window is short. Use Hide sidebar / Show sidebar on wide screens, or Menu / Close on phones. The operational destinations and permission rules are unchanged.

This is a first targeted usability pass, not a claim that every screen has been redesigned. General-purpose tasks arrived in 1.34.0. Navigation and session continuity arrived in 1.34.1; daily department/shift handovers arrive in 1.34.3. Task-specific checklists remain the next separate increment. The six recovery steps through 1.33 are reconstructed, not byte-identical original archives. Network settings and server-start behaviour remain unchanged. Windows, phone/live-network and persistent-browser-storage acceptance still require testing.