What applies to you

The denominator is the whole problem

Every percentage in a compliance tool is a fraction, and the fraction is only as good as its bottom half. KinopiQ resolves which requirements your organisation actually owes before it measures anything.

Start an assessment

Four axes

What decides whether a requirement is yours

All four have to pass. A requirement whose envelope does not match your organisation is hidden entirely — it is not shown as an unmet gap, because it is not one.

Size: Seven bands. Your worker count and your revenue are banded separately, and you sit in whichever gives the smaller of the two — B Lab’s own rule, and the one most often got wrong.
Sector: Five sectors, split by operational footprint: agriculture, manufacturing, wholesale and retail, and services with either a minor or a significant footprint.
Phase: Year 0 to certify, Year 3 and Year 5 to recertify. Phases are cumulative, so an organisation at Year 5 still owes everything from Year 0.
Risk flags: Some sub-requirements are triggered by risk rather than size — a high-risk sector, or operating in a high-risk geography. Those come from B Lab’s risk-profiling step.

B Corp · V2.1 · one organisation

35 of 48 requirements apply

Applies to youOut of scope — not counted against you

Illustrative. What applies depends on your worker count, revenue, sector, certification phase and risk flags.

Size bands

Banded on workers and on revenue, then the smaller one wins

A five-person consultancy turning over $80m is not asked to do what a 5,000-person manufacturer does, and the reverse holds too. Revenue bands are defined in USD; KinopiQ converts from your reporting currency.

Band	Workers (FTE)	Annual revenue
No workers	0	£0
Micro	up to 9	up to $1m
Small	up to 49	up to $10m
Medium	up to 249	up to $50m
Large	up to 999	up to $250m
Extra large	up to 5,000	up to $1bn
Extra extra large	above 5,000	above $1bn

Bands as published by B Lab in Standards V2.1. KinopiQ stores the derived band alongside the figures it came from, so a change to either is reflected in your applicable set immediately.

The rule that surprises people

Marking something not-applicable raises your score

Not-applicable removes a requirement from both sides of the fraction rather than counting it against you. It needs a written reason, and an assessor will read that reason — so it is a judgement you record and defend, not a way of quietly deleting work.

Met — countsIn progress — countsUnmet and mandatory — blocksNot applicable — leaves the fraction

Only what applies to you

The right denominator

Record your worker count, revenue, sector and certification phase. KinopiQ resolves the requirements that genuinely apply to an organisation of that shape, and hides the rest. A requirement that does not apply to you is invisible — not sitting there as an unmet gap.

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.

Standards that stay current

Editions, not vibes

Six frameworks, each carrying its own edition, effective date and lifecycle. When an edition is superseded — as ISO 14001:2015 was, and TCFD before it — the app says so and names the transition deadline rather than going quietly stale.

In development

Find out what you actually owe

A company profile takes a few minutes, and it is the difference between a number you can defend and one you cannot.

Start an assessment Talk to us