The CometX Method

Scope → Evidence → Build → Transfer.

Four steps, in that order, on every engagement. It is not a proprietary secret — it is published here precisely so you can hold us to it, and so another organization can use it without paying us anything.

The four steps

Each one has a test it must pass before the next begins.

Step 01

Scope

Decide what would count as success — before anything is designed.

  • Who has to do something differently, and what exactly?
  • What would change if this worked, and how would you know?
  • What is already known, and what genuinely needs finding out?
  • What is out of scope, written down, so it stays out.

Most engagements fail here, quietly, by starting from a deliverable instead of a decision. We will tell you if your budget does not match your need rather than deliver less and say nothing.

Step 02

Evidence

Find out what is true, at the smallest scale that answers the question.

  • A rapid evidence review before any new data is collected.
  • Primary research only where the answer does not already exist.
  • Methods and limits stated up front, with a confidence rating attached.
  • Findings tested with the people they describe before they are published.

Confidence ratings are not decoration. A thin answer labelled as thin is more useful than a confident one that will not survive contact with your context.

Step 03

Build

Turn the finding into something usable on a Monday morning.

  • Training, tools, templates or policy — whatever the finding actually implies.
  • Accessible by default: WCAG 2.2 AA before it goes out, not on request.
  • Plain language, because a finding nobody finishes reading changes nothing.
  • Built with your team in the room, not delivered to them.

This is where most research stops and most consulting starts. Doing both is the point: the people who found the evidence are the people who build the response to it.

Step 04

Transfer

Leave, and have it keep working.

  • Documentation your team wrote, not documentation we wrote for them.
  • A named person inside your organization who can run it.
  • Source files, templates and data handed over, not retained.
  • A follow-up at twelve months to find out whether it survived.

Dependency is a business model, not a service. The measure of an engagement is whether you can do it next time without us — which is why we ask a year later whether you did.

Why publish it

A method you cannot inspect is a claim, not a method.

Consultancies usually keep their approach vague, because vagueness is commercially useful — it makes comparison hard and scope creep easy. We would rather be comparable.

Publishing it also means an organization with no budget can follow the same sequence themselves. That costs us some work and is entirely consistent with being a not-for-profit.

Hold us to it

If an engagement with us skips a step — no scoping call, no evidence review, nothing handed over — say so. Write to contact@cometx.ca and we will fix it.

Where it shows up

The same four steps, whatever the practice.

Training, an accessibility audit, an evaluation or an EDIA review all run through the same sequence. What changes is the evidence, not the shape.

Free to reuse

This method is published under Creative Commons BY 4.0, like everything else we put out. Use it, adapt it, teach it — just credit CometX.