Step 1 · Question
Narrowed until it can be answered.
What we do, in detail
Four things, with one line kept deliberately sharp.
Program 01 · SIC 63990
Information and research
The value in this work is rarely the answer; it is knowing how much weight the answer will bear. So anything supplied comes with its provenance and with the parts that could not be established, because a confident summary that conceals a gap is worse than no summary at all. A client making a decision needs to know which of three facts is solid and which is an inference.
Step 2 · Sources
Found, and weighed against each other.
Step 3 · Checked
Against a second source where possible.
Step 4 · Supplied
With provenance and with the gaps.
Step 1 · Brief
Audience, purpose and length.
Step 2 · Draft
Sourced as it is written.
Step 3 · Check
Facts, names, figures and dates.
Step 4 · Correct
By a route agreed in advance.
Program 02 · With corrections
Publishing
A publisher is judged less by its mistakes than by what happens after one. So the correction route is decided before publication rather than improvised under pressure: who can be told, how quickly a change is made, and whether a correction is marked as one. Quietly editing a page and hoping nobody kept a copy is the cheapest option available and the one that costs the most when it is noticed.
Program 03 · What it brings with it
Letting users post
A comments box is two days of development and a permanent set of obligations, and the order in which people discover that is usually the wrong way round. The questions are concrete: can one user see another's content, is there any route for a child to reach it, what would a risk assessment have to say, and who inside the organisation is going to own it. Sometimes the honest answer is that the feature is not worth what it brings.
Step 1 · Functionality
Exactly what a user could post or see.
Step 2 · Reach
Who can encounter it, including children.
Step 3 · Owner
Who inside the organisation holds it.
Step 4 · Decide
Including deciding not to build it.
Step 1 · Route
Visible, and reaching a named person.
Step 2 · Triage
What is urgent, and what is not.
Step 3 · Log
Decision, reason, time, by whom.
Step 4 · Appeal
A way to object to a removal.
Program 04 · Routes that work
Reporting and takedown
Most small services have no reporting route at all, or one that reaches an inbox nobody reads. The practical fix is unglamorous: a visible way to report, a named person who receives it, a log of what was decided and when, a stated timescale, and a route for the person whose content was removed to object. The log matters more than people expect, because a decision nobody recorded is a decision nobody can show they made.
A question to answer, or a feature about to go live?
A free first conversation, with no obligation. If the honest answer is that a feature is not worth what it brings, we will say so.