The same problem keeps coming back wearing a different name.

Turn drift into visible control as you scale.

A named status for every project — not green, amber, red, or a number out of ten.

The companion portal to The Control Standard. Score projects across the operation, watch drift over time, and decide whether repeated pain is behavioural, procedural, or software-shaped — before you spend on the wrong fix.

Free · No account needed · A 5-minute scored check · Built around The Control Standard by Andrew Ward.

controlstandard.tools/dashboard

Acme Studio · Workspace

Your projects

Add project
  • Q3 client onboarding

    Owner: you · next step due Thu

    Strong, Room to Sharpen
  • Internal billing rebuild

    Decision 12 Jul · fallback agreed

    Sound, But With a Vulnerability
  • Sales onboarding pilot

    Owner: Priya · no fallback named

    Multiple Areas Drifting

Team · control points

9 of 11 held

Your projects stay in Jira, Trello or the spreadsheet. This is where you see whether they're under control.

What control means here

Not a project tool. An operating layer above the work you already do.

The same problem keeps showing up in a different shape. That's drift hiding inside activity — and it gets more expensive as you scale. See whether work is genuinely owned, dated, decided and backstopped, in plain English, before you hire, build, or buy your way around it.

ControlStandard.Tools is the companion portal to The Control Standard by Andrew Lee Ward — a behavioural control layer that sits above your project management tools and gives every piece of important work a named owner, a dated next step, a decision date, a fallback, and a named status.

Vague

  • "WE'RE ON IT"

  • "SHOULD BE FINE"

  • "CHASING IT NOW"

Under control

  • PRIYA OWNS IT.
  • DUE THURSDAY.
  • FALLBACK NAMED.

Four things hold work under control: owners, dated next steps, decisions and escalations, and fallbacks. Everything in this product is built around making those four visible.

Free to try

Free resources to try the standard first.

Try the standard on your real work before you commit to anything. Run a five-minute diagnostic, print the pocket reference, keep whatever's useful — no card, and for most of it, no account.

Free report · 5 min

Drift Report

Score your work against the ten disciplines and get a named status back — not a number out of ten.

Get my Drift Report

Free report · 5 min

Pain Automation Score

Score one repeated pain. Some are worth software. Most aren't yet — and we'll say so.

Score a repeated pain

From The Control Library: guides to project controls, delegation and status reporting · glossary — drift tax, control points, named statuses

How it works

One loop: learn it, score it, apply it, track it, systemise it.

Not another project app — a control layer above the tools you already run. Everything sits on one loop, built to surface drift across the operation before it shows up in a board pack.

  1. 01

    Learn

    A short course for every chapter of the standard.

  2. 02

    Diagnose

    Score where your work is actually drifting.

  3. 03

    Apply

    Owners, dates, decisions and fallbacks on real work.

  4. 04

    Track

    Watch the drift fall, check-in by check-in.

  5. 05

    Improve

    Decide which recurring pain is worth systemising.

Diagnostics & Friction Log free · no credit card · 5 free Control Index snapshots

Interactive courses

Learn the standard, don't just read it.

Short, interactive courses — one per chapter of The Control Standard. Learn the moves the portal asks for through retrieval practice and worked scenarios, so your weekly control checks aren't guesswork.

  • Retrieve, don't re-read — questions, decisions, and worked examples, not passive video.
  • Bridges to the work — each course ends with the matching chapter assessment and a cue back into the portal.
  • Stand-alone, by design — no need to have read the book first.

Orientation + Chapter 1 free, forever · ~10–20 min per sub-module

Line illustration: an open book with a red bookmark, a rising sequence of course cards emerging from its pages, and an arrow connecting the topmost card to a project clipboard.

Two ways in

Score the pain, or build the system around it.

Decide whether a repeated pain is worth automating before you spend — behavioural, procedural, or software-shaped.

The Control Standard — book cover

The thinking behind the tools

The operating standard behind every screen: The Control Standard.

The standard these tools are built around — owners, dated next steps, decisions, and fallbacks. Read it once, then use the companion to apply it on a Tuesday morning.

Beyond the portal · separate service

Pain genuinely software-shaped? Scorchsoft can build it.

If a diagnostic shows your repeated pain is software-shaped, Scorchsoft — the team behind the standard — builds custom portals, workflows, dashboards and integrations around it. Different engagement, different commercials, not part of the portal subscription.