Frequently Asked
Questions

SealsLog is a digital security seal tracking system for UK freight forwarding operations subject to CAA Aviation Security requirements. It replaces paper-based seal logs with a fully auditable digital record of every seal issued, used, and returned.

Visit app.sealslog.com in any modern browser. Enter your username and password. If you have access to multiple sites, a site selector will appear — choose the branch you are working at today.

On the login screen tap Forgot password? and enter your registered email address. You will receive an email with your username and a new temporary password. You must change this on your next login.

On the login screen tap Request an account. Fill in your name, email address, and select your branch. Your request is sent to the site administrator. Once approved you will receive your login details by email.

• Standard User — book seals out and in, manage drivers, register stock, view records
• Super User — everything Standard can do, plus create new Standard User accounts
• Org Admin — manages all users and sites within their organisation, access to archive and broken seals report, can amend closed records
• Platform Admin — full access across all organisations

From the Daily Log tap + Book Out Seals. Select the driver, date of use, and reason. Tap seal numbers from the inventory to select them — they appear in the bar at the bottom. Tap Confirm Book Out when done.

Yes. The Date of Use field defaults to today but can be changed to any future date. The record will not appear in Outstanding until that date arrives.

Drivers are managed in Admin → Drivers. Any user can add a new driver. Enter the full name and employee ID and they appear in the booking dropdown immediately.

• Page 1 — CAA Security Audit Record. Stays in the office. Driver and issuing officer both sign.
• Page 2 — Departing Vehicle Checks sheet. Travels with the driver. Produced for applicable reasons only (e.g. Night Run).
• Page 3 — Airline Manifest. ATF sites only.

Go to Outstanding and tap Book In on the relevant record. Each seal is shown as a tile — tap to cycle through states:

• First tap — green ✓ = returned intact, goes back to stock
• Second tap — red ! = broken (mandatory comment required)
• Third tap — back to unticked = used or missing

Complete the checklist and tap Confirm Return.

Yes. If all seals were used on the job, leave them all unticked and confirm. Tick All Seals Accounted For to confirm this is intentional.

Yes. Expand the closed record on the Daily Log and tap ✏ Amend Seal Record. You can change any seal's status. A mandatory amendment note is required. The change is permanently logged in the audit trail.

All seals must be returned or fully accounted for no later than the end of the following operational day. Records past this deadline are automatically flagged as Overdue in the Outstanding tab.

The seal is flagged as broken with a mandatory comment. Its status is set to broken and it does not return to stock. It appears in red ⚠ in the stock box view and is included in the 30-day Broken Seals Report.

Go to Admin → ⚠ Broken Seals. This generates a printable report of all broken seals in the last 30 days, including seal number, record reference, driver, site, date, and the mandatory broken comment.

Yes, using the ✏ Amend Seal Record function on any closed record. An amendment note is required and the change is audit-logged.

Go to Seal Stock → + Register New Box. Enter the seal range and quantity. A unique Box ID is auto-generated. A printable ticket is produced — attach it to the physical box.

The Available count shows the total seals currently in stock and ready to issue. Issued, used, and broken seals are not counted.

Yes. Click any row in Seal Stock to expand it. Each seal is colour-coded: green = in stock, yellow = issued out, red ⚠ = broken, grey strikethrough = used.

Yes. From Seal Stock tap ⇄ Transfer Box. Select the box and destination site. A reason is required. The transfer is logged in the audit trail and the seals become available at the new site immediately.

SealsLog handles seal number reuse automatically. If a seal number from a new box already exists as used or missing, the system resets it to in_stock linked to the new box. The original usage history is retained in the audit trail.

Go to Admin → Users → + Add User. Enter the username, display name, email address, role, and site. A welcome email with login credentials and a full tutorial is sent automatically. The user must change their password on first login.

In Admin → Users, click ⚙ Sites on the user. Tick the sites you want them to access. Their home site is always included. When they log in the site picker will show all permitted sites.

In Admin → Users, click ✏ Edit on the user. You can change their display name, email, home site, role, and active status. Every change is logged in the audit trail.

The Archive moves old returned records out of the active daily log to keep performance fast. Archived records remain fully searchable. Archive is accessible to Org Admin and above via Admin → Archive.

SealsLog is designed specifically to meet the record-keeping requirements of the Civil Aviation Authority and Department for Transport for UK freight forwarding operations. Every seal movement generates a timestamped, tamper-evident audit record.

No. The audit log is append-only and cannot be modified or deleted by any user. When records are amended, both the original and the amendment are preserved with full timestamps and usernames.

During book-in, leave the missing seal unticked. It is recorded as used/missing. Add a note in the discrepancies field.

Chrome, Firefox, Safari, and Edge. For the best mobile experience use Chrome on Android or Safari on iOS. Microsoft Edge with Tracking Prevention set to Strict may block the email service — use Balanced or Basic mode if you experience issues sending emails.

The app shell loads from cache so you will see the login screen offline, but all data operations require an internet connection. A stable connection is required for normal operation.

• HTTPS encryption for all data in transit
• bcrypt password hashing — passwords never stored in plain text
• Supabase PostgreSQL database with enterprise-grade security
• Session-based authentication — sessions expire on logout
• Role-based access control — users only see and do what their role permits

• Check your internet connection — a stable connection is required
• Try the Archive function to move old records out of the active view
• Use the Search tab rather than scrolling through large daily logs