Read a verification report

What "Valid", "Intact, but not every identity is confirmed" and "Not valid" mean, and what each signer's lines say.

The result at the top

Sovrasign Verify says	Meaning	What to do
Valid: "Nothing changed since it was signed, and every signer's identity checks out."	Nothing changed after any signature, and every signer's sign-in is confirmed by the trust list.	Nothing.
Intact, waiting for a trusted timestamp	Nothing changed, but some sign-ins count only once a trusted timestamp covers them. Sovrasign adds one when the envelope ends.	Check the final copy, sent when everyone has signed.
Intact, but not every identity is confirmed	Nothing changed, but the trust list does not confirm at least one signer's sign-in. Each signer's lines say why.	Use Sovrasign's published trust list (see Verify a signed PDF), or select Fetch the providers' current keys.
Not valid	The file was changed after a signature, or its evidence is damaged.	Do not rely on this copy. Ask the sender for the original PDF.
Made by a newer version	The document was made by a newer version of the signing engine than the page.	Reload the page, then check the file again.
No Sovrasign signatures	The PDF has no Sovrasign signing history.	Other kinds of PDF signatures need another verifier, for example Adobe Acrobat.
Could not check this file (error code `verification_failed`)	The file could not be read.	Check that you chose the right file, a PDF you downloaded rather than a printout or a scan.

Under the result, a summary gives the document's title and its state, for example "Completed: all 2 signers signed." or "Waiting for signatures: 1 of 2 signed." An envelope with several documents lists each one with its pages. Download the certificate of completion makes the summary page from the PDF itself.

Each signer

Signers lists every step in order: who prepared and sent the document ("Prepared and sent by"), then each signature ("Signed by") or refusal ("Declined by"). For each:

Valid or Not valid: whether this step checks out.
The assurance level, for example "L2 Account". It says what the identity rests on, not how good the signer is: L1 Email (a code sent by email), L2 Account (a sign-in with Google, Microsoft or Apple), L3 Strong, L4 ID checked, L5 Qualified. "via Sovrasign" means the check rests on Sovrasign's own service, for example the email code.
How they proved who they are, for example "Signed in with Google as ana@example.com; the sign-in is sealed into this signature" or "Proved control of ana@example.com with a one-time code sent by Sovrasign (lower assurance)". When the identity does not count, a line says why, for example "This verifier's trust list does not include this sign-in provider."
The time. With a trusted timestamp: "Signed ... (trusted timestamp, ...)". Without one: "Signed ... (signer's device clock, not independently confirmed)", and the limits the evidence does prove, for example "Made after ... (sign-in token issued) and before ... (trusted timestamp, ...)". On Free, Sovrasign adds one trusted timestamp to the whole document when the envelope ends: it bounds every signing time before it.
The signature's look: a drawn signature or a typed name. It is decoration: the sign-in says who signed.
Consent: "Agreed to electronic records and signatures (disclosure ..., ...) on ...", with the version and language of the disclosure the signer read.
A short code after "Sig", to compare two copies or to quote.

Activity recorded in the document lists the events sealed in the PDF.

Technical details and trust list

Technical details and trust list shows the sign-in providers the page trusts, the report's technical fields and Raw report (JSON) with every detail. A notice says when the trust list includes the test sign-in, which exists only on development copies of Sovrasign: a result there proves nothing about a person.

Never load a trust list because the sender of a document asks you to: a false list could make a forged signature look genuine.