Verification tasks
Verification tasks are requests you send to third-party auditors or testing organisations (verifiers) to review and independently validate specific documents attached to a product's DPP. For DPPs that require third-party attestation — particularly EV and Industrial batteries under EU Battery Regulation 2023/1542 — verification tasks are how you engage an independent reviewer and track their decision.
What Verification Tasks Are
A verification task links a specific document to a specific verifier. The verifier receives access to that document and the associated DPP product data, reviews the evidence, and records an Approved or Rejected decision. Their decision and comment become part of the DPP's permanent audit trail.
Verification tasks are not a substitute for a formal conformity assessment by a Notified Body where one is required by regulation. They are a platform-based coordination mechanism for the independent review workflows that support the claims in your DPP.
When You Need Verification Tasks
Third-party verification is particularly relevant for:
- Carbon footprint declarations — Annex XIII of EU Battery Regulation 2023/1542 requires third-party verification of carbon footprint performance classes for EV, LMT, and rechargeable industrial batteries from specified compliance dates.
- State of health and performance data — independently verified test results strengthen the credibility of performance claims.
- Supply chain due diligence attestations — for EV batteries, independent review of the due diligence framework and its implementation.
- Recycled content claims — third-party verification of recycled content percentages is required from specified compliance dates.
- Any DPP claims that your organisation does not generate internally — if the data comes from a supplier or third-party test laboratory, having an independent verifier cross-check the claim against the underlying evidence adds a layer of assurance.
Consult the applicable implementing acts for your battery category to determine exactly which claims require third-party verification and from which compliance date.
Creating a Verification Task
Verification tasks are created from within a product's document list — there is no separate Verification section in the sidebar.
- Open the product you want to arrange verification for.
- Navigate to the Documents tab.
- Locate the document you want a verifier to review.
- Click Request Verification on that document row.
A dialog opens where you configure the task:
Enter the Verifier's Email
Enter the email address of the verifier. If this email address belongs to an existing Traceable Verifier Portal account, the task is immediately visible to them in their portal. If the email address is not yet associated with a Verifier Portal account, Traceable sends an invitation email, and the task becomes visible once they register.
You can assign a task to any email address — there is no pre-approved verifier list on the platform. It is your responsibility to ensure the verifier you assign is appropriately accredited or qualified for the specific claims being verified.
Add Instructions
Use the instructions field to provide the verifier with the context they need to complete the task:
- The regulatory provision or standard under which the verification is being conducted
- The specific question you need answered (e.g., "Please confirm that the carbon footprint declaration for this product is supported by the attached lifecycle assessment report and that the methodology is consistent with Annex IV requirements")
- Your contact details for questions
Clear instructions reduce back-and-forth and improve the quality of verification findings.
Send the Task
Click Request Verification. The verifier receives an email notification. The task appears against the document with status Pending.
Tracking Task Status
The verification status of each document is shown in the product's Documents tab:
| Status | Meaning |
|---|---|
| Pending | The task has been created and the verifier has been notified, but they have not yet submitted a decision |
| In Review | The verifier has opened the task and is actively reviewing |
| Approved | The verifier has reviewed and approved the document |
| Rejected | The verifier has reviewed and rejected the document, with a comment explaining why |
What to Do if a Task Is Rejected
A rejected verification task means the verifier found that the submitted document could not confirm the claim. Rejection does not necessarily mean the data is wrong — it may mean the supporting documentation is insufficient, the evidence is ambiguous, or the presentation of the data does not align with the applicable standard.
Step 1: Read the Verifier's Comment
Open the rejected task and read the rejection comment carefully. A well-written comment will specify:
- Which aspect of the document was insufficient
- The basis for rejection
- What would be needed for approval
Step 2: Address the Issues
Depending on the nature of the rejection:
- Missing or wrong documentation — upload the correct document to the product's document library
- Incorrect field value — correct the value in the DPP editor (see Edit a Product)
- Scope ambiguity — if the verifier was unclear on what they were being asked to verify, clarify in the instructions when you resubmit
- Supplier data required — if the rejection is due to missing upstream evidence, send a data request to the relevant supplier (see Send Data Requests)
Step 3: Request Re-verification
Once the issues have been addressed, request a new verification task on the updated document. In the instructions, explain what has changed since the previous submission so the verifier can focus their review efficiently.
Related
- Product Documents — managing the documents that verification tasks are created from
- Verifier Portal Guide — what verifiers see when they receive a task