Knowella

Container and Trailer Seal Check

The seal check that fails in practice isn't a missing seal — it's a matching one that nobody actually read. A receiver glances at an intact seal, assumes it's fine, and never lifts the delivery note to compare the number underneath. A re-sealed or substituted load passes visually every time, because the test that's supposed to run is a character-by-character comparison, and the test that actually runs is a glance.

KnowLogisticsChecklistLOG-004Pinned in navigation39 fields across 4 sectionsFull researchSee the form

Reviewed by Siddarth SinghCSPLast reviewed 16 August 2026

Basis
FSMA Intentional Adulteration rule
Workspace
KnowLogistics
Form type
Checklist
Completed by
The receiver, on every sealed arrival
Review trigger
Any seal number that doesn't match, or any sign of tampering

The short version

  • A container and trailer seal check is a checklist used in KnowLogistics that verifies the seal number against the paperwork and records its condition before the doors are opened, built against the FSMA Intentional Adulteration rule.
  • The check exists because an intact seal proves nothing by itself — only a number that matches the paperwork character-for-character proves the load wasn't opened in transit.
  • A mismatch is treated as a security and food defense event, not a paperwork note: doors stay closed, a manager is informed, and the carrier is contacted before the load is opened.
  • It feeds Security Incident and Receiving Inspection, so a failed seal check routes a load into the security process before receiving inspection ever begins.

What this is

What is a container and trailer seal check?

What is a container and trailer seal check?

It is a checklist completed by the receiver on every sealed inbound arrival, built against the FSMA Intentional Adulteration rule. It verifies the seal number on the paperwork against the number on the vehicle or container, and records the seal's physical condition before the doors are opened.

When is a container and trailer seal check completed?

It's completed at the point in the process it protects — on arrival, before the doors open — every time a sealed load arrives. A check performed after unloading has already started has missed the point it exists to cover.

What makes a seal number 'match exactly'?

Every character stamped on the physical seal must correspond to the sequence on the delivery note, with none substituted, transposed or assumed from a partial read. A close match on a worn or partly legible seal is not the same as an exact one, and this template treats them as different answers.

Scope

When is a container and trailer seal check required?

This checklist is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on.

Use this template when

  • A sealed container or trailer has arrived, or is about to, and the seal needs verifying before the doors open
  • The workspace is being set up, or the register needs an entry added or retired
  • You are running the Inbound and Receiving programme and this is one of its steps
  • A linked record needs this one to exist: feeds Security Incident and Receiving Inspection
  • A seal number cannot be matched exactly to the paperwork, however minor the discrepancy looks

Do not use it for

  • Delivery Appointment Record, which books an inbound delivery into a dock slot and records whether it arrived when it said it would.
  • Receiving Inspection Record, which checks an inbound delivery against the purchase order and the specification once the doors are already open.
  • Over Short and Damaged Report, which records a discrepancy between what was ordered, what the paperwork says and what physically arrived.
  • Container Devanning Record, which records how a container was unloaded once it has already been let through the seal check.
  • Anything outside KnowLogistics, which belongs in the workspace that owns that process

Compliance mapping

Which FSMA Intentional Adulteration rule requirements does this satisfy?

This checklist satisfies a specific regulatory obligation, not a general good-practice habit. Each section maps to a requirement under the FSMA Intentional Adulteration rule.

ClauseRequirementWhere it lands
21 CFR 121.126 — Food defense plana written food defense plan naming each actionable process step and its mitigation strategyHeader
21 CFR 121.130 — Vulnerability assessmentthe seal is the mitigation strategy assigned to the receiving actionable process stepHeader
21 CFR Part 121 Subpart C — mitigation strategy monitoringthe mitigation strategy is monitored at the frequency the food defense plan specifies, by someone able to perform it correctlyVerification
21 CFR Part 121 Subpart C — verification of mitigation strategiesverification that monitoring is happening and effective, hence the independent second check on the sealVerification
21 CFR Part 121 Subpart C — corrective actionsa documented corrective action whenever the mitigation strategy fails, i.e. whenever the seal does not check outIf it does not match
21 CFR 121.4 — Qualified individual / trainingthe checker, and anyone escalating a mismatch, has food defense awareness training appropriate to their roleHeader
21 CFR Part 121 Subpart E — recordsrecords of monitoring, corrective actions and verification created at the time and retainedOutcome

