CSRD Consultant Kickoff: A 30-Day Playbook for the First Month After You Sign

The selection cluster tells you how to pick a CSRD consultant. Almost nobody writes about what happens the Monday after you sign. That's a shame, because the first thirty days do more to decide the outcome of your engagement than anything after them. The wrong opening month gives you a consultant who is guessing at your organisation for four weeks, an internal team that treats the project as somebody else's job, and a governance model that surfaces bad news three sprints too late.

This is the playbook I would run if I signed a CSRD consulting engagement tomorrow. It assumes you have already answered the build-or-buy question, chosen a consultant, and compared the proposals. What follows is the operational month between "signed" and "materiality workshop." In the CSRD implementation roadmap, this month is Phase 1.

Why the First 30 Days Decide the Whole Report

CSRD engagements are unusual in three ways that make the opening month load-bearing.

They cross more functions than any other compliance project you have ever run. Finance owns the reporting boundary and the controls, sustainability owns the topical content, HR owns ESRS S1, procurement owns most of the Scope 3 data, legal owns the wording of anything risk-adjacent, and IT owns whatever tool you eventually pick. A consultant walking into that cast without an org chart, a stakeholder map and named counterparts is billing hours to figure out who to email.

They have a fixed filing date. Every week of drift in month one is a week you cannot claw back from the assurance walk-through at the end. There is no expanding the runway.

They fail quietly. A slipping technology project throws build errors. A slipping CSRD project produces the same weekly status updates ("data collection is progressing") until someone realises in month five that three legal entities never named a data owner. The first month is where you install the tripwires that make silent failure impossible.

Everything below is designed around those three facts.

Week 1 — Charter, Governance, and the RACI

The first week is not about CSRD content. It is about making sure the second week can be about CSRD content.

Kickoff meeting (day 1 or 2)

Two hours, in person if you can get everyone in the same room, video otherwise. Invite: your CSRD sponsor (usually CFO or general counsel), head of sustainability or ESG lead, head of finance/controlling, head of HR, head of procurement, head of internal audit, IT lead, and the consultant's engagement partner plus their day-to-day lead.

A working agenda:

Segment	Time	Owner
Why we are here, filing date, scope	15 min	Sponsor
What "good" looks like (past assurance findings if any)	10 min	Sponsor
Consultant methodology and team	30 min	Consultant partner
Draft workplan and critical path	20 min	Consultant lead
Governance model and RACI walk-through	20 min	Consultant lead
Data room, tools and access	10 min	Internal PM
Decisions and open questions	15 min	Sponsor

The last segment matters most. Every kickoff produces open questions ("do we consolidate our Turkish subsidiary?", "is Site X in scope?"). Write them down live, assign an owner and a due date, and re-open them in the first weekly.

Charter document

One page. Sign it. It sets the scope of the engagement (which ESRS topical standards you plan to disclose against based on the pre-materiality view), the filing date, the sponsor, the steering committee membership, the escalation path, budget, and what is explicitly out of scope. Explicit out-of-scope items save more arguments in month four than any other artefact.

The consultant will offer to draft this. Let them. Sign it inside week 1. If you are still redlining the charter in week 3 you are already off track.

Governance model

Two bodies, no more.

Steering committee. Sponsor, one or two exec peers, consultant partner, internal project lead. Meets monthly for an hour. Job is to unblock, resolve scope disputes, approve go/no-go on materiality and pre-issue drafts, and adjudicate anything that touches other functions' targets. Steering committees that meet every two weeks become status meetings; monthly forces real decisions.

Working group. Internal project lead, consultant day-to-day lead, one named counterpart per function (finance, sustainability, HR, procurement, legal, IT). Meets weekly, 45 minutes, standing agenda. Every function has to have a named counterpart, not a rotating attendee. If procurement sends a different person each week you have no procurement.

Escalation from working group to steering is by exception, not routine, and always from the internal PM. Consultants should not escalate around your PM — that is the fastest way to lose control of your own project.

RACI: what the consultant does and what stays yours

There is no single right RACI, but there is one wrong shape: consultant Responsible and Accountable on anything. Accountability cannot be outsourced under CSRD. The board signs the sustainability statement.

A defensible split for a first-time reporter, mid-market group:

Workstream	Responsible	Accountable	Consulted	Informed
Scoping / reporting boundary	Finance	CFO	Consultant, legal	Sustainability
Double materiality workshop design	Consultant	Head of sustainability	Sponsor	Working group
Double materiality decisions	Head of sustainability	Sponsor	Consultant, working group	Board
Data gap analysis	Consultant	Head of sustainability	Function leads	Steering
Data collection execution	Function leads	Head of sustainability	Consultant	Sponsor
Disclosure drafting (technical)	Consultant	Head of sustainability	Function leads, legal	Sponsor
Disclosure sign-off (content)	Head of sustainability	Sponsor	Board audit committee	Consultant
Controls documentation	Internal audit	CFO	Consultant	Sponsor
Assurance liaison	Head of sustainability	CFO	Consultant	Sponsor
XBRL tagging	Consultant	CFO	IT, finance	Sponsor

