01
Internal contractual document
Confirms a scope or relationship while the document itself remains private.
Loading...
Loading...
Verified evidence
This page explains how COREVIA International links its public claims to sources, permissions and a suitable publication level.
Evidence principle
Verification covers the source’s existence, date, scope, associated rights and what it genuinely allows us to conclude.
Some records remain private: they may support an internal review without becoming public documents or exposing sensitive data.
Eight categories
The selected category must match the nature of the information being reviewed.
01
Confirms a scope or relationship while the document itself remains private.
02
Explicit approval of a fact, quotation or publication right.
03
An image cleared of private data and linked to the relevant project.
04
An image with an identified project, date, owner and rights.
05
An accessible address allowing information to be checked publicly.
06
A handover or approval record shown without confidential content.
07
Dated content issued by an identifiable and relevant source.
08
A result defined by a method, period and reviewable source.
Internal evidence may support verification without being made public. Only its approved metadata may then be mentioned.
Review levels
The level describes the depth of review and available permission; it does not measure commercial value.
01
Must not be published as fact.
02
An internal source exists and its scope has been reviewed.
03
The information holder also approves publication.
04
The information can also be checked against a public source.
Usage rules
Every publication preserves the scope, date and limits of its source.
01
Never generalise evidence beyond the project or period it covers.
02
Review information when it becomes old or the context changes.
03
Define every statistic, its unit and calculation method.
04
Do not attribute a result to an action unless the source demonstrates it.
05
Review the fact, wording, name, logo and each media item separately.
06
Suspend content if its source or permission becomes uncertain.
Acceptable formats
These examples show the type of information expected in the register.
01
URL, author or body, access date, supported claim and restrictions.
02
Linked project, owner, date, consent, visible people and factual caption.
03
Value, unit, period, calculation method, source and review date.
04
Origin, exact wording, verified identity, allowed attribution and context.
Information protection
A record may be useful for internal review while remaining unsuitable for public disclosure.
Invoices, contracts, bank documents and transaction references.
Passwords, keys, secrets, internal identifiers and administrator accounts.
Private email addresses, numbers, addresses and other personal data.
Unredacted screenshots, non-public client data and sensitive information.
Logos, portraits or photographs without confirmed publication rights.
Documents whose authenticity, date or owner cannot be reviewed.
Verification cycle
Review continues whenever the information, source or permission changes.
01
Define exactly what the site intends to publish.
02
Associate an appropriate record or reference.
03
Review its origin, authenticity and scope.
04
Confirm the covered period and currency of the information.
05
Review consent and publication limits.
06
Choose between internal, anonymised or public use.
07
Trace the status, approved pages and restrictions.
08
Suspend or update when the situation evolves.
Confidentiality
Publication always depends on the project level and the rights granted for each item.
01
The information may be displayed within its recorded limits.
02
Content may be presented without identifying the client.
03
The record may support internal review but must not be disclosed.
Frequently asked questions
No. A confidential record may support internal verification, but only approved, non-sensitive information may be made public.
Only if permission explicitly covers the official logo, its use, display context and the actual relationship presented.
It needs a definition, source, reference date, calculation method, permission and review rule.
A project remains absent whenever its evidence, rights, confidentiality or the elements needed for an accurate presentation are not all confirmed.
The affected content is suspended, its dependencies are reviewed and it is republished only after a full new verification.
Discover the method organising the scoping, approvals, checks and delivery of each assignment.