Understand

When the version in your hands matters

Construction submittals, permits and certificates, and sales proposals fail in the same way: a later file keeps an earlier name. The version in your hands is the one you will build from, rely on, or accept. One seal tells you whether that copy is the issued file.

Updated October 2, 2026 · 6 min read

One check, three places it shows up

These are not three products. A submittal, a permit, and a proposal are different documents with the same failure: someone sends a file that is not the issued version, and the filename still looks right. Sealing the issued file gives every later holder the same check.

The version in your hands

1
The issued version is sealed
Safe path
That file gets a fingerprint and a verification link.
2
The file travels under one name
Email, a shared folder, or a portal forward keeps the filename.
3
A different version keeps the name
Risk point
An older revision, a marked-up copy, or an edited price.
4
The holder checks the copy in hand
Safe path
No account. Match means this is the sealed version. Mismatch means it is not.

The name can stay. The bytes are what the seal checks.

Construction submittals

A shop drawing or product submittal is approved at a revision. The site team, the subcontractor, and the supplier then pass PDFs around. A marked-up sheet or a superseded revision is easy to forward under the approved filename. The crew builds the detail that is in the file they opened, not the detail that was approved.

Seal the approved file. Anyone on the chain can open the link with no account and check the PDF in their hands. A mismatch means this is not the sealed revision, even when the filename matches. The seal does not approve the drawing. The reviewer still does that. The seal shows whether this copy is the one that was sealed after that approval.

Permits and certificates

A permit, a completion certificate, or an inspection record is often a PDF that later readers treat as the record. A cleaned-up scan, an earlier draft, or a re-exported file can carry the same name. A counterparty or an inspector then relies on a version that was not the one issued.

Sealing the issued file lets the next holder check the copy they have. Opcilo does not replace the authority that issued the permit or the certificate, and it does not make a file official. It shows whether this file is the one that organization sealed, and who sealed it.

Sales proposals

A proposal leaves with a price, a scope, and a discount. A later copy changes one of those and keeps the name Proposal.pdf. The buyer is about to accept a file. The seller needs the same file in front of the buyer. If the bytes differ, they are not looking at the same offer.

Seal the proposal you send. The buyer opens the link with no account and checks the file they received. A match means this is the sealed proposal. A mismatch means the copy in hand is not that version — price, scope, or wording changed after the seal.

The check itself is the sealing loop in what document sealing is. For lookalike filenames and real-looking codes, see same filename, real-looking code.

Frequently asked questions

Do submittals, permits, and proposals need different seals?

No. Each issued file gets its own seal, and the check is the same: the copy in hand either matches that seal or it does not. The three examples are one point.

Does the filename tell me the revision?

No. A superseded submittal, an earlier permit draft, and an edited proposal can all keep the issued name. The seal compares bytes, not the filename.

Does a seal make a permit official?

No. The issuing authority still issues the permit or certificate. The seal shows whether the file you hold is the one that was sealed, and who sealed it.