Wavelink 1.34.19 / focused Task details

One Task. One focused section.

Open a general Task and use Overview, Checklist, Work & review, Discussion, Linked records or the authorised Manage task section. Next action opens the right section before its existing form. Inventory-verification tasks keep their scoped workflow.

Section changes do not save results, submit or approve work. Hidden steps still count. Same-task/session refresh retains temporary view choices; account/task changes reset them. Finish or cancel an open form before navigating.

Original files folder organisation is future work. Existing source files, revisions and exact source links are unchanged. Preserve unsent work, back up and update in place; do not uninstall first or clear browser storage.

Wavelink / 01

Get started

A shared workspace for your team

Wavelink brings checklists, logs, inventory and toolbox talks into one shared project workspace. One Windows PC runs the hub. Team members use that hub from their phones, tablets or other computers.

In Admin, use the scrollable grouped sidebar. Hide sidebar and Show sidebar let you choose a compact Workspace selector when needed. Read Find your workspace for the command locations.

Set up the hub

1. Run the Wavelink installer on the Windows hub PC. Use a 64-bit Windows 10 or 11 computer and an internet connection for setup. Follow your organisation’s software approval policy.
2. Open Wavelink Admin and choose the project. Create its first administrator if new; otherwise use your current project account.
3. Open Settings, review the hub name and project defaults, then save. Under Users & access, add a named account for each team member.
4. In Hub & phones, choose the team-facing PC IP, select Save address, then Start server. Share the saved address or QR on the approved local network.
5. Create a practice checklist and check that sign-in, recording, synchronisation and any required approvals work before operational use.

Join an existing hub

You do not need to install another hub. Connect to the team’s network, open the address supplied by your administrator and sign in with your own account. From the Operations dashboard, choose Checklists or Logs. Keep the hub PC running and connected while the team needs to share or synchronise work.

Your role

Wavelink 1.34.10 / workspace continuity

Find your workspace

One browser workspace; the familiar desktop Admin sidebar.

Use the main sidebar

Open Home, Checklists, Logs, Fleet & vessels, Inventory, Toolbox Talks, Handovers, Tasks, Maintenance, Certificates or Calendar from the left-aligned browser sidebar. Named administrators also have Administration. The sidebar scrolls independently; it is not replaced by duplicated Home cards.

Fleet stays in the application

Choose Fleet & vessels. Its vessel, manifest and access views appear inside the same main workspace, with the project header and sidebar retained. It uses the current valid account. Asset-custody, manifest and administration shortcuts use the same workspace. Returning to Fleet retains its selected view and filters during this page session.

Keep open work safe

Save or close an open Fleet form before switching workspaces. Navigation and browser Back cannot silently discard it or submit it. An expired session opens the main sign-in; an in-memory Fleet form can resume after the same account signs in. Another account cannot adopt that open form. This is not an offline Fleet draft store: reloading or closing the page can lose unsubmitted wording.

Expand logs without leaving

In a logbook, choose Expand view to hide the surrounding sidebar and project strip in place. Your account, logbook, section and filters remain. Choose Return to normal or press Escape when no entry dialog is open. A separate log window is optional, not required for expansion.

Wide screens, phones and desktop Admin

Use Hide sidebar / Show sidebar on wide browsers, or Menu / Close on narrow windows. Desktop Admin retains its own left-aligned sidebar and explicit controls. Its deliberately selected Open browser workspace command still opens a browser; it does not transfer a native credential into a browser.

Account, connection and boundaries

Use Account for account actions and help. Connection & saves reports saved/local/uncertain work; Fleet also reports its live connection. Current permissions are checked by the hub. New navigation does not grant access, synchronise different hubs or fix network reachability. Daily department/shift handovers, task-owned checklists and scratch readings are available. Fault Reports now adds a separate report-to-closure workflow; evidence uploads and automatic Task creation remain future extensions.

User instructions

Connection & saves

Know what is local, confirmed or still uncertain

Open Connection & saves above the main browser workspace or Fleet portal. Opening this panel, checking the hub connection or reviewing a warning does not submit a form or finish work.

Connection is not a save confirmation

Connected to hub means this tab recently received a complete hub response. Not recently checked means that observation is older than 30 seconds. Hub not reachable can mean a stopped server, blocked network or unreadable response; it is not a diagnosis of internet availability. Wavelink does not test the internet. Local use needs access to the running hub, which may work without internet. Browser network and live-update indicators do not prove a save succeeded.

Work on this device

The main workspace separates queued checklist changes, conflicts, checklist drafts, log drafts, operation forms and a new-checklist draft. A form says Saving draft on this device while storage is pending and confirms the local draft only after that write completes. Local storage is tied to the existing browser profile and hub address. It is not a hub backup.

Only already-queued checklist changes retry automatically. Log, maintenance, inventory and other operation drafts still need review and an explicit Save. Opening the panel or using Check hub connection does not send them. A photo held in a draft is not hub evidence until its containing submission succeeds.

When the save outcome is uncertain

A timeout, lost response or server error can happen after the hub saves an action. The panel keeps a local request receipt marked Uncertain save result. Reconnecting, loading the record or successfully saving another action does not silently clear it.

1. Keep the original page and draft. Do not immediately create another receipt, placement, maintenance completion or stock movement.
2. Open the linked saved workspace and inspect the intended record and its history. Close or keep any existing edit form before using a navigation link.
3. Where the original form supports a stable operation ID, an explicit unchanged retry uses that same request identity. A confirmed response can resolve the receipt. A changed request is not the same retry, and an access/conflict rejection of a retry does not prove the first attempt failed.
4. When manual checking is necessary, choose I checked this result... only after checking the saved record. This records Reviewed — outcome not verified, not “Saved to hub”, and makes no operational change. It releases the local warning gate for a different action. Ask a manager when the physical or saved outcome cannot be established.

Wavelink blocks a different new request to the same unresolved action/target until review. It also prevents a second concurrent submission of the same request. Forms lock during a submission so a pending edit is not silently replaced by the response.

Fleet is still online-only for forms

Fleet receipts, placements, manifests and vessel-log forms need an explicit online save. They are not offline drafts or an automatic outbox. Fleet keeps request metadata in the current tab’s session storage, which can survive a same-tab refresh but is not durable form recovery and may be lost when that tab or browser session ends. Keep an uncertain form open and export its receipts before leaving.

Recovery, access and limits

The journal records action identifiers, request status and device-clock timestamps, not passwords, tokens, full forms or evidence. It is not a server audit trail or proof that a physical operation happened. The panel shows receipts scoped to the signed-in account and project; exports should still be handled as internal information. Main-workspace recovery exports include the receipt metadata with existing supported drafts. Fleet exports receipts only.

User instructions

Review effective account access

Read the current policy before changing it

Open Users & access → select a user → Review effective access… as a current administrator. This is a read-only view: it does not enable an account, change permissions, acknowledge alerts or open private work. Disabled/deleted accounts are shown without effective access; retained configuration is not erased.

The review combines account status and role, project-wide workspace capabilities, active departments and effective department-head appointments, Fleet site roles, separate vessel log permissions and the effective rights for each linked logbook. View dependencies and the private-task backup safeguard are reflected in the result. An administrator's full access is clearly distinguished from a project user or a vessel-only account.

Read the scope correctly

Project-wide permissions are not narrowed by department membership or a vessel filter. Private task membership, named reviewers, ownership, record state and approval rules remain additional checks. A capability shown as granted does not assign the person to a task or authorise a physical operation.

Vessel-only accounts have no access to unscoped project workspaces. A logistics role does not automatically grant logbook rights. Review the site's separate log permissions and the linked logbook's effective capabilities; a withdrawn link or inactive site prevents vessel-only log access. Administrators retain project-wide log access. Archived status and site state remain relevant to particular actions.

Inactive-site logistics role capabilities describe retained role rights, not a permission to make a new movement on an inactive site. Existing workflow and active-site validation is still authoritative. A temporary sign-in lock is shown separately; the review does not infer that every existing session has been revoked.

Copy or save an internal summary

Copy internal summary and Save internal summary… read current permissions again. Export also rechecks after choosing a filename. Revoked administrator access clears the stale review and prevents a new summary. The UTF-8 .txt file contains account/access information, not passwords, password hashes, tokens, task contents or operational evidence. Protect it as internal information. It is a snapshot, not a permission grant, certified audit record or proof of continuing access.

Full database backups are different from operational reports

The review shows actual full-backup eligibility, not just the permission checkbox. Existing policy allows an appropriately permitted named project user to download a database only while the private-task safeguard permits it. When any private task exists, only an administrator can download the full database. Vessel-only accounts cannot export it. Current account state is checked again before delivery, together with private-task presence in the actual snapshot.

Use Backups & support → Save full database backup… in Admin or Workspace menu → Full database backup (sensitive)… in the browser. Both require deliberate acknowledgement of an unencrypted, unfiltered copy. The browser first checks current eligibility without downloading a database; opening the warning is not a download. The server requires an explicit acknowledgement on the download request and does not cache the response. An old client requesting /api/backup without that review receives a warning rather than a database; reload the app without clearing drafts.

Full backups contain saved records, accounts and password hashes, private work, permissions, original documents and stored evidence. They do not include active sessions, browser-only drafts, unsent photographs, unsaved editor changes, external files not stored in the database or HTTPS private keys. Password hashes are not plaintext passwords but still require protection. Permission changes cannot recall copies already downloaded. Check the browser download and the actual saved file: a download request is not proof of a successful disk save or a usable restore.

History-bearing .ajproject transfers, including selected workspaces and their dependencies, remain administrator-only, unencrypted and not recipient/vessel filtered. They are not a substitute for an operational report. This update does not add encryption, automatic redaction or new vessel-scoped workspaces. Review report contents and intended recipients before sharing.

Full-database downloads require a named, current account. Shared legacy sign-in codes cannot download them; sign in with an eligible named account instead.

Wavelink / 03

Choose the hub network address

Use the interface your team can reach

A survey PC can have several network interfaces. Choose the IP on the approved network used by phones and other operators, not a sensor-only interface. The address is saved separately for each project.

1. Synchronise or export unsent work on every device. Stop the hub server; keep the existing project and data folder.
2. Open Admin → Hub & phones. In Phone IP address / hostname, select a detected address or type the correct one. A plain IP is enough. The app adds the saved HTTP/HTTPS protocol and port.
3. Choose All local interfaces to keep the usual listener and share just this chosen address. Choose Selected IP only to restrict the listener to one numeric IP assigned to this PC. A hostname requires All local interfaces.
4. Choose Save address. The displayed address and QR change together. An unsaved edit is labelled Preview; an invalid edit clears the previous QR. Copy saved address uses only the saved setting.
5. Start the server, then use the saved address or QR on the team devices. The browser menu’s Connect another phone uses the same saved address.

Changing networks, ports or secure access

Refresh addresses updates the choices without replacing your selection. A saved IP is not silently changed when another adapter is detected. If Selected IP only is unavailable, start is blocked with an explanation rather than switching to a different interface.

Set the listening port and HTTPS certificate/key under Settings while the hub is stopped. A pasted complete URL must match those settings. Changing the IP does not reconfigure Windows networking, firewall rules, routes or certificates. Have IT reserve a suitable IP and ensure the devices can reach it.

User instructions

Use the Operations dashboard

Nine workspaces in the same project

Home gives Checklists, Logs, Tasks, Maintenance, Inventory, Toolbox Talks, Certificates, Calendar and Fleet & vessels equal prominence. Each opens the selected project’s own saved work. Use the navigation bar to switch, or the AJ logo to return Home.

Quick access includes approvals, original documents, local drafts and Help. Unsent work shows checklist changes, log drafts and Inventory/Toolbox forms for this account and project. Opening a workspace does not create, submit or discard work.

On a laptop, scroll the Admin sidebar to reach additional workspaces. Hide sidebar offers a compact Workspace selector when deliberately chosen. Browser updates keep the scroll position and do not replace open forms or a selected group of inventory rows. Native Admin uses explicit Refresh.

Compact mobile home

The nine workspace cards use equal space in a two-column layout. The icons and labels identify each area. A saved-work notice continues to show any local drafts that need attention; opening a card does not submit those drafts.

Fleet & manifests is available in the Admin Operations group and through the browser’s Vessels & manifests link. Opening Fleet from the main navigation reuses a valid project sign-in; opening the portal directly may require sign-in. Project-wide workspaces remain unchanged for existing project users; explicitly vessel-only accounts use the restricted portal instead.

Vessel-specific Logs are available through /fleet → Logbooks only after an administrator links the book and grants the account separate site log permissions. Existing project-wide accounts retain their broader access. Read Use vessel-specific logbooks and Set vessel log permissions before commissioning restricted accounts.

Fleet is a main workspace

Fleet & vessels is available in the main browser navigation and as a full Home card, alongside Inventory and Logs. In Windows Admin, use Operations → Fleet & manifests. There is no need to find a small shortcut at the bottom of Home.

Save an open form or use Keep draft & close before switching. The browser carries the current sign-in to Fleet in the same tab and checks it against the current project. Unsent project drafts are preserved, not submitted. An expired or invalid sign-in requires signing in again. Project-wide users can return using Operations home; vessel-only users keep their restricted Fleet workspace.

Needs attention

Above the nine workspace cards, Needs attention summarises your accessible tasks, dated maintenance, certificate dates and assigned log issues. Project administrators also see received equipment groups awaiting placement. Project-only operators are not given Fleet access, and vessel-only accounts keep their separate portal.

Tasks distinguish open work, overdue dates, items awaiting your review and unread updates. Maintenance shows overdue work and work due within seven days, with undated open work identified separately. Completed orders with a blocked recurring follow-up are counted and linked separately as follow-ups needing review; a completion does not disappear merely because the next order cannot be planned. Certificates use their saved reminder window; an unrecorded expiry is not described as valid.

The summary is read-only and normally refreshes every 30 seconds while Home is visible. It shows a limited preview and links to the authorised saved records. A connection or permission error shows unavailable, not zero outstanding work. The existing unsent-work panel remains separate. Counts do not approve equipment or complete work.

Wavelink / 05

Choose and manage projects

A separate workspace for each job or project

1. Open Wavelink Admin and choose a project. Sign in with an enabled Administrator account belonging to that project.
2. Use Projects → New project… to create a separate workspace. Enter its name and choose a new or empty data folder. Open the project and create its first administrator.
3. To use a folder already on this PC, choose Add existing folder… and select the folder containing that project’s saved data.
4. To change projects, synchronise or export phone work first. Choose the project and select Open selected project. Confirm the switch. The current hub stops; sign in to the other project, then start its server.

Every project has its own checklists, logs, inventory, toolbox talks, accounts, departments and settings. An administrator in one project does not automatically have access to another. A project name in a job record is descriptive; it does not move that record into another project database.

Use a smaller project-selection window

The project list scrolls while the action buttons stay visible at the bottom. When the window is narrow, the buttons move into two rows. Resize or maximise the window for a larger list; restoring it keeps the controls accessible.

Select a project and choose Open selected project, or press Enter while the project list has focus. Use Tab to move between controls and Space to activate a focused button. Cancel or Esc closes the chooser without changing projects. Larger text can increase the minimum window size so labels remain readable.

What the phones see

The active project is named below the phone header. When a different project appears at the same address, the phone blocks automatic submission and shows Keep saved work & switch project. Review the change and sign in again. The previous project’s local work stays separately saved in that browser.

A missing project folder is not replaced with an empty database. Reconnect its drive or choose an available project. Your old combined history remains in its original project; it is not automatically divided into projects.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Wavelink / 06

Choose application and data folders

Know where the program and project records are saved

Setup now displays both locations. Changing only the application folder does not move project data. To relocate an existing project during setup, choose a different Project data folder and confirm the copy. Use a new or empty folder separate from the application and other projects.

1. Synchronise/export phone work, save a backup and stop the hub. Close other Admin windows and standalone hub processes.
2. In Admin, open Projects → Change active project data folder…. Choose a new or empty folder and review both locations.
3. Confirm the copy. The application verifies the database and switches the registered project to the new folder. Sign in again and check your records before restarting the hub.
4. Use Copy active data-folder path to confirm the location now in use. Future project settings, logs and records are saved there.

If a folder change does not finish

Keep the original project folder. Close Setup and all Admin/hub windows, then use the latest installer to try again. Choose a new or empty destination. If a folder left by a failed attempt contains files, keep it and choose a different empty folder; do not merge or delete project copies to force installation.

If access is still denied, ask IT to check access to the chosen folder. Do not disable security protection or switch Windows accounts to bypass the error. Once successful, use Copy active data-folder path and check your records. Use a reliable local drive; separate project copies do not synchronise.

Wavelink / 07

Manage user accounts

Access for the right people; attribution stays with their work

