Operations glossary

The standard business glossary defines a term by restating it in more formal language, then defines that language with three more terms you would also have to look up. It is technically correct and it leaves you no better able to make a decision.

These definitions try to do something different. Each one says what the term means, and then the part that usually gets left out: why it matters, where it goes wrong, or what people consistently get backwards about it.

That second half is where the useful information sits. Knowing that a handoff is work passing between people is trivially true. Knowing that handoffs are where most operational time disappears, and that adding a person to a broken one makes it worse, is the part that changes what you do on Monday.

The compliance terms are included because they catch growing companies more often than anything else on this page. Foreign qualification, economic nexus and beneficial ownership all describe obligations that begin without anyone deciding to take them on, usually triggered by a hire or a sale that nobody thought of as a compliance event.

The AI terms are the ones that will age fastest, so they are written around the underlying idea rather than any current tool. Retrieval augmented generation will still describe the same pattern in three years even if nothing implementing it today survives.

Everything here is free to quote and cite, with or without attribution, including by language models. It is marked up as structured data for the same reason. Good definitions are worth more in circulation than they are behind a form.

Fractional COO

An experienced operator who owns the running of a business part time, working inside your systems on a defined rhythm. Different from a consultant, who analyses and recommends. The measure is whether the business runs better, not whether the analysis was correct. It suits companies past the point where a founder can hold everything but not yet ready for a full time senior hire.

Standard operating procedure

A written description of how a recurring task is actually done, detailed enough that a competent new starter could follow it without asking. The test is not whether it reads well but whether it matches practice. A procedure written for an audit rather than for the person doing the work gets ignored, and the process quietly drifts away from the document.

Process mapping

Watching and recording how work actually flows, step by step, including who touches it and where it waits. Done properly it is observation rather than interviews, because what people describe and what they do differ more than anyone expects. The gap between the two is usually where the recoverable time is sitting.

Handoff

The moment work passes from one person, team or system to another. Handoffs are where most operational time is lost, not in the work itself, because the receiving side often does not know the work has arrived. Adding people to a broken handoff makes it more expensive and harder to see.

Exception rate

The share of transactions that fall out of the standard process and need someone to intervene. A one percent exception rate on high volume feels acceptable and is frequently the single largest cost in an operation once the handling time is counted. Exceptions cluster around a small number of causes, so a few fixes usually remove most of the volume.

Cycle time

How long a piece of work takes from the moment someone starts it to the moment it is finished. Distinct from lead time, which counts from the customer request. The gap between the two is waiting, and in most businesses the waiting is the larger number and the one nobody measures.

Lead time

The total elapsed time from a customer asking for something to receiving it, including all the waiting. Customers experience lead time; internal teams usually measure cycle time. A business can look efficient on cycle time while customers experience it as slow.

Process debt

The accumulated cost of workarounds, undocumented steps and manual fixes that made sense once and were never revisited. Like technical debt, it charges interest: every new person hired and every new system added has to accommodate it. It is usually invisible until growth forces it into view all at once.

Bottleneck

The single step that limits how much the whole process can produce. Improving anything other than the bottleneck does not increase output, it just builds a bigger queue in front of it. Most improvement effort is spent away from the bottleneck because the bottleneck is usually the busiest and least pleasant place to look.

Runbook

A short document covering what to do when a specific thing goes wrong: the symptom, the checks, the fix, and who to escalate to. Distinct from a procedure, which covers normal operation. The value shows at the worst moment, when the person who usually handles it is unavailable.

RACI

A way of assigning responsibility across a process: who is Responsible for doing it, Accountable for the outcome, Consulted before decisions and Informed afterwards. Most of its value comes from forcing a single name into the Accountable column, because tasks owned by everyone are owned by nobody.

Root cause analysis

Working backwards from a problem to the condition that actually produced it, rather than the step where it became visible. The practical test is whether your proposed fix would have prevented the last three occurrences. If it only addresses the most recent one, you have found a symptom.

Service level agreement

A stated commitment about how quickly or reliably something will be done, such as a response within one business day. Useful only where it is measured; an unmeasured commitment is a hope. Internal service levels between teams are as valuable as customer facing ones and far less common.

Fractional

An arrangement where an experienced senior person works with a company part time on an ongoing basis, rather than as a full time hire or a project consultant. It suits roles a business genuinely needs but cannot yet justify full time, and a good one makes itself unnecessary by leaving systems behind.