What it does not cover

  • Seal Present, which confirms a seal exists at all — a trailer that arrives unsealed with no exception raised has already failed before any numbers are compared.
  • Numbers Match Exactly, which is a character-by-character comparison against the delivery note, not a glance that a seal is there and looks intact.
  • Second Person Verified, which is the independent check that turns a lone receiver's assumption into a verified control, not an optional second signature.
  • Doors Kept Closed Pending Instruction, which stops the load being opened and the evidence being lost before a manager has decided what happens next.
  • Security Incident Raised, which is the record that a mismatch was treated as a security and food defense event rather than closed out as a paperwork correction.

Global

Container and Trailer Seal Check requirements by country

Seal integrity sits at the intersection of a mandatory US food safety rule and voluntary trade-security frameworks, and which one governs a site changes what 'compliant' means.

United States

FSMA Intentional Adulteration rule (21 CFR Part 121)

a mandatory food defense control for registered facilities where receiving is a named actionable process step

the seal check must be monitored, verified and corrected exactly as the facility's food defense plan states, independent of whether anything was actually tampered with.

United States (customs)

C-TPAT Minimum Security Criteria

a voluntary supply-chain security programme naming container/trailer seal verification, via view-verify-twist-tug, as a baseline requirement for certified importers

losing C-TPAT status over a poorly evidenced seal check costs a company its trusted-trader benefits at the border — a commercial consequence separate from any food safety finding.

International

ISO 17712 (mechanical seals for freight containers)

sets the classification — high-security, security or indicative — the physical seal must meet, and the numbering convention the paperwork is compared against

a check against a seal never rated to the class the shipment required is verifying the wrong thing correctly, however carefully the numbers are compared.

How to complete it

How to complete a container and trailer seal check, step by step

Ticking every box on this checklist isn't the same as the seal check holding up under scrutiny. Four judgement calls decide whether the record proves what it claims to.

What 'matches exactly' tolerates

A seal number worn, greased or partly obscured isn't automatically a match or a mismatch — it's a decision. Treating an unreadable digit as a pass because the rest looks close is how a genuine substitution gets waved through under the field meant to catch it.

When 'not required' is a real answer

Second Person Verified scores 'Not required' the same as 'Yes'. That's only defensible if the workspace has defined which lanes, carriers or load types need the second check — otherwise 'not required' is just the answer a rushed receiver reaches for.

Photograph as evidence, not as a formality

A photograph taken after the fact, of a seal already cut or a load already moved, satisfies the field without preserving what it exists to preserve. It's only evidence if taken before anything about the seal's state has changed.

Where a mismatch stops being a discrepancy and becomes an incident

Discrepancy Found and Security Incident Raised are separate questions, and the record doesn't force a Yes on the first to produce a Yes on the second. Deciding that threshold at the moment of receiving, rather than by a policy set beforehand, is how genuine tampering gets recorded as a clerical note.

What auditors find

Most common container and trailer seal check findings

Across sites running this checklist, the same gaps keep showing up between what the form asks and what actually gets verified.

FindingClauseWhat fixes it
Seal numbers are compared by eye against a delivery note in a different format (leading zeros, dashes) than what's stamped on the seal, so mismatches are missed rather than recorded.21 CFR 121.130 — Vulnerability assessmentStandardise the seal number format the paperwork must state, and reject any delivery note where the two formats can't be compared directly.
'Second Person Verified' defaults to 'Not required' as the fast path, so the field stops meaning anything on sites that never define when a second person is needed.21 CFR Part 121 Subpart C — verification of mitigation strategiesSet the rule for when a second check is mandatory — a high-risk lane, a first-time carrier — at workspace level, not left to the receiver on the day.
Photograph Taken is answered 'N/A' by default when a phone has no signal or charge, removing the only durable evidence a seal was checked at all.21 CFR Part 121 Subpart E — recordsMake the photograph mandatory unless a supervisor overrides it, and log the override separately from a genuine N/A.
A mismatch is logged and a Case ID raised, but 'Security Incident Raised' is left No because the receiver assumes quality, not security, owns it.21 CFR 121.126 — Food defense planRoute every 'Discrepancy Found: Yes' answer to a mandatory Security Incident Raised prompt rather than leaving it a free judgement call.
'Doors Kept Closed Pending Instruction' is answered after the doors have already been opened to check the load, defeating the control it's meant to record.21 CFR Part 121 Subpart C — mitigation strategy monitoringSequence the form so doors-closed is answered and locked before contents verification unlocks.
Training records for the receiver completing the check aren't linked from this template, so a food defense audit can't show the checker was qualified.21 CFR 121.4 — Qualified individual / trainingLink the Checked By and Receiver fields to a training register so competency evidence travels with the record.