Open Admin → Users & access. Add a named account for each person and assign Technician, Supervisor or Administrator access. Department membership controls eligible item approvals; it does not grant administrator access.

New and reset passwords must contain 6–128 characters. The same minimum applies when a user changes their own password. Existing passwords continue to work without being reset. Prefer a longer unique passphrase and follow your organisation’s account policy.

Who can open the Admin console?

Any enabled Administrator account on the same hub can sign in. It does not have to be the first administrator. An account from a different hub will not give access. A deleted or disabled account cannot sign in.

Remove or restore an account

Deletion requires the exact User ID and a reason. You cannot delete your signed-in account. At least one enabled administrator must remain.

Accounts belong to the selected project. Setup-only profile imports create disabled Technicians: assign a password and reviewed role before enabling them. Full-project transfers retain imported administrator credentials.

Per-user operational access

Select a user in Users & access and choose Permissions… to control viewing, entry, correction and other actions. Read Set user permissions for the available choices. Administrators keep full access; restricted users use Technician or Supervisor roles.

For a person who must see only selected vessels, use Fleet & manifests → User vessel access and explicitly choose Vessel-only access. General project permissions and department membership are not vessel boundaries. Read Set vessel-only access before changing an account.

Wavelink / 08

Complete a checklist

Record the work, then synchronise

Confirm the active project before recording work. Dive number / Record number is optional. When it is blank, the app shows a stable REC- reference based on the record ID; it does not invent a dive number.

1. Choose New checklist / dive, select a published type and review its title, revision and stages. Enter the job details. Leave Live checklist off unless this record needs new items during the job.
2. Open Checklist document details and Read before starting to read the required instructions. Both panels start collapsed and retain your choice during refreshes. Tap reference pictures to enlarge them.
3. Open each applicable item. Record its result, required readings and notes. Use N/A only where appropriate, with a reason. A required-photo item needs at least one submitted photo for Complete or N/A; instruction pictures do not count.
4. Save and synchronise with the hub. Resolve conflicting or pending entries before treating the shared copy as current. For Awaiting approval, the assigned reviewer uses Review approval. An assigned checker may also approve their own saved work; checking never approves automatically.
5. Before finalising, resolve outstanding checks and approvals, synchronise participating devices and complete team readiness. Finalise a two-stage checklist in order.

When the connection drops

Answers in an already loaded record can be saved locally for reconnection. Creating records, approving and changing checklist structure need the hub. Local pending work is not part of the hub record or its backup.

Reports

Use Export PDF and review the reference, stages and finalisation status. An active-record report is not proof of completed or approved work.

See Record photographic evidence for camera and attachment steps, and Set up item approval for reviewer assignments. Follow any separate-review requirements in your organisation’s procedure.

Linked originals open under Checklist document details → Linked original documents. Retrieving them needs a hub connection and a compatible viewer.

Background updates keep the visible item and scroll position. Open reading panels keep their state; open forms are not replaced. A new page, section or full reload starts a fresh view.

Wavelink / 09

Build a checklist step by step

A guided route from an idea to a saved checklist

Open Admin → Checklist Editor → Builder wizard…. The wizard creates a new reusable type; it does not create a completed job record or change an existing checklist.

1. Starting point. Start blank, paste an outline, or choose a training example. In an outline, use one item per line and put # before a section heading. Examples require review and adaptation to your procedure.
2. Name & stages. Enter the checklist name, equipment/system and optional code. Choose one or two stages and name them. A new two-stage draft converted to one stage moves its items to that stage after confirmation.
3. Sections & items. Use Manage sections and Add item. Double-click an item or choose Edit item / options for readings, reference pictures, optional/required photographic evidence and a named or department approver. Select the applicable stage(s) for every item.
4. Introduction & details. Add explanatory text, warnings and overview pictures, or set document ownership and related procedure references. These optional panels are reading material, not completed checks.
5. Review & save. Preview the complete checklist and check reviewer setup. Leave Publish now unticked to save an unfinished draft. To publish, enter a change summary, confirm your review and select Save checklist. New records can use a published checklist.

Keep work without publishing

Back and Next keep your current wizard changes. At Review & save, save as a draft to continue later in the normal Checklist Editor. Cancel asks before discarding unsaved wizard work. The wizard does not save automatically while you move between steps.

The existing New / Generate, Example setups and advanced editor remain available. Publication records the signed-in administrator and applies to new job records only. Always follow the approved operating procedure.

Optional source links

In Introduction & details, choose Link original documents and tick the exact revisions already stored in the project. Add originals through the main Original documents tab first. Save the wizard draft or publish after review; no original is mandatory.

Wavelink / 10

Build a checklist type

Create a reusable template, not a completed record

1. Choose New / Generate. Enter the checklist name, equipment/system and optional code. Choose one or two stages and name them. To change the stage count of an existing type, create a new type.
2. Start blank or paste an outline. Alternatively, use Example setups → Use example as new draft. This creates a separate draft without replacing another checklist or copying completed answers.
3. Use Manage sections, Add item, Edit item, Remove and the move buttons to organise the tasks. Set each item’s stage(s), readings, units and required fields.
4. Choose Separate approval only for items needing a named or department reviewer. Photographic evidence can be Off, Optional or Required; it is separate from reusable instruction pictures.
5. Use Introduction & pictures before the list and each item’s Pictures & notes for guidance. Import checklist… accepts a prepared .ajcheck package. Preview the complete draft.
6. Choose Save draft to keep unfinished work. After review, use Publish revision, enter a change summary and confirm. Existing records keep their original checklist; use optional Live controls for eligible changes to one active record.

Examples and reviewer setup

Examples demonstrate sections, readings, stages and approvals; they are not complete or approved procedures. Replace sample wording and review every requirement. Use Check reviewer setup to see missing departments or enabled reviewers. Configure membership before publishing. The practice numeric range is a demonstration, not an operational limit.

Paste your own outline

Use Show text-format example in New / Generate. Enter one item per line and start section headings with #. The generator arranges your text; it does not write procedures or invent safety limits.

# Preparation
Record the approved procedure reference
# Handover
Record the handover evidence reference

Use Link originals… to connect the draft to saved source documents. This does not generate checklist items or substitute a file upload for operational review. Save and publish deliberate link changes for new records only.

Wavelink / 11

Checklist document details

Identify the reusable checklist and its published revision

1. In Checklist Editor → Library actions → New / Generate, enter the checklist name, equipment and optional code, such as AJ-MOB-001.
2. Open Checklist details to set the code, owner or department, procedure reference and purpose or scope. You can also edit the title, stage names and tools.
3. Choose Save details to draft, then Save draft in the editor to keep unfinished changes on the hub. After review, select Publish revision.

The Checklist document details panel starts collapsed. Tap or click its heading to open it, and tap again to close it. Your choice stays in place while the record refreshes. Opening another record or reloading the page starts with the panels collapsed again. The same document information is included in PDF exports, whether the panel is open or closed. Times are identified as UTC.

A prepared document import keeps source references separate from application authorship. Resolve its Import review points, including uncertain source revision or approval status, before publishing.

The collapsed document panel also shows Linked original documents when sources were selected. These identify the original file revision, not the app’s checklist revision. Expand the panel to open/save the file through the hub.

Wavelink / 12

Keep and link original documents

The source file and the working checklist remain separate

1. Open Admin → Original documents → Add original…. Select the file, enter its title, code, source revision and notes, then confirm permission to share the complete file.
2. Open / save original… downloads an unchanged copy for your normal viewer. Editing that copy does not update the library; use Add revision for an updated source.
3. Optionally select Checklist Editor → Document tools → Link originals… or the Builder’s Introduction & details step. Save and publish after review. Existing records keep their exact source revision.
4. Project users with access open Menu → Original documents or Checklist document details → Linked original documents. A hub connection and compatible viewer are required.

Supported files

Excel originals keep all worksheets, hidden tabs, formatting, formulas, pictures, VBA and saved connections unchanged. Wavelink does not run macros, calculate cells or refresh queries. A container check is not a malware scan or content approval.

Original file or working log?

Original documents stores the source without creating log rows. Use Logs → Logbook setup → Import workbook… or a prepared .ajlogs package for the separate reviewed log import.

Revisions, archive and removal

Add revision… keeps the earlier file. Archive / restore… hides a source from new selections without breaking saved links. Used by… shows those links. Permanent deletion requires an archived, unreferenced source, its exact title and a reason.

There is no embedded Excel editor or automatic offline file cache. Download an authorised copy beforehand. Reports list references without embedding files. Source and checklist revisions stay separate.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Wavelink / 13

Add introductions and pictures

Explain the procedure before and alongside the checks

Before the checklist starts

In Checklist Editor → Document tools → Introduction & pictures, add sections for purpose, scope, equipment, personnel and warnings. Each section has a heading, plain text and optional pictures. Select Information or Warning and arrange the sections using Move up / Move down. Choose Save introduction to draft, then Save draft.

Attach a picture to an item

1. Open Add item or Edit item. In Pictures & notes, enter the explanation and optional source section/step. Use Separate approval to choose an actual reviewer or department when required.
2. Choose Add picture… and select a PNG or JPEG. Add a useful caption and an accessibility description. Preview the image and check its labels remain legible.
3. Save the item, save the checklist draft and use Preview checklist to review the introduction and image placements. Publish only after the content has been reviewed.

The original photo is unchanged. A compressed reference copy is included with the checklist, its new records, reports and transfer files. You may attach up to eight pictures to an item or introduction section, with up to 30 distinct pictures per checklist. A checklist has a total picture-size limit; the editor explains when smaller copies are needed.

Earlier checklist annotations

The item editor uses Pictures & notes for instructions and Separate approval for reviewer requirements. There is no separate descriptive-role field to complete. Earlier role text remains under Original checklist annotations in the read-only preview and PDF report; it is not shown as an assignment on the checklist screen. Existing source wording, saved checks and approvals are not erased.

Read on a phone or in a report

The introduction appears under Read before starting, which starts collapsed. Tap or click the heading to read it, and tap again to close it. Automatic checklist updates keep your open or closed choice; they do not reopen the panel. Read the required instructions before work, then collapse them to return to the checks. Item pictures appear beside their instructions; tap a picture to enlarge it without losing an open answer or review form. The PDF includes the introduction and relevant pictures. Open and save the record while connected before relying on offline access.

Wavelink / 14

Record photographic evidence

Make photographs optional or required for selected checks

Choose the requirement

As an administrator, open Checklist Editor → Add item / Edit item → Photographic evidence (recorded work). Choose the requirement for that item, then save the draft and publish the reviewed revision.

Take or choose photographs

1. Sign in with your own account and open the item on the phone or browser. Under Photographic evidence, choose Take photo or Choose photos. The device controls whether it opens a camera or a file picker.
2. Select JPEG or PNG images. Review each thumbnail, enlarge it to check legibility and add an optional caption. Remove a mistaken selection before saving.
3. Enter the status, readings and note. Select Save check or Confirm complete, then confirm synchronisation. Merely choosing a photo does not complete the item.

A photo starts as a local draft. Closing the form retains that draft. Only saving and synchronising the check records it on the shared hub. Use View photo evidence on the item to inspect the attached photographs.

Existing checklist records keep their original requirements. A new published revision affects new records only. In an explicitly Live record, an administrator may configure evidence for a new or genuinely unused item; recorded items and finalised stages remain protected.

Wavelink / 15

Review and keep photo evidence

Approvals, offline work, reports and transfers

Review photographs and recorded values together

When the item requires separate approval, its assigned reviewer opens Review approval. Saved photos load beside the readings and technician’s note. Enlarge and examine them before approving. A failed photo load blocks the approval control; reconnect and reopen the review.

In Admin, use Records → Manage / Live edit → select an item → View photo evidence. Choose a stage when both stages have evidence. The native approval window also has Review photo evidence. A photograph alone never grants operational approval.

Changing the attached photos, a caption, an answer or a reading requires fresh approval. Earlier submitted image copies and changes remain in history; removing a photo from a later check does not erase its earlier evidence. Finalised stages cannot be changed.

Work without a connection

Open the app and checklist while connected before relying on offline access. New selected photos are compressed and saved with the local draft or queued check. They reach the hub when the check synchronises. Existing hub photos load on demand: reconnect to view one that is not already loaded in this app session. Approval decisions always need the hub.

Use JPEG/PNG files smaller than 20 MB and no larger than 24 megapixels. The app saves a resized copy, up to 1,600 pixels on its longest side and 500 KB per photo, with camera location metadata removed. Your original file is unchanged. Convert unsupported formats to JPEG before selecting them.

Reports and project handover

PDF reports include the current item photos, captions, submitting user and hub-received time. The received time is not a verified camera capture time. Full record/audit export retains earlier submitted photos as well.

Project backups and full-project transfers include saved evidence with its records. Checklist-only exports carry the photo requirement and reference pictures, not completed answers or submitted evidence. Transfer files are not encrypted; store and share them using your organisation’s approved method.

Wavelink / 16

Import a prepared work instruction

Review the source, not just the file format

1. Open the intended project. In Checklist Editor → Document tools → Import checklist…, select a supplied .ajcheck package. Review its title, item count, pictures and outstanding review points.
2. Confirm Import as a new draft. The new type is unpublished and does not replace any existing template or completed record.
3. Use Preview checklist, Introduction & pictures and each item editor to compare the text, photo placement and stage mapping with the controlled source. Open Original checklist annotations in the preview when earlier source notes are present.
4. Open Import review. Record what was checked or corrected before marking a point reviewed and resolved. Resolve every outstanding point before publication.
5. Review the code, source procedure reference and local reviewer assignments. Save the draft, publish after responsible local review and test a practice record before operational use.

The app imports prepared checklist packages; it does not automatically interpret arbitrary Word or PDF documents. A prepared adaptation can retain the source’s introductory material, numbered steps and pictures. Source revision and Wavelink publication revision are separate.

For reusable sharing, choose Export checklist… in the editor. This exports the current editable draft with its pictures but no completed work or signatures. Imported named-person approvals must be assigned to a local reviewer. Keep the source document available for comparison.

To keep the original Word/PDF alongside the adapted checklist, add it separately to Original documents, then link the saved revision in the draft. Importing the prepared .ajcheck does not automatically attach your computer’s source file.

Wavelink / 17

Organise and delete types

Keep the library clear without losing job records

Open Checklist Editor → Library actions → Manage types…. Search by name or system and use the filter to view Available & drafts, Archived, Deleted or All types. The Records column shows how many records use each type, including deleted records.

Delete an unwanted type

1. Select the type in Manage types, or select it in the editor and choose Delete type….
2. Review the name and record count. Enter the checklist name exactly as displayed and give a reason.
3. Choose Delete type. It is removed from normal selection. To undo this, open the Deleted filter and select Restore deleted.

Permanently remove a checklist type

In Manage types, select the original or a custom type and choose Delete permanently…. There is no need to archive or delete it first. Review the record count, type the name exactly and enter a reason. Confirm only when the reusable template is no longer needed.

Archived types are hidden from the editor selector by default. Use Show archived to find them. A library may be empty: use New / Generate or Example setups to start again. Existing jobs remain under Records.

Wavelink / 18

Manage departments

One place for teams, members and approval assignments

1. Open Admin → Departments → Add department. Enter a clear name and an optional description, then save.
2. Select the department and choose Manage members. Click users to select or remove them; search by name or User ID. Add a reason and save. A user may belong to several departments.
3. Use Members to see account status, application role and all department memberships. Disabled accounts cannot approve. Membership does not give administrator access.
4. Open Assigned checks to see current templates, saved drafts, record items and historical references. Double-click a row to view its details.
5. In Checklist Editor → Edit item → Separate approval, select Department / group and choose the team. An enabled member must be assigned before publishing the rule.

Rename or retire a department

Existing approval groups appear automatically in the directory after updating. Membership changes take effect on the next refresh; approvals always check the current assignment. Restore or reactivate the team when reopening older work that needs it. The Change history tab records directory changes.

Departments belong to the current project. Selected setup transfers can include departments and new-user memberships. Review named matches explicitly; imports do not silently give memberships to existing users.

Departments can also receive Issues assignments. Active assigned issues block department deactivation until resolved or reassigned. Historical assignment references are retained and can prevent permanent deletion. Membership and general application access remain separate.

Use Department heads to explicitly designate enabled members who may lead and review private verification work. Supervisor status or ordinary membership is not sufficient. Read Designate department heads for permissions and current-membership rules.

Wavelink / 19

Set up item approval

Checking an item and approving it are separate actions

Choose who may approve

1. Create enabled accounts in Users & access. For department review, assign members through Departments → Manage members.
2. In Checklist Editor → Edit item → Separate approval, choose Not required (default), Named person, or Department / group. Assign an enabled reviewer, save the draft and publish after review.
3. A named rule permits that account; a department rule permits an eligible enabled member. Being an administrator is not an approval assignment or an override.