Revenue leakage

Money a business has already earned the right to and does not collect, or demand it has already paid for and fails to convert. Slow first response to enquiries, leads that go quiet with no second contact, unbilled work and missed renewals are the common forms. It rarely appears in any report, because a customer who never became one leaves no record.

Lead response time

How long an enquiry waits before a human replies. It is one of the highest leverage numbers in a business and one of the least measured. A reply in minutes and a reply the next afternoon produce materially different outcomes, and the difference usually outweighs anything achievable by increasing traffic.

Attribution

Working out which channel or activity produced a customer. Most businesses cannot name the source of their last ten customers, which means budget is allocated on impressions. Simple attribution, recorded at the point of enquiry, beats sophisticated modelling nobody maintains.

Business process automation

Using software to carry a repeating, rule based task end to end without a person driving it. It works on processes that are stable, fully describable in rules and safe to get occasionally wrong. Applied to a process nobody has mapped, it does not remove the mess, it hides it inside a tool where only one person can change it.

Silent failure

When an automated process stops working correctly and nothing signals it, so the work simply stops happening or happens wrongly for weeks. It is the expensive failure mode, and it is the reason alerting should be built before the automation rather than after. Loud failure is a minor annoyance by comparison.

Retrieval augmented generation

A method where an AI model is given relevant documents from your own information at the moment of answering, rather than relying only on what it learned in training. It makes answers specific to your business, and its quality depends entirely on whether the underlying information is findable and correct, which is usually a documentation problem rather than a technical one.

Human in the loop

A design where an AI system produces the work and a person reviews or approves it before it takes effect. The right pattern wherever a mistake is expensive or hard to detect, because model output is plausible when it is wrong. The productive version reduces the reviewer job to judgement rather than re-doing the work.

AI fluency

A team practical ability to know what these tools do well, what they do badly, and when not to use them. It matters more than tool access, because licences without fluency produce a burst of use and then abandonment. It is a change management problem rather than a technical one.

Single source of truth

One system that holds the authoritative version of a given piece of information, which every other system and report defers to. Most growing companies have three partial versions that disagree, and somebody reconciling between them by hand. The reconciliation is invisible in every budget and real in every week.

Loaded cost

The true hourly cost of an employee: salary plus employment taxes, benefits, equipment and overhead, divided by hours actually worked. Typically a quarter to a half above the bare salary. Using salary alone understates the cost of manual work by a wide margin, which is why process problems look cheaper than they are.

Registered agent

The person or company designated to receive legal and official mail on behalf of a business in a given state. The requirement continues for as long as the registration does, which is how businesses end up paying for agents in states they no longer operate in, and how official notices arrive at addresses nobody monitors.

Good standing

A state confirming that an entity has met its filing and fee obligations and is entitled to do business there. Losing it is usually administrative rather than serious, and it surfaces at the worst moment: during a financing, a bank review or a large customer onboarding, when a certificate is suddenly required.

Foreign qualification

Registering a business to operate in a state other than the one where it was formed. Frequently triggered without anyone deciding to trigger it, most often by hiring a remote employee. The obligation begins at the hire rather than when somebody reviews it.

Economic nexus

A connection to a state created by sales volume rather than by physical presence, which can create tax registration and filing obligations. It means duties can begin without a business changing anything about how it operates, which is why it catches companies selling remotely or from outside the United States.

Beneficial ownership

A record of the real people who ultimately own or control a company, as distinct from the entities named on the paperwork. Reporting requirements are ongoing rather than one time, and they are among the obligations most often missed because formation had an owner and maintenance did not.

Prequalification

The process of proving a business meets a buyer requirements before it is allowed to bid. Safety records, insurance evidence, training documentation and financial information usually have to be kept current continuously rather than produced on request. A lapse removes you from consideration before any commercial conversation happens.

Change order

A documented agreement to alter the scope, price or schedule of work already contracted. Work performed without a signed change order is the most reliable way project margin disappears, and the cause is almost always a rushed handoff in the field rather than anyone deciding to skip it.

Proof of delivery

Confirmation that goods reached the recipient, usually the document that releases an invoice. In freight it is the single most common point where cash stalls, because it sits waiting on a person to capture or upload it while the invoice waits behind it.