Operating record
The single chain of records a business runs on: customer, opportunity, quote, project, work, invoice, payment — plus the inventory, roles, and reporting that hang off it. In an operating record these are separate records joined by references, not separate systems that get re-keyed into each other.
Why it matters in practice. The test is whether you can answer a question without opening a second system. If "what have we billed this client for the work finished in March" needs a spreadsheet join, the chain is broken somewhere.
Often confused with Relationship record, Quoted, billed, and collected, Payment.
Relationship record
The record for a company or a person: contacts, tags, custom fields, files, and the full activity timeline. It is what you read before you pick up the phone, and it is the record that later documents attach to rather than a copy of.
Why it matters in practice. When ownership changes or someone leaves, the history stays on the record, so a handover becomes reading rather than reconstruction. Duplicates are the failure mode here — the same company arriving as a lead, a company, and a contact with a slightly different name.
Often confused with Lead, Operating record.
Lead
An enquiry you have captured but not yet qualified into a company you deliberately sell to. A lead carries a source, and it can be assigned, worked, and later promoted into a company record that outlives the enquiry.
Why it matters in practice. Leads rot when ownership lives in someone's head. A dated next action on the record is what stops a warm enquiry from quietly dying over somebody's holiday.
Often confused with Opportunity, Relationship record.
Opportunity
A deal in progress: source, owner, sales process, stage, next action, and a lost reason if it fails. The stages are yours rather than the vendor's, and each stage can carry the action required before anything is allowed to move on.
Why it matters in practice. A won opportunity is what a project is created from. When it carries the client and the agreed scope, the delivery team never has to reconstruct the brief from an email thread.
Often confused with Lead, Quote.
Quote
The structured commercial proposal: line items, tax treatment, terms, validity, and a send state. It is a record in the system, not a PDF that happened to be emailed.
Why it matters in practice. A quote is the only place where a price is agreed before it becomes a claim. If quotes are raised in email, the business has no quoted state to report on, and no way to see agreed work that was never invoiced.
Often confused with Invoice, Scope, Quoted-to-billed.
Scope
What was agreed to be delivered, including the deliverables, the exclusions, and the assumptions it rests on. Scope is the boundary of the job — anything that changes it is a change order rather than a quiet addition.
Why it matters in practice. Scope decides what is legitimately billable. When scope lives in a chat thread, a finished project has nothing to invoice against and a billing disagreement becomes a memory contest.
Often confused with Deliverable, Change order, Permission scope.
Deliverable
A specific thing the scope says will exist when the work is done — a document, a build, a report, an agreed quantity of something. A deliverable is named and priced; a task is a step taken to produce it.
Why it matters in practice. Naming deliverables is what lets a project be judged complete. Without them, "done" is a matter of opinion and the invoice date has to be argued rather than read.
Often confused with Scope, Delivery record, Change order.
Delivery record
A record of work performed that is not itself a priced deliverable: a site visit logged, a support hour recorded, an item counted and handed over, a task marked complete. It evidences that the activity happened; the money comes from the scope or the rate that already covers it.
Why it matters in practice. Service businesses bill on time and quantities, so this record is the evidence that the billable work actually took place. When those records do not attach to the client and the project, the invoice has to be re-derived from somebody's memory at month end.
Often confused with Deliverable, Scope, Invoice.
Change order
The record of a change to agreed scope: what is changing, why, what it does to cost and schedule, and who approved it. It is added to the original agreement rather than quietly replacing it.
Why it matters in practice. Without a change order, extra work is absorbed in silence and surfaces months later as a project that billed below what it cost. With one, the conversation is about the price of the change rather than about who gave it away.
Often confused with Scope, Quote, Project profitability.
Project status
The current state of a piece of delivery work — planned, in progress, blocked, delivered, and so on. It is most useful when it is derived from the tasks that are genuinely done rather than from the most optimistic person in the room.
Why it matters in practice. Status is what turns "can we invoice this yet" into a checkable answer. A status nobody maintains stops reflecting reality within weeks, so keeping it current is a habit rather than a feature.
Often confused with Delivery record, Scope, Quoted, billed, and collected.
Quoted, billed, and collected
Four separate facts about the same relationship: what has been quoted, what has been invoiced, what has actually been recorded as received, and what is still owed. Collapsing them into one revenue number is how a profitable-looking month turns out to be unpaid invoices.
Why it matters in practice. The gap between quoted and billed is agreed work nobody invoiced — the most commonly missed loss in the whole chain. The gap between billed and collected is your receivables. Both are invisible once the four states are averaged into a single number.
Often confused with Allocation, Receivables, Cash flow vs profit.