Check and approve, including your own check

1. Check the item and supply its required readings and photographs. Save and synchronise. The item shows Awaiting approval; its checked result remains visible.
2. The assigned reviewer opens Review approval or My item approvals. Your own checks are included when you are the named approver or an eligible department member.
3. Review the hub-saved result, readings, notes and submitted photos. Confirm Approve or Request changes. Requesting changes requires a reason and does not erase the check. Checking and approval are separate actions with their account and time recorded; a same-person approval is labelled in the record and report.

When approval must be repeated

Changing the result, readings, note, record details, photo or caption requires fresh approval. Finalisation stays blocked until all required items have valid approval, including N/A entries. Reconnect if saved photos cannot load; a reference illustration is not submitted evidence.

Wavelink / 20

Use an optional live checklist

Add job-specific tasks as the work develops

Live mode applies to one record and starts off by default. It is useful for a mobilisation or other evolving work list. It does not change the master template or enable live changes on other records.

1. When creating the record, tick Live checklist. For an existing record, the creator, a supervisor or an administrator can select Enable Live checklist and record a reason.
2. While connected, choose Add live item. Enter the task, section and applicable open stage, then save. On the PC, use Records → Manage / Live edit.
3. Review the updated list with the team. Each new item starts Pending; earlier completed checks and readings remain intact.
4. Continue checking the items and complete the team readiness step again before finalisation. Turn live editing off when no further structural changes are needed.

Protected items

Only genuinely unused items can be reworded or removed. Items with recorded work and finalised stages are protected. Add another task rather than rewriting evidence already recorded. An administrator is required to add or change a live item that carries an approval requirement.

Updates on other devices

Connected, active phones receive changes on their next refresh. A sleeping or disconnected phone receives them after it resumes and reconnects. Refresh and confirm the latest list before relying on it. Local work against a changed item may need review rather than automatic submission.

From the PC, an authorised user can add instruction pictures and explanations when adding or editing an unused live item. Pictures in existing saved work are not replaced. Introduction changes are master-draft changes for future records only.

An administrator may set Off, Optional or Required photo evidence when adding or editing an unused live item, on the PC or through the browser. A creator or supervisor cannot remove a photographic-evidence requirement. Once work is recorded, add a new item instead of changing its definition.

Wavelink / 21

Manage checklist records

A record is one job’s checklist and its evidence

Checklist types are reusable templates. Records are the individual job checklists created from those types. Use Checklist Editor → Library actions → Manage types for templates and Records for job records.

Delete an active record

1. As an administrator, open Records and select the active checklist.
2. Choose Delete active checklist. Review the reference, enter the required reason and confirm the exact reference.
3. The record leaves the normal list and can no longer accept edits or synchronisation. To recover it, select the Deleted filter, choose the record and use Restore deleted.

Deletion here is recoverable: saved answers and history are retained. Fully finalised records are protected from this option. Removing a record does not remove its checklist type.

Wavelink / 22

Export and import project workspaces

Take the saved work you need to another PC

Open Admin → Projects → Export — choose contents…. This screen now lists every current workspace, not just reusable checklist setup. Save unfinished work, stop the hub and make a backup before transferring.

Choose the contents

1. Choose Complete project for a whole-project handover. It is selected by default. Review the workspace counts, including empty sections.
2. Or choose Selected workspaces, then tick Checklists, Logs, Inventory, Stock verifications, Private tasks, Maintenance, Toolbox Talks, Asset profiles and pictures, Certificates or Original documents.
3. Required supporting workspaces are included automatically and identified below the selection. Dependencies include entire workspaces, not only linked items. For example, certificates require inventory and asset profiles; private tasks require their verification results and inventory.
4. Review the privacy confirmation and choose Save project export…. The file ends in .ajproject. Your source project is unchanged.

What each workspace includes

Calendar events and current date/low-stock alerts are generated from the retained dates and rules. There is no separate calendar database to select. Shared user and department history is retained even when some workspaces are omitted.

Import as a new project

1. On the destination PC, open Projects → Import — choose contents… and select the .ajproject file. Review the actual saved contents and counts.
2. Keep Complete project to import everything in that file, or choose a smaller supported selection. You cannot recover work that was omitted when the file was exported.
3. Confirm the contents and select Continue to new project…. Give it a name and a new or empty data folder. An existing project is not overwritten or merged.
4. Open the imported project and sign in using an enabled administrator account from the export. Configure the destination’s approved network address and trusted connection separately.
5. Check saved records, attachments, assignments and reports before using it operationally. Coordinate the handover: two independent copies do not synchronise automatically.

Imports use a new project identity. QR labels linked to the previous project may need to be generated again. A historical project with additional unrecognised tables can be transferred in Complete mode; a selective transfer stops rather than guessing which data to omit.

Transfer reusable definitions instead

For checklist-only setup, choose Need reusable setup without operational history?… in the export window. This is the earlier setup importer/exporter, kept for compatibility; it is not the all-workspaces project handover. It can provide new unpublished checklist drafts, original files, disabled Technician profiles without transferable passwords, department definitions and suggested defaults. Review mappings and assign local reviewers before enabling accounts or publishing.

For a Logs definition, Inventory structure/current-item package, or Toolbox form, use that workspace’s own export option. Those formats are deliberately narrower: do not use them as a substitute for a full backup of certificates, asset pictures, maintenance or task history.

Fleet and manifest dependencies

Vessels and manifests now appears in the project-workspace selector. Inventory and Fleet depend on each other so a selected inventory transfer cannot drop recorded custody or shipment history. Fleet also retains the supporting asset profiles, certificates, maintenance and source documents. Dependencies include whole workspaces, not just the shipped rows.

Complete project copies and complete backups retain all fleet tables, original shipping files and history. Narrow Inventory structure/current-item packages cannot retain this complete fleet evidence: exporting allocated item rows through that format is blocked. Use a full or dependency-aware project transfer. Structure-only inventory export remains available.

Vessel log scope in transfers

Complete project copies retain logbook-to-vessel links, per-user site log rights and their access-change history. A history-bearing selected Logs transfer includes these with the retained site directory and accounts; omitting Logs omits its scope and rights too. The transfer remains administrator-only, unencrypted and not filtered to a single vessel.

A standalone .ajlogs export transfers a logbook without vessel grants. It imports as a new project-only logbook. Review its content and deliberately link it to a local vessel and users before using it in the vessel portal. It does not modify or restore the original scope automatically.

Wavelink / 23

Phone access and installation

Use the team’s hub address

The administrator chooses and saves the team-facing address in Hub & phones. The displayed URL, QR and browser Connect another phone page use that choice. An adapter refresh does not override it. Read Choose the hub network address when using a PC with several networks.

Open the hub address supplied by the administrator, or scan the QR code from Hub & phones. A phone connects to the PC hub; it does not need its own Windows installer.

Add a home-screen shortcut or install the app

Choose Install app below the page header or Install app / home-screen options from the menu. Follow the instructions shown for your browser. Some devices provide a shortcut; a full app installation is offered only when the browser supports it.

Full installation and offline reopening require a secure connection trusted by the device and a successfully loaded app. Your administrator or IT team should arrange secure access. Do not bypass certificate warnings or disable browser protection.

Work safely offline

Before depending on offline access, open the app and the relevant record while connected. Test reopening it without the connection. A home-screen icon alone does not prove that offline access works. The hub is still needed to share records, create new records, approve items and change checklist structure.

A change of active project at the same address requires an explicit browser switch and a new sign-in. The previous project’s saved work remains separate. At a different address or PC, recover/synchronise the old browser workspace before handover.

The separate Fleet portal requires a live hub connection for its logbooks and entry forms. The main project app’s offline queue does not apply to Fleet. Save or cancel its open form before closing or switching accounts.

Wavelink / 24

Secure connections

Ask your administrator or IT team to arrange trusted access

A trusted secure address begins with HTTPS and opens without a certificate-warning page. Ask your hub administrator for the approved address and any device-enrolment instructions. Do not simply change the letters in an existing address and assume it is ready.

Before changing the address

1. Synchronise all devices and save a hub backup. Preserve any local work that cannot yet be sent.
2. Have IT confirm the hub’s address and install a suitable certificate. In Admin, the certificate and key settings are under Settings.
3. Use only an approved trust certificate on your phone or computer. Never copy or share the hub’s private key.
4. Restart the hub as instructed and open the approved secure address. Sign in again if requested. Stop and ask IT for help if the browser reports a certificate problem.

Record certificate renewal responsibility with your administrator. Contact support for setup assistance when no IT-managed certificate service is available.

User instructions

Back up and update

Protect the shared record of work

Save a full project backup

Open Backups & support → Save full database backup…. Keep it in an approved protected location. It includes saved checklists, logs, inventory, box relationships, verifications, private tasks, maintenance, toolbox acknowledgements, users, original files, certificates, asset pictures and low-stock settings.

Update the application

1. Synchronise or export device work, including separate log windows. Save a project backup.
2. Stop the hub and close Admin. Run Setup under the same Windows account, keeping both existing Application and Project data folders.
3. Choose Install / update. Do not uninstall first, clear browser data or relocate the project merely to update.
4. Open the expected project with an existing account and restart at the saved address. Reload devices, confirm the version and test a practice record.

Restore or transfer

Restoring replaces the current saved project state. Coordinate with the team, preserve current work, stop the server and use Restore a hub backup. Sign in again and review unsent device work against the restored records before submitting it.

To move a complete project to another PC, use Projects → Export — choose contents, with full history, then import as a new project. Its new hub identity means inventory QR labels need reviewing and reprinting. Narrow inventory exports do not carry asset profiles, photographs, certificates or maintenance history.

An unexpected first-account screen after an update means stop and check the project and Windows account. For removal, read the separate Uninstall help: complete uninstall can permanently delete selected projects. Keep required backups outside all selected deletion folders.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Vessel log scope in transfers

Complete project copies retain logbook-to-vessel links, per-user site log rights and their access-change history. A history-bearing selected Logs transfer includes these with the retained site directory and accounts; omitting Logs omits its scope and rights too. The transfer remains administrator-only, unencrypted and not filtered to a single vessel.

A standalone .ajlogs export transfers a logbook without vessel grants. It imports as a new project-only logbook. Review its content and deliberately link it to a local vessel and users before using it in the vessel portal. It does not modify or restore the original scope automatically.

Update recovery in 1.23

Before an update changes dependencies or application files, Setup snapshots the known application files, existing private runtime, installation settings and project catalogue. On Windows it also records the affected shortcut files and uninstall registry values. This uses additional disk space; a snapshot failure stops before update commands run.

A detected installation failure attempts to restore that snapshot. The project databases, documents and browser drafts are not rolled back. If you deliberately chose a new project location and a verified copy was already made, that copy can remain; do not run it as a second hub.

If an interrupted setup is detected, the next run restores the previous installation and then asks you to close and reopen Setup so the restored locations are read again. If recovery cannot finish, preserve the reported snapshot and journal, do not launch the app, and contact support. This is not a substitute for a project backup. Real Windows and power-loss testing remains required for this release.

User instructions

Uninstall Wavelink

Review exactly what leaves this PC

Open Uninstall Wavelink from the Start menu, or use the Windows app-uninstall entry for Wavelink. The same removal wizard opens. Use the Windows account that installed the app. For an earlier version, the separate removal-tool ZIP opens this wizard without updating the app.

Before confirming

1. Synchronise or export work on every phone. Export any projects you need and keep the backup OUTSIDE the folders you intend to remove. Stop the hub and close Admin and Setup.
2. Application-only removal is selected by default. Review each exact project path. To delete project data, choose Complete uninstall and deliberately tick the verified folders to remove. Newly discovered or added folders stay unticked.
3. Confirm that you have preserved the work you need. Type REMOVE, select Uninstall and confirm the final warning. Removing a project is permanent; reinstalling the app does not recover it.
4. Read the removal result. A locked, missing, linked or unverified location is reported rather than silently declared removed. Close programs using a locked folder and use Check again before retrying.

What stays outside this removal

The private application runtime and recognised setup logs are removed. Shared Python remains because other applications may use it; it is also needed by the removal wizard. The tool does not scan all drives or delete unrelated files, other Windows users’ installations, separate installations, exported copies or external backups. Shared/network projects must be handled by their owner. A local copy of an earlier project can be selected explicitly.

Browser and phone storage, saved passwords, pinned shortcuts and installed trust certificates are not removed by uninstalling the PC hub. After recovering all required local work, remove this app’s saved site data and home-screen shortcut on each relevant device through that browser’s controls. Do not clear other sites or another project’s workspace. Ask IT before removing a trusted certificate that may be shared.

Safer removal choices

Wavelink 1.23 starts with Remove the app only selected. Project-deletion boxes start empty. Switching to Complete uninstall does not select projects automatically. Tick each verified folder deliberately, or use Select all available only after reviewing the list.

Check again preserves your choices for folders that are still verified. New or newly added folders stay unticked; unavailable folders are deselected. Refreshing clears the typed REMOVE confirmation. Returning to application-only removal clears all project-deletion selections.

If Setup recovery is pending, uninstall stops before deleting files. Keep the recovery snapshot, close the hub and rerun Setup first. Recovery snapshots that could not be cleaned up may remain for support; unrelated files are not removed automatically.

Wavelink / 27

Find and move inventory

Select the equipment, choose its destination and review the move

Open Inventory and choose the inventory list. Search by item, model, serial or asset reference. Location, owning department and original source tab are separate filters; a source tab is not automatically a department.

Search remains visible. Use Filters for location, department and original source tab. More tools holds QR labels, new verification sessions, exports, low-stock alerts and expand/collapse commands; everyday move actions stay visible.

On a smaller Admin window, Filters… opens location, department and original-source choices. More actions… keeps Add, Edit, Open, History and Archive available while leaving the main movement controls visible.

Select rows on a computer

Click a row to select it. Ctrl-click adds or removes individual rows; Shift-click selects a range in the displayed order. Ctrl+Shift-click adds a range. On a Mac browser use Command instead of Ctrl. With the table focused, Ctrl+A selects visible rows and Escape clears the selection. Selecting does not move stock or verify any result.

Use Open selected, or double-click a box, to see its contents. Double-click an ordinary item for its details. On phones, tap the item name to open it and use the selection boxes to select several items. Filters and collapsed boxes can hide rows: movement uses the displayed selection, not hidden matches.

Choose the right move action

The movement form shows the selected top-level records, their current positions and the number of nested records that follow. Review the destination, enter the reason, tick the confirmation and choose Confirm move. Nothing moves merely by selecting or opening the form.

Partial quantities apply only to eligible non-serialised, untagged stock with known quantities, never boxes. Blank moves the whole record. Quantities remain conserved; unknown quantities are not assumed.

Wavelink / 28

Build an inventory

Create the structure before entering stock

1. As an administrator, open Inventory → List setup → Inventory Builder. Enter the list name and purpose.
2. Add storage locations, one per line. Unassigned and In use are supplied automatically. Department custody uses existing project departments; manage those under Departments.
3. Add optional fields only when needed. Available types are text, number, date and dropdown choice. Item name, model, serial, asset, quantity, dates, department and location are already included.
4. Review and select Create inventory. This saves an empty list, not an imported stock count. Add items or import a prepared inventory package separately.

Back and Next retain changes inside the open wizard. Nothing is saved until Create inventory. Cancel asks before discarding unsaved builder changes. Additional-field structure is fixed after creation; locations can be added later through Locations.

Permissions

Administrators build/import lists. Under Users & access → Permissions, control View inventory, Add and edit items, Move items, Run stock verifications and Export reports separately. Users with role defaults receive the applicable new access; users with explicitly restricted settings require an administrator to grant the new permissions.

By default, technicians can view inventory and check stock; supervisors can also add/edit and move items. Administrators have full access. Department membership is not a substitute for an application permission.

Wavelink / 29

Stock verification

Verify inventory without losing your place

1. Open an inventory and choose Stock verification → New stock verification on the PC, or New stock verification in the browser. Name the exercise and choose all items or a location/department scope.
2. Start the stock verification. Its scope is a fixed list of active records at that moment. All start unchecked even when a previous stock verification covered the same equipment.
3. Work through Still to verify. Open an item and choose Found / verified, Missing or Discrepancy. Enter counted quantity when an expected quantity is recorded. Explain missing or discrepant results. Save the verification result.
4. Saved results move to Verified. Reopen the same stock verification to continue later. Use All items to compare progress. Refresh to see checks saved by other users.
5. Close completed only after every scoped record has a current check. Explain the outcome and explicitly acknowledge any recorded discrepancies. Cancel verification records an unfinished exercise without pretending it was complete.

Verified means a result was recorded, including Missing or Discrepancy—not that equipment was found or is fit for use. Results do not automatically change inventory quantities. Selecting rows for movement does not verify them.

