Using the EviWrite Framework Badge
The EviWrite Framework Badge is a public alignment signal.
It is intended for organisations that follow the EviWrite Framework and want to show that they take evidence readiness seriously.
The badge is not an EviWrite verification mark. It does not mean EviWrite has checked the organisation’s records, approved its claims, certified its processes, backed its evidence, anchored its files, or authorised use of the controlled ⓔ mark.
The badge should help visitors understand one thing clearly:
This organisation says it follows EviWrite’s public Framework guidance for stronger digital evidence practices.
That claim must stay narrow.
Quick Read
- The EviWrite Framework Badge signals public Framework alignment, not EviWrite-backed verification.
- Organisations should only use the badge if they apply the Framework honestly and maintain evidence practices that match the claim.
- The badge is useful because it gives visitors a simple trust signal without pretending that every record has been checked by EviWrite.
What this means
Using the EviWrite Framework Badge means an organisation is publicly stating that it follows the EviWrite Framework for evidence readiness.
This may include guidance around origin, time, sequence, custody, independence, retention, recovery, verification, privacy, portability, and claim boundaries.
The badge is designed for websites, policy pages, evidence-readiness pages, service pages, assurance pages, provider pages, and organisational trust pages.
It should help users recognise that the organisation has adopted a structured approach to evidence.
It must not be used as a shortcut to stronger claims.
Framework alignment is self-applied public guidance.
EviWrite-backed evidencing is a controlled evidencing route through EviWrite or an authorised evidencing channel.
The badge belongs to the first category, not the second.
Why it matters
Many organisations make trust claims without explaining the evidence practices behind them.
They say they protect records, preserve proof, use responsible processes, verify information, handle provenance, keep audit trails, or support transparency. But visitors often cannot tell whether those statements have any defined evidence model behind them.
The EviWrite Framework Badge can improve that position.
Used properly, it shows that the organisation is not inventing vague trust language. It is aligning itself with a published evidence-readiness framework and accepting clear claim boundaries.
That can benefit customers, users, partners, advisers, auditors, researchers, creators, procurement teams, and institutional reviewers.
But a badge can also mislead if it is used badly.
If the badge suggests EviWrite verification where none exists, it becomes a false trust signal. That damages the user, the organisation, and the integrity of the Framework.
What proper badge use should include
A stronger Framework Badge position usually includes:
- Framework alignment — the organisation follows the EviWrite Framework in its evidence practices.
- Clear placement — the badge appears where users can understand what it means.
- Plain explanation — the site explains that the badge refers to public Framework alignment.
- Claim boundary wording — the site states that the badge does not mean EviWrite has verified or backed individual records.
- Relevant evidence practices — the organisation can explain how it applies the Framework.
- Internal responsibility — someone is responsible for keeping badge use accurate.
- Review process — the organisation periodically reviews whether it still follows the Framework.
- Correction process — inaccurate badge wording is corrected promptly.
- No controlled mark confusion — the badge is not confused with the controlled ⓔ evidential mark.
- No record-level overclaiming — individual files, claims, datasets, or records are not described as EviWrite-backed unless they were created through an authorised route.
The badge should increase clarity, not create ambiguity.
Eligibility principles
An organisation should only use the EviWrite Framework Badge if it can honestly say that it applies the Framework in a meaningful way.
At minimum, the organisation should be able to explain:
- Which evidence records or workflows the Framework applies to.
- How it preserves minimum evidence records.
- How it handles origin, time, sequence, custody, retention, recovery, and verification.
- How it controls evidence claims.
- How it prevents Framework alignment from being confused with EviWrite-backed evidencing.
- Who is responsible for maintaining the organisation’s evidence-readiness practices.
- How inaccurate public claims will be corrected.
The badge should not be used by organisations that merely like the idea of the Framework but do not apply it.
Public trust signals must be earned by practice, not decoration.
Common weak points
Framework Badge use is weak or misleading when:
- the badge appears without an explanation
- visitors cannot tell what the badge means
- the badge implies EviWrite has verified records
- the badge implies EviWrite has certified the organisation
- the badge is placed beside unsupported claims
- the badge is used on individual records as if they are EviWrite-backed
- the badge is visually confused with the controlled ⓔ mark
- the organisation cannot explain how it follows the Framework
- Framework alignment is used to imply legal proof, ownership, authorship, permission, or compliance
- the badge remains on a site after the organisation stops applying the Framework
- marketing language turns public guidance into implied endorsement
These failures turn a useful badge into a misleading signal.
How to apply this yourself
Before placing the badge on a website, create a badge-use note.
Ask:
- Why do we want to use the badge?
- Which evidence practices are Framework-aligned?
- Which records, claims, services, or workflows does the badge relate to?
- Where will the badge appear?
- What explanation will appear near it?
- Does the wording clearly say this is public Framework alignment?
- Does any wording imply EviWrite verification, approval, certification, sealing, anchoring, or backing?
- Could users confuse the badge with the controlled ⓔ mark?
- Who is responsible for reviewing badge use?
- What correction will we make if the badge is used inaccurately?
Then write the badge explanation plainly.
Do not rely on the badge alone to carry the meaning.
Suggested badge wording
A clear badge explanation may say:
“We follow the EviWrite Framework for digital evidence readiness.”
A fuller version may say:
“This organisation follows the EviWrite Framework for digital evidence readiness. Framework alignment means we apply EviWrite’s published public guidance. It does not mean EviWrite has verified, certified, approved, sealed, anchored, or backed individual records.”
Use wording like this close to the badge.
Do not hide the explanation in a distant policy page if the badge appears on a trust, service, product, or assurance page.
What this does not prove
Use of the EviWrite Framework Badge does not automatically prove:
- ownership
- authorship
- copyright
- permission
- legality
- originality
- authenticity
- accuracy
- compliance
- audit approval
- certification
- EviWrite verification
- EviWrite-backed evidencing
- that individual records carry the controlled ⓔ mark
The badge signals alignment with public evidence-readiness guidance. It does not prove the underlying claims.
Framework-aligned claim boundary
Acceptable wording may include:
“We follow the EviWrite Framework for digital evidence readiness.”
or:
“Our evidence practices are aligned with the EviWrite Framework.”
It must not be used to imply:
- EviWrite has verified the organisation
- EviWrite has audited the organisation
- EviWrite has certified the organisation
- EviWrite has approved the organisation’s records
- EviWrite has backed individual records
- EviWrite has anchored files
- EviWrite has authorised use of the controlled ⓔ mark
- the organisation’s claims are proven by EviWrite
- the organisation’s records are EviWrite-backed unless created through an authorised evidencing channel
Framework-aligned means public guidance was followed.
EviWrite-backed means the record was created through EviWrite or an authorised evidencing channel.
Related checklist
Use the Framework Badge Eligibility Checklist to check whether your organisation’s badge use is accurate, explainable, bounded, and clearly separated from EviWrite-backed evidencing.