The verification page says the content changed

The integrity check is recomputed from the current record, so it reports a change even when the approval itself is untouched.

Troubleshooting · 3 min read

The verification page does not trust the fingerprint stored beside an approval. It rebuilds every version hash from what is in the record right now and re-checks the chain. So "the content changed" means the current record no longer matches what was approved — not that the approval was altered, which cannot happen.

  • The version was replaced after signing. Publishing a new version is the normal way this happens, and the approval still refers to the older one.
  • The file behind the version moved or was re-uploaded. The fingerprint covers the stored file location as well as the title, so replacing the asset changes the answer.
  • The title of the deliverable was edited after the sign-off.

None of these are recoverable by re-running the check, and none of them are things Stria can quietly repair. Rewriting a record so that an old fingerprint matches again would manufacture evidence, which is exactly what the fingerprint exists to prevent, so the write is blocked at the database rather than left to good intentions.

What to do depends on why it moved. If the change was legitimate, publish the current state as a new version and collect a fresh sign-off — the new certificate will verify cleanly and the old one stays true about the older version. If you cannot account for the change, that is worth knowing, and the certificate you already sent is the record of what was originally agreed.

Note: A signed contract, statement of work or change order leaves this field blank rather than reporting a pass. There is no version chain behind a document to re-derive, so Stria declines to answer instead of implying a check it did not run.

Open the verification page — in your Stria workspace.

More on troubleshooting

Start your 14-day trial · All help articles · Email support