Use Return to unverified with a reason to revisit a result; previous evidence remains in History. Closed reports keep their close-time item and check details even if equipment moves later. PDF export is available from the stock verification.

Saving a stock check needs a connection. Browser check forms can be kept locally, but are never submitted automatically. Reconnect, reopen Local forms, review and Save to hub. A changed item/version can require starting the check again against current data.

Review an earlier result

When you reopen an item already verified, its saved result, counted quantity and notes are shown as the starting values. Change only what you have reviewed and provide a reason before replacing that result. Opening the editor does not save a new verification.

Found / verified uses green. Missing uses red; Discrepancy and verification required again use amber. On a phone the outcome is also shown beneath the item name. Always read the result text: colour alone is not a decision about equipment availability.

For a restricted assignment, use Tasks rather than an ordinary stock verification. An ordinary stock verification remains shared with users who have the relevant Inventory access. Read Assign private verification tasks and Keep items inside boxes and kits.

Open the right item by QR

Choose Scan QR in the browser verification. Use Start camera on a supported browser with trusted HTTPS, read a QR photograph where supported, or paste the scanned label link or complete asset ID. On the PC, Scan / enter QR… accepts a USB/Bluetooth scanner or a pasted link. Scanning only locates the item: inspect it, enter the result and save deliberately. An earlier saved result is shown for review rather than overwritten.

A code from another project or an item outside this verification is rejected. It is not added to the original scope. Use a separate verification for additional items. Read Scan labels during stock verification for camera availability and recovery.

Keep an item where you found it

In the item’s verification form, choose Found elsewhere? Move & verify…. Select a location / area or destination box and enter a movement reason. Review the affected-item count, then save the move and verification together. This needs both Inventory view and Move items permission, as well as verification access. Without movement permission, record the different position in your notes and ask an authorised person to update it.

Moves do not change the recorded quantity to match a count. Current results and PDF reports include the saved before/after position and movement reason. Earlier movement/check evidence remains in History. Closed verifications are not changed.

In-transit assets cannot be changed or marked Found: receive them through Fleet first. Quarantine release remains a separate, explicit action.

Wavelink / 30

Import and export inventory

A separate list, not an automatic merge

1. Save a project backup. In Admin → Inventory → List setup → Import inventory, choose a prepared .ajinventory file. The inventory importer does not accept an arbitrary Excel layout.
2. Review the proposed list name and item-record count. Confirm to create a new separate inventory. Existing lists, checklists, logs and accounts are not overwritten.
3. Inspect source review notes on imported records. Blank quantities remain unknown; source rows are not automatically merged on repeated names or asset labels.
4. Assign local departments deliberately after import. Source department information may be kept as evidence, but account memberships and active custody assignments are not created from a source name.

Choose what to export

Inventory → List setup → Export offers an .ajinventory package with current active item records, or structure only when Include current active item records is unticked. A structure-only file contains the list, locations and additional-field definitions but no stock. Exact repeated package imports in the same project are blocked.

The CSV export contains current values for active and archived records, along with source information and review notes. Item/source identifiers remain text. CSV is a reference table, not an inventory package to re-import.

Setup packages exclude archived items, movement history and stock verification progress. Use a full project backup or full-history project transfer to preserve the complete database, including all inventories, stock verifications and toolbox talks. A full transfer creates a separate project, not two synchronised copies.

Imported source worksheet names and cell values remain available independently of current custody. The importer does not guess owning departments from room names, source tabs or empty location cells. Filter by Original source tab and assign custody deliberately after checking the physical stock. Do not import the same stock again merely to change a filter or assignment.

Current-item exports retain container IDs and remap parent links during import. They do not automatically assign source departments. Full project transfers preserve current department assignments, open/private verification work and maintenance history.

Full project transfers include asset photographs, certificate files, contact and low-stock settings. Narrow inventory packages do not include those additional asset records. A transferred project has a new hub identity: review and reprint QR labels.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Wavelink / 31

Conduct a toolbox talk

Discussion and understanding, then personal acknowledgement

1. Open Toolbox Talks → New toolbox talk. Choose an available published form. The record keeps that exact form revision.
2. Enter Site / Location, Project Number, Client, JSA reference, the work description and event date/time. This application records the event time in UTC; confirm any source document’s time convention.
3. Tick only the discussion elements actually covered. Complete the supervisor’s understanding questions with Yes or No. They start unanswered.
4. Select all named project users attending, and use Add guest for visitors without accounts. Adding a name does not sign for them. Save the talk before requesting acknowledgements.
5. Each attendee signs in, opens the saved talk, reads it and selects I have read and understood or Acknowledge personally. Each person confirms only their own acknowledgement.
6. When all understanding answers are Yes, every listed project user has acknowledged and all listed guests have witnessed acknowledgements, the talk owner or an administrator may finalise it. Finalisation locks the record.

Changing saved content, prompts, understanding answers or attendees requires all attendees to acknowledge the revised content again. Prior acknowledgements stay in History; they do not count as signatures of new content. Refresh before final review when another person is updating the talk.

Project users acknowledge personally; a supervisor cannot sign as another account. Guests use the separate witnessed typed-name process in Add guests and collect acknowledgements. Neither method is a certified digital signature or authority to start an operation.

Permissions control viewing, conducting, acknowledgement and export. The owner or an administrator with conduct access can edit, cancel or finalise. Cancellation requires a reason and retains history.

First briefing or a later amendment?

The first briefing uses Save briefing without a change reason, including an untouched newly created talk. Later saved changes need a reason and renewed acknowledgements. Saving identical values does not create another content revision.

Select several topics or attendees

Topics and attendees are in separate tick-box groups. Check all discussion topics requires confirmation that every topic was covered. Clear discussion topics resets those ticks. Select all eligible users selects attendees; Clear attendees removes that selection. These controls do not answer understanding questions, acknowledge or finalise. The title and Close control remain visible while scrolling.

Wavelink / 32

Build and import toolbox forms

Keep reusable forms separate from recorded meetings

1. In Admin → Toolbox talks, open Toolbox Builder. Enter the form name, optional document code and purpose.
2. Add discussion prompts one per line. An optional group prefix uses a vertical bar, for example LOTO | Electrical. Prompts are discussed/not-marked ticks, not checklist completion results.
3. Add Yes/No understanding questions and the supervisor instruction. All questions must ultimately be Yes before a meeting can be acknowledged or finalised.
4. Enter the declaration attendees must read. Review the form, then save an unpublished draft.
5. Open Templates / publish, preview the form and its source, then deliberately publish the reviewed form with a change summary. A published form can be revised without changing earlier talk records.

Use a prepared source form

Import form accepts a prepared .ajtoolbox file. It creates a draft, retains source attribution and does not copy names, signatures, discussion ticks or completed answers. Review and publish locally before use. Uploading the original Word form to Original documents is a separate way to preserve the source; it does not build a talk automatically.

Export form saves the reusable definition and attribution without meeting history or acknowledgements. Archive hides a form from new talks, while previous talks keep their own revision. Full project backups and full-history transfers retain templates, meeting records and acknowledgement history.

Drafts and reports

PC form edits must be saved before closing. Browser forms save typed changes to Local forms in the existing guarded workspace. Keep draft & close does not submit anything. Reconnect, reopen the form and choose Save to hub. Version conflicts preserve the local form rather than overwriting another person’s changes.

A toolbox PDF includes site/project/JSA details, event time, work description, all discussion prompts, understanding answers, project-user acknowledgements and a separate table of guest names, typed acknowledgements and witnesses. Open or cancelled records are clearly identified. Source authorship and revision are not the same as the account importing or publishing a form.

First publication records the reviewing administrator and time without asking for a reason for changing a form that has not been published before. Confirm the source and form review. Later publications still require a change summary.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Wavelink / 33

Add guests and collect acknowledgements

One shared talk, each participant’s own confirmation

Project users

The talk owner selects the attendees and saves the briefing. Each participant signs in with their own project account, opens the same talk from Toolbox Talks, reads it and chooses I have read and understood. Several participants can acknowledge independently; no one signs for another account. Up to 150 participants, including guests, can be listed.

Add visitors without accounts

1. The owner opens Conduct / update in the browser, or Open / conduct in Admin. Choose Add guest and enter the visitor’s name and optional organisation. Save the changed roster with a reason. Adding a name alone is not confirmation of attendance or a signature.
2. After the briefing details and understanding responses are saved, choose Guest acknowledgement beside the person’s name. In Admin, select the talk and choose Guest acknowledgement, then select the guest.
3. Pass the device to the guest. They read the saved work description, discussed elements and declaration, type their full name exactly as listed and confirm personally.
4. The facilitator confirms that they witnessed that guest acknowledge in person, then saves Record witnessed acknowledgement. A browser connection is required; acknowledgements are not queued or sent later automatically.

Changes and final review

Changing saved briefing content or the participant roster requires all participants to acknowledge that revised version again. The earlier acknowledgements remain in History. A stale screen cannot acknowledge newer content. Adding further attendees before collecting acknowledgements avoids unnecessary re-signing.

The owner or an administrator finalises only after every understanding response is Yes, every listed project attendee has personally acknowledged and every guest has a witnessed acknowledgement. A No requires rebriefing, not an automatic change to Yes. Finalisation locks the record; create a further talk when circumstances change.

Viewing or acknowledging a talk does not grant conduct permission. Export PDF identifies registered-user and guest acknowledgements separately, with their recorded UTC times. Full project backups retain the complete history; form-only exports do not transfer signatures or attendance.

Wavelink / 34

Help and support

Keep the detail useful and your data private

Contact Adriano Carneiro

Use Contact or email support@mywavelink.com with the version, action and exact message. A non-sensitive screenshot can help. Nothing is sent automatically.

Review logs before sharing. Do not send passwords, private keys, client information or operational records without authorisation.

A required-photo warning means completion evidence is missing; instruction pictures do not count. Use JPEG/PNG, preserve drafts and reconnect for unloaded pictures.

Originals need the correct project, access, connection and a compatible viewer. Do not rename extensions to bypass file checks.

Task access may change after reassignment. Preserve unsent work and ask the administrator. Reopen separate log drafts using their saved window links.

Wavelink / 35

Create and use logbooks

Operational events alongside your checklists

Logbooks belong to the selected project. Use them for events, measurements, issues and offset registers alongside your checklists. For restricted accounts, read Use vessel-specific logbooks; that separate portal has no offline queue.

Work in the log table

Open Admin → Logs, or Logs in the browser. Choose a book and section. Scroll within the rows or across columns; headings and controls remain visible. All columns shows every field. Open an event for its full details.

LOG ON is green and LOG OFF is red. New day entries use a warm highlight; a DNP marker stays explicit. Line status uses green for Completed, yellow for Partial and red for Not Attempted. The event/status text remains visible: colours do not control equipment, approve a run or certify work.

Create, enter and correct

1. On the PC, open Logbook setup → Log Builder wizard to select sections and fields. Review and create an empty logbook. Set up offset tables adds missing standard registers to an older logbook.
2. Choose Add entry. On the phone/browser, LOG ON and LOG OFF prefill an event form only; review its actual UTC time and values, then Save to hub. Nothing is submitted by the shortcut alone. The signed-in account identifies the author; no surveyor initials are required.
3. Select a saved row before choosing View / correct or History. The author or an authorised supervisor/administrator can correct it with a reason; earlier values remain in History. Voiding does not erase an entry. Source initials remain separate from the importer.

Filters and automatic updates

Entries are newest first. Filters opens over the table without shrinking it. Apply search/dates, then Close filters. Clear UTC dates to include unconfirmed times. Routine updates retain scrolling and forms; desktop Refresh keeps the selected section and page. Another logbook, deliberate navigation or a full reload can start a fresh view.

Open Logbook details & source notes separately. On a phone or short window, swipe the action bar sideways for the remaining commands; Add entry and LOG ON/OFF remain at the start.

For imported equipment pages, use References → Review selected. Releasing a page controls team access; it is not engineering approval.

Assign Issues through the user/department selector. Recipients follow Assigned to me; assignment does not grant edit permission.

Use Expand view or Open separate window to keep the log visible while working elsewhere. Section legends are contextual; read Expand a log and keep another window open for independent drafts and recovery.

Wavelink / 36

Import a multi-tab operations workbook

Review every tab before creating a historical logbook

1. Open Admin → Logs → Logbook setup → Import workbook. Choose an XLSX/XLSM up to 64 MB with no more than 100 worksheets. No macros, calculations, external files or queries are executed.
2. Review the inventory of every sheet, including hidden or excluded sheets. Toggle the desired tabs and use Review selected sheet to inspect counts, mappings, warnings and sample values.
3. Enter the new logbook name and confirm the destination project, source status, units and permission to import. Confirm Survey times as UTC only when verified; otherwise retain the unconfirmed source times.
4. Import into new logbook creates a historical snapshot, not a merge or live connection. An exact repeat workbook import is blocked in that project.

What becomes a working section

Recognised OnlineLog, Survey, SVP, Weather, Line Status, Draft and Issues layouts use explicit field mappings. Recognised Lever Arms and C-O layouts add offset register entries. Blank template rows and status placeholders are not invented records. Unrecognised headers remain reference-only.

Lever Arms convention blocks remain separate, with their original axis labels. C-O Qinsy-sign and respective-system-sign groups become separate entries. Saved values, inactive formulas and source cells are retained. No signs or frames are converted, no units or origins are inferred, and formula results are not recalculated. Imported offsets are unverified source records.

References and sensitive material

Selected tabs also retain source-reference pages containing saved cells, explanatory text, picture placements and layout notes. Source errors stay visible; source names and initials are not authenticated account signatures. The signed-in importer is recorded separately.

Passwords, IO Moxa and Corrections are excluded as whole tabs because of credential/service-access information. Every other reference page starts restricted to administrators. Review the complete cells and pictures before release; other pages may still contain confidential details.

For vessel-only readers, review and link the whole book under Fleet & manifests → Vessel logbooks & permissions. That portal requires separate log rights and a hub connection; it does not use this workspace’s offline queue.

Wavelink / 37

Review equipment and illustrated references

Keep historical settings separate from current instructions

Imported equipment pages preserve saved workbook cells, explanatory text and source pictures. They start restricted to administrators. Release lets the project team read a page; it does not approve its technical content.

1. Open Admin → Logs → References…. Select a source page; the first available page is selected automatically. Choose Review selected… or double-click it.
2. Choose Open full page to inspect all the saved cells, notes and full underlying images. If the default viewer cannot open, the app shows the saved file path.
3. Check confidential information, current applicability and equipment revision. Enter a reason and tick the acknowledgement, then choose Release to team.
4. Users with Logs and reference-view access can open the released page under Equipment & references. Use Restrict page to stop future app access; copies already downloaded cannot be recalled.

Pictures and source limitations

Underlying images may reveal content outside an Excel crop. Review every picture before release. Inactive source formulas, source errors and recorded sign conventions are preserved, not recalculated or certified. Vector-only connectors and the exact Excel layout are not reproduced. Instruction pictures are not evidence of newly completed work.

Keep useful evidence

Open full page saves a local preview inside the project’s reference_previews folder. Treat that file as confidential too. Use the log reference export options to transfer the source pages and pictures deliberately; a full project backup preserves their saved database content. The original workbook remains the authoritative source for its exact presentation.

For vessel-only readers, review and link the whole book under Fleet & manifests → Vessel logbooks & permissions. That portal requires separate log rights and a hub connection; it does not use this workspace’s offline queue.

Wavelink / 38

Export and transfer logbooks

Choose definitions, historical entries or reference material

Export the working log as a table

On the phone/browser select Export report. In Admin use Logs → Report. Excel and PDF use a compact log table with the same column order, newest-first rows and LOG ON/LOG OFF colours as the working view, rather than a separate page of labels for every entry.

1. Choose Working columns for the compact view, or All columns and Notes for the complete field set. The browser initially follows the current All columns setting.
2. Review search, UTC dates and Include voided. All matching saved entries are exported, not only the currently displayed page. Clear UTC dates to include unconfirmed source times.
3. Choose Excel log table for the current section, or All log sections for one worksheet per section. Headings and Date/time are frozen. The file contains literal saved values without executable formulas or macros.
4. Choose PDF log table for the selected section. The report is landscape, with repeated table headings and page numbers. Wider tables use A3; very wide All columns reports continue in numbered column groups with identifying columns repeated. The limit is 1,000 entries.
5. CSV contains the same chosen table values but no colours or formatting. Text that could be interpreted as a formula is quoted for spreadsheet safety.

Transfer definitions or full log history

Use Admin → Logs → Logbook setup → Export / import for a portable .ajlogs package. Definitions are always included; tick entry history, reference pages and reference pictures as needed. For definitions only, leave all three off. Offset registers travel with their definitions and selected history.

