How it works
Plenty of activity. The hard question is whether the work is genuinely under control.
ControlStandard.Tools isn't another project tool. It's one closed loop — learn the standard, diagnose where you're drifting, apply it to real work, track the trend, and systemise the pain that keeps coming back. Here's the whole thing, stage by stage.
The loop
Five stages, then round again.
No competitor closes this loop in one place. A learning platform stops at "learn". A project tool starts at "track". The value is the circle — and it never really ends, because new work and new joiners keep arriving.
-
01
Learn
Pick up the standard — a short course per chapter.
-
02
Diagnose
Score where your work is actually drifting.
-
03
Apply
Give the work owners, dates, decisions, fallbacks.
-
04
Track
Watch the drift fall, week over week.
-
05
Improve
Decide which recurring pain is worth systemising.
Improve feeds straight back into Diagnose — the loop keeps turning.
Stage 01 · Learn
Everyone nods at "just take ownership." Almost no one has been shown what that actually means.
The standard is a concrete set of moves, not a mindset. Short, interactive courses make it learnable on its own — one per chapter of the book, retrieval-based, not video-based.
Start learning the standardYour curriculum · 3 of 10 complete
Learn the Standard
- Orientation
- What "under control" means
- Ownership beyond task completion
- 03 Executive usefulness In progress
- 04 The control toolkit
- + five more chapters
Stage 02 · Diagnose
You can feel that something's drifting. You can't yet say what, or how badly.
Two short diagnostics turn a vague worry into a named, specific read. Both are free, and neither needs an account.
Get a free Drift ReportDrift Report
Q3 client onboarding
Six of ten disciplines plotted · 3 flagged
Stage 03 · Apply
"We're on it" is where most updates end. It's also where the drift hides.
The Project Control Index turns a vague project into something genuinely owned, dated, decided and backstopped — discipline by discipline.
Create a free accountControl point
Vendor contract signed by Thu
- Owner
- Priya
- Target date
- Thu 28 Aug
- Decision-by
- Tue 26 Aug
- Fallback
- Bridge SOW
Stage 04 · Track
A score taken once is a guess. A score taken every week is a trend you can coach.
Check-ins turn the index into a trend. For a manager, the whole team's drift rolls up in one place — without booking another status meeting.
And it isn't only projects. Delegate ownership of a function, a goal, or a standing responsibility — with what good looks like, the constraints, and a check-in rhythm — and a delegation map shows you who owns what and whether it's on track.
Project Control Index
Q3 client onboarding · 8 weeks
3.6 ↑ 0.8 since wk 1
Stage 05 · Improve
The same problem keeps coming back. The hard question is whether it's worth fixing properly.
The Friction Log captures recurring pain the moment it bites; the Systemise Review decides what to do with it. Free on every plan.
Start your Friction Log — freeSystemise Review · this week
-
Mon
Chased finance for invoice status again — third time this month.
Software-shaped -
Wed
Onboarding doc got out of date again.
Write it down -
Fri
Status meeting overran — everyone had read the digest already.
Live with it
Built for a team to trust
The plumbing a manager needs to sign off on.
Not the headline — but real, and the same standards Scorchsoft holds on the custom software it builds.
Roles & permissions
Admin, Manager, Contributor and Viewer roles, per-user overrides, and per-project access controls.
2FA & Single Sign-On
Opt-in two-factor with org-level enforcement; OIDC and SAML single sign-on on the Scale plan.
Read-only REST API
Bearer-token API on Business and above — feed your project and check-in data into BI tools and dashboards.
Audited & encrypted
Every organisation's data is tenant-scoped, sensitive secrets are encrypted at rest, and access is audit-logged.
What this is not
Deliberately not a task tracker, a Kanban board, a CRM, or a course platform.
ControlStandard.Tools is a control layer that sits above the tools you already use. It doesn't own your tasks, files, messages or calendars — it answers one question those tools can't: is this work genuinely under control, or are we just busy around it? If a feature wouldn't help you answer that, it isn't here.
Seen the loop?
Try it free, or see what each plan includes.
The diagnostics and the Friction Log are free, no card needed. Pricing only matters once you know the loop earns its place.
Still have questions? Read the frequently asked questions.
/ 19 Get started
Interactive courses
The pain it solves
Everyone nods at “just take ownership.” Almost no one has been shown the actual moves — so it stays a slogan instead of becoming a skill.
Each chapter of the book becomes a short, interactive course built on retrieval practice, not video you half-watch. You make the call on a real scenario, then see what a controlled operator would have done — and why. It is learnable on its own, one chapter at a time, and Orientation and Chapter 1 are free forever.
Browse the coursesChapter 02 · Scenario
A direct report says “it’s basically done.” You ask one question. Which?
Right — “done” hides the risk. You just surfaced it.
Chapter assessments & certificate
The pain it solves
Reading a chapter and being able to apply it are not the same thing — and you have no way to prove the difference to a manager.
Every chapter ends with an assessment that checks you can actually use the standard, not just recognise it. Pass them all and you earn a verifiable certificate with a public verification page — something concrete to put in front of a boss or on a profile, backed by a record anyone can check.
Certificate of the Standard
Awarded to Priya N.
All 10 chapters · assessed and passed
Team chapter progress
The pain it solves
New joiners absorb “how we work here” by osmosis — so everyone ends up with a slightly different idea of what good looks like, and you only find the gaps under pressure.
Managers see who has completed which chapter at a glance. Every joiner picks up the same standard, the same way — so the bar is set once, deliberately, rather than depending on whoever happened to train them.
Team · chapter progress
Drift Report
The pain it solves
You can feel a piece of work slipping, but “it feels off” is not something you can act on — or raise with anyone — without sounding vague.
A five-minute self-score against the ten disciplines turns the worry into a named, specific read. You get a status back — not a bare number out of ten — with the disciplines that have quietly drifted called out, so you know exactly where to look. Free, and no account needed.
Get a free reportDrift Report
Room to SharpenTen disciplines plotted · 3 flagged
Pain Automation Score
The pain it solves
Some recurring pain genuinely needs software; most just needs a decision. Guess wrong and you either build the wrong thing or suffer the same friction forever.
Score one recurring pain and get an honest read on whether software, a process change, or simply living with it is the right fix — before anyone spends a penny building anything. It is a cooling-off step between “this is annoying” and “let’s build something.”
Score a recurring painPain Automation Score
“Chasing finance for invoice status, every month.”
Project Control Index
The pain it solves
“We’re on it” is where most updates end — and it is exactly where the drift hides, because nobody has said what “it” actually requires.
First you pin down the outcome and the 3–5 pillars that must hold for it to land. Then you score the project across all ten disciplines. A vague project becomes something genuinely owned, dated, decided and backstopped — discipline by discipline, with the weak points impossible to wave away.
Project Control Index
Q3 client onboarding
Pillars that must hold
- Data migrated clean
- Sign-off by 30 Sept
- Single named owner
Ten disciplines
Control points
The pain it solves
A task with an owner and a due date still drifts — because nobody agreed what should be true, when the decision must be made, or what happens if it slips.
Every critical item gets the four-point framework: what should be true, the target date, the decision-by date, and the fallback if it does not land. The next step is never ambiguous, and a slip triggers a plan instead of a surprise.
Control point
Vendor contract signed by Thu
- Owner
- Priya
- Target date
- Thu 28 Aug
- Decision-by
- Tue 26 Aug
- Fallback
- Bridge SOW
Accountable ownership
The pain it solves
When everyone is responsible, no one is. “The team owns it” is how an outcome ends up owned by nobody — and how the post-mortem has no one to learn with.
Each project carries a single named Directly Responsible Individual, with an append-only history of who was accountable and when. Accountability has a name and a date, not a committee — and the handovers are on the record, so nothing silently changes hands.
Accountable owner (DRI)
Priya N.
since 12 Aug · current
History
- Priya N. · 12 Aug
- Marcus T. · 1 Jul – 12 Aug
Check-ins & trend
The pain it solves
A score taken once is a guess. Without a trend you cannot tell whether a discipline is recovering or quietly getting worse.
Re-score on a cadence and every check-in is kept immutably. Watch a discipline climb from 2 to 4 over eight weeks — and, just as usefully, watch one slide — so you can ask what changed while the answer is still fresh.
Control Index · 8 weeks
3.6↑ 0.8
Cadence reminders
The pain it solves
Good intentions to “review this weekly” survive about a fortnight. Then the re-score quietly stops and the trend goes stale without anyone noticing.
Set a review rhythm and get a quiet nudge when a re-score is overdue. It is a reminder you asked for — not another notification fighting for your attention — so the cadence holds without depending on your memory.
Review rhythm
Onboarding re-score is due
Last checked 8 days ago
Team dashboard
The pain it solves
Most weeks you genuinely cannot say which of your team’s projects are drifting — so you find out when something is already on fire.
Every project rolls up by latest score, with the failing disciplines called out per owner and an org-wide trend over time. The whole team’s drift sits in one place — so you can see trouble forming without booking another status meeting to dig it out.
Team dashboard
Q3 onboarding
Priya
Billing migration
Marcus
Partner API
Joey
Needs-review inbox
The pain it solves
The things that need a manager’s attention are scattered across projects, people and weeks — so the loudest problem wins, not the most important one.
Five lanes of what actually needs you: cadence drift, drifted control points, stale check-ins, escalations, and mission gaps. The work surfaces itself instead of waiting for you to go hunting — so attention follows importance, not volume.
Needs review
Manager Brief
The pain it solves
1:1 prep is either skipped or a scramble five minutes before — so the conversation drifts to whatever is top of mind, not what actually matters.
Three sentences you can paste straight into 1:1 prep for any direct report: the highlights, what has drifted, and the opener worth leading with. Prep that takes ten seconds and points the conversation at the thing that needs it.
Manager Brief · Marcus
CopyHighlight: closed the data-migration risk early.
Drifted: billing project hasn’t been re-scored in 12 days.
Open with: “What’s blocking the billing re-score?”
Weekly digest
The pain it solves
A dashboard only helps the manager who remembers to open it. Most weeks, nobody does — and the drift compounds in the gap.
The needs-review inbox can land in your inbox once a week, so the signal comes to you. Staying on top of your team’s drift stops depending on remembering to check a screen — it arrives, already sorted, when you have a moment to read it.
Your week in control
Monday · 7:00am
- • 2 projects need a re-score
- • 1 control point slipped its date
- • Joey’s onboarding is trending up
Delegate ownership
The pain it solves
Delegating a task is easy; delegating an outcome is where it falls apart. Hand someone a result and a fortnight later you are not sure if it is on track, drifting or forgotten — so you end up chasing, which defeats the point of delegating at all.
Hand someone an outcome — not just a task — with what good looks like, the constraints, and a check-in rhythm. They can name a deputy or sub-delegate a part beneath them. Ownership delegation is a different thing from handing out tasks: it gives a line manager a real mechanism to keep track of everything they have handed out across the team, instead of holding it all in their head.
Handing over an outcome
- Outcome
- Run the new-market launch
- What good looks like
- 3 pilot clients live by Q4
- Check-in rhythm
- Fortnightly
Delegation map
The pain it solves
Across a team, ownership lives in a dozen heads and as many email threads. You cannot coach what you cannot see — and the responsibilities that go quiet are exactly the ones that bite.
Every responsibility you have handed out, who owns it, and whether it is holding — on one map. It is a coaching aid for 1:1s, with a dedicated lane for ownership that has gone quiet, so a responsibility cannot slip out of view just because no one has mentioned it lately.
Delegation map
Friction Log
The pain it solves
The small recurring annoyances never make it to a review — you are too busy working around them to write them down. So they recur forever, unexamined.
Log a moment of friction in one line, the instant it bites — no forms, no triage, no category to pick. It waits quietly until you are ready to look at it. Capturing the pain is nearly free; that is the whole point, because pain you never recorded is pain you can never fix. Free on every plan.
Friction Log
- MonChased finance for invoice status again.
- WedOnboarding doc out of date — again.
Systemise Review
The pain it solves
Recurring pain feels like it should be fixed “properly” — but without a moment set aside to weigh it up, every annoyance gets the same helpless shrug.
On a cadence you choose, work through everything you logged. Each pain gets a clear verdict — automate it, write it down, or deliberately live with it. It turns a vague pile of irritations into a short list of decisions, so the things worth systemising actually get chosen.
Systemise Review · this week
-
Chased finance for invoice status — 3rd time this month.
Automate -
Onboarding doc out of date again.
Write it down -
Status meeting overran.
Live with it
Software-shaped pain → Scorchsoft
The pain it solves
Sometimes the honest answer is “this needs software” — and then nothing happens, because building it is somebody else’s job and you do not know whose.
When a pain is genuinely software-shaped, the portal points — softly — at Scorchsoft, the team who can build the workflow that removes it. It is routing, not a sales pitch: the diagnosis you already trust simply tells you where the fix lives.
When to bring in Scorchsoft“Chasing finance for invoice status, every month.”
This pain keeps recurring and a tool would remove it.
Could Scorchsoft build this?
A soft pointer — not a sales pitch.
Seen the loop?
Pick where you start.
Try the loop free, or unlock the whole standard on an Individual or Team plan.
Register for free
The Drift Report and Pain Automation Score, Orientation and Chapter 1, and the Friction Log — no card needed. You won't get the other nine courses, tracked projects with history, or the team views until you upgrade.
Create a free accountUnlock the full loop
All ten courses, your certificate and unlimited tracked projects with full history on Individual. Add a shared workspace, manager dashboard, delegation map and weekly digest on Team.
See plans & pricingStill weighing it up? Read the frequently asked questions.