How Do You Track a Supplier Sustainability Campaign?

Track a supplier sustainability campaign with one row per supplier, a controlled set of campaign states, and a dated next action for every open request. Keep contact status, platform progress, submission review, and target attainment separate. A supplier can reply without submitting data, finish a questionnaire that fails review, or have an accepted disclosure without meeting your climate target.

What must the tracker tell you?

Someone opening the tracker should be able to answer five questions without searching through email:

1. What does this supplier need to provide?
2. Who currently owns the request at the supplier?
3. What has happened since the request was sent?
4. What is blocking completion?
5. Who must do what next, and by which date?

If the tracker cannot answer all five, the weekly review becomes a meeting where people reconstruct the campaign from memory.

Download the supplier engagement campaign tracker (CSV). The template includes example rows for CDP, EcoVadis, and Watershed. Delete those rows before using it.

Which campaign states should you use?

Use a short list of states with explicit entry and exit rules.

Campaign state	Entry rule	Required next action
Contact missing	No current person and validated email are available	Research the responsible function and validate an email
Ready to contact	Request, deadline, and contact are approved	Send the initial request
Request sent	Initial message was delivered	Schedule the first follow-up
Acknowledged	Supplier confirmed receipt or ownership	Confirm the completion date or blocker
Started	Platform or supplier confirms work has begun	Monitor progress without sending unnecessary reminders
Blocked	A named issue prevents progress	Assign the support or escalation action
Submitted	Supplier says the request is complete	Confirm receipt and start review
Under review	Internal reviewer has the submission	Accept it or return an exact correction
Returned for correction	Submission failed a stated acceptance rule	Request only the missing or incorrect information
Accepted	Reviewer confirmed the submission meets the request	Record evidence and next reporting date
Escalated	Normal outreach failed and procurement or leadership now owns the next step	Record the escalation decision and date

Do not use “in progress” as the only state between sent and complete. It hides the difference between a supplier actively answering, one waiting for technical help, and one that has not touched the request.

Why should platform status and campaign status stay separate?

CDP, EcoVadis, Watershed, and other systems report their own states. Those states describe activity inside that platform. They do not always describe the work your team must do next.

For example:

• EcoVadis: Not yet connected. Campaign state may still be Request sent. Your next action is direct outreach to the right person.
• EcoVadis: Answering, 65%. Campaign state may be Started or Blocked. Ask what is preventing the remaining sections.
• Watershed: Submitted. Campaign state should move to Under review until your team checks the reporting period, units, boundary, and reasonableness.
• CDP: Response available. The supplier may have disclosed to investors without sharing the response with your company. Confirm requester access before marking it Accepted.

Keep the original platform wording in one column and your operational campaign state in another. This prevents a platform status change from silently closing work that still needs review.

What fields should you track?

Supplier identity and priority

Record:

• supplier name and stable internal ID;
• legal entity or site where relevant;
• Scope 3 category;
• estimated emissions and coverage contribution;
• annual spend;
• supplier tier or priority; and
• procurement or category owner.

The stable ID matters when supplier names differ across procurement, carbon accounting, and disclosure platforms. Do not rely on a typed company name as the only join key.

Request definition

Record:

• platform or collection channel;
• request type;
• reporting period;
• required fields or evidence;
• acceptance rule;
• deadline; and
• internal reviewer.

“Provide emissions data” is not a testable request. State whether you need corporate Scope 1 and 2, product-level emissions, revenue for allocation, methodology, verification status, supporting evidence, or a completed assessment.

Contact coverage

Record:

• primary contact name, role, and email;
• email validation date;
• backup contact;
• supplier relationship owner; and
• the source of each contact.

A supplier is not ready for outreach because an address exists in the ERP. Confirm that the person still works there and that their function matches the request. See How Do You Find the Right Contact at a Supplier?.

Campaign activity

Record:

• initial request date;
• last contact date;
• current campaign state;
• platform state and progress percentage;
• blocker;
• next action;
• next-action date; and
• escalation owner.

Do not store every email body in the tracker. Keep the message history in email or the campaign system and use the tracker to show current state and next action.

Submission and review

Record:

• submission date;
• submission status;
• reviewer;
• review date;
• correction requested;
• evidence link;
• accepted date; and
• next reporting date.

This is the part that distinguishes a response dashboard from a completed-data dashboard. A high response rate can coexist with a low acceptance rate.

