A Long Contract Should Explain How the Work Can Change

A commercial essay on long engagements: scope boundaries, changing assumptions, adaptation costs and the decisions that keep a contract workable after signature.

The signature fixes less of the future than it appears to

A long engagement begins with an account of work that has not yet happened. Both sides describe outputs, timing, resources and responsibilities under assumptions that may later change. The contract can create important certainty about those commitments. It cannot make the operating environment stop moving. A commercially serious agreement should therefore explain how change will be recognised and decided, rather than rely on the hope that the original description will remain sufficient.

This essay examines the management of a continuing commercial relationship, not the enforceability of particular clauses or the legal allocation appropriate in a specific jurisdiction. Those matters require qualified advice. Its practical proposition is that a long contract needs a decision architecture as well as a statement of scope. The parties should understand which changes are already included, which require a new agreement and what happens while the distinction is being resolved. Otherwise a document intended to reduce uncertainty can become the setting in which uncertainty accumulates without an owner.

Make the assumptions inspectable

A price and delivery promise may depend on the volume of work, the quality of information supplied, access to particular people or the continued availability of a technical environment. If those assumptions remain implicit, one party may believe the commitment is unconditional while the other believes it applies only under the expected conditions. The disagreement becomes visible only after someone has relied on the offer.

Imagine a hypothetical service provider maintaining a company's reporting process for several years. The initial price might assume a particular set of systems and a reasonably stable number of reporting entities. If the customer later acquires several businesses using incompatible systems, the work may change materially. The provider should not be able to invent a hidden assumption after the fact, and the customer should not have to guess which changes the price already covers. An inspectable starting account identifies the relevant operating conditions so that later decisions can be made against something both parties understood.

A boundary should identify a decision, not merely a prohibition

A scope statement that says additional work is excluded may be technically clear while leaving the practical response unresolved. Who decides whether a request is additional? What information is needed? How quickly must the decision be made? What happens if the customer needs an answer before the pricing discussion can be completed? These questions determine whether the boundary can function during ordinary work.

The process should distinguish correcting an unmet original obligation from accepting a genuinely different task. A provider should not charge extra simply because delivery was more difficult than expected. A customer should not redefine a new objective as a correction merely because the same team is capable of performing it. The distinction requires evidence about the promise and the request. An agreed route for examining it can reduce the temptation to settle the matter through pressure, delay or an informal favour that later becomes a disputed precedent. A useful boundary directs the next decision rather than merely supplying a phrase for an argument.

Changes can arrive in small increments

A relationship can become substantially different without a single dramatic instruction. A slightly different format, an additional meeting and another exception may each appear manageable. Together they can change the resources required or the capacity available for other work. Examining only requests large enough to trigger a formal dispute can leave the cumulative change invisible.

This does not mean recording every ordinary conversation as a chargeable event. The parties need a proportionate way to notice when the pattern of work is departing from the original arrangement. A periodic review of outputs, volumes and recurring exceptions may be more useful than a complex approval form for every adjustment. The record should serve a commercial question: does the existing commitment still describe what is being delivered? If it does not, the response may be a different process, a revised price or a decision to stop providing an unnecessary variation. Adaptation becomes more credible when the whole pattern can be examined.

Keep the change log useful to the people doing the work

A record can become so detailed that nobody can find the decision it was intended to preserve. The operational account should make the current arrangement easier to understand, with earlier versions retained as appropriate evidence rather than mixed indiscriminately into daily instructions. A person performing the work needs to know which requirement applies now.

A useful change record identifies the request, the decision, the reason and the effect on relevant commitments. It should also identify the date from which the change operates. These details help separate a genuine revision from a misunderstanding about which version somebody received. The purpose is not to create documentation for its own sake. It is to prevent the same change from being interpreted differently by sales, delivery and the customer. A continuing contract deserves a record that supports performance rather than merely proving that many messages were exchanged.

Connect direction to the next reviewable commitment

No Plan, No Future, my book, is a relevant reading connection for the distinction between activity and an organised direction. In a long commercial engagement, direction becomes practical through the commitments the parties can actually review. A statement that the relationship will remain flexible is weaker than an agreed way to identify a change and decide its consequences.