Reference pages may include historical source rows even when entry history is unticked, as well as restricted information. Their export includes restricted pages. Packages are not encrypted. Import creates a new logbook, not a merge; imported pages need a new local review. Full project backups and full-history project transfers include saved logbooks.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

Vessel log scope in transfers

Complete project copies retain logbook-to-vessel links, per-user site log rights and their access-change history. A history-bearing selected Logs transfer includes these with the retained site directory and accounts; omitting Logs omits its scope and rights too. The transfer remains administrator-only, unencrypted and not filtered to a single vessel.

A standalone .ajlogs export transfers a logbook without vessel grants. It imports as a new project-only logbook. Review its content and deliberately link it to a local vessel and users before using it in the vessel portal. It does not modify or restore the original scope automatically.

Wavelink / 39

Record lever arms and angular offsets

Keep coordinates, origins and sign conventions explicit

Lever arms record sensor positions relative to a stated origin and coordinate convention. C-O records angular corrections and their sign convention. Keep different systems and axis conventions separate; do not assume missing units or convert signs without an approved basis.

1. Open the intended logbook and choose Set up offset tables…. The window shows whether Lever arms / offsets and C-O / angular offsets already exist, with their entry counts.
2. Choose Open table for an existing section. To add missing sections, review the change note and choose Add missing tables. If both are present, nothing needs adding.
3. To record an offset, select its section and choose Add entry. Enter the sensor, convention, origin, axis labels, values and units.
4. To load historical Excel measurements, use Import workbook… or import a prepared .ajlogs package. That creates a new populated logbook; setting up tables alone does not copy measurements.

Wavelink / 40

Set user permissions

Give each account the access it needs

1. Open Users & access → select user → Permissions… as an administrator.
2. Start from Role defaults, View only or All operational access, then review each tick box. Viewing an area is required before its action permissions can be enabled.
3. Enter a reason and Save permissions. The user signs in again with the new access; saved work is not erased.

Existing explicit restrictions do not gain new capabilities automatically. Source files already downloaded cannot be recalled by changing permissions. Project, user, department, template and library management remain administrator-only.

For a person who must see only selected vessels, use Fleet & manifests → User vessel access and explicitly choose Vessel-only access. General project permissions and department membership are not vessel boundaries. Read Set vessel-only access before changing an account.

Vessel-specific Logs are available through /fleet → Logbooks only after an administrator links the book and grants the account separate site log permissions. Existing project-wide accounts retain their broader access. Read Use vessel-specific logbooks and Set vessel log permissions before commissioning restricted accounts.

Wavelink / 41

Build a logbook step by step

Create the sections and entry forms your team needs

1. Open Admin → Logs → Logbook setup → Log Builder wizard…. Choose Vessel operations, Activity only, Issues and handover, Weather and SVP, or Blank custom log.
2. Enter a name and an optional purpose. The logbook belongs to the project currently open.
3. Add, rename, reorder or remove sections. Built-in sections include Activity, Survey runs, SVP, Weather, Line status, Draft measurements, Issues, Lever arms and C-O. Each section becomes a tab.
4. Choose each section and configure its fields: text, number, date, time or dropdown. Add units, required fields and choices. Do not add author initials; the signed-in account and save time are recorded automatically.
5. Review the full structure, tick the review acknowledgement and choose Create logbook. The new empty logbook is selected; choose a section and Add entry to begin.

Back and Next retain changes only inside the open builder. Nothing is saved until Create logbook. Cancelling asks before discarding the unfinished setup. This does not publish a checklist, copy history or overwrite another logbook.

User instructions

Assign issues and follow alerts

Select an actual project user or department

1. Open an Issues section and select Add entry or correct an existing entry that you are permitted to edit.
2. Under Assigned to, choose Unassigned, an enabled project user, or an active department with eligible members. On the PC, choose User or Department first, then the target.
3. Review the event and save it to the hub. Saving an offline draft does not send an alert. Assignment is a separate action from checklist approval.
4. The recipient opens Assigned to me in the browser navigation, or Admin → Logs → Assigned to me…. Open an issue to read its current details and acknowledge its alert.

Browser alerts update while the application is open and connected. Department assignments notify the enabled members who can view Logs at the time of assignment. Current department members also see the outstanding issue in their assigned list. The Windows list can be refreshed explicitly. There are no email messages, operating-system notifications or background push alerts.

Marking an alert read does not resolve the issue. Resolve it by saving Issue status as Resolved, with the required correction reason. Resolved, voided and archived issues leave the active list. Reopening or changing the assignee generates a fresh alert; ordinary edits do not generate repeated alerts.

For vessel-only readers, review and link the whole book under Fleet & manifests → Vessel logbooks & permissions. That portal requires separate log rights and a hub connection; it does not use this workspace’s offline queue.

Opening and reading an alert

In the project browser and Fleet portal, an issue alert is marked read only after its authorised entry has loaded and been displayed. Only notification revisions covered by that displayed entry are acknowledged. A failed load, changed project/account or newer unseen revision must not be silently cleared.

An acknowledgement failure is shown separately: the entry may have opened even though its alert remains unread. Reading never resolves the issue. Likewise, background refresh of an already open task does not acknowledge a new task revision; explicitly opening the task can acknowledge it. Unavailable badge counts show a question mark rather than a reassuring zero.

Wavelink / 43

Choose dates and times

Calendar and clock controls without changing the time basis

Editable date fields provide a calendar control; time fields provide a time selector. You can still type values manually. In Windows Admin, choose Date…, Time… or Calendar / time…. Select a date, adjust hours/minutes/seconds and choose Use selection. Cancel leaves the original value unchanged.

In the browser, use the calendar or clock button beside the field. A full log event timestamp also offers Calendar & clock…: choose the date and time, then Use selection. The date and time are combined explicitly as UTC, not converted from the laptop or phone’s local timezone.

Date-only fields stay dates. Time-only measurements keep the time basis stated by their field or source; the picker does not confirm an unknown timezone. Blank optional fields stay blank unless you select or enter a value. Creation, saving and approval timestamps are automatic records, not editable picker fields.

Wavelink 1.34.10 / user instructions

Assign and review operational tasks

General work, maintenance activities and certificate checks — without a fictitious inventory item.

One entry point, four clear steps

Open Tasks → New task in the browser or native Admin. Choose General work, Maintenance activity, Certificate check or the existing Inventory verification workflow. A project administrator or designated department head with Tasks management creates the assignment. Follow Work → People & due date → Checklist & link → Review & create. Enter clear instructions, priority, eligible named assignees, department and optional UTC due time. The final confirmation starts unticked.

Follow the next action

Since 1.34.4, task details show Next action above the instructions: Continue checklist, Save work findings, Prepare submission or Open review, according to the hub-saved work and your permissions. Continue opens the first unrecorded step, labelled Step N of total; opening it does not record or complete it. Local forms are not hub-saved results. The existing submission button stays disabled until findings and all checklist results are saved. Submission and reviewer acceptance still need separate confirmation.

Find a step without changing the work

Search step wording, stage, section or a saved result note. Filter All steps, Not recorded, Issues / not applicable or Recorded. The shown/total count identifies hidden steps. Clear filters restores the full original order without resetting any result. Hidden steps still count toward submission. Same-task/account filter preferences survive a refresh/save while the current browser session or native task window remains open; they are not durable or cross-device drafts. Issues remain issues after reviewer acceptance, not Done. Refresh after someone else changes the task.

Link a source, or keep it standalone

Select no link, or search for one exact saved asset, maintenance order or certificate revision. Creation checks the chosen version again. A link does not grant source access, copy source evidence or follow a replacement certificate automatically. Readers without source permission see unavailable, not its identity or details. Changed sources are marked for review. Related tasks on source pages use current task permissions. Do not copy restricted source wording to an inappropriate task audience.

Record findings, then submit and review

Only assigned people with Tasks perform can Record work notes. Administrators who perform work must be assigned deliberately. Saving notes starts work; changes to saved findings require a reason. Comments are immutable additions, not completion evidence. Submit for review shows the saved notes and requires confirmation. A designated department head or administrator reviews, then completes or returns the task with a reason. Same-person review is labelled and is not independent approval.

Control responsibility without rewriting evidence

Managers can reassign open work, change priority/due date or cancel with a reason. Reopening a general task preserves prior results in history but requires fresh notes and review. Current eligible assignees are required to reopen. Closed inventory verifications remain locked. Opening the task acknowledges only its displayed notification revision; background refresh and source-page reads do not acknowledge, submit or complete work.

Protect private forms, history and copies

Readers are current assignees, explicitly appointed department heads and project administrators—not every department member. Local browser forms reuse the existing account/project-scoped storage and require a confirmed local save before sending. Local forms are not auto-submitted. After an uncertain response keep the form open and use Retry unchanged request; check the record and Connection & saves before different work. Request receipts are metadata only; recovery exports may contain private typed text. Native unsaved dialogs are in-memory only. Do not clear browser storage.

PDFs are current saved task snapshots, not complete history or copied source attachments. Full backups, transfers and downloaded reports remain unencrypted sensitive copies. Once general tasks exist, do not downgrade below 1.34.3. No new schema, dependencies, firewall or server-start changes are included.

Task limits and remaining extensions

One optional source link; 1–50 assignees; 160-character title, 6,000-character instructions, 8,000-character findings and up to 100 comments of 2,000 characters. Source search shows the first 100 matches. There are no new task photo/file uploads or automatic repeating tasks; source attachments remain in their existing workspaces. Continue testing Windows, phones, live connectivity and durable browser storage with fictional data.

Keep the checklist inside the task

In Checklist & link, choose No checklist, Use an existing template or Build from scratch. Scratch still accepts a title and one step per line; # starts a section. Select Edit steps & add readings to edit individual steps inside this form, or open the editor directly with a blank step. Add, remove or reorder steps; their readings and guidance move with them. Nothing invents procedure wording.

Author readings in the task draft

For the selected scratch step, choose Add text reading or Add numeric reading. Enter a distinct label, optional unit and Required for Done. Numeric readings need explicit lower and upper limits, both inclusive and within ±1e12; blank, non-finite or inverted limits are rejected. Use decimal-point notation and your approved procedure, not guessed operating limits. Add optional step guidance and review the entire definition before creation.

Limits: 200 steps, 12 readings per step, 2,000 characters per step wording, 4,000 per guidance, 160 per title/section/reading label, 40 per unit and 40,000 total authored text characters. The structured draft is retained by the existing account-scoped browser form mechanism; this is not a new offline queue. Keep 1.34.8 or later while structured scratch drafts remain; old clients do not understand these draft fields. Native unsaved forms remain in memory. Saved definitions are fixed; no reusable library template is published.

An authorised creator can copy a compatible published Checklist template after explicitly confirming its wording may be shared with the task's readers. Revision and checksum are checked again on save. The fixed task-owned copy retains stages, guidance and reading limits, but no answers, signatures or stage approvals. Templates needing photo evidence, item approvals, reference pictures, linked source files or conditional winch checks are marked unavailable; use their original Checklist workspace rather than remove their rules. Maintenance-plan templates are not part of this picker.

Add checklist is also available on an existing general task before work starts, provided no notes or checklist have been saved. Once added, steps cannot be replaced or removed. Inventory verification continues its original stock-check workflow.

Save results, then review exceptions

Within task details, record each step as Done, Issue / outstanding or Not applicable, or leave it Not recorded. Issues and not-applicable steps need notes. Done needs required readings; out-of-limit readings must be recorded as Issue with an explanation. Saved results record their author/time. Changes require a reason and keep history. Saving a step does not submit the task or approve equipment.

Save findings and record every step before submitting. Review shows saved readings and notes. Completion with issues or not-applicable steps requires an additional unchecked-by-default acceptance; otherwise return for correction. Acceptance does not turn an Issue into Done. Reopening requires fresh findings and a new checklist cycle, preserving previous results in History. Current saved results appear in the task PDF.

Browser checklist forms use existing account-scoped draft/retry protection, not an automatic offline queue. Native unsaved forms remain memory-only. Preserve unfinished work before reloading/updating. After task checklists are saved, keep 1.34.3 or later; older releases do not enforce these completion gates. See the task-checklist guide for restrictions and source-sharing permissions.

Create corrective work from a fault

In Fault Reports, choose Create corrective Task to use this same four-step editor and checklist options. Review the separate Task audience; observed fault wording is copied only by explicit choice. Task creation and its fault link save together. Their work, review and closure stay separate. Related fault reports are shown only with current access.

Keep 1.34.8 or later while corrective Task drafts remain. The draft retains the original source revision and operation; a stale report is not silently rebased.

Wavelink / 44

Inventory verification tasks

The preserved fixed-scope stock-check workflow

Inventory verification is one of the task types. For standalone activities, maintenance or certificate checks use Tasks → New task and choose the appropriate category. Verification retains its frozen item scope and saved results.

1. In Tasks → New task → Inventory verification, enter a clear title and choose the inventory. A creator must be an administrator or a designated head of the responsible department with Task management and Inventory view permission.
2. Choose the responsible department and one or more enabled users with Tasks view and perform access. A Supervisor or department member is not automatically a department head.
3. Select the item records. Choose Selected records only, Selected boxes and all their contents, or Selected boxes only. Check the scope carefully; a box-only task is not a contents verification.
4. Optionally choose a UTC due date/time and add instructions. Save the private task. Its scope is frozen at creation; later inventory additions are not silently added.
5. Assignees open Tasks → Assigned to me, record results and submit for review. The responsible head or an administrator reviews the submission and either returns it with instructions or completes it.

Task lists, direct links, verification results, history and PDF reports check current access. Removing an assignee or department-head membership removes access to that task on the next request. Existing downloaded reports or saved local recovery copies cannot be recalled. Use trusted accounts and protect devices.

Tasks can contain Missing and Discrepancy results. Submission requires every scoped item to have a current result; the reviewer explicitly acknowledges discrepancies before closing. Moving an item or its box requires rechecking when it changes the expected position. A completed report keeps its closing state.

In-app NEW UPDATE alerts identify assignments, reassignments and review changes. Open a task to acknowledge the current alert. This does not complete the work. Alerts require the app to be open and connected; there is no email or background push notification. A due date does not create an automatic recurring task.

Choose all inventory or a whole section

Create verification task offers all active inventory, a location, an owning department, an original source tab, a box, or selected individual items. Review the item count and separate box-contents choice. Search only filters the preview of a whole section; it does not reduce the scope. The saved scope is fixed; an inventory change before creation requires refreshing. Choosing all never bulk-marks stock Found.

Scan and relocate during assigned verification

Use Scan QR in the open task to find one of its assigned items. Scanning does not reveal items outside your task or change its scope. Read-only or submitted tasks do not open an editable check.

An authorised assignee may use Found elsewhere? Move & verify… only with Inventory view and Move items permissions. Assignment alone does not grant movement rights. A box containing items outside this private task cannot be moved from the task: an authorised person must use Inventory, then the assigned records are refreshed and rechecked. Submitting, reviewing and task privacy work as before.

On a computer, the inventory-item picker also supports Ctrl-click, Shift-click and Ctrl+A within the visible list. On touch devices keep using the selection boxes. These select records only: confirmation, verification, dispatch and receipt remain separate deliberate actions.

Wavelink / 45

Designate department heads

Membership and leadership are separate decisions

1. Open Admin → Departments and select the responsible team. Add the relevant users under Manage members first.
2. Choose Department heads…, select the enabled members who should lead this team, enter a reason and save. More than one head is permitted.
3. In Users & access → Permissions, grant Tasks view. Grant Task management plus Inventory view only when this person must create or reassign work. Grant Tasks perform when they will record verification results.
4. A designated head can view and review private tasks for that department. Ordinary members, heads of other departments and unrelated Supervisors cannot open them.

Removing a person from the department, disabling their account or removing task access stops their head access. Existing task results and authorship remain unchanged. Current assignments can block retiring a department until the work is resolved or reassigned.

Wavelink / 46

Record maintenance work

Use reviewed routines and separate work orders

Maintenance has its own routine library and work-order history. A routine is a reusable instruction; a work order records one occasion on which that instruction is carried out. The application does not supply equipment procedures or approve an item for return to service.

1. An administrator creates and publishes a reviewed routine in the Maintenance builder.
2. Open Maintenance → New work order, select the published routine, enter the title and equipment description, and optionally add a reference, UTC due time and work instructions.
3. Choose the people who may record the work. Leaving the selection empty permits any user with Maintenance work permission. Maintenance managers may record work on any order.
4. Open the work order. Expand Introduction, routine details & reference pictures when needed. Record each step with the readings, notes and photographs required by the routine, then save to the hub.
5. Where approval is configured, the eligible named person or department reviewer reviews the saved result and evidence. Checking and approval are separate actions. The assigned reviewer may approve their own check; both actions are recorded.
6. A maintenance manager reviews and completes the order only when all steps are complete or justified N/A and all required readings, photographs and approvals are present. A cancelled order keeps its unfinished results.