Case in point

Case in point: the seal that was intact and still wrong

A receiver at a cross-dock site checked a bolt seal, saw it undamaged, ticked Seal Intact And Undamaged as Yes, and moved straight to unloading. The seal number on the trailer read 0041862; the delivery note read 0041682 — two digits transposed. Nobody had compared the two strings character by character, because 'the seal looked fine' had quietly become the actual test being applied.

The transposition surfaced three weeks later during a food defense drill, when an auditor pulled the paperwork and matched it against the photograph on file. The seal had never been tampered with — the numbers had simply been mistyped at origin. But the check meant specifically to catch a substituted or altered seal had passed a load it was never actually applied to, and the only reason the gap surfaced was the audit, not the process.

The template

The template, field by field

The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.

39fields
4 sections
Reference
LOG-004
Archetype
Checklist
Record ID
SEAL-2026-000
Scoring
Seals intact and matching
Direction
High is good
Singleton
Yes
Basis
FSMA Intentional Adulteration rule
Links
Feeds Security Incident and Receiving Inspection
Tags
Inbound, Security, Seal
Sections
4
Fields
39
Follow up fields
4
Repeating sections
0
Links out
3
Field typesOwn ID, generated on saveCase thread and parentPick list from a registryLinked to another templateFollow up, dashed outlineScored

Header

13 fields
Text

Check ID*

Generated on save

Auto sequence. Format SEAL-2026-000.

The record's own ID. Other templates point at this value.

Single Choice

Status*

Scored

Drives who this goes to next.

  • Planned2 pts
  • In progress2 pts
  • Complete3 pts
  • Deferred0 pts
  • Open0 pts
  • Closed3 pts
  • Overdue0 pts
Date & Time

Date and Time*

Users

Completed By*

Pick List

Site*

From FDN-001 Site NameFilter: Status is Active
Text

Site ID*

Linked

Format SITE-000.

Links to FDN-001 Site ID

Text

Vehicle Or Container Number*

Text

Seal Number On Paperwork*

Text

Seal Number On Equipment*

Single Choice

Seal Type

Optional
Bolt sealCable sealPlastic strip sealPadlock
Text

Delivery Note Reference

Optional
Users

Checked By*

Info

A Mismatched Seal Is An Event

The seal number is the only evidence the load was not opened between despatch and here. A number that does not match the paperwork is a food defense and security event, not a note for the file.

Verification

6 fields
Single Choice

Seal Present*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Numbers Match Exactly*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Seal Intact And Undamaged*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Seal Applied To The Correct Point*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Second Person Verified*

Scored
  • Yes3 pts
  • Not required3 pts
  • No0 pts
Single Choice

Photograph Taken*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator

If it does not match

6 fields
Single Choice

Doors Kept Closed Pending Instruction*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Manager Informed Immediately*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Carrier Contacted*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Load Segregated On Unloading*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Contents Verified Against Manifest*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Security Incident Raised*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator

Outcome

14 fields
Single Choice

Seal Verified*

Scored
  • Yes2 pts
  • No0 pts
  • N/Aexcluded from denominator
Single Choice

Discrepancy Found*

Scored
  • No3 pts
  • Yes0 pts
Text

Case ID

OptionalThread keyShows if Discrepancy Found equals Yes

Thread key

Single Choice

Product Integrity Affected*

Scored
  • No3 pts
  • Possibly1 pt
  • Yes0 pts
Text

Hold ID

OptionalLinked

Links to QUA-003 Hold ID

Text

New Seal Applied

Optional
Single Choice

Action Required*

Scored

Raise the action record, then enter its reference here.

  • No2 pts
  • Yes0 pts
Single Choice

Priority

OptionalScoredShows if Action Required equals Yes
  • High0 pts
  • Medium1 pt
  • Low3 pts
Text

CAPA ID

