Yüklənir

Evidence Statements

An Evidence Statement is a traceable assertion or measurement made by a company for a defined product release, release at a facility, batch, or physical instance. It records what is supported, whom it concerns, its period, retained document revision, review, and permitted audience.

For example, a report may support results for sample items from batch MAY-001 at Factory North. The scope must stay explicit; it is not proof that every individual battery was tested.

Choose the correct scope

  • Product release: the approved model revision.
  • Release and facility: that revision at the named factory.
  • Batch: the selected manufacturing batch.
  • Instance: the exact individual item.

Selected batch/instance must agree with the release. Evidence from another factory, period, or item cannot silently fill a missing requirement.

Who prepares and approves it

A Product Editor, Product Governance Manager, Company Administrator, or permitted evidence contributor prepares a draft for its actual declaring company. An authorized Product Governance Manager, Company Administrator, or explicitly delegated evidence approver reviews it.

Independent verification also requires a different verifier company and retained verification evidence. The actor needs appropriate authority for that verifier. A checkbox does not create that authority, and approval of a Product Claim or product edit is not evidence approval.

Create and review a statement

  1. Open Logistic → Quality → Evidence Statement, search existing records, and choose + Create new evidence statement.
  2. Select the release and only the facility, batch, or instance needed to express the true scope.
  3. Select the declaring company, enter Requirement Key, and provide an assertion or measured value. A numeric measurement requires a known unit. Explain the method and limits in the assertion/report; the current form has no separate Method input.
  4. Add validity dates, the exact retained Document Revision, and page where applicable.
  5. Set Audience to Public, Authorized, or Restricted according to permitted disclosure. Identify independent verification only when supported.
  6. Create the draft, apply Submit in Lifecycle decision, then have an authorized reviewer apply Approve or Reject with a reason.

Maintenance and blockers

Retain the exact document bytes before citing them. Ordinary document replacement cannot substitute new bytes into approved evidence. A public assertion does not automatically authorize downloading a restricted supporting document.

Use a new statement with Supersedes Evidence for a correction to the same scope/requirement. Approval preserves and withdraws the earlier record. Use separate statements for genuinely different factories, batches, or periods. Review expiry and refresh affected passport drafts separately.

Missing assertions, invalid units/dates/pages, inconsistent scope, inaccessible documents, unsupported independent verification, mismatched predecessors, or changed review versions block the relevant operation. Correct the actual source rather than broadening sample evidence to pass readiness.

Instance observations · Product releases · Production batches · Digital product passports · Maintaining traceability and evidence