Published case studies
This first case study covers a consultancy's workflow, not a company's own disclosure, so it has no footprint figures. Those belong to EMCL's clients. The next ones will be first reporting cycles run by companies themselves.
What a case study here will contain
Most vendor case studies leave out the only useful part. A company adopted a product, everything went well, and there is a quotation from a job title.
The ones worth reading describe what was actually hard: the data that could not be found, the site that never responded, the boundary decision that had to be revisited, the assumption an assurance provider rejected. That is what a company facing the same problem needs to know, and it is what we ask participants to let us publish.
The structure we use
The starting position
What existed before: what was measured, what governance was in place, what the deadline was.
What was collected, and how
The practical mechanics, including which collection approaches failed before one worked.
What went wrong
Named specifically.
The numbers, where the participant permits
Footprint split by scope, and what surprised them, published only with explicit agreement. If a section does not apply, as with a consultancy, we say so.
What they would do differently
In their words, reviewed by them, not paraphrased by us.
Taking part
If you are running a first cycle and would be willing to have it written up, we would like to talk. You have full editorial approval over the text and over whether you are named at all.
Very few accounts of a first Nigerian reporting cycle are published, so every company learns the same lessons privately. That is worth changing.