Skip to content
Back to examples

Technical capability demonstration

Product evidence

Already have a Battery Passport? The assurance job starts underneath it.

Situation

A real public passport publishes model, chemistry, nominal capacity, assembly and cell-supplier fields. The next assurance question is what authoritative source supports each field and what should reopen it.

Scoriors job

Connect each selected field to its authoritative source and owner, then define field-level change triggers.

Resulting split

CLEAR · UNKNOWN · HUMAN REVIEW

A supplier or cell-model change reopens supplier fields; chemistry/BOM changes reopen composition fields; capacity/model changes reopen identity and performance fields. Unrelated fields remain controlled.

Capability demonstrated

Field-level provenance · source ownership · targeted re-test control

EVIDENCE BASIS - PUBLIC SOURCES
IDENTITY - ANONYMISED
CLIENT WORK - NO
CONCLUSION LEVEL - OBSERVATION + BOUNDED INFERENCE

Technical detail

Inspect the technical evidence trail

Follow the source roles, observation record, dependency reasoning, affected and preserved work, unknowns, owner actions and re-test trigger.

What we reviewed

Manufacturer technical/product documentation · authorised downstream product surface

Observation record

Bounded public-passport snapshot

What we observed

Model, chemistry, nominal capacity, assembly and cell-supplier fields are published.

Why it mattered

A mature passport still benefits from field-to-source provenance, ownership and targeted re-test triggers.

What Scoriors checked

Each field should connect to an authoritative source and owner so only affected fields reopen after a change.

What Scoriors found

What still held

A supplier or cell-model change reopens supplier fields; chemistry/BOM changes reopen composition fields; capacity/model changes reopen identity and performance fields. Unrelated fields remain controlled.

What was affected

Map published field to authoritative source, owner, evidence state and change trigger; retain unknowns rather than infer internal absence.

What remained uncertain

Internal source records, ownership, approval history, source-system joins and applicability decisions.

What needed another check

Connect each selected field to its authoritative source and owner, then define field-level change triggers.

Professional boundary

No claim of incompleteness, error or non-compliance; no legal classification, LCA authorship, regulatory sign-off or platform implementation.

Re-test trigger

Supplier/cell model, chemistry/BOM, capacity/model, assembly/operator data, source system or rule change

Source basis

Source role / type
Manufacturer technical/product documentation · authorised downstream product surface
Observation record
Bounded public-passport snapshot
What cannot be inferred
No claim of incompleteness, error or non-compliance; no legal classification, LCA authorship, regulatory sign-off or platform implementation.

Company identity and direct commercial-source links are omitted from anonymised examples. Full source references are retained in the underlying evidence record and can be shared where appropriate in a scoped review.