The reading connection is an author perspective, not a substitute for professional contract advice or evidence about a particular transaction. Its useful role is to encourage a more demanding question: does the plan organise the decisions that will be needed after the work begins? If it only describes the desired result, the parties still need a route through the uncertainty between intention and delivery. That route should remain visible even when the relationship is friendly enough that neither side expects to need it.

Distinguish temporary strain from a new normal

A short disruption can justify flexibility without requiring a permanent redesign. A continuing change may require a new arrangement even if both sides initially treat it as temporary. The difficulty is that the label temporary can persist long after the original operating conditions have disappeared. The contract remains unchanged while the actual work becomes something else.

A hypothetical customer might ask for additional support during a system migration. The parties can define a limited period, the expected work and a review point if the migration takes longer. The review point matters because it prevents goodwill from becoming an indefinite obligation by default. It should not be an excuse to abandon a customer at a vulnerable moment. It should make the next conversation timely enough that support can continue on terms both understand. Flexibility deserves a defined purpose and a route back to a stable arrangement. Otherwise the relationship can depend on continuing exceptions that neither side is willing to recognise as its normal operation.

Payment and risk need the same calendar

A contract can allocate work in stages while payment, customer approvals and outside dependencies follow different schedules. The resulting gaps can leave one party financing work or waiting for a decision without a clear limit. Examining the calendars together reveals whether the arrangement requires an exposure that the headline price does not explain.

This differs from choosing payment milestones for a single project. The long-engagement question is whether those milestones remain appropriate as the work changes. A service with ongoing obligations needs to understand how delayed information, paused activity or a requested acceleration affects the commercial commitment. The parties should avoid assuming that one standard clause settles every case. The relevant discussion connects the actual resource decision to the payment or approval that supports it. Clear timing also makes a problem easier to raise before it becomes a threat. A party can explain a developing gap while there are still several ways to resolve it, rather than use an imminent interruption as the first occasion to renegotiate.

Keep authority visible when personnel change

The people who negotiated an agreement may not be the people who later operate it. A new manager can inherit a document without understanding the informal expectations that surrounded its signature. A supplier's team can change while the customer assumes the same knowledge and discretion remain available. The contract therefore needs an operational record that survives a change of participants.

That record should identify authorised decisions, accepted variations and unresolved questions. It should also distinguish an exception granted by one person from a general amendment on which future work can rely. The objective is not to preserve every message indefinitely. It is to maintain an intelligible account of the arrangement currently being performed. When a new participant arrives, they should be able to understand what has changed and which questions require fresh approval. A long relationship becomes fragile when practical authority exists only in the memory or goodwill of individuals who may no longer be present to explain it.

A review should permit a real outcome

A scheduled review can create the appearance of adaptability without giving either party a route to act on what it finds. If price, scope, timing and delivery method are all treated as untouchable, the meeting may simply record an increasingly unworkable arrangement. The parties should know which decisions the review can produce and how disagreement will be handled.

A credible outcome might be a revised process, a narrower service, an additional commitment or an orderly end. Ending an engagement is not automatically a failure of cooperation; sometimes it is the responsible response to conditions that no longer support the original exchange. The important point is to distinguish a managed conclusion from an interruption used as leverage. A long contract should remain understandable throughout its life, including when it needs to change. Its commercial value lies not only in the certainty created at signature, but in the discipline through which later uncertainty becomes a decision both sides can recognise and carry out.

Gabriel Nicolaev — CyGuru

Editorial photograph for illustration.

FOLLOW THE CONNECTION

Another angle on this subject

Continue through related ideas, decisions and consequences.

Money & Business

Customisation Should Earn Its Complexity Before You Price It

A commercial essay on pricing bespoke work through its operating consequences, from exceptions and coordination to maintenance after delivery.

Money & Business

Payment Milestones Should Follow the Risk in the Work

A commercial essay on structuring project payments around observable progress, buyer protection and the supplier’s exposure before final delivery.

The CyGuru Column

Choose an Ambition Whose Costs You Are Willing to Own

A CyGuru essay on inherited definitions of success, the costs hidden inside an attractive goal and the work of choosing what ambition should demand.