How should you run the weekly campaign review?

Export the latest platform statuses before the meeting. Join them to the tracker using a stable supplier ID where possible.

Review the campaign in this order:

1. Past-due next actions. Reassign or complete anything whose action date has passed.
2. Missing contacts. Prioritize high-emitting suppliers that cannot yet receive the request.
3. New platform activity. Move suppliers that connected, started, submitted, or changed progress.
4. Blocked suppliers. Route technical questions, missing data, account problems, and payment objections to named owners.
5. Submissions awaiting review. Protect reviewer capacity so completed questionnaires do not sit untouched.
6. Returned submissions. Confirm that the supplier received a specific correction request.
7. Escalations. Decide which suppliers justify procurement, category-manager, or leadership involvement.
8. Accepted suppliers. Record the evidence and next reporting date before closing them.

Finish with no overdue row lacking an owner and date. “Follow up soon” is not a next action.

How should you prioritize the open queue?

Do not sort only by the age of the request. Use four inputs:

1. Emissions or target coverage: How much does this supplier contribute to the program goal?
2. Deadline risk: How little time remains for outreach, supplier work, review, and correction?
3. Completion distance: Can one correction close the supplier, or has no contact been found?
4. Commercial influence: Can procurement or a category owner move the request?

A high-emitting supplier waiting on one corrected unit may deserve attention before an older request sent to a low-impact supplier with no working contact.

Which measures should appear on the campaign dashboard?

Keep counts and rates tied to a clearly defined denominator.

Outreach coverage

• suppliers in scope;
• suppliers with a validated primary contact;
• suppliers with a backup contact;
• requests delivered; and
• suppliers still missing a contact.

Engagement

• acknowledged;
• started;
• blocked;
• submitted; and
• escalated.

Accepted outcomes

• submissions accepted;
• submissions returned for correction;
• emissions or spend coverage accepted;
• qualifying targets confirmed; and
• suppliers overdue.

Do not combine these into one completion percentage. The program owner needs to know whether the constraint is contact coverage, supplier participation, internal review, or evidence quality.

How do you manage several collection platforms?

Use one campaign tracker above the platform exports. Preserve each platform’s supplier ID and status, but map every row to the same internal campaign states.

This lets the team run one weekly review when:

• one supplier is completing EcoVadis;
• another is sharing data through CDP;
• another is answering a Watershed survey;
• another is sending a spreadsheet by email; and
• another has an accepted public target that needs annual confirmation.

The accounting or assessment platform remains the record for the submitted data. The campaign tracker remains the record for contacts, reminders, blockers, review, and escalation.

When does a spreadsheet stop working?

A spreadsheet remains workable when one person can keep the status current, follow-ups are limited, and submissions do not require repeated review.

It starts to fail when:

• several people send messages from separate inboxes;
• platform exports must be reconciled every week;
• contact replacement becomes a separate queue;
• hundreds of next-action dates must be scheduled;
• suppliers reply with referrals, questions, and partial submissions;
• reviewers return submissions for correction; or
• campaign history must be reconstructed for an audit.

At that point, the spreadsheet can still define the data model, but email handling and status updates need a campaign system.

Frequently asked questions

Should you track one row per supplier or one row per request?

Use one row per supplier when every supplier receives the same request. Use one row per supplier-request pair when suppliers have several requests, reporting periods, products, or sites. Do not put several independent deadlines and acceptance states into one cell.

Should product-level data use a separate tracker?

Use one row per supplier-product-request combination when completion and evidence differ by product. Keep the supplier ID so the rows can still be grouped for contact and escalation work.

How often should you refresh platform status?

Refresh before each campaign review and more often near the deadline. A weekly export is a reasonable starting point. Increase the frequency when questionnaire progress or accepted submissions change daily.

Who should own the tracker?

Assign one campaign operator to maintain state and next actions. Sustainability owns program scope, technical reviewers own acceptance, and procurement owns commercial escalation. Shared ownership without one operator usually produces stale rows.

Where Bridgecurrent fits

Bridgecurrent maintains the operational layer around the tracker. It finds and validates the supplier contact, sends the request from your company domain, follows up according to the current state, records replies, and flags technical or commercial decisions for your team. Book a 20-minute call and bring a supplier list. We will show you how the open rows would move through the campaign.