Assigned users restrict who may record steps; Maintenance view remains project-wide for users granted that permission. A maintenance order is not a private verification task. Administrators publish routines; users with Maintenance manage may create and close work orders but do not automatically become step approvers.

A saved work order retains its original routine revision, introductions, reference pictures and source links. Later routine publication does not rewrite it. Amending a saved step requires a reason and makes earlier approval require fresh review. Finalised orders are locked.

Use Saved readings & evidence to inspect current submitted photos. Reference pictures explain the procedure and never count as completion evidence. Photo selection is limited to the same supported JPEG/PNG formats and item limits used for checklists. Hub receipt time is not verified camera capture time.

To link a new order to an inventory asset, open Asset details → New linked maintenance. The asset page and Calendar open that exact job. Earlier free-text equipment descriptions are not guessed into inventory links.

For a saved project handover across all current workspaces, use Projects → Export — choose contents… and choose Complete project or a supported selection. The preview lists current workspaces and required dependencies. Read Export and import project workspaces before sharing; original-file and private-history permissions are not a filter on the exported database.

In-transit assets cannot be changed or marked Found: receive them through Fleet first. Quarantine release remains a separate, explicit action.

Wavelink / 47

Build a maintenance routine

A guided path from your procedure to a saved draft

1. Open Admin → Maintenance → Maintenance builder…. Start blank or paste your reviewed outline, one step per line with # before a section. No manufacturer limits or technical instructions are generated.
2. Enter the routine title, equipment/system, optional code and stage names. One or two labelled stages are available. The maintenance work order records each applicable step; stage labels organise the work and do not operate equipment or substitute for procedural sequencing.
3. Add and arrange sections and steps. Each step can have text or numeric readings, units, required fields, reference pictures, optional/required photo evidence and a named or department approver.
4. Add optional introductory text, warnings and pictures. Record document ownership and procedure references, and optionally link exact original-document revisions.
5. Preview and check reviewer setup. Leave Publish now unticked to save an unfinished draft. Select Publish now, confirm the content review and save to make that routine revision available for new work orders.

Back and Next keep the unsaved wizard contents. Nothing is saved until Save routine on the last step. Reopen a saved draft using Edit routine / builder…. A validation error does not publish the routine; correct the issue before retrying.

Publication records the administrator and time, not a free-text signature. Later published revisions retain their prior revision history and do not alter existing work orders. Archive a routine to stop choosing it for new orders while keeping old records.

Wavelink / 48

Keep items inside boxes and kits

One container, separately identifiable contents

Mark an inventory item as a box / container. Place other existing items inside it with Put in box, or add a new item while the box is open. Each item keeps its own identity, serial, quantity and history; placing it inside a box does not duplicate it.

Browse contents

Use Open selected on the PC or tap a box name on the phone. The breadcrumb shows the box path. Up one box returns to the parent; All inventory returns to the full list. Opening a box clears previous filters so its contents are not hidden by the old search. Expand/collapse arrows remain available in the tree.

Adding an item while a box is open starts with that box selected. Review the field before saving. Search still finds nested items and shows their containing box. Location and owning department are inherited from the containing box.

Move equipment without losing the hierarchy

Select contents and use Take out of box to store them elsewhere, or Put in box to choose another container. Moving a whole box includes its descendants once, even when a child row was also selected. Invalid destinations are excluded; the server checks the current hierarchy again before saving.

Received equipment and its journey

An item received into a holding area stays visible as Received — awaiting placement. Use Fleet & manifests → Receiving & placement to record its final position rather than an ordinary local move. Asset details → Item journey shows available saved custody and movement events for the same item ID. Existing receipts are not automatically reclassified.

Wavelink 1.34.10 / workspace continuity

Expand a log and keep another window open

Keep logging visible without an unnecessary second sign-in.

Expand the current browser view

Use Expand view beside the logbook title. It hides surrounding navigation without loading another page or creating another session. The selected logbook, section and filters remain. Choose Return to normal or press Escape when no entry dialog is open. Opening another workspace exits focus mode.

An optional separate browser window

Choose Open separate window only when a second view is useful. Wavelink passes a one-use, short-lived session handoff into that new same-origin window, then the hub validates it. A valid account normally continues without another login. No password or token is placed in its URL, and the opener is detached. Popup blocking, expiry, changed hub/account or an invalid handoff can require sign-in.

Keep separate editing workspaces

A separate window retains its own guarded local draft store. It does not merge or share unsent forms with the main writer. Opening the identical saved window twice still has one-active-writer protection. Another account cannot claim earlier account-scoped drafts. An expired or revoked session is not revived; every saved operation retains its ordinary server-side permission checks.

Reopen and recover deliberately

Use Account > Separate log windows / drafts to reopen saved window records with a freshly validated current session. Keep the records and browser storage until each window's work is saved or exported. A normal project backup does not include unsent browser drafts. Review uncertain results before retrying; navigation never submits an entry automatically.

A separate Windows Admin window

Desktop Logs > Open separate window uses the same signed-in administrator in its existing native workflow. Resize or maximise that window separately. Each entry still needs a deliberate Save; closing main Admin closes its native log windows.

Connection and recorded meaning

These are views of the same project, not a second hub or synchronised database. Phones may open another tab rather than a floating window. Activity retains LOG ON, LOG OFF and New day; Line Status retains Completed, Partial and Not Attempted. Colours, entries and log views do not authorise equipment operation.

Wavelink / 50

Keep certificates with equipment

A certificate register, not a certificate issuer

1. Open Certificates → Certificate wizard. Enter the title, certificate number, type, issuing organisation and source revision.
2. Select the actual inventory item or items covered by the source. A certificate can cover up to 50 item records; a link is optional.
3. Enter the dates as stated: issue, valid from, expiry, next inspection and renewal target. Choose Expiry not recorded, Expiry date is recorded or Source explicitly declares no expiry. Enter the due-soon reminder window in whole days.
4. Optionally select a responsible project user or department and record scope, conditions, limitations and notes. This is a contact assignment, not a permission grant.
5. Review the information. Save as Draft while unfinished, or Recorded / active when the supplied information is ready for tracking. The PC wizard can attach files on its final page; in the browser, save the record and then use Attach file.

Attach the original PDF and supporting PNG/JPEG pictures, up to 12 files of 20 MB each per revision. Certificate attachments are kept unchanged. The file opens or downloads using the device’s supported viewer; no signature or authenticity is inferred. On the PC, attachments are saved after the record: an upload error leaves the record available and reports unfinished files.

Dates and renewals

A recorded expiry remains within its stated date until that UTC day ends. Due soon uses your reminder window; Expired means that date has passed. Future valid-from dates, unknown expiry and an explicit no-expiry declaration remain distinct. Draft, withdrawn, archived and superseded revisions do not generate active expiry calendar entries.

Use New revision for a renewed source. It creates a draft without inventing new dates or copying old certificate files as new evidence. Add the new source and dates, then Activate replacement after review. Earlier revisions, files and history remain available. Archive hides a record from normal selection without erasing it.

Permissions separately control viewing certificate files, changing records and exporting register reports. Asset links do not bypass inventory permission. Full project backups/transfers include the certificate register, files and history. Narrow inventory or checklist-only packages do not carry this register.

Keep the actual certificate file

Use Attach certificate file in the browser certificate record, or Add certificate file… on the PC. The PC wizard also accepts files in its final step. On a phone, save the certificate record first, then attach the original.

Supported formats are PDF, Word DOCX, Excel XLSX/XLSM/XLSB/XLS/XLTX/XLTM, PNG and JPEG. The limit remains 20 MB per attachment and 12 files per certificate revision. The larger limit used by Original documents does not apply here.

The original file is retained unchanged, including every page or worksheet. Use Open / save original file… on the PC, or the listed file in the browser, to retrieve it with your device’s supported viewer. This is not an embedded Office editor.

A project transfer that includes Certificates carries the original attachments, all certificate revisions and linked inventory. A renewal is a new reviewed revision; do not replace the previous issued document simply to hide an expired date.

User instructions

Open asset details and photographs

Connected asset workspace: identity, recorded custody and linked work

Open Asset / pictures / QR from Admin Inventory, use the browser asset link, or scan the item's project-specific label. The same item ID is used; nothing is verified, acknowledged, moved or saved simply by opening the page.

Find the record you need

Overview shows the asset reference, serial, inventory, recorded location, containing boxes, responsible contact, quantity and notes. The summary shows certificate records, open maintenance and accessible verification tasks. Counts are limited to your permissions; they are not a completeness check or an “equipment ready” decision. Unknown quantity is not zero.

Documents & photographs links to the actual certificate records and their source files. Current records appear first; archived and superseded revisions are separately expandable. Draft, withdrawn, missing-expiry and not-yet-valid states remain explicit. Identification photographs are not work-completion evidence. On Admin choose Load identification photos; browser photos load with a visible success or unavailable state.

Maintenance separates open orders from completed/cancelled history. Open orders show overdue, due within seven days, scheduled or undated status. Open the work order to review its instructions, evidence and approvals. Enabled maintenance cycles create one next order after saved completion. Pending follow-ups needing review are shown separately, not buried in completed history. Existing orders remain one-off unless a manager enables a cycle.

Linked tasks shows only verification tasks whose saved scope explicitly contains this item and which your current account may view. Completed/cancelled tasks are separately expandable. Opening the asset does not read a task alert. A box-only task does not automatically apply to its contents. General log issues are not guessed from names or serial numbers; review them in Logs.

Movement history loads saved changes, allocations, dispatches, receipts and placements only when requested. Browser history is inline; Admin opens the existing item-journey window. Actual event times are distinguished from saved record times. Missing events and dates are not invented.

Contents shows the direct child records of a box, with archived children separate. Open a child box for its contents or use a containing-box link to move up the hierarchy. Finding a box does not verify everything inside it.

Custody is not live positioning

In transit, the inventory location is explicitly labelled Last recorded inventory location, not the item's confirmed present position. Received items awaiting placement show their Recorded holding location. Use the authorised Fleet receipt/placement workflow; quarantine release is separate. Project workspace access alone does not grant Fleet access. Ordinary browser movement controls are not offered for archived, in-transit, awaiting-placement or quarantined items; server permission and state checks remain authoritative.

Edit, refresh and keep your evidence

Notes, low-stock settings, photograph upload, certificate creation and linked maintenance retain their existing forms and permissions. Photos are PNG/JPEG up to 20 MB within the supported pixel limit; the stored identification photo is a resized JPEG. Removing it from the gallery retains earlier audit evidence.

The browser needs the hub connection for this page and its attachments. The “records loaded/checked” time is a successful read, not a saved change. Failed asset loads remove previous summaries rather than presenting them as current; failed history and photographs show unavailable with a retry/refresh path. Admin reads the local project. This is not a general offline asset cache.

Chosen upload files are not offline drafts: keep originals until upload succeeds. Supported metadata forms retain their existing device drafts. Never clear unsent work. Full project backups/history-bearing transfers preserve asset profiles, files and links; narrow current-item inventory packages do not. Review private data and dependencies before sharing a project transfer.

Wavelink / 52

Print and scan inventory QR labels

A locator for an asset, not a password or approval

1. Open Inventory → List setup → Print QR labels… on the PC, or Print QR labels in the browser inventory. Select some rows first only when you need labels for those rows.
2. Choose All active items, Selected rows, By location / area, By owning department, By original source tab or One box. All refers to the current inventory list, not every project or only the rows visible on screen.
3. For a box, select Include contents to label its nested items as well. Otherwise only the matching box is labelled. Each item is included once. Archived items are excluded.
4. Review the item count and page count, then choose A4 sheets (eight labels per page) or single 70 × 40 mm labels. Generate label PDF creates all matching labels, up to 5,000. The on-screen name preview may be shorter than the full list.
5. Print at 100% / actual size. Test one label with the intended phone before printing the whole inventory. From an asset page you can still print that one item’s label.

What the label opens

The saved project and asset identity are encoded, never a password. A normal phone scan opens the asset after sign-in and access checks. A box opens its current contents; changing those contents does not require another label. Moving or renaming an item in the same project keeps its identity.

Inside an open stock verification or private task, use Scan QR instead to open that item’s verification form. The app checks that the item is inside the current scope. A box scan opens its own result, not every child result.

QR label printing requires Inventory view and export permissions. It does not change stock quantities, verification results or asset history. Keep printed labels and exported PDFs appropriate for the organisation’s data-sharing policy.

Wavelink / 53

Use the linked project calendar

Open the record behind every date

1. Open Calendar from Home or the Admin navigation. Use Previous month, Next month or This month. The browser also offers a month picker and Agenda-only view.
2. Tick the categories you need. The default overview includes certificate expiry/inspection/renewal dates, maintenance due dates, private-task deadlines and toolbox talks. Optionally include checklist record dates, inventory onboard/offload dates and confirmed-UTC log events.
3. Choose a day to see its agenda. In the browser click the event itself; on the PC select an event and choose Open linked record… or double-click it.
4. The link opens the particular certificate, work order, private task, talk, checklist, asset or log entry—not just its workspace. PC links to talks, checklists and log entries use the running hub and browser; certificates, assets, tasks and maintenance open their native detail windows.

A date-only source is shown as all day. Timed work uses UTC. Missing dates and unconfirmed log times are not invented or assigned to today. Low quantity is not a dated event, so use the separate Low-stock alerts link rather than creating a false expiry date.

Calendar view is an additional permission, not a way around other permissions. It only includes source work the current account may see. Private task titles, counts and links are excluded for unrelated users. A saved link still checks access when opened.

Project administrators can enable Manifest dates for planned shipment departures and arrivals. Each event opens the actual manifest in the Fleet portal. Vessel-only users use the Fleet calendar. It includes their authorised shipments and can show permitted log entry events when selected.

Wavelink / 54

Set low-stock alerts

A separate rule for each quantity-tracked item

1. Open the item’s Asset details, then Stock alerts & notes on the PC or Notes & low-stock in the browser.
2. Enable the low-stock alert and enter the quantity below which an alert is needed. For example, a threshold of 5 alerts at 4, but not at 5. Use the same unit as the item’s quantity.
3. Optionally select a responsible user or department. Save the settings; later changes require a reason.
4. Open Low-stock alerts from Inventory, Calendar or Home’s shortcut. Select an alert to open the exact item and review its current quantity. Update stock through the normal inventory-edit workflow when the physical quantity changes.

Rules start off. Empty quantity means unknown, not zero. A configured item with unknown quantity appears as Quantity unknown, separately from confirmed low stock. Quantities are not summed across boxes, locations or similar names. Each rule covers that one item record.

The alert clears when the saved quantity reaches or exceeds the threshold, the rule is disabled, or the item/list is archived. Moving a whole item retains its rule. A partial-quantity split leaves the source rule with the source record; review and configure any rule needed on the new destination record.

Verification results do not automatically change inventory quantity. A recorded Missing or Discrepancy result therefore does not automatically create a low-stock alert. Review the discrepancy and deliberately correct the current quantity when appropriate.

Wavelink / 55

Scan labels during stock verification

Find the scoped item, then inspect and save

1. Open the intended Stock verification or private verification task first. Choose the camera-shaped Scan QR button.
2. Choose Start camera, allow access on your approved hub and point the rear camera at one Wavelink label. Where supported, Read a photo of the QR label can decode a clear picture instead.
3. The scanner stops when it reads a code and checks the current project, permissions and verification scope. It opens that item’s check without saving a result. A previously verified item shows its existing values.
4. Inspect the equipment. Record Found / verified, Missing or Discrepancy, counted quantity where required, and notes. Save deliberately. A box is checked separately from its contents.
5. Close the scanner or use Stop camera when finished. Camera capture stops when the scanner closes, the page is hidden or the workspace is left. Frames are processed locally and are not uploaded or stored as task evidence.

When the in-app camera is unavailable

Live camera scanning needs trusted HTTPS, permission to use the camera and a browser that provides a QR detector. The program checks these capabilities; not every browser or device supplies them. QR-photo decoding also needs that detector. There is no cloud decoding service or automatic browser-protection bypass.

On ordinary HTTP, or an unsupported browser, use your phone’s normal camera or approved QR reader to copy the label link. Return to Scan QR and paste it into QR link or complete asset ID, then choose Open verification item. A USB/Bluetooth scanner can type there too. On the PC, use Scan / enter QR… for the same lookup. Do not clear website data or switch the hub address with unsent work.

A label is a locator, not permission

The code must identify this project and an item in this verification. Other-project and out-of-scope scans show an explanation without opening unrelated inventory. The original scope stays unchanged. Submitted/closed or read-only work cannot be edited through the scanner.

