Quick reference definitions for the terms that come up constantly in agency scope conversations.
A
The specific, agreed conditions a deliverable must meet before a client can formally sign off on it as complete.
An optional service offered alongside a core engagement, priced and scoped separately from the main contract or retainer.
A supplementary document attached to an existing contract that adds new terms or provisions without altering the original ones.
An approach to controlling project scope through short, iterative work cycles (sprints) with scope re-prioritized at the start of each cycle, rather than fixed entirely upfront.
A formal, signed change to one or more specific clauses in an existing contract, replacing or modifying the original language.
A section of a scope document listing the conditions a project's timeline and pricing rely on — such as timely client feedback or access to third-party systems — and what happens if they aren't met.
B
C
The defined, repeatable procedure an organization follows to evaluate, approve, price, and document any proposed change to project scope.
A formal request to add, remove, or modify project scope, usually with an associated price and timeline adjustment.
The specific sequence of steps — request, estimate, client approval, execution — a change order moves through from being flagged to being billable.
A standardized template used to document a proposed scope change, including what's being added, its cost, and its impact on the timeline, before it's approved.
A client's formal, documented approval of a deliverable, milestone, or change order — typically required before an agency proceeds to the next phase or invoices for the work.
A contract provision — sometimes a standalone non-disclosure agreement — restricting how each party may use or share the other's confidential information.
A signed modification to an executed contract's terms — see Amendment for the general definition; this term specifically refers to amendments made to the core master service agreement rather than a project-level SOW.
Selling a client an additional, different service beyond what they currently buy — as distinct from upselling, which expands the current service.
D
A timeline within a statement of work specifying what will be delivered and by what date, often broken into phases or milestones.
To formally remove a deliverable or requirement from a project's agreed scope, typically to control cost or timeline, with a corresponding adjustment to price or schedule.
The initial stage of an engagement, before scope is finalized, where an agency gathers information about a client's needs, constraints, and existing systems.
A contract provision specifying how disagreements between the parties — including scope or payment disputes — will be resolved, such as through mediation, arbitration, or litigation, and in what jurisdiction.
E
The actual average hourly rate an agency realizes on a project or client, calculated as total revenue divided by total hours worked — which can differ significantly from the quoted or standard rate.
A shorter-form document, often used instead of a full master service agreement, that outlines the basic terms of an engagement — scope, fees, and duration — typically for smaller or shorter projects.
A section of a statement of work explicitly listing what is not included in the engagement, used to prevent ambiguity about the project's boundaries.
F
The gradual, incremental addition of features to a product or deliverable beyond its original specification, often driven by stakeholders wanting "just one more thing."
A pricing structure where the client pays a single, predetermined total price for a defined scope of work, regardless of the actual hours the agency spends delivering it.
A contract provision excusing one or both parties from performance obligations when extraordinary events outside their control — natural disasters, war, government action — make performance impossible.
G
Adding extra features, polish, or effort to a deliverable beyond what the client asked for or is paying for — often initiated by the agency's own team, not the client.
A contract provision specifying which jurisdiction's laws apply to interpreting and enforcing the agreement, regardless of where either party is located.
The percentage of project or client revenue remaining after subtracting the direct cost of delivering the work (primarily staff time), before overhead and other business expenses.
I
A contract provision where one party agrees to compensate the other for losses or damages arising from specific risks, such as IP infringement or breach of the agreement.
A contract provision specifying when and how ownership of work product (designs, code, copy) transfers from the agency to the client — commonly upon final payment rather than upon delivery.
A disagreement between an agency and a client over whether a billed amount is owed, often triggered by disagreement over whether specific work was in scope.
K
A contract provision entitling the agency to a specified payment if the client terminates the engagement or cancels a project after work has begun but before completion.
Two related but distinct contract terms: a kill fee typically compensates for work-in-progress and lost opportunity cost when a project is stopped mid-engagement, while a cancellation fee more narrowly reimburses specific committed costs (like non-refundable third-party spend).
L
A contract provision specifying the consequences of a client paying after the agreed due date, such as interest charges, late fees, or suspension of work.
A retrospective record, compiled at project close, capturing what went well, what didn't, and what should change on future engagements — including scope-related issues.
A contract provision limiting the maximum amount one party can be required to pay the other in damages, often capped at the total fees paid under the contract.
M
The overarching legal contract between an agency and a client that governs the general terms of the relationship — payment terms, liability, IP, confidentiality — under which individual statements of work are executed.
A payment structure where the client pays a portion of the total project fee upon completion and approval of specific, predefined milestones, rather than one lump sum or hourly billing.
N
The percentage of revenue remaining as profit after subtracting all costs — delivery labor, overhead, tools, salaries not tied to specific projects — the bottom-line profitability figure, as distinct from gross margin.
A contract provision, common in time-and-materials engagements, setting a cost ceiling the client will not be billed beyond without prior written approval, even if actual hours worked exceed the estimate.
O
A contract provision specifying which third-party costs (software licenses, stock assets, ad spend, travel) are billable to the client separately from the agency's own fees, and how they're reimbursed.
Any client ask that falls outside the deliverables, limits, or timeline defined in the current contract or SOW.
P
A contract provision specifying when and how the client must pay — due dates (e.g., Net 30), accepted payment methods, currency, and any deposit or upfront payment requirements.
A structured review conducted after a project ends, examining what happened — including budget, scope, and timeline performance — to identify patterns and improve future engagements.
A short document authorizing a project and outlining its objectives, high-level scope, stakeholders, and success criteria — typically created at the very start of an engagement, before the detailed SOW.
A formal document marking a project's completion, summarizing final deliverables, budget performance against the original estimate, and any outstanding items.
The overall discipline of defining, documenting, controlling, and validating what is and isn't included in a project — encompassing scope statements, change control, and scope verification throughout the engagement.
The client's final, formal approval that an entire project is complete and matches what was agreed — the project-level counterpart to sign-off on individual deliverables or milestones.
The overall gap between a project's planned scope, timeline, and budget versus what actually happened — a broader measure than budget variance alone, since it also captures timeline and deliverable-count deviation.
A proposal is a non-binding pitch outlining a suggested approach, timeline, and price to win the work; a contract (or signed SOW) is the legally binding agreement both parties are actually bound by once signed.
R
The percentage of an agency's standard billing rate it actually collects, calculated as revenue collected divided by (hours worked × standard rate) — a measure of how much value is being captured versus given away.
The gradual expansion of a project's functional or technical requirements over time, typically driven by evolving stakeholder needs rather than a single deliberate scope change — closely related to scope creep and feature creep.
The process of collecting and documenting a client's needs, constraints, and expectations for a project, typically conducted during discovery, before scope is finalized and priced.
A contract where a client pays a recurring fee (usually monthly) for an ongoing, defined scope of work or availability, as opposed to a one-off, fixed-scope project.
Work delivered under a retainer agreement beyond the monthly scope or hours the client is paying for, in a given billing period.
A retainer agreement provision specifying whether unused hours or deliverables from one billing period carry forward to the next, or expire ("use it or lose it").
A contract provision capping the number of revision rounds included in a project's price, with additional rounds billed separately.
A single cycle of client feedback and corresponding agency edits on a deliverable, typically counted against a contract's revision limit.
S
Language in a contract or SOW that is vague or open to multiple reasonable interpretations about what is or isn't included, creating the conditions for scope disputes.
The approved, documented version of a project's scope — statement of work, work breakdown structure, and acceptance criteria together — used as the fixed reference point against which all later changes are measured.
Work delivered on a project that falls outside what was originally agreed in the contract or statement of work — usually added gradually, in small increments, without a corresponding change in price or timeline.
The specific activities within a project's discovery phase focused on determining what work is actually needed — distinct from the broader discovery phase, which may also cover relationship-building, stakeholder alignment, and technical audits.
A concise, explicit description of what a project includes — and often what it excludes — used as the core reference document for what work has been agreed.
The process of formally confirming, with the client, that delivered work matches the agreed scope — typically happening at project milestones or completion, distinct from scope verification's more technical, internal check.
An internal, often technical check that completed work matches the documented requirements and acceptance criteria — typically done by the delivery team before work is presented to the client for validation and sign-off.
A contract provision defining the specific performance standards an agency commits to — response times, uptime, turnaround times — typically used in ongoing retainer or support engagements.
A document defining a specific engagement's deliverables, timeline, revision limits, and exclusions.
A formal, signed modification to an existing, executed SOW — the SOW-level equivalent of a contract amendment, used when a project's scope needs to change materially, not just via a single small change order.
T
A contract provision allowing either party to end the engagement without cause, typically with a notice period, as distinct from termination for breach.
A pricing structure where the client is billed for actual hours worked at an agreed rate, plus materials/expenses, rather than a fixed total price — the counterpart to a fixed-fee contract.
U
Time or deliverables an agency has produced for a client but has not invoiced for — including both intentionally absorbed costs (write-offs) and out-of-scope work that was never flagged or change-ordered.
Selling a client more of the same type of service they already buy — a larger scope, higher tier, or additional volume — as distinct from cross-selling a different service.
The percentage of an employee's or team's total available working hours that are spent on billable client work, as opposed to internal, administrative, or unbilled time.
W
An approach to controlling project scope where requirements and deliverables are fully defined and locked before work begins, with subsequent phases proceeding sequentially — the counterpart to agile's iterative approach.
A hierarchical decomposition of a project's total scope into smaller, defined, manageable components or tasks — used to estimate effort, assign work, and check that all agreed deliverables are actually accounted for.
A deliberate decision by an agency to not invoice for work already performed — distinct from unbilled work generally, which may include work that simply wasn't flagged or tracked rather than intentionally forgiven.