What we believe
Reporting what
actually matters
We started from a simple observation: most sustainability reports are written to satisfy the organization that produces them, not the people who need to read them. We think that's worth changing.
Back to homeFoundation
Where this all comes from
Sustainability reporting borrows its vocabulary from financial accounting — materiality, disclosure, assurance — but often doesn't borrow the discipline. Financial accounts are subject to rigorous verification because people make real decisions based on them. We believe ESG data deserves the same treatment, for the same reason.
People making investment decisions, procurement choices, and regulatory judgments are increasingly relying on sustainability disclosures. When those disclosures are vague, inconsistently assembled, or quietly optimistic, the people relying on them are working with something less useful than they think.
Our work is shaped by the view that this matters — not as a technical compliance point, but as a practical question of trust. Organizations that report honestly, even where the picture is incomplete, build more durable credibility than those that project an image of comprehensive performance they can't fully substantiate.
Philosophy
The discipline of honest measurement
There's a version of sustainability reporting that exists primarily to project a positive image. The figures are selected for their favorability, the language describes intentions more than outcomes, and the gaps are filled with forward-looking statements. Reports like this aren't false exactly — but they're not particularly useful either.
Then there's reporting that applies the same care to environmental and social data that competent accountants apply to financial figures. Sources documented. Methodology explained. Gaps identified and acknowledged rather than glossed over. Comparisons between years possible because the methodology didn't change.
The second kind is harder to produce. It's also considerably more valuable — both to the stakeholders reading it and to the organization that produced it, which now has a factual foundation for understanding where it actually stands.
Vision
What we're working toward
A world where sustainability disclosures are as trustworthy as financial ones — not because regulation forces it, but because organizations understand why it matters and have the practical capability to do it well.
We're not under any illusion that this happens quickly. But each organization that builds honest, documented reporting practice makes the overall landscape a little more reliable. That's the contribution we're trying to make, one engagement at a time.
We keep this vision in view without letting it make us precious about the practical work. Most organizations aren't starting from a perfect position — they're starting from where they are. That's fine. That's where we start too.
Core beliefs
What we actually believe
These aren't values statements produced for a website. They're the positions that inform how we work — and the things we'd say directly if you asked.
Accuracy is not optional
A figure in a report should reflect what actually happened. When it can't, that needs to be explained. We don't accept the idea that approximate data presented confidently is a reasonable substitute for accurate data presented honestly.
Gaps are information too
An organization that says "we don't yet measure this, and here's why" is telling stakeholders something real. One that fills the space with vague language is telling them something too — just less honestly. We consistently recommend the former.
Substance over presentation
A well-designed report that lacks solid data is a liability, not an asset. Stakeholders with real expertise can tell the difference — and the ones making important decisions tend to be exactly those people. We prioritize the content, not the wrapper.
Progress beats perfection
We'd rather help an organization produce an accurate report of a partial picture than an impressive-looking report of a complete fiction. The first is something you can build on. The second is a problem waiting to surface.
Frameworks serve a purpose
Reporting frameworks exist because stakeholders need comparable, structured information. We use them as genuine tools, not as boxes to check. When a framework requirement is genuinely applicable to your situation, we take it seriously. When it isn't, we say so.
The reader comes first
Reports are written for the people who will read them — investors, procurement teams, regulators, employees. If a disclosure doesn't communicate usefully to those readers, it hasn't done its job, regardless of how it looks internally.
In practice
How beliefs become work
Abstract principles only matter if they change how things are done. Here's where ours show up in practice.
How we handle missing data
When data isn't available, we document why, indicate what would be needed to collect it, and note what we've done in its place — whether that's an estimate with stated assumptions or a frank acknowledgment that the figure isn't yet measurable. We don't fill gaps with language that obscures them.
How we select frameworks
We start by understanding your stakeholders and what they need to know. The framework follows from that — not the other way around. An organization reporting to a small set of supply chain customers has different needs from one filing with institutional investors, and the framework choice should reflect that.
How we write disclosures
We write in plain language that describes what happened and what was measured. We separate current performance from future commitments explicitly, because conflating the two is one of the more common ways reports mislead without technically being inaccurate.
How we give advice
Recommendations are proportionate to your situation. We don't suggest data collection systems an organization isn't resourced to maintain, or reporting scope that exceeds what your stakeholders actually need. Practical suggestions that get implemented are more valuable than comprehensive ones that don't.
How we work with you
Starting from where you are
Every organization we work with is at a different point. Some have been reporting for years and want to strengthen their methodology. Some are producing their first report and aren't sure where to begin. Some have received questions from stakeholders they couldn't fully answer and want to address that.
We adapt to the situation rather than applying the same process to everyone. What stays consistent is the standard we hold the work to — the accuracy of the data, the honesty of the disclosure, the usefulness of the output to whoever reads it.
We also try to be straightforward about what we can and can't do for you. If your situation calls for something we're not best placed to provide, we'll say so rather than taking on work that won't serve you well.
We listen before we recommend
Understanding what your stakeholders need and what your organization can realistically support shapes every recommendation we make.
We explain our reasoning
When we suggest a particular approach, we say why. You should be able to evaluate our reasoning, not just accept our conclusions.
We respect your priorities
You know your organization and its constraints better than we do. Our job is to give you accurate information and practical options, not to override your judgment about what to do with them.
How we improve
Thoughtful improvement, not change for its own sake
Reporting standards evolve. Stakeholder expectations shift. Regulatory requirements expand. We track these changes so our clients don't have to — but we filter carefully for what's actually useful.
Framework evolution
When frameworks update — GRI revisions, ISSB standards, TCFD alignment — we assess what the changes mean practically for the organizations we work with and update our approach accordingly.
Data methods
Better tools for collecting, organizing, and verifying ESG data become available over time. We adopt them when they genuinely improve accuracy or reduce client burden — not to add complexity.
What we don't change
The core standard — accurate data, honest disclosure, useful output — doesn't shift with trends. How we achieve it evolves; what we're trying to achieve doesn't.
Integrity
How we hold ourselves to account
It would be inconsistent to advocate for honest reporting while being vague about our own work. So here's what accountability looks like from our side.
We document the methodologies we use. We explain our recommendations and can defend them if challenged. If we make a mistake — a figure that was calculated incorrectly, a framework requirement that was missed — we correct it, explain what happened, and update our process to prevent recurrence.
We also try to be transparent about scope. There are things we're well-placed to do and things we're not. A Readiness Review is a review, not an assurance engagement — we say so clearly, because conflating the two would mislead clients about what they're getting.
We document what we do
Every significant judgment in a report — what was included, what was excluded, how a calculation was done — is documented so it can be reviewed.
We describe our scope accurately
We tell clients clearly what a service does and doesn't provide — and what would be required to go further if they need it.
We don't overstate our conclusions
When data supports a conclusion, we state it. When it suggests a direction without being definitive, we say that too.
We correct errors openly
Mistakes happen. How they're handled matters more than the fact that they occurred.
Working together
This isn't a service done to you
Good reporting requires knowledge from both sides. We bring framework expertise and data methodology; you bring organizational knowledge that no external party can replicate.
Your knowledge is essential
The context behind your data — why a figure looks the way it does, what changed during the year, what's being worked on — can only come from inside your organization. We ask for it and use it properly.
We work at your capacity
Not every organization can dedicate the same internal time to reporting. We adapt to what's practical for you rather than requiring a standard level of engagement that doesn't fit your situation.
The goal is your capability
We'd rather leave you in a stronger position to manage reporting than create dependency on our involvement. When we set up data processes, we document them clearly so your team can run them.
Long-term view
Thinking past the next report
A single well-prepared report is worth having. A consistent track record of honest, well-documented reporting across multiple years is worth considerably more. Stakeholders who see the same careful methodology applied year after year develop a different kind of confidence than those who see a polished one-off.
We set up data processes that are intended to persist. When a new framework requirement emerges, the data infrastructure is already in place to meet it. When a stakeholder asks a specific question about a figure from two years ago, there's documentation to answer it.
This is the practical version of long-term thinking in reporting: building something that gets more useful over time rather than starting from scratch each cycle.
For you specifically
What this philosophy means when we work together
You'll know what we're doing and why
We explain our methodology and recommendations. You won't receive outputs you can't account for.
We'll tell you where your reporting has gaps
Honestly, with context, and with practical suggestions — not as a sales pitch for additional services.
You'll be able to stand behind the report
Every figure will have a documented source. You'll be able to answer questions about it with confidence.
The work will compound over time
Each year builds on the last. By year three, you'll have a multi-year track record that's genuinely valuable.
We'll be straight with you
If something isn't achievable in your timeframe or doesn't make sense for your situation, we'll say so rather than finding a way to proceed anyway.
Your team will learn from the process
We document what we do clearly enough that your people understand it and can contribute meaningfully to future reporting cycles.
If this resonates
Let's talk about your reporting
If this way of working sounds like what you're looking for, we'd be glad to hear about your situation. A short conversation usually gives us both a clear sense of whether there's a good fit.
Get in touch