OptionalLinkedShows if Action Required equals Yes

Format CAPA-2026-00000.

Links to FDN-014 CAPA ID

Users

Action Owner

OptionalShows if Action Required equals Yes
Users

Receiver*

Signature

Signature*

Users

Security*

Signature

Second Signature*

LOG-004 · record IDs look like SEAL-2026-000 · Feeds Security Incident and Receiving Inspection

Open in Knowella

Run it with agents

From a document you fill in to a programme that runs itself

The form is the easy part. Deciding when a mismatch is a security incident, keeping the photograph attached as evidence, and proving the receiver was trained is what actually slips.

KnowLogistics

Holds the seal check register against every sealed arrival, links each check to its Receiving Inspection Record, and keeps the paperwork-versus-seal comparison auditable.

KnowSafe

Owns the Security Incident record a mismatch routes into, and keeps the escalation from doors-closed to manager-informed to incident-raised moving without a gap.

KnowComply

Maps this check against the FSMA Intentional Adulteration rule's vulnerability assessment and mitigation strategy requirements, and surfaces where a site's records won't stand up to an audit.

Ella
Ella

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.

This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.

Glossary

Container and Trailer Seal Check definitions and key terms

Actionable process step
A point in the supply chain that an Intentional Adulteration vulnerability assessment identifies as significantly vulnerable, where a mitigation strategy is legally required. Receiving is commonly designated as one.
Mitigation strategy
A control put in place at an actionable process step to significantly minimise or prevent an intentional adulteration vulnerability. The seal, plus the check that verifies it, together form the strategy for an inbound load.
High-security seal (ISO 17712)
A seal classification under ISO 17712 rated to resist a defined set of tools and forced-entry attempts for a minimum time, distinct from the lower 'security' and 'indicative' classes.
Chain of custody
The unbroken record of who held, moved or had access to a load between despatch and receipt. An intact, matching seal is the primary evidence custody was not broken in transit.
C-TPAT minimum security criteria
Baseline controls a US Customs-Trade Partnership Against Terrorism member must maintain, naming container and trailer seal verification, via view-verify-twist-tug, as a specific requirement.

FAQ

Frequently asked questions about container and trailer seal check

What is a container and trailer seal check?+

A checklist completed by the receiver on every sealed inbound arrival, verifying the seal number stamped on the trailer or container matches the paperwork, and recording its physical condition before the doors are opened. It sits inside KnowLogistics' Inbound and Receiving programme.

Why does a seal check matter if the seal is intact?+

An intact seal only proves the doors haven't been opened if its number also matches what despatch recorded. A seal that's undamaged but carries the wrong number, or is applied to the wrong point, has still failed the check the paperwork is supposed to guarantee.

Who has to do the seal check, and how many people?+

The receiver does the primary check on every sealed arrival. A second, independent person verifies it where the workspace's rules call for one — this template treats 'not required' as a valid, scored answer, but that threshold has to be defined somewhere, not left to the day's receiver.

What happens if the seal numbers don't match?+

The doors stay closed pending instruction, a manager is informed immediately, and the carrier is contacted. Once opened under instruction, contents are checked against the manifest and a Case ID, and where warranted a Security Incident, are raised.

Is a mismatched seal always a security incident?+

Not automatically — Security Incident Raised is a separate Yes/No judgement from Discrepancy Found. In practice, any transposition or substitution not immediately explained by a paperwork error at origin should default to raising the incident rather than closing it as a discrepancy.

How does this template connect to the rest of the programme?+

It feeds Security Incident and Receiving Inspection. A clean seal check clears the load into the Receiving Inspection Record; a failed one routes into the security process first.

Keep going

Related templates and programmes

Industries this is written for

Siddarth Singh

Written and reviewed by

Siddarth Singh

Founder & Chief Executive Officer, Knowella

Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.

  • Certified Safety Professional (CSP), Board of Certified Safety Professionals
  • MBA, University of Chicago Booth School of Business
  • MS and BS, The Ohio State University, Industrial and Systems Engineering
  • Six Sigma Black Belt
Verify with BCSP →

Sources and last review. Reviewed 16 August 2026 against:

  • FSMA Intentional Adulteration rule (21 CFR Part 121)
  • ISO 17712 — Mechanical seals for freight containers
  • C-TPAT Minimum Security Criteria — Importers

This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.