Versions, “outdated” and PDF

A version does not change

Every publication creates a new version. Its text is frozen, together with the date, the underlying scan and the person who approved it. Corrections appear as a new version; the old one is kept as a record.

This is not a convenience but the basis for showing an authority or in a dispute what was declared at which time.

Earlier versions and PDF

• The public address always shows the current version.
• The public page links all earlier versions; each is marked as archived.
• A PDF is generated for every version. You find it in the website’s “Overview” tab under “Download as PDF” and on the public page.

“Outdated”

When a later scan of the same website finishes and its result differs from the published state, the service marks the statement as “outdated”.

• The statement stays online, unchanged, at the same address – also in embeds and the WordPress plugin. A linked statement must not disappear.
• You see the marking in your account: on the website, on the overview and on the publishing page. After a scheduled scan, the email mentions it too.
• A configured webhook receives the declaration.outdated event: Setting up webhooks and verifying signatures.

Visitors do not see the marking. All the more reason for you to act.

Publishing a new version

In the website’s “Overview” tab, choose “Publish a new version”. The same requirements apply as the first time – including manual checks added with the new scan: From scan to published statement.

Your mandatory details and assessments are kept. The summary before approval says which version becomes the previous one.

After approval, the public address shows the new version immediately; embeds and the WordPress plugin follow with a delay: WordPress doesn’t show the statement, or shows an old one.

How often to republish

A statement must describe the actual state and be reviewed regularly; a date that is years old is a defect in itself. With a scheduled scan you learn when something has changed.