How to use this builder
Step 1. Name the delivery: who it is from, who it goes to, and when. Step 2. List each signed file exactly as delivered — filename, the date it was signed, and its honest AI label. Step 3. Tick only the delivery checks that are actually true, then print or copy the note and send it with the files — as the email body or a page attached next to the provenance report. A note that overstates is worse than no note: the whole point of signing is a record that stays honest.
Step 1 — The delivery
Step 2 — The signed files, as delivered
One row per file, named exactly as the delivered file is named — the recipient will check that file, not a screenshot of it and not a platform copy. The AI label is the one the signature itself carries: none, AI-assisted edits disclosed, or AI-generated elements disclosed. Up to 10 files per note; for a larger batch, build one note per delivery.
Step 3 — Delivery checks
The six checks: 1) the attachments are the signed copies themselves, not platform downloads or messaging-app copies; 2) the provenance report (or its equivalent record) travels with the files; 3) the untouched originals stay kept by the sender, separate from the delivered copies; 4) every file’s AI assistance is disclosed in the table — or honestly marked none; 5) the note tells the recipient that verification is free and needs no account; 6) the signer-status paragraph is included, so “Unrecognized” is explained before the recipient meets it.
Your delivery note
Delivery Note — Signed Files
From: — · To: — · Delivered: —
NO FILES YET
The files below carry Content Credentials (C2PA) signatures. Each signature records who signed the file and when, and shows whether the file has changed since signing. You can check any of them free — no account, no software, no payment.
| File, as delivered | Signed | AI assistance | Note |
|---|---|---|---|
| (add files above) | |||
How to verify, in three steps. 1) Open the public Content Credentials Verify site, verify.contentauthenticity.org. 2) Drop in the delivered file itself — not a screenshot of it, and not a copy downloaded from a platform or a messaging app, which is a different file. 3) Read the result: the signer’s name, the signing time recorded inside the credential, and whether the file has changed since signing.
One honest line about signer status. If the checker labels the signer “Unrecognized”, it means the signer’s certificate is not yet on the C2PA public trust list. The signature itself still validates, the checker still names the signer, and the changed / unchanged result still holds — there is simply no trust-list badge yet. ProvenanceMark states this about its own certificate openly, on its product page and here: judge the record by what it shows, not by a badge it does not claim.
What the signature does and does not prove. It proves the file has not changed since the moment it was signed, and records who signed it, when, and with which tool. It does not prove that what a photo or video shows is true, and it does not prove the signer created every element — the AI column above is the honest record of that. Provenance starts at signing; it cannot rewrite what happened before.
This note was prepared with the free Provenance Delivery Note Builder at getdoubleproof.com. The note itself is not a credential and not a verification result — the proof lives inside each signed file. New to Content Credentials? Read the Content Credentials Guide.
Files not signed yet? Get it done for you, by email.
ProvenanceMark signs your originals with tamper-evident C2PA Content Credentials and returns the signed copies with free public verification for every file and a provenance report PDF for the batch. Starter — $14 one-time, up to 50 files. Archive — $79 one-time, up to 500 files. One-time payment, no subscription, 30-day money-back guarantee. Straight talk: our signer certificate is not yet on the C2PA public trust list, so the Verify site labels the record Unrecognized and warns that the issuer could not be recognized — it still names ProvenanceMark as the signer, and the signature itself is cryptographically valid.
Earlier in the chain? Write the record with the free Provenance Record Builder and check readiness with the free Batch Audit Checker.
Why a signed file still needs a note
A Content Credentials signature is quiet: nothing on a photo’s face says the proof is inside it. So deliveries fail in predictable ways. The client opens the platform preview instead of the file and concludes there is no credential. A stock reviewer checks the file, meets the word “Unrecognized” with no context, and files the work under “suspicious”. A buyer asks months later how the work can be checked, and the answer has to be reconstructed from memory. The note prevents all three at the only moment they can be prevented — the delivery itself. It names the exact files, states the signer and the signing dates, carries the honest AI labels, gives the three free verification steps, and explains the signer status in advance, while the sender still has the originals and the report within reach.
Frequently asked questions
How is this different from the Provenance Record Builder and the Batch Audit Checker?
Those two work before signing: the Record Builder writes the record of your originals, and the Batch Audit Checker scores a batch for signing readiness. This builder works after signing, at delivery: it writes the note that travels with the signed files to the recipient, so the proof inside each file is actually found, checked and understood.
Does this builder sign my files or verify them?
No. It only writes the delivery note. Signing is a separate step, and verification is done free by the recipient at verify.contentauthenticity.org, using the delivered file itself — no account, software or payment needed.
Why send a note at all — doesn’t the proof travel inside the file?
The credentials do travel inside the file, but recipients often open a platform or messaging copy instead of the file itself, never learn that a free check exists, or meet the word Unrecognized with no explanation and assume the worst. The note fixes all three: it names the file to check, gives the three verification steps, and explains the signer status before the recipient has to guess.
The checker says a file has changed since signing. What should happen?
The copy being checked is not the untouched signed copy — it was recompressed, re-saved or passed through a platform, which makes it a different file. Re-send the original signed file itself. Never sign the changed copy and present it as the original delivery: that would record a new, shorter history and call it the old one.
Can I use this note for files signed by a different service?
Yes. The note is wording, not a credential. Keep the signer name and signing dates accurate for whoever signed the files, and keep the signer-status paragraph honest: if that signer is on the C2PA public trust list, say so; if not, keep the Unrecognized explanation in.
Is anything I type sent to DoubleProof?
No. This builder runs entirely in your browser tab. Names, filenames and notes are never sent to DoubleProof or stored anywhere. If you print or copy the note, keeping it private is up to you.
ProvenanceMark is an independent service applying the public C2PA specification; it is not affiliated with or endorsed by C2PA or the Content Authenticity Initiative. This page is general information, not legal advice.