The pattern: consultant is Responsible where depth or throughput matters (workshop design, gap analysis, drafting, tagging). Your internal owner is Accountable on everything. Sponsor is Accountable on the three items that touch the financial statements (scoping, controls, assurance liaison), because the CFO already has that accountability under financial reporting and this borrows the muscle.

Get the RACI signed inside week 1. It is easier to argue about a RACI when nothing has gone wrong than when the first data request has been sitting on procurement's desk for three weeks.

Week 2 — Data Room, Systems, Stakeholders

Now the consultant needs raw material.

The data room

Not a hypothetical data room. A shared drive, a Notion, a SharePoint, something the consultant can read without asking every time. Populate it in week 2 with:

• Legal entity structure with ownership percentages and consolidation basis.
• Latest annual report and any prior sustainability report, CDP submission, TCFD disclosure, GRI content index, or ESG rating responses (Sustainalytics, MSCI, EcoVadis).
• If you were subject to the NFRD, the prior non-financial statement.
• Group risk register and the last two management-level risk reviews.
• Materiality assessment output from any prior framework (GRI, integrated report).
• Current chart of accounts and the trial balance mapping used for consolidation.
• HR headcount by legal entity, country, gender and function.
• Site list with location, ownership, activity type, energy source, and any environmental permits.
• Procurement spend by category and, if you have it, by supplier country.
• Existing environmental data: energy invoices, fuel consumption, refrigerant top-ups, water bills, waste manifests. Whatever you have. The consultant will tell you what is missing.
• Board and audit committee terms of reference, and any sustainability governance charter.
• Any prior interaction with your future assurance provider (findings from a limited assurance readiness review, if you did one).

This is a lot. Do it anyway. The alternative is the consultant sending twelve targeted requests over four weeks, each waiting three days for a reply.

Systems and access

Give the consultant access, not printouts. That means a read-only account (or a nominated internal proxy) for:

• The general ledger or ERP for materiality-adjacent transactions.
• The HR system for S1 metrics.
• Any existing sustainability software (Sphera, Watershed, Persefoni, Novisto, homegrown Excel — whatever you use).
• Your document management system for prior board and audit committee papers.
• Slack or Teams — a named external channel avoids weeks of email lag.

Access requests routinely take two to four weeks. Start them in week 2 so they land by week 4.

Stakeholder map

The double materiality process needs a defensible stakeholder engagement plan. Build the map in week 2 so the consultant can start scheduling interviews in week 3. Segment by:

• Internal (executives, function heads, operational sites, workers' council)
• Value chain (top suppliers by spend and by Scope 3 exposure, key customers, downstream users)
• Financial (top shareholders, lenders, insurers)
• Affected communities and civil society (local communities near sites, NGOs, regulators)

For each, name a real person and a channel. "Workers' council" is not a stakeholder — the elected chair of the works council of your German subsidiary is. Do this now, or the workshop will slip.

Week 3 — Materiality Design and Assurance Alignment

By week 3 the consultant has enough context to start real work.

Materiality methodology memo

A three to five page methodology memo the double materiality assessment will follow: how you define impact, financial and combined materiality; the scoring scale; the aggregation logic; the stakeholder engagement plan; and the evidence trail. This is the document your assurance provider will ask for first. Write it now, review it now, sign it now. Do not run a workshop without an approved methodology memo — it is the difference between "we did a materiality assessment" and "we can defend our materiality assessment."

Assurance kickoff

Book a call with your assurance provider in week 3, not week 30. Share the charter, the RACI and the methodology memo. Ask three questions:

1. What have you seen fail in first-time CSRD assurance walk-throughs?
2. What evidence do you expect for each materiality decision?
3. What is your view on the boundary and consolidation assumptions in the charter?

Getting the assurance provider on-record on scope and methodology in month one closes off entire categories of month-nine surprises. Consultants who resist a three-way conversation with your auditor are protecting billable hours.

Draft workplan freeze

The workplan the consultant showed on day 1 was a draft. In week 3 they should hand you a version they will commit to: a Gantt with a critical path, a milestone list, a per-week resourcing table (theirs and yours), and named risks. Freeze it. Track against it. Any change requires a written change request through the steering committee, not a Slack message.

Week 4 — First Milestones and the Day-30 Health Check

You should end the month with actual deliverables, not just process.

Milestones you should have by day 30

• Signed charter with scope, filing date and out-of-scope items.
• Signed RACI matrix.
• Populated data room and granted system access.
• Approved materiality methodology memo.
• Frozen workplan with critical path and named milestones.
• Working group calendar for the next six months in place.
• Steering committee dates for the year booked in every calendar.
• Assurance provider aligned on scope and methodology.
• Stakeholder map with named contacts.
• Slack/Teams channel with the internal team, the consultant team and your assurance lead.
• One-page project status template agreed and the first status shared.

If any of these are missing at day 30 the project has already slipped.

Day-30 health check

Ninety minutes, sponsor plus internal PM plus consultant lead. Not a status meeting — a diagnostic. Score yourselves honestly against ten questions:

1. Does every function have a named, engaged counterpart? (Not a name on paper — someone who showed up to two working groups.)
2. Do we have written scope, and has it survived a week without change?
3. Do we have written methodology, and has our assurance provider seen it?
4. Do we have data-room coverage of every item on the list above?
5. Do we have system access, or are we still emailing PDFs?
6. Do we have a workplan with a critical path, not a to-do list?
7. Do we have a governance rhythm that has actually met once? (Not "will meet next week.")
8. Do we have a shared communication channel used by all sides?
9. Do we have any decisions logged, or only discussion?
10. Do we have a stakeholder map that would survive a workshop next week?

Two "no"s means recover this week. Four or more means stop the workstreams, run a two-day reset, and rebuild. It is far cheaper to reset in month one than in month five.

Day-30 Red Flags

Some patterns show up early and predict trouble later. Treat any of these as a real problem, not a first-month teething issue.

• The senior consultant you interviewed is not on the day-to-day team. This is the single most common bait-and-switch. You bought their expertise. If you are getting managers who cite the partner rather than answer questions, escalate to the engagement partner and put the seniority mix into the change request log.
• Your consultant is asking you to run their own methodology workshops. They are Responsible for the design. If you are drafting the workshop, you are paying twice.
• Every request goes through the consultant's engagement partner. Fine as escalation, not fine as routine. You should have a day-to-day lead you can WhatsApp.
• Function heads are sending delegates to the working group. Get the named counterpart back in the room. This is a governance problem, not a scheduling one.
• Weekly status is upbeat with no numbers. Ask for the delta since last week in the workplan, in data collection percentage, in materiality progress. "Progressing" is not an answer.
• The consultant is avoiding your assurance provider. Two reasons this happens: they think it is your job (fair — but they should support), or they are hoping to close scope disputes before the auditor sees them (not fair). Force the three-way conversation in month one.
• You have not made a single hard decision yet. Not "reviewed a paper" — decided something that closes options. First-month engagements that produce no decisions are producing no scope.
• Change requests are informal. If the workplan has already changed twice by Slack, install a change control template now. Every scope change costs money or time; make sure everyone sees the invoice.

What You Get Out of a Well-Run First Month

The deliverable at the end of month one is not a report. It is a controllable project. Everything above exists to make month two boring: the methodology is agreed, the RACI holds, the working group meets, decisions get logged, and the consultant is working with the grain of your organisation instead of against it.

That is what your consultant's fee actually buys in month one: not analysis, but the operating system for the next eleven months. If you spent your engagement partner's time on a Gantt chart, you spent it well.

FAQ

Who should own the consultant relationship internally?

One senior internal person, always. On first-time engagements this is usually the Head of Sustainability, but a strong finance or internal audit lead can also do it. What matters is that there is a single throat to choke on both sides, and that they have the calendar to actually run it. Splitting the internal ownership between "the sustainability lead handles content and finance handles commercials" always ends with each blaming the other for scope drift.

What if we cannot get every function head to name a counterpart in week 1?

Escalate to the sponsor by end of week 2, not month two. A missing named counterpart is a leading indicator of a data gap. The sponsor's job is to make functions engage; if the sponsor cannot make that happen, the engagement should stop until they can.

Should the consultant be in our steering committee?

Yes, and only as an attendee. The steering committee should be able to challenge and, if needed, direct the consultant. That's harder if the consultant is a voting member.

How many days per week should the consultant be on-site?

For a first-time reporter, one day a week on-site during weeks 2–8 is the pattern that works best. Enough to build relationships and pick up organisational knowledge that never makes it to Slack, not so much that you are paying travel time. After month two, on-site is only needed for workshops and steering meetings.

What if the consultant proposes to skip the RACI or the charter?

Do not skip either. If they push back, that is a signal the consultant is trying to keep the shape of the engagement flexible so they can bill against whatever comes up. That is the opposite of what you want.

How do we know the consultant is doing enough in month one when the deliverables are mostly documents?

Track effort against the resourcing table. A first-month engagement for a mid-market first-time reporter typically runs 8–15 consultant days in month one. If the resourcing table says 10 days and time reports show 3, you have a staffing problem to raise in the first steering.

Find a CSRD Consultant Who Runs a Real Month One

A consultant who cannot describe their first thirty days in the level of detail above is a consultant who improvises the first month. That is expensive.

At CSRD Experts we curate independent CSRD consultants and boutique firms across Europe, filterable by expertise, industry and location. Ask any of them how they run week one before you sign — and use the playbook above to score the answer.

Browse the CSRD Experts directory →