KinopiQ

Evidence and proof

The proof behind the story you tell

Most organisations doing this work end up writing an impact report — something they publish, hand to a funder, or put in front of a board. The awkward part is never the writing. It is finding the document that backs each sentence, months after the fact.

The same work, twice over

Your impact report is already sitting in your assessment

Working through a standard means writing down what you committed to, what you actually did, and what proves it. That is not preparation for the report — that is the report. KinopiQ keeps the three together, so nobody has to reconstruct them from a shared drive each spring.

61%

of the B Corp requirements that apply to us are met

48

documents standing as evidence across four topics

7

requirements we recorded as not applicable, each with a reason

  • The claim

    The requirement itself, in the standard’s own words, with its code so anyone can look it up.

  • The narrative

    The note you wrote against it — what you actually did, in your own voice. This is the paragraph that ends up in the report.

  • The proof

    The documents you linked. A reader who wants to check a line can, and one who doesn’t never has to.

KinopiQ does not write your report or design it for you. What it does is make sure that when you sit down to write, every claim already has its evidence attached and its wording agreed.

Impact snapshot

Workers

B Corp · V2.1 · reporting year 2026

What we said we’d do

What we did

Pay every worker at or above the real Living Wage.

Accredited with the Living Wage Foundation in March. Lowest hourly rate now sits 8% above the real Living Wage.

MetAccreditation certificatePayroll summary

Measure our operational emissions for the first time.

Scope 1 and 2 measured across the year; Scope 3 partially mapped, with supplier data still to come.

In progressEmissions inventory
Illustrative. Every line here is something KinopiQ already stores — the requirement, the note you wrote against it, its status, and the documents you linked as proof.

Who this is for

An assessor is one reader, and rarely the important one

Certification is a milestone, not the goal. The reason to keep a clean record is that several different audiences ask you the same question in different words — and only one of them is asking for compliance.

Your customers

More of them are asking what you stand for before they buy — and increasingly asking you to prove it rather than assert it.

Funders and investors

A grant application or a diligence pack goes faster when the claim, the number and the document behind it already sit together.

Your board

Direction of travel, not just a snapshot. What moved since last year, what did not, and what is blocking the next milestone.

The people who work for you

The clearest signal that a commitment was real is being able to show what came of it. That is a hiring and retention story as much as a compliance one.

An assessor or auditor

Give them a viewer seat and they read the whole record without you assembling anything. That matters — it is just not the only reason to keep it.

One record, written once, that all of them can read — at the level of detail each one needs.

Upload once

One document can prove several things at once

An employee handbook is evidence for a fair work requirement, an inclusion requirement and a human rights requirement simultaneously. Modelling evidence as one document per requirement would make you upload it three times — which is precisely the busywork this product exists to remove.

  • Link, don’t duplicate. Attach a document to as many requirements as it proves.
  • Counted where it matters. Every requirement shows how much evidence stands behind it, so thin spots are visible before someone else finds them.
  • Kept private. Documents live in a private store and are reached only through short-lived signed links — the browser never talks to the storage backend directly.
  • Enforced in the database. Access is gated on workspace membership by row-level security, not just hidden in the interface.
The evidence library, showing documents and the requirements each is linked to

Sharing

Let people see the working, not just the headline

A workspace holds one organisation — its profile, its enrolments, its answers and its evidence. People are invited into it by email, with a role that decides what they can do.

Owner

Everything, plus inviting people, changing their role and removing them. A workspace has exactly one.

Editor

Change answers, upload and link evidence, and edit the company profile. Cannot manage membership.

Viewer

Read everything and change nothing — the seat for a board member, an adviser, an assessor or an auditor.

You can also record an accountable owner against each individual requirement, so it is clear who is answering for it.

Worth being clear about

KinopiQ holds the material. You still tell the story

KinopiQ does not design or publish an impact report, and it does not export finished graphics today — that is on the roadmap, not in the product. It is not a certification body and does not submit anything on your behalf. What it gives you is the record underneath: what applies to you, what you have done about it, what proves it, and what is still outstanding.

Evidence, attached once

Proof where it belongs

Upload a document and link it to every requirement it proves. One employee handbook can stand as evidence under fair work, inclusion and human rights at the same time, without uploading it three times.

A score you can defend

Computed, not asserted

Every percentage is worked out on the server from the applicable set. Only leaf requirements count, so nesting never inflates the total, and marking something not-applicable — with a reason — raises your score instead of depressing it.

Blockers kept separate

No false comfort

Unmet mandatory requirements are reported on their own, apart from the headline figure. Ninety-five per cent with one mandatory gap is not ninety-five per cent of the way to certified, and KinopiQ will not let a progress bar imply otherwise.

The whole team, one record

Owners, editors, viewers

Invite colleagues into a workspace by email as editors or viewers, and give each requirement an owner. Your auditor or certification body gets read access without being able to change the answers.

In development

Do the work once, and have something to show for it

Bring your policies, reports and board minutes, link them to what they already prove, and stop rebuilding the same evidence pack every year.