CDP2026resourcesandguides

Step 1. Secure access, roles, and internal approval flow

Start with the “who” and the “how” in the CDP Portal. CDP defines the Submission Lead as the main point of contact and the person responsible for managing the configuration and submitting the final response.

Also review the Administrative Fee before entering the questionnaire. If the fee step is not completed, submission will not be enabled. With the right role, you can prepare the configuration and coordinate the team’s work without blockers.

• Appoint a Submission Lead and a backup owner, with clarity on what each person does and when.
• Define who provides data for modules such as Climate Change, Water Security, and Forests, and what evidence supports each data point.
• Align an internal calendar with validation milestones so you reach export with consistency.

Step 2. Define scope, modules, and verify routing early

CDP 2026 activates routing based on your initial configuration. That is why your first draft should include a check of modules and sections to prevent part of the effort from ending up outside the questionnaire.

Use the step-by-step guides, the question bank materials, and the 2026 scoring methodologies to prioritize which topics to prepare first.

• Confirm which modules are activated for your situation and define any relevant opt-in before you begin.
• Prioritize categories of material data for your scoring strategy and your operating context.
• Plan value chain evidence, including supplier data, so you do not reach September without a history.

Step 3. Build an evidence-ready data layer

In CDP, scores depend on the consistency of your answers and traceable evidence. The difference between “having data” and being “ready for assessment” is often in the lineage: source, method, assumptions, and version.

Build a canonical data layer so the team can respond consistently across modules and sections. That way, when you export and review, the data does not break.

• Collect Scope 1 and 2 emissions using documented methods and boundaries, including assumptions.
• Prepare Scope 3 and supplier engagement evidence for the themes activated by routing.
• Centralize Forests evidence with risk controls and due diligence traceability when applicable.

Step 4. Validate data quality, consistency, and your preparation checklist before submitting

Before entering the submission window, activate data quality controls. It is not just about checking numbers. Ensure consistency, units, assumptions, methodology, and evidence availability wherever the questionnaire requires it.

Keep key 2026 cycle dates in mind: the deadline to submit an eligible response is the week starting 14 September, and the questionnaire closes in the week starting 26 October.

• Run a routing test and confirm that the evidence matches what is shown in the questionnaire.
• Review units, assumptions, and methodology, and validate that traceability is sufficient for review.
• Prepare an evidence pack before exporting (including the documentation needed for collaboration and drafting).

Step 5. Submit in September with control and set up post-submission management

Submitting is not the end. To maintain quality, keep the context: method versions, evidence that supports each block, and a record of decisions. This helps you make changes and handle possible reviews.

If you export for drafting and collaboration, do it from the Portal. CDP lets you export the questionnaire or sections, so it is useful to be clear about which version you export and what you use it for.

• Ensure the Submission Lead keeps a history of decisions and evidence.
• Plan internal reviews after submission to correct what is needed.
• Use the calendar as the baseline for the next cycle so you repeat the process with less risk.

How Dcycle helps you prepare your CDP disclosure

Dcycle helps you prepare CDP 2026 as a governed process. Standardize your data layer, connect evidence to metrics, and maintain traceability between source, method, and response.

In practice, you reduce last-sprint risk: when evidence is structured and versioned, the team answers more consistently, and the work becomes reusable across cycles.

• Traceable evidence from source to review-ready outputs.
• Quality and consistency controls so routing does not surprise you at the end.
• A reusable data layer for multiple reporting needs.

Quick checklist before exporting

Before exporting from the Portal, use a minimal checklist. That way, you do not miss evidence, avoid inconsistencies in assumptions, and do not export an incomplete version.

• Does every key answer have associated and findable evidence?
• Are assumptions and units consistent with the defined methodology?
• Is the evidence pack complete for the modules that actually appear in the questionnaire?

How to maintain consistency across teams and cycles

CDP 2026 is a cycle that repeats. To turn the work into capability, you need the system to repeat the process without restarting governance every year.

• Version methodology and factors, and record changes by period.
• Centralize ownership and define validation checkpoints in the workflow.
• Prevent each team from recalculating with different rules for the same indicator.

Your next step: organize evidence and submit with more control

If today your preparation depends on reconstructing information or following the evidence trail manually, start putting order in place now. Structure your canonical layer, validate routing early, and keep the context so you do not lose time when September arrives.

• Start with what is material and build coverage in stages.
• Ensure each answer has lineage and available evidence.
• Prepare something you can repeat with lower risk every year.