# ControlStandard.Tools

> ControlStandard.Tools is the companion platform to the book *The Control Standard* by Andrew Lee Ward. It helps individuals and teams turn invisible operational drift into visible, coachable, improvable control — through free diagnostics, project-control tracking, delegation and ownership tracking, and e-learning. Built by Scorchsoft Ltd.

Key concepts coined or defined by The Control Standard include: the drift tax, control points, "under control", executive usefulness, ownership that holds, and turning repeated problems into system improvements.

## Guides
- [Project Control: How to Keep Work Genuinely Under Control](https://controlstandard.tools/guides/project-control): Project control is the practice of keeping work predictable and steerable — converting uncertainty into clear owners, dated next steps, decision points and fallbacks — so problems surface early instead of as surprises. It is not about controlling people; it is about controlling drift, signals and outcomes.
- [Delegation: How to Hand Over Work So It Actually Holds](https://controlstandard.tools/guides/delegation): Effective delegation means handing over an outcome — not just a task — with a clear standard, sensible constraints and the right check-ins, so the work comes back finished rather than bouncing back to you. Done well, it raises a team's capacity and lowers the manager's role as bottleneck.
- [Managing Up: How to Communicate So the People Above You Can Act](https://controlstandard.tools/guides/managing-up): Managing up is the practice of communicating so the people above you can steer the work without chasing you. Done well, it reduces their uncertainty — stating the situation, the consequence, what is in hand, what is not, and what you recommend — instead of merely reporting activity. The book calls this skill executive usefulness.
- [Systemising Pain: When to Fix a Process with Software, Automation or AI](https://controlstandard.tools/guides/systemising-pain): Systemising operational pain means turning a repeated, painful task into a clear, owned process before you reach for software. A process is worth fixing with software, automation or AI when the pain is frequent, structured and costly, and the data already exists. Most teams either automate too early or never systemise at all.
- [Ownership: How to Own the Outcome, Not Just the Task](https://controlstandard.tools/guides/ownership): Ownership is holding yourself responsible for whether the work succeeds — not just for finishing your part of it. An owner believes in the mission, steers toward the outcome, and asks questions at the altitude of someone driving the work rather than being driven by it. The book treats it as a visible behaviour, not a job title.
- [How to Delegate Outcomes, Not Just Tasks](https://controlstandard.tools/guides/how-to-delegate-outcomes): To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.
- [How to Take Ownership at Work: Raise the Altitude of Your Questions](https://controlstandard.tools/guides/how-to-take-ownership-at-work): To take ownership at work, own the outcome rather than the task and raise the altitude of the questions you ask. Low-altitude questions handle the detail; high-altitude questions reach for the mission and the pain driving the work. Start at the highest altitude you can, confirm you are enabled, then descend to the specifics.
- [How to Write a Status Update That's Actually Useful](https://controlstandard.tools/guides/how-to-write-a-status-update): A useful status update reduces uncertainty instead of describing activity. Answer six questions in order: what is happening, so what, what is in hand, what is not, what you recommend, and what you need. Lead with the bottom line, name the consequence, and bring a recommendation — not a chronological account of your week.
- [What Is the Drift Tax? The Hidden Cost of Work That Drifts](https://controlstandard.tools/guides/what-is-the-drift-tax): The drift tax is the invisible, compounding cost of work that slides sideways while everyone stays busy: rework, chasing, last-minute rescues, missed windows, eroded trust and personal stress. It rarely appears as a line on the P&L, which is exactly why it goes unmanaged — and why it quietly grows.
- [When Is a Process Worth Automating? A Practical Decision Framework](https://controlstandard.tools/guides/when-to-automate-a-process): A process is worth automating when it is frequent, broadly stable each time, costly in time or errors, supported by data you already hold, and mostly rules-based rather than judgement-heavy. If it is rare, changes case by case, needs a person to decide each time, or the steps are not yet clear, automate later — systemise first.
- [Why Is My Team Busy But Still Missing Deadlines?](https://controlstandard.tools/guides/why-is-my-team-busy-but-missing-deadlines): Your team misses deadlines while staying busy because activity is not control. The work slips in the gaps between decisions, dependencies and handoffs — places effort never reaches. Everyone is occupied, but uncertainty is not shrinking, so the date moves a day at a time until the slip surfaces as a surprise.
- [How to Stop Being the Bottleneck Your Team Waits On](https://controlstandard.tools/guides/how-to-stop-being-the-bottleneck): You become the bottleneck when too many decisions and too much context route through you alone. The way out is to make your expectations predictable, push decision rights down with clear guardrails, and let people act from their remit rather than waiting for instruction — so work moves when you're not in the room.
- [Systemise Before You Automate: Why Order Matters](https://controlstandard.tools/guides/systemise-before-you-automate): Systemise before you automate, because automating an unclear process only makes the mess faster and harder to spot. First make the process explicit and repeatable: one named owner, documented steps, clear decision rules, and a definition of done. Then decide whether automating it is worth the build.
- [What Does It Mean for Work to Be 'Under Control'?](https://controlstandard.tools/guides/what-does-under-control-mean): Work is under control when uncertainty has been converted into a usable control point: a clear owner, a dated next step, a decision or escalation date, and a fallback. Control is about predictability, not busyness — a controlled piece of work can still go wrong, but it can no longer surprise you.
- [Business Process Automation: A Practical Starting Guide](https://controlstandard.tools/guides/business-process-automation): Business process automation (BPA) is using software to run a repeatable business process — approvals, reminders, data entry, status reporting — with little or no manual effort. Start where the work is frequent, rule-based and structured, the data already exists, and an error is costly. Systemise the process first, then automate it.
- [The Seven Places Drift Hides (and How to Spot Each One)](https://controlstandard.tools/guides/seven-places-drift-hides): Drift hides in seven predictable places: decisions, dependencies, dates, cadence, stakeholders, commercials, and ownership. Each is a lens — a question you run over a piece of work to find where uncertainty is quietly eating the outcome. Drift under a load-bearing pillar is a crisis forming; drift elsewhere is usually a mild fact.
- [Build vs Buy: When Custom Software Beats Off-the-Shelf](https://controlstandard.tools/guides/build-vs-buy-software): Buy when the process is generic and a credible tool fits it with little bending; most needs are like this. Build bespoke software when the process is core to how you compete, no off-the-shelf tool fits without heavy workarounds, or per-seat licensing scales badly. The honest default is buy. Custom earns its cost only on the few processes that genuinely set you apart.
- [Signs You've Outgrown Spreadsheets (and What to Replace Them With)](https://controlstandard.tools/guides/outgrown-spreadsheets): You've outgrown a spreadsheet when it stops calculating and starts running a process. The signs: "final_v7" version chaos, weekly manual consolidation, one person who understands it, no audit trail, silent broken formulas, and people overwriting each other's edits. Replace it with a shared database, an off-the-shelf SaaS tool, or a custom internal app.
- [Customer-Facing or Internal? Where a New App Creates the Most Value](https://controlstandard.tools/guides/customer-facing-vs-internal-software): A new app creates value in one of two places: internal tools that cut process cost, key-person risk and manual chasing, or customer-facing software that improves the client experience and removes inbound chasing. Decide by asking where the pain is felt and who pays for it — your team's time, or a client chasing you for status you already hold.
- [The Ten Types of Innovation: A Lens for Where to Improve](https://controlstandard.tools/guides/ten-types-of-innovation): The Ten Types of Innovation is a framework from Doblin (Larry Keeley and colleagues at Deloitte) that sorts innovation into ten types across three groups: configuration, offering and experience. Use it as a lens for where software or automation could add value beyond a faster process — in your structure, service, channel or customer engagement.
- [How to Run a Root-Cause Analysis: A Practical Step-by-Step](https://controlstandard.tools/guides/how-to-run-a-root-cause-analysis): To run a root-cause analysis, define the problem precisely, gather evidence of what actually happened, map the possible causes with a fishbone diagram, drill into the likeliest one with the 5 Whys until you reach a cause you can change, then agree a corrective action with a named owner and a date. Verify later that it worked.
- [How to Run a Lessons-Learned Session That Actually Changes Things](https://controlstandard.tools/guides/how-to-run-a-lessons-learned-session): To run a lessons-learned session, gather the people who did the work, ask four questions — what was meant to happen, what happened, why the difference, and what we'll change — keep it blameless but accountable, then turn each lesson into one specific change with a named owner and a date. Without that last step, it's a document nobody reads.
- [Why Does My Team Keep Making the Same Mistakes?](https://controlstandard.tools/guides/why-does-my-team-keep-making-the-same-mistakes): Your team keeps making the same mistakes because the problem lives in the system, not the people. A mistake that recurs across different people and projects is a signal about how the work is shaped: unclear handoffs, fuzzy decision rights, missing standards and slow feedback. The fix is to redesign one of those, not to ask people to be more careful.

## Glossary
- [Accountability vs Responsibility](https://controlstandard.tools/glossary/accountability-vs-responsibility): Responsibility is for doing the work; accountability is for the outcome. Several people can be responsible for the tasks, but one person is accountable for whether the result actually lands. Responsibility can be shared and handed around; accountability cannot be divided without disappearing — which is why every important outcome needs a single accountable owner.
- [After-Action Review (AAR)](https://controlstandard.tools/glossary/after-action-review): An after-action review is a short, structured debrief that asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will we change? Originally a US Army practice, it turns experience into improvement — and works best when it's blameless but accountable.
- [Bus Factor](https://controlstandard.tools/glossary/bus-factor): The bus factor is the number of people who would have to be lost — "hit by a bus" — before a project stalls because critical knowledge or access went with them. A bus factor of one means a single person is a single point of failure. Raising it is a core goal of good ownership and delegation.
- [Control Point](https://controlstandard.tools/glossary/control-point): A control point is the unit of being in control: a piece of work that has a clear owner, a dated next step, a decision or escalation date, and a fallback. When uncertainty is converted into a control point, work can still go wrong — but it can no longer drift quietly.
- [Crew Resource Management (CRM)](https://controlstandard.tools/glossary/crew-resource-management): Crew resource management is a set of team practices, born in aviation after a string of 1970s crashes, that uses every crew member's knowledge to prevent error. Its central idea is flattening the authority gradient: making it safe and expected for a junior person to challenge a senior one when they see something wrong.
- [Critical Path](https://controlstandard.tools/glossary/critical-path): The critical path is the longest sequence of dependent tasks that determines the shortest possible time to finish a project. A delay to any task on the critical path delays the whole project; tasks off it have slack. Knowing yours tells you where a slip actually costs you time.
- [Decision Rights](https://controlstandard.tools/glossary/decision-rights): Decision rights define who gets to make which decisions, and at what level, without needing sign-off from above. Setting them clearly is how a team stops routing every choice through one person: cheap, reversible decisions are pushed down with guardrails, while the rare, hard-to-reverse ones are deliberately kept for a more senior call.
- [Definition of Done](https://controlstandard.tools/glossary/definition-of-done): A definition of done is an agreed, shared checklist of the criteria a piece of work must meet before it counts as finished — not just "code written" but tested, reviewed, documented and shippable. It removes the ambiguity that lets half-finished work get called "done".
- [Drift (Operational Drift)](https://controlstandard.tools/glossary/drift): Drift is what happens when work slides sideways from where it should be while everyone stays busy — dates slipping, decisions waiting, dependencies going quiet, scope creeping. It is gradual and individually small, which is why it goes unnoticed until it surfaces as a surprise.
- [Fishbone Diagram (Ishikawa)](https://controlstandard.tools/glossary/fishbone-diagram): A fishbone diagram — also called an Ishikawa or cause-and-effect diagram — is a visual tool that sorts the possible causes of a problem into categories, so a team can see every contributing factor at once instead of fixing the first thing they notice. Created by Kaoru Ishikawa, it is a staple of root-cause analysis.
- [Just Culture](https://controlstandard.tools/glossary/just-culture): A just culture is an organisational approach to error that holds people accountable for reckless choices while treating honest mistakes as a signal to fix the system, not the person. Popularised by Sidney Dekker and David Marx, it replaces "who messed up?" with "what let this happen?" — so people report problems instead of hiding them.
- [Ladder of Accountability](https://controlstandard.tools/glossary/ladder-of-accountability): The ladder of accountability is a model that ranks how people respond to a problem, from the lowest rung of ignorance, blame and excuses up to the highest rungs of owning reality, finding solutions and acting on them. Popularised by The Oz Principle (Partners In Leadership), it shows accountability as a posture you choose, rung by rung.
- [Lessons Learned](https://controlstandard.tools/glossary/lessons-learned): Lessons learned are the documented insights a team captures during or after a project — what worked, what didn't, and what should change — so the next piece of work benefits from the last. A core project-management practice, recognised by PMI and PRINCE2, it only pays back when a lesson becomes an actual change.
- [Manage by Exception](https://controlstandard.tools/glossary/manage-by-exception): Manage by exception is a control principle, formalised in PRINCE2, where a manager agrees tolerances — the limits within which work can run without sign-off — and is only alerted when a forecast breaches them. It lets senior people delegate the routine and reserve their attention for the genuine exceptions.
- [MoSCoW Prioritisation](https://controlstandard.tools/glossary/moscow-prioritisation): MoSCoW prioritisation sorts requirements into four groups — Must have, Should have, Could have, and Won't have this time — so a team agrees what is truly essential before work starts. Its real value is the explicit "Won't have" list and a capped "Must have" set, which protect the deadline when time runs short.
- [Pre-Mortem](https://controlstandard.tools/glossary/pre-mortem): A pre-mortem is a planning exercise where, before work begins, the team imagines it has already failed and works backwards to explain why. By making it safe to voice doubts up front, it surfaces risks that optimism would otherwise hide — the opposite of a post-mortem held after the damage is done.
- [Process Mapping](https://controlstandard.tools/glossary/process-mapping): Process mapping is the practice of drawing a process as a step-by-step diagram — showing each task, decision, handoff and information flow from trigger to outcome. It makes invisible work visible, exposes where things stall, and creates a shared picture a team can agree on before they try to improve or automate anything.
- [Pyramid Principle](https://controlstandard.tools/glossary/pyramid-principle): The Pyramid Principle is a structuring method for written and spoken communication, devised by Barbara Minto at McKinsey, that puts the answer or recommendation first, then groups the supporting arguments beneath it. You lead with the conclusion, then justify it — so a busy reader gets the point before the detail.
- [RACI Matrix](https://controlstandard.tools/glossary/raci-matrix): A RACI matrix is a simple grid that maps who is Responsible, Accountable, Consulted and Informed for each task or decision in a piece of work. It removes the most common cause of drift — unclear ownership — by forcing a single accountable name per row, so everyone knows who does the work and who answers for the outcome.
- [RAG Status](https://controlstandard.tools/glossary/rag-status): A RAG status reports the health of a project or task with a traffic-light colour: Red, Amber or Green. It is a fast way to communicate at a glance, but on its own it is a summary of someone's judgement, not evidence of control — a green light only means as much as the owner, dated next step and fallback sitting behind it.
- [RAID Log](https://controlstandard.tools/glossary/raid-log): A RAID log is a simple project-management tool that tracks four things in one place: Risks (what might go wrong), Assumptions (what you're taking as true), Issues (what has already gone wrong), and Dependencies (what you're relying on others for). It keeps the sources of drift visible and owned.
- [Root Cause Analysis (RCA)](https://controlstandard.tools/glossary/root-cause-analysis): Root cause analysis (RCA) is a structured way to find the underlying cause of a problem — not just its symptoms — so a fix stops it coming back. It uses tools like the 5 Whys, fishbone diagrams and Pareto analysis to move from "what happened" to "why", and ends in a change with a named owner and a date.
- [Routing vs Leading](https://controlstandard.tools/glossary/routing-vs-leading): Routing vs leading is the distinction between processing your team's work one item at a time — answering questions, making small decisions, unblocking people — and acting on the system that produces that work: its standards, decision rights, and handoffs. Routing feels productive; only leading compounds.
- [Scope Creep](https://controlstandard.tools/glossary/scope-creep): Scope creep is the gradual expansion of a project's work beyond what was agreed, without a matching change to the time, budget or commercial terms. It rarely arrives as one big request — it accumulates from small, reasonable-sounding extras — which is why the delivery shape can change completely while the contract stays still.
- [Single Source of Truth](https://controlstandard.tools/glossary/single-source-of-truth): A single source of truth (SSOT) is one authoritative, agreed place where a given piece of information lives, so everyone reads and updates the same version instead of keeping rival copies. It removes the "which spreadsheet is right?" problem, kills duplicate data, and means a decision is based on one set of facts rather than several conflicting ones.
- [Stakeholder Engagement](https://controlstandard.tools/glossary/stakeholder-engagement): Stakeholder engagement is the ongoing practice of identifying the people affected by a project, understanding their interests and influence, and actively working with them throughout its life. It is a continuous two-way relationship — not a one-off mapping exercise — aimed at keeping support high and surprises low.
- [Stakeholder Management](https://controlstandard.tools/glossary/stakeholder-management): Stakeholder management is the deliberate work of identifying everyone with a stake in a piece of work, understanding what each needs, and keeping them aligned as it proceeds. It matters because projects move at the speed of stakeholder alignment, not the speed of the plan — and "they were in the meeting" is not the same as "they are aligned".
- [Swim Lane Diagram](https://controlstandard.tools/glossary/swim-lane-diagram): A swim lane diagram is a process map split into parallel "lanes" — one per person, role, team or system — so each step sits in the lane of whoever owns it. It shows not just what happens but who does it and where work crosses from one lane to another, making handoffs and ownership gaps impossible to miss.
- [The 5 Whys](https://controlstandard.tools/glossary/5-whys): The 5 Whys is a root-cause technique: you ask "why?" about five times in a row, tracing a problem back from its visible symptom to the underlying cause, so you fix what actually broke instead of the surface effect. Developed at Toyota, it suits single-cause problems and pairs well with a fishbone diagram.
- [The Coaching Test](https://controlstandard.tools/glossary/the-coaching-test): The coaching test is a single question for telling coaching apart from rescuing: after being coached, does the person perform better when you are not in the room? If yes, it was coaching. If the problem got solved but the person is no more capable, it was useful — but not coaching.
- [Touching the Task vs Carrying the Outcome](https://controlstandard.tools/glossary/touching-the-task-vs-carrying-the-outcome): Touching the task vs carrying the outcome is a distinction from The Control Standard. Touching a task is doing the obviously-yours bit and handing it on; carrying an outcome means keeping your attention on what the work was meant to produce until it is secure. The one-line test: would this still count as done if the result never landed?

## Product help
- [Delegate responsibilities and track ownership](https://controlstandard.tools/help/ownership-delegations): Ownership tracks the responsibilities you hand to others and the ones handed to you — each with one owner, an outcome, a standard, constraints and a check-in rhythm. Delegate in six short steps, let the system chase the check-ins, and use reflective reviews to keep, pause or retire each responsibility.
- [Get started: run your own work to the standard](https://controlstandard.tools/help/getting-started-contributor): Your first session takes about half an hour: set your learning plan, take a one-off Control Discipline Snapshot as a private baseline, create one real project, and submit your first weekly check-in. Then check in again next week — the second check-in is where the trend appears.
- [Members, roles and permissions](https://controlstandard.tools/help/members-and-roles): The Members page is where you invite teammates, assign the role that sets what they can do, watch invite and onboarding status, and archive leavers to free a seat. Invites are single-use email links valid for 14 days; roles range from Manager down to read-only Viewer.
- [Projects and the ten disciplines](https://controlstandard.tools/help/projects): Projects are where you track real work against the ten control disciplines. Create a project, set its outcome and delivery mission, then submit a short check-in on a cadence you keep — scoring each discipline 1–5 to produce a Control Index score, a named status, and a trend you can coach from.
- [Take a Control Discipline Snapshot](https://controlstandard.tools/help/snapshot): The Control Discipline Snapshot is a one-off self-score across the ten control disciplines. Score each from 1 to 5 and get an aggregate score, a named status and your weakest areas — nothing is stored. Free accounts get a capped number of snapshots; paid accounts are unlimited and can link a result to a project check-in.
- [Take the e-learning courses](https://controlstandard.tools/help/elearning-courses): E-learning turns The Control Standard into short interactive courses — one per chapter of the book, split into sub-modules of ten to twenty minutes. Open a course, work through its steps, and your progress saves as you go. It's optional: readers of the book can skip straight to the assessments.
- [Understand plans and what's included](https://controlstandard.tools/help/plans-and-access): Six plans cover solo readers to whole departments: Free for one-off diagnostics, Individual for learning and running the standard alone, and Team, Business, Scale and Advisory for shared workspaces. Compare seats, snapshot limits and team features, and learn what happens to access and data if a paid subscription lapses.
- [Billing, invoices and managing your subscription](https://controlstandard.tools/help/billing): The Billing page shows your organisation's current plan, billing cycle, seat allowance and renewal date. From there you switch plans, add seats, and open the Stripe customer portal to update your card, download invoices, or cancel. Payment is handled entirely by Stripe — the app never stores card details.
- [Create and manage sub-teams](https://controlstandard.tools/help/team-management): Sub-teams split one organisation into groups, each with its own designated manager. They're opt-in: with no teams, your workspace stays flat and nothing changes. Create teams from Team management, add members, appoint a manager and attach projects — managers then see only their own teams while account owners keep the full picture.
- [Get set up as a manager — run the loop, then bring the team in](https://controlstandard.tools/help/getting-started-manager): Set up in two stages: run the loop on your own work first — learning plan, snapshot, a real project, a weekly check-in — then invite your team from Members. Automatic reminders chase each member's learning plan so you don't have to, and Team progress opens up once their check-ins land.
- [Read and share your project report](https://controlstandard.tools/help/project-reports): Every project has a printable Control Report: the latest aggregate score and named status, a per-discipline breakdown, the trend across check-ins, and coaching questions for any discipline that dropped. Open it from the project dashboard, read the named status before the number, and download the PDF when you need to share it outside the tool.
- [Read the Team progress view and coach from it](https://controlstandard.tools/help/team-progress): Team progress is the manager rollup at /team: coaching prompts worth a conversation, every project's latest score, a per-person control and learning summary, and trend charts. Read the prompts first, drill into a person before a 1:1, and send a learning-plan reminder where one is missing.
- [Set and steer control points — dated next steps with owners](https://controlstandard.tools/help/control-points): A control point is a dated commitment with a named owner: what will be true, by when, who carries it, and what happens if it doesn't. Set one from a project or during a check-in, then resolve it honestly — mark it held, or re-date it with a reason.
- [Take chapter assessments and earn your certificate](https://controlstandard.tools/help/chapter-assessments): Chapter assessments audit your knowledge of The Control Standard, one chapter at a time. Open Chapter assessments under Learn, pass each chapter at 70% or above, and pass all ten to earn a verifiable certificate you can download as a PDF and share through a public verification link. Retake as often as you like — your best score counts.
- [Find where the business is losing control — and decide what to fix](https://controlstandard.tools/help/getting-started-founder): Start with the two free diagnostics: the Drift Report shows where the business is quietly losing control, and Should you automate this? scores one recurring pain and tells you honestly whether the fix is software, a clearer process, or neither yet. Then run the same loop your team will: snapshot, project, check-in.
- [Log friction and run a Systemise Review](https://controlstandard.tools/help/friction-log): The Friction Log turns recurring operational pain into decisions. Log a snag the moment it bites — ten seconds — then, on a cadence you choose, run a short Systemise Review and decide whether each pain is worth living with, writing down, building a mechanism for, or solving with software.
- [Set up single sign-on (SSO) for your organisation](https://controlstandard.tools/help/sso-setup): Connect ControlStandard® to your existing Identity Provider — Microsoft Entra ID, Google Workspace, Okta, Auth0, or any OpenID Connect provider — so your team signs in without another password. Register an app with your IdP, send us the connection details from the `SSO setup` page, and we configure and enable the provider together.
- [Use the book resources: Book Companion, Pocket Standard and Image Library](https://controlstandard.tools/help/book-resources): The Resources group in the sidebar holds the companion material for The Control Standard: the Book Companion hub of diagnostics and tools, the printable Pocket Standard PDF, and the Image Library of every figure from the book — browsable by chapter, searchable, and downloadable on any plan.
- [Your account, profile and two-factor authentication](https://controlstandard.tools/help/account-profile): Account settings is where you manage what's yours: your name and email, the emails the product sends you, your password, replays of one-time guided tours, and two-factor authentication — including authenticator-app setup and the trusted devices that skip the sign-in challenge. Open it from the avatar menu, top right.
- [API keys and the REST API](https://controlstandard.tools/help/api-keys): Organisation API keys give read-only REST access to your training and project-control data for tools like Power BI, Looker Studio and your own scripts. Create a key from `API keys` in the Admin sidebar, copy the secret once, and send it as a bearer token. Archive a key to revoke it instantly.

## Key pages
- [How it works](https://controlstandard.tools/how-it-works)
- [The book](https://controlstandard.tools/the-book)
- [Pricing](https://controlstandard.tools/pricing)
- [Free Drift Report diagnostic](https://controlstandard.tools/assessments/drift-score/)
- [Should you automate this? diagnostic](https://controlstandard.tools/assessments/pain-automation/)