After a successful lookup, Found elsewhere? Move & verify… is available only to users allowed to move inventory. Enter the destination and reason, review box contents affected, then explicitly save. Scanning alone never moves equipment, records a result or changes quantity.

Wavelink 1.34.10 / workspace continuity

Manage vessels and shore bases

A controlled logistics workspace within the selected project.

Open the integrated workspace

Choose Fleet & vessels in the browser sidebar. Vessels, manifests, receiving, assets, logbooks, issues, calendar and setup stay under the same main header and valid login. The standalone /fleet bookmark remains available and may require its own sign-in; normal main-workspace navigation does not use that separate page. Desktop Admin keeps Operations > Fleet & manifests.

Set up sites deliberately

A project administrator uses Vessels & bases > Add vessel / base for vessels, shore bases, warehouses or workshops. Record the verified name, type and optional site details. Allocate existing stock only after confirming its physical site; boxes include active nested contents. Enter a reason. Initial allocation is not inferred from item names; later site changes use a manifest.

Grant the appropriate access

Use Access & setup for vessel grants. Site names, inventory locations, departments and Supervisor status do not grant vessel access automatically. Logbooks and Assigned issues need separately granted vessel-log permissions. Vessel-only accounts remain restricted to their authorised logistics and enabled logbooks, not older project-wide workspaces. Test sender and receiver access with fictional records first.

Find equipment and evidence

Assets & transit shows permitted equipment, shipments, images, box contents, certificates and linked maintenance. A multi-asset certificate requires access to every linked asset. Recorded site custody is separate from ownership and department custody. Dispatch makes equipment In transit; it does not create a second destination copy. Review confidential document contents before sharing.

Protect unfinished forms

An open Fleet form blocks leaving for another workspace until saved or closed. Lists and filters are retained while the main page remains open. Session expiry requires main sign-in; only the same account can resume its open in-memory form. Nothing is automatically saved by navigating or signing in. Fleet still needs a reachable hub and does not have a new offline draft queue.

Keep project and network boundaries

All sites belong to this project database. Separate databases are not combined or synchronised; imports have a new hub identity. Current custody determines supported asset access; downloaded copies cannot be recalled. Existing accounts and backend permissions still control access. Keep the approved private network; this release adds no public hosting, cloud sync or network repair.

Wavelink / 57

Set vessel-only access

Explicit site roles without project-wide access

1. Create the person as an enabled, named non-administrator account in Users & access. Existing passwords continue to work.
2. In Fleet & manifests → User vessel access, select the account. In the browser, use Access & setup → Edit access.
3. Choose Vessel-only access, then select a role for each permitted site. Leave other sites at No access.
4. Review the access warning, enter a reason and save. Saving revokes the person’s current sessions. They must sign in again through /fleet.

For operational logs, separately grant Log permissions. Read Set vessel log permissions; logistics roles do not open logbooks automatically.

Understand the access models

Project workspace access keeps the earlier project-wide permissions. Vessel-only access blocks those screens and permits granted logistics sites and separately enabled logbooks. Switching back restores the broader project profile. Preserve earlier device-only work before changing access.

The same checks protect the portal’s lists, guessed links, asset evidence files, shipment reports and calendar results. Vessel-only accounts cannot obtain a full project backup or enter the Windows Admin console. Department membership and Supervisor status do not bypass the restriction.

Shipments involving another site

Preparing a new manifest requires Operator or Manager access at its origin and at least Viewer access at the destination. The recipient needs destination Operator or Manager access to receive an existing manifest. A source-only operator can dispatch a prepared authorised manifest; a destination-only operator can receive it.

A sender or recipient can see the shipment route and line snapshots, not the other site’s unrelated work. Both sides may inspect shipped assets in transit. After receipt, current asset access follows the destination; the sender keeps the shipping snapshot, not future asset records.

Wavelink / 58

Dispatch and receive with manifests

Record the journey, then the final inventory position

Open Fleet & manifests in Admin, or Fleet & vessels in the browser. The Manifest wizard guides Route, Items and boxes, Transport details and Review. Select an origin and destination site, choose saved equipment and record the carrier, manifest number and planned dates. Save a draft, then attach the actual carrier paperwork as needed.

1. Review the draft and mark it Ready. Neither step moves the equipment. A prepared box includes its selected complete group; review the contents before dispatch.
2. At physical departure, select Confirm dispatch, enter actual UTC, the exact manifest number and a reason. Shipped item identities become In transit; other ordinary moves cannot bypass the shipment.
3. At arrival, select only the complete root items or intact box groups received. Choose Receive selected. By default this records a holding area and leaves final placement outstanding. Choose the explicit Final location alternative only when that is already physically known.
4. Open Receiving & placement for the pending groups. Record the final location or destination box with an actual time, note and confirmation. Unreceived groups remain In transit; pending received groups stay visible until placed.
5. Record a physical return at the origin when appropriate, or an exception for missing or short contents. Close only after every group has an actual receipt or return and no final placement is still pending.

Partial receipt means independently shipped root records or complete box groups. Whole saved records are shipped; split eligible bulk quantities in Inventory before preparing a part-quantity shipment. Per-child receipt of a dispatched box and automatic write-offs are not provided. Unknown quantities are not invented.

A damaged receipt remains quarantined. A final quarantine-store placement and an authorised quarantine release are separate actions; neither automatically does the other. A planned arrival is never an automatic receipt.

Attach PDF, DOCX, Excel, PNG or JPEG originals, up to 20 MB per file and 24 per manifest. Files are stored unchanged; macros and external connections are not executed. The manifest PDF lists saved route, items, receipt/return outcomes, final positions and supporting-file names. It is not a replacement for original carrier documents.

Read Receive equipment and record final placement for the full receiving workflow, and Follow an item’s journey for the consolidated history. These controls record actions; they do not authorise lifting, certify equipment or resolve insurance claims.

Wavelink / 59

Receive equipment and record final placement

Nothing disappears between the manifest and inventory

A manifest refers to existing inventory item records. Do not import or create another copy when those items arrive. Receipt and final placement update the same item identities, keeping certificates, pictures and maintenance links attached.

Confirm what physically arrived

1. Open the dispatched manifest. Select only the complete root items or intact box groups that physically arrived, then choose Receive selected.
2. The receipt form defaults to Holding area — place in inventory later. Enter the actual receiving area, UTC receipt time, condition and note. Confirm the manifest number and save.
3. The saved receipt records custody at the destination. Other unreceived groups remain In transit. Follow Receiving & placement to see received groups still needing a final position.

When the equipment is already in its final position, choose Final location — record placement now in the receipt form and enter that actual location. This is an explicit alternative; receipt does not silently assume the holding area is final. Older receipts made before this workflow are retained as recorded and are not converted into pending work.

Put received equipment away

1. Open Admin → Fleet & manifests → Receiving & placement…, or the Receiving & placement link in the browser Fleet navigation.
2. Review the manifest, receiving site, current holding area, receipt time and number of item records in each group. On the PC, select one or more complete groups from the same manifest and receiving site; on the phone, open one group with Place in inventory.
3. Choose a standalone final location, or an available destination box in the same inventory list at the receiving site. A received box keeps its own contents when placed inside another box. Quarantined stock must stay in a separate location, not an available box.
4. Enter the actual UTC placement time and a note, review the groups and destination, tick the confirmation and save. The whole placement is saved together. A changed item or box requires a new preview; no partial move is reported as successful.
5. Check the updated asset and manifest. The receiving entry disappears only after the final placement is saved; the original manifest line retains its receipt and placement details. Close the shipment after every dispatched group is settled and every pending placement is recorded.

Returns, damage and interruptions

A physical return can also be received into an origin holding area and placed later. Damaged receipts remain quarantined. Putting them in a quarantine store records their position but does not release them; a quarantine release before placement still leaves final placement outstanding. Missing or short box contents remain an unresolved shipment exception, not a completed receipt.

Fleet forms need a hub connection. After an uncertain response, inspect the manifest or refresh the receiving list before repeating the action. Retrying the same saved operation does not move equipment twice. Full project backups and history-bearing Fleet transfers retain pending receipts, final placement details and history. No arrival, position or physical action is inferred from a planned date.

Wavelink / 60

Follow an item’s journey

One item identity from registration to its current position

Open an inventory item through Asset / pictures / QR… → Item journey… on the PC, or Item journey on the browser asset page. Fleet asset pages also include an Item journey link. In the receiving window, select a group and choose Item journey.

The page shows the current custody state, site, location and container path, followed by the available saved events. It brings together inventory registration, original source/import information, local box and location changes, site allocation, related manifests, dispatch, physical receipt, final placement and recorded quarantine releases.

The same inventory ID follows the equipment. No second item is created by receiving or placement, and moving a box does not detach its contents. Use the item’s established History when the full field-change detail is needed. Older evidence is shown as recorded; missing times or undocumented movements are not invented.

Changes recorded outside Wavelink are not tracked until entered. Physical labels identify the item; scanning never confirms a receipt, move, verification or approval by itself. Keep source documents and follow the project’s movement procedures.

Wavelink / 61

Use vessel-specific logbooks

Operational logs without opening the wider project

Open the team’s saved hub address followed by /fleet, sign in with your named project account and choose Logbooks. A vessel-only account sees only whole logbooks deliberately linked to sites where it has log access.

Open and record work

1. Choose the vessel or base, then open a logbook. Its vessel name stays above the log title. Use the section tabs to select Activity, Survey runs, Weather, Issues or another configured section.
2. Use Add entry when your assigned log permissions allow it. Enter the actual event time in UTC, the required fields and notes. Calendar and time controls are available; no surveyor initials are required.
3. Review the form and choose Save to hub while connected. The app separately records your account and the save time. LOG ON/OFF only prefill an Activity event; they do not control recording equipment.
4. Open an entry to read the complete saved values. With the appropriate permission, choose Correct entry, enter a reason and save. Earlier values remain in History. Void entry preserves the record rather than deleting it.

Keep the log readable

Scroll within the coloured table; headings and the first column stay visible. Use All columns for detail, Filters for search, UTC dates and voided entries, or Expand view for more room. Legends follow the section, not every tab.

Routine updates retain your place and leave an open form alone. Save before changing workspace, signing out or closing the window.

Assigned issues and calendar links

An Issues entry can be assigned to users or departments allowed to read that book. Open Assigned issues for outstanding work. Reading an alert does not resolve it or grant editing rights. Alerts are in-app, not email or background push.

In Calendar, select Log entry events or Shipments and log events. Each opens its saved source. A range of up to 93 UTC days shows up to 500 authorised events with confirmed times. Voided entries and archived books are excluded. Narrow the range when advised.

References and reports

References appears only when you may view released reference pages. The administrator must first release each page in the project Logs workspace. Source screenshots, text and inactive formulas are reading material, not equipment approval. Uploaded source material may contain confidential information; review it before granting access.

Export report requires its own permission. CSV, PDF and Excel include all matching saved rows, not just the page shown. Choose working/full columns and clear UTC filters to include unconfirmed times. These table reports omit reference pictures and full history.

Wavelink / 62

Set vessel log permissions

Link the whole book, then grant only the actions needed

Prepare and link the logbook

1. As a project administrator, create or import the logbook in Logs → Logbook setup. Review the complete history and source references. For a new vessel, normally create a separate logbook.
2. Open Fleet & manifests → Vessel logbooks & permissions. Select the book and choose Link / review vessel. Choose the site, read the entry/reference counts, enter a reason and confirm the content review.
3. Choose Save vessel link. The scope covers the entire history and future entries, without editing them or granting access. Do not label mixed-vessel history as one vessel to expose it in the portal.
4. In User vessel access, give an enabled non-administrator Vessel-only access and the relevant site role. In Log permissions, select their vessel row and enable the required actions.

Choose the log actions

Adjust the tick boxes after choosing a preset. View is needed for actions; Correct any includes Correct own. A logistics Viewer can separately be a log Contributor. The two permission sets remain independent.

Save with a reason. The affected user must sign in again. Permissions apply to all enabled logbooks of the selected site, not to every vessel or separately to each logbook. Removing a site grant clears that site’s log permissions; adding the site later does not restore them without review.

Withdraw access without moving history

Use Withdraw vessel access to hide a linked book without deleting it. Link / review vessel can restore only the same site. Its vessel identity cannot change; create another book for another vessel. Project-wide access is unchanged.

Archived books remain available for authorised reading, not new entries or corrections. Archive or withdraw active books before deactivating their site. Earlier downloads cannot be recalled.

Recovery release 1.30.1

Administer people from the browser

Current project access, with deliberate online changes

Sign in with a named, enabled project administrator. Open Administration in the sidebar, or /admin on the existing hub address. This opens the same project and account store as desktop Admin; there is no second user library.

People and access

Find a saved user by name or User ID. Select the person to edit their display name, role or enabled state; reset another user's password; review project permission flags; or open Review effective access. Create a new user with an initial password and a reviewed project role. Use Account > Change my password for your own password. Another administrator must disable or demote your account. Account and permission changes revoke the edited person's existing sessions.

The read-only review combines current permissions, departments and effective heads, Fleet roles, separate vessel-log rights and full-backup eligibility. Reading the review neither changes access nor acknowledges a task. Department names are not a vessel boundary. Vessel-only project flags are retained; use the existing Fleet tools for site access and separate logbook grants.

All operational access does not silently add full-database backup permission. A new backup grant requires a separate acknowledgement. Full database backups remain unencrypted and not recipient-filtered; existing private-task restrictions still apply.

Departments

Choose Departments to create or rename a team, edit its description, choose members, appoint eligible enabled members as heads, or activate/deactivate the department. Review recorded references and recent history. Native reference rules can block deactivation. Renaming retains earlier names and references; removing membership does not erase recorded work. These controls do not merge or permanently delete departments.

Review, save and retry

Each change requires a reason and an initially unticked confirmation. Open editors require a live hub and are not offline drafts. Fields lock while sending. A record changed by another administrator is rejected instead of overwritten; cancel and reopen its current saved version.

After a lost or ambiguous response, keep the form open and use Retry unchanged request. The same action ID confirms an earlier saved change instead of duplicating it. The metadata receipt contains identifiers and status, not the form or password. Closing an uncertain editor can lose its in-memory contents and does not undo a committed change. Preserve the receipt and inspect the saved record before beginning a different action.

One navigation sidebar

Home centres on Needs attention and unsent work. The old repeated Home workspace-card grid and horizontal workspace strip are replaced by one grouped, independently scrolling sidebar. Wide screens have Hide sidebar / Show sidebar; narrower screens use Menu, Close menu, Escape and a backdrop. Account contains identity and personal/tools actions. Fleet uses the same navigation shell, but retains its existing site, role and logbook restrictions.

The header connection indicator opens Connection & saves. Only a healthy redundant strip with no outstanding local work is hidden. Uncertain saves, pending work, conflicts and connection/storage failures remain visible. Reading a page does not confirm an uncertain save.

Still on the host PC

Installation/removal, first administrator setup, project folders, hub start/stop, network/TLS, transfers and template import, original-source review and picture-editing tools stay in desktop Admin; checklist/routine text authoring is also available in the browser. The existing desktop sidebar is preserved. No firewall, advertised address, port or protocol is changed.

HTTP does not encrypt passwords or management traffic. Use an approved trusted network and trusted HTTPS for confidential shared-network work. The host must remain running. This recovery line preserves browser administration from 1.28.1 and adds the documented 1.29 template/routine editor; it is not an identical original archive.

Recovery release 1.30.1 / step 2 of 6

Author checklist templates and maintenance routines

A hub draft first. A separate saved-revision review before publication.

Sign in as a named project administrator and open Administration > Templates & routines. The browser uses the existing native definition library, not a second store. Search or filter by kind and lifecycle. Both native Admin and browser work against the same saved revisions.

Create a blank definition

Choose New definition, select Checklist or Maintenance routine, then enter its title, system, code and one-stage or two-stage labels. Enter a reason and tick the confirmation. The result is an unpublished, empty hub draft. No procedures, check results, operating limits or maintenance intervals are invented.

Details and one selected check

Details contains the title, system, document code, owner/department, purpose, stage labels, new-record defaults and tools. In Sections & steps, choose one section and one check. Add, move and reorder sections or checks; edit wording, guidance, responsible role, stage inclusion, readings, photo requirements and eligible reviewer. Reordering retains stable section/check IDs and reading keys. Visible numbers are not automatically rewritten.

Text readings and numeric readings can be optional or required. Numeric readings need an explicit finite minimum and maximum; neither is inferred from an imported document or earlier result. The browser cannot switch an existing definition's workflow mode. Use native Admin for specialised structural/import changes.

Preserve references and source material

Original-document revision links and bytes, imported source review, introduction pictures, check reference pictures, procedure references and supported extension data remain attached. The editor displays references read-only. It merges only supported edits by stable identity, rather than replacing the entire definition. Removal that would discard protected metadata is blocked. Unsupported document-control extensions are read-only because native publication would otherwise normalise them away. Review source links, imports and pictures in native Admin.

Save a hub draft; then review publication

The editor's Review tab previews the proposed in-memory contents, not a published revision. Enter a reason and explicitly confirm Save hub draft. This does not change the published head. Close the saved editor, choose Review saved draft for publication, and inspect the exact server-saved wording, limits, references and reviewer requirements. A second reason and initially unticked confirmation are required to publish.

Publication is blocked for incomplete checks, missing stage coverage, unresolved source/import review or ineligible required reviewers. The review token is tied to the exact draft and current eligible reviewer list. A later edit or changed eligibility requires a fresh review. Publication records a definition revision; it does not authorise an operation.

Retained drafts, archive and restore

A checklist draft retained from before the published head is read-only. Open the current published version to begin another revision and separately confirm replacing the retained old draft. Archive prevents selecting a definition for new work, without deleting its existing records or revisions. Restore is explicit; restoring an unpublished draft does not publish it.

Existing evidence stays with its record

Completed and open checklist records keep their saved definition snapshots, readings, photos and approvals. Existing maintenance orders keep their steps and evidence. A changed routine may require the existing recurring-maintenance follow-up review; this editor does not silently update an order or bypass that review.

Online authoring and uncertain saves

Open edits are held in this tab and are NOT offline drafts. Keep the hub reachable. Controls lock while sending. A lost response may mean the action already saved; keep the editor open and use Retry unchanged request. A metadata-only receipt identifies the original action without storing the full template. Check the current saved definition before starting a different action. Closing the tab or changing account can lose in-memory edits; a receipt cannot reconstruct them.

Concurrent native/browser edits are rejected, not merged. The old wording remains read-only until you deliberately close/reload it. Failed reads remove stale details. Existing operational offline drafts and uncertain-save warnings are not cleared by opening this editor.

The checklist and maintenance editor was reconstructed as 1.29.1 Recovery. Toolbox forms use different publication semantics; Handovers is now a separate workspace. Browser logbook design remains a later step.

Recovery release 1.30.1 / step 3 of 6

Author toolbox-talk forms in the browser

Reusable wording and revisions, separate from recorded briefings.

Sign in with a named project administrator account, then open Administration > Templates & routines. The same library now includes checklist templates, maintenance routines and toolbox-talk forms. Search or filter by kind and status. Actual briefings remain in the operational Toolbox Talks workspace.

Create a complete unpublished form

Choose New toolbox form. In Details, enter the title, optional document code, purpose, supervisor instructions and personal acknowledgement declaration. New wording starts blank; use the procedures approved for your operation. In Discussion, add one to 100 grouped prompts. In Understanding, add one to 20 Yes/No questions. The editor shows one selected prompt or question at a time; phone layouts use a compact selector. Add, remove or reorder entries as needed.

Open Review to inspect all wording. Enter a reason and tick the initially unchecked confirmation, then choose Save unpublished hub draft. The complete native form constraints apply even to draft saving; incomplete forms cannot be saved. Saving a draft does not publish it, create a briefing or acknowledge anything.

Publish the exact saved draft separately

Reopen the saved form and choose Review saved form for publication. The hub checks the exact saved definition and current authority. Inspect the wording, enter a reason, and explicitly confirm Publish reviewed revision. Changing the saved form in another window invalidates that review; stale content cannot overwrite the new state.

Propose a revision of a published form

Published toolbox forms have no parallel saved hub draft. Choose Propose revision. These edits stay only in the open browser tab. After changing the wording, open Review and choose Review this complete form with the hub, then confirm publication separately. Any wording change invalidates review and consent. An unchanged reviewed form does not create an extra revision. Closing or reloading before publication loses the proposal; the existing published form remains unchanged.

Previous talks keep their own evidence

Reordering uses the native positional references in the new form revision; it does not relabel old answers. Open, finalised and cancelled talks retain their saved form, discussion results, answers, attendees, guests, personal acknowledgements and witnessed-guest acknowledgements. Archive prevents selection for future talks without deleting previous evidence. Restore is explicit; restoring an unpublished form does not publish it. Opening or publishing a form is not acknowledgement, permit-to-work or approval to operate.

Retain original source and unsupported fields

Source/import metadata stays attached. Pending imported-source review and unsupported extra definition fields are read-only in this editor. They are not discarded or automatically approved. Document import, source editing and source-review resolution remain in native Admin. The native toolbox service and existing project database remain authoritative.

Online authoring and uncertain results

These authoring forms are NOT offline drafts. Keep the hub reachable and save complete unpublished drafts regularly. A published-form proposal remains in memory until publication. This is separate from supported operational briefing Local forms.

Controls lock while sending. After a lost response, keep the editor open and use Retry unchanged request. An exact retry confirms the original action without a duplicate revision. A later rejected request does not prove an earlier uncertain save failed. Metadata-only receipts contain identifiers/status, not the full form or declaration, and cannot reconstruct a closed editor. Account/session or project invalidation clears sensitive authoring fields without clearing operational drafts.

This toolbox authoring step was reconstructed in 1.30.1. Handovers is now a separate operational workspace in 1.33.1; see its dedicated instructions. The original toolbox source and briefing records remain unchanged.

Handovers / daily continuity in 1.34.10

Daily handovers, one department and shift at a time

Continue your saved draft, then pass reviewed outstanding work to the next shift without overwriting history.

Open Handovers in the main browser sidebar. Native Admin > Handovers > Open Handovers in browser opens the same saved hub address. The hub must already be running. Use your own named project account; this release does not create a second native editor or change network settings.

Your department's day

Choose an Operational date, a Vessel / site label and an active Department, then select Show day. The initial date comes from this device's calendar: choose the actual operational day explicitly. Vessel/site is a text label, not Fleet access or a Fleet vessel identity. Consistent labels group together ignoring case and repeated spaces. Department identity, not its display name, separates departments. Retired departments cannot start new shifts.

The daily view shows only your own private drafts and publications your account can currently read. It is not a complete crew roster and does not reveal another author's private work. Existing ungrouped handovers remain in All saved handovers; their dates are not guessed into daily groups.

Start, continue, or hand over to the next shift

Use Start today's handover or Start daily handover when no accessible daily publication or saved draft is present. Enter outgoing and incoming shift names, actual period start/end and an explicit time basis. Review the exact proposed setup, give a reason and confirm Create private shift draft. Creation saves a new author-only record, not a publication, and opens Work & priorities for this shift's notes.

Continue my draft opens your existing saved shift rather than making a new record. The create action prevents a second active private draft for the same author, label, department and day. This is not a global lock on other people's invisible drafts.

After publication, choose Start next shift. The proposed outgoing/incoming names reverse the previous pair and the previous period end is offered as the next start; check both. Enter the new end. The operational date stays explicit: a night shift can cross midnight within the same department's day, or you may choose the next day. No schedule, duration, time-zone conversion, missing day or automatic publication is inferred.

Select earlier outstanding work, hazards and incoming priorities to carry forward, with equipment status and additional notes optional. Each copied section is labelled as earlier published wording. Situation/summary, completed work, acknowledgements and named recipients are not copied. The chosen department is proposed as the new audience; review it before publishing. Recheck and edit the facts for your shift. The saved copy is independent, not a live link; later source changes do not update it.

The daily date, department, shift pair and vessel/site context are fixed for that record. Review them before creation; deliberately discard an incorrect unpublished draft and create the right context rather than moving saved evidence. The actual work period and text remain editable. Use Other handover for an ordinary ungrouped or full-hitch handover; Prepare from previous retains the separate multi-source preparation workflow.

Deliberately save your shift's work

In Work & priorities, select one section at a time: situation/summary, completed work, equipment/system status, outstanding work/issues, hazards/restrictions/controls, incoming priorities or additional notes. Write your own reviewed facts. These notes do not update any task, asset, maintenance result or checklist.

Select the intended people or departments in Audience, inspect the full in-tab review, enter a reason and confirm Save private hub draft. Incomplete drafts may be saved with a valid title and valid supplied values. Saving is not publication. An incoming colleague creates their own shift from the published predecessor; they cannot edit your private draft.

Publish the exact saved draft

Reopen the saved handover and choose Review saved draft for publication. Read the exact saved wording and audience returned by the hub, enter a publication/change summary and separately confirm Publish reviewed revision. Publication requires the period, time basis, situation/summary and at least one other eligible recipient. A saved edit or changed eligible audience after review requires another review; there is no silent substitution.

Who can see it?

Drafts belong only to their author in the application, including when another administrator is signed in. Published content requires current Handovers view permission and either explicit named-person selection or current membership in a selected active department. The author retains access while their account/capability is eligible. Administrator and department-head status alone do not add readers. Vessel-only accounts are excluded. Explicitly saved old permission dictionaries do not automatically gain the new capabilities; review them in Users & access. Accounts using role defaults receive the new default Handovers capabilities.

A reader needs access to both the current audience and the selected historical revision's audience. New recipients do not gain earlier revisions outside their audience. Deactivating an account, department or capability can remove current access. Department names and retired user identities stay attached to history; administration dependency checks expose no private handover wording.

Revise without rewriting evidence

Start private revision explicitly copies the author's latest publication into a separate private working draft. The published revision stays available unchanged. Save changes, review and publish separately. A changed publication creates a fresh revision; previous text and acknowledgements remain with their old revision. No acknowledgements are copied forward. Unchanged reviewed wording does not create an extra publication. Discarding a private revision leaves the published one intact. Discarding an unpublished draft removes its wording but retains an archived audit identity. Archive hides a record from default lists and stops new acknowledgements; restore does not publish a draft.

Personal acknowledgement and reports

A recipient opens the current saved publication, chooses Read & personally acknowledge this revision, reads all wording and confirms the declaration personally. Nobody signs for another account, and the author cannot sign as an incoming recipient. Reading, history browsing and PDF export never acknowledge. This records communication, not approval to operate or completion of outstanding work. Starting the next shift does not acknowledge the previous one. The author can view recorded acknowledgements by revision; the separate Current recipients view now resolves the current published audience; see the continuity instructions.

Export displayed published PDF exports only the permitted saved publication and the acknowledgements visible to that reader. The published PDF identifies the daily date, department snapshot and outgoing/incoming shift when present. Private draft wording is not exported by this button. The downloaded file cannot enforce future audience changes; share it only with an authorised recipient. Check the actual browser download and saved PDF.

Online forms and uncertain results

These forms are NOT offline drafts. Save private drafts to the hub regularly. Unsaved changes exist only in this tab. Controls lock while saving. After a lost response, keep the form open and use Retry unchanged request; exact retries do not duplicate publications or acknowledgements. A later rejection does not prove an earlier uncertain action failed. Receipts retain identifiers/status, not the full text, and cannot reconstruct a closed editor. Stale proposals remain read-only until explicitly closed/reloaded. Signing out or changing accounts removes in-tab private contents without clearing unrelated operational drafts.

Backups, transfers and compatible versions

Full backups remain unencrypted and contain private handover drafts and restricted publication history. Once handover content exists, browser full-database downloads are restricted to eligible administrators; the copied snapshot is checked too. A selected-workspace transfer includes all handover drafts/history when Handovers is selected, not only that recipient's records. Omitting Handovers removes its content and audit records from the disposable copy. It does not edit the original project. Protect account hashes and all confidential contents.

The original Handovers component uses five tables. Daily grouping in 1.34.3 adds optional metadata inside those existing records; it adds no new tables. Use a compatible 1.31.1 Recovery or later compatible recovery build after adding Handovers. Do not reopen the project in an earlier application: it cannot enforce the new backup restrictions. After creating grouped daily handovers, keep version 1.34.3 or later; older versions do not understand the daily grouping. Unrecognised original/future handover formats are rejected, not migrated. Native restore preflights the component and retains a rescue backup. Test with fictional data before operational use.

Preparation from previous handovers, dashboard summaries and the author-only current recipient roster were introduced in 1.32.1 and remain available; see the separate continuity instructions. Browser logbook design is now available in 1.33.1, with its own setup and navigation guide. Network investigation is parked, not diagnosed or fixed. The installer is unsigned and online; actual Windows, phone and network acceptance remain required.

Handovers / preparation, daily continuity and recipient evidence

Prepare handovers and review current recipients

Carry forward selected published wording deliberately, without copying sign-offs or calling old work new.

Daily department / shift work: use the daily view in Handovers and Start next shift to retain the selected operational day and department. That focused flow copies selected unresolved sections from one current publication. The separate Prepare from previous workflow below still accepts up to 12 sources and creates an ungrouped handover. It does not infer a daily group. Both preserve private drafts and independent acknowledgements.

Prepare a new private draft

In the main browser, open Handovers > Prepare from previous, or open an active current publication and choose Prepare a new handover from this. Use your own named account with Handovers view and create permissions. Source lists show only currently permitted, active published revisions, never somebody's private working revision. The native Admin shortcut still opens this browser workspace.

Enter a new title and choose Daily / shift or Full hitch. Search published sources by title, author or period, or filter their type. Select up to 12 sources. Configure one selected source at a time and explicitly choose its work sections; none is selected automatically. Move sources earlier/later to set the copy order. The list is paged at 50 results. A selected source must still have the same current publication when the private copy is created.

Choose Review exact prepared wording. The hub supplies exact selected text with an earlier-wording heading for each source. It does not generate an automatic summary, infer completed work, truncate long sections or copy source drafts. Combined sections over 8,000 characters are rejected; choose fewer source sections. Changing the title, type, selected sources or sections clears the review and confirmation. Read the preview, give a reason and tick the initially unchecked confirmation, then choose Create reviewed private draft.

Finish the new period before publication

The result is a new, author-only private hub draft with its own identity. Its period dates, time basis, location and audience start blank. No signatures, approvals, source recipients or completion results are inherited. Use Edit private draft to review every historical statement, enter the new period, choose the intended audience and save. Use the existing separate saved-draft publication review to publish deliberately. Neither preparation nor viewing the preview acknowledges the original handovers.

The author's Preparation sources record retains source identities, revisions and selected sections. Links check current access to the original records. It is an independent copy, not live synchronisation: later source changes or access withdrawal do not update or erase a copy already saved. Publishing copied wording to a chosen audience does not grant that audience access to the originals. The author must have authority to share the wording with the new audience; source restrictions are not inherited by the new draft.

Needs attention

Home now separates handovers awaiting your personal acknowledgement from your private hub drafts. Each preview shows up to five entries, with actual counts and links to the corresponding saved record. The author sees only their own draft titles; a recipient sees the published title, not an author's private revision. Archived handovers and revisions already acknowledged are not pending. An account without acknowledgement permission is not shown an acknowledgement action. These are not unread-email counts: opening a handover does not acknowledge it.

An unavailable summary is shown as unavailable, not zero. Rechecking the dashboard, source list or roster changes no task, equipment state, maintenance result or signature.

Current recipients: an author-only review

Open your handover and choose Current recipients for its current published revision. This resolves current enabled project accounts and current members of selected active departments, not a frozen publication-time attendance list. A person selected both directly and through a department appears once; the author is excluded. Review personal acknowledgement status, pending acknowledgements and view-only accounts separately. A new department member has not automatically signed. The view-only count covers currently eligible people with no signature and no acknowledgement capability.

Signatures recorded by people no longer in the current roster remain in a separate evidence section. Earlier published revisions keep their own signatures. An archived handover requests no new acknowledgements. Inactive departments and unavailable named selections are reported without silently selecting substitutes. Only the author can see this full roster; a recipient, unrelated administrator or department head cannot use it to inspect other recipients' current status. Refresh clears stale names/counts first. A changed publication requires reopening the current record.

Online saving and recovery

These forms are NOT offline drafts. Controls lock while saving. After an uncertain response, keep the form open and use Retry unchanged request; an unchanged retry confirms the same created draft, even if the original source later changes. A different request ID is a different action. Receipts contain identifiers and status, not full source wording, and cannot reconstruct a closed form. Read-only previews create no mutation receipt.

Full backups remain unencrypted and can contain private preparation copies, source metadata and restricted history. Existing administrator-only content-bearing Handovers backup checks remain. This step adds no tables or new runtime dependency and leaves previous evidence, server-start and network settings unchanged. Use a compatible recovery build, never downgrade to a pre-Handovers application. Windows, live-phone/network and persistent browser-storage acceptance remain required.

Next separate upgrades

1.33.1 Recovery adds the browser logbook designer and left-aligned navigation. General-purpose tasks arrived in 1.34.0 and remain available. Daily department/shift continuity arrives in 1.34.3. Task-specific checklists remain the next separate increment. Existing inventory-verification tasks remain unchanged.

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 project administrator account. Open Administration > Logbook designer, or Logs > Design logbook. 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. Original-workbook import, .ajlogs package import and offset-table setup remain in native Admin. 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.