When Something Happens That the Contract Doesn't Cover

No matter how carefully a contract is drafted, actual work always produces situations that were never written down.

A web design client asks for post-delivery access analytics reports "while you're at it." Midway through a software project, the client company's parent corporation sends an unexpected directive to change the specifications. A photography shoot is thrown off schedule by weather that nobody anticipated. None of these scenarios appear anywhere in the contract.

Some freelancers assume that because something is not in the contract they are free to refuse it. Others assume the opposite — that silence in the contract means they have no choice but to comply. Both assumptions are wrong. What matters is how to interpret that silence and how to negotiate around it.

When a situation arises that a contract does not address, the law does not treat it as entirely unresolved.

Civil law fills contract gaps by considering not just the written text but also the purpose of the agreement, the course of negotiations, industry custom, and the principle of good faith and fair dealing (Civil Code Articles 1(2) and 90 et seq.). This process of "supplementary interpretation" bridges the spaces left blank in written contracts.

Interpretation Based on the Contract's Purpose

The overall objective of the contract can be used to infer what the parties intended for specific situations. For example, if a service agreement was made "to support the completion of a website," routine operational checks and minor corrections may reasonably be understood as included. Conversely, work that clearly exceeds the contract's stated purpose may require a new fee agreement even if the contract says nothing explicit about it.

Application of Industry Custom

Practices that are standard in a given industry can be binding even without explicit written terms. If "two rounds of revisions at no charge" is a widely recognized custom in the design industry, that custom may function as a benchmark even when the contract omits any mention of revision limits.

Reference to Prior Transaction History

In ongoing relationships with the same client, the precedents set in past projects influence the interpretation of the current agreement. If free post-delivery support was provided in previous engagements, it is possible that a similar expectation has now been established.

The key insight is not that silence in a contract grants total freedom to refuse, nor that it requires unconditional compliance. The correct position is: "What does the silence mean given the full context, and what judgment does that call for?" This interpretive space is precisely what creates room for negotiation.

Situations not addressed in a contract generally fall into four types. The root causes and appropriate responses differ for each.

Type 1: Additional Work Requests

Requests that exceed the original scope arrive during or after the project — often framed as "while you're at it" or "can you add one more screen?"

The defining characteristic here is that the client typically does not recognize the request as an addition. They see it as a natural extension of the existing scope and have not budgeted for extra fees. Without a clear line drawn by the freelancer, these requests tend to escalate.

Type 2: Specification Changes

The client's requirements shift partway through the project. "We want to change the target audience" or "we saw a competitor and want to change direction" effectively tries to rewrite what was originally agreed.

What makes specification changes difficult is that clients often describe them as "revisions" or "adjustments," assuming no additional fee applies. Many such changes arise from an incomplete initial requirements definition, blurring the boundary between "what was agreed" and "what has changed."

Type 3: Third-Party Intervention

Someone outside the original contract relationship — a client's supervisor, a related company, an external consultant — begins influencing the work. The client delivers the message: "My manager said to change it" or "our advisor told us to revise this."

A notable feature of this type is that the client's own representative is often uncomfortable too. The project contact wants to honor the original agreement but cannot override internal authority. If the freelancer does not respond calmly, the working relationship with the contact person can be damaged even when neither party is truly at fault.

Type 4: Force Majeure and External Factors

Natural disasters, disease outbreaks, changes in the client company's business situation, or regulatory shifts make performance of the contract difficult for reasons unrelated to either party's will.

The typical dispute here is about risk allocation: who bears the cost of a delay caused by force majeure? Is a time extension accepted without additional fees? How is compensation handled if partial non-performance occurs? These questions are frequently absent from contracts.

What happens in the first few days after an unforeseen event determines the trajectory of everything that follows.

Immediate Documentation (Within 24 Hours)

When an unexpected request or change in circumstances is communicated, send a written confirmation by email the same day. The goal is to put the verbal communication into text and verify mutual understanding.

Subject: [Confirmation] Additional Request Regarding [Project Name]

Dear [Name],

I would like to confirm my understanding of what was communicated today.

Request received: [Describe the request or change specifically]
Original contract scope: [Describe the original agreement]
Date and time received: [Date and time]

Please let me know if this matches your understanding.
Once confirmed, I will follow up separately regarding feasibility and any applicable conditions.

A reply to this email becomes documentary evidence of the facts. If no reply is received, resend with a note such as "As we confirmed by phone earlier today..."

What to Absolutely Avoid at the Outset

The single most damaging thing to do immediately after an unforeseen event is to verbally agree on the spot. Once verbal agreement is given, negotiating for additional compensation becomes significantly harder.

Make it a practice to say "Let me look into that and get back to you" and always respond in writing. Even under pressure to answer quickly, buying time with "I'll confirm and follow up" is worth the pause.

Visualizing the Situation and Estimating Costs

In parallel with documentation, calculate concretely how much additional time and money the requested work would require. Specific hours multiplied by an hourly rate provides a defensible basis for negotiation rather than a vague feeling of being overburdened.

If the additional work amounts to roughly 10–20% of the original scope, absorbing it as a goodwill gesture may be a reasonable choice. When it exceeds 30%, the situation calls for either a supplementary contract or a written change order.

Here are practical approaches for each of the four types.

Responding to Additional Work Requests

First, determine whether the request falls within the original scope or represents new work. Reread the deliverables definition in the contract and assess whether the request could reasonably be included. If it is clearly outside scope, present an additional estimate.

When the boundary is ambiguous, put the request in writing and ask: "My understanding is that this request falls outside the original scope. I am anticipating an additional fee of approximately [amount] — could you confirm your understanding?" This framing invites the client to explain why they believe it is within scope, which moves the conversation onto factual ground.

Responding to Specification Changes

A written change order is the best solution when specifications shift. Summarize the change in content, any additional fees it generates, and the revised schedule on a single document, and obtain signatures from both parties.

When a client resists a written change order, explaining that "this is needed for accounting purposes on our end" often works. The goal is to establish written documentation of changes as a normal business practice rather than a sign of distrust.

Sample change order structure:

Change Order Agreement

Original Scope:
[Original agreed content]

Revised Scope:
[Content after change]

Additional Fee Due to Change:
Amount: [Amount] (before tax)
Payment due: [Date]

Revised Schedule:
New delivery date: [Date]

Both parties agree to the above.
Contractor: [Signature / Date]     Client: [Signature / Date]

Responding to Third-Party Intervention

When a third party's instructions threaten to override the original agreement, the critical move is to anchor the discussion to what was agreed with the client contact. Acknowledge the third party's perspective without dismissing it, while making clear that "any change to the original agreement requires a new mutual agreement."

Avoid blaming the client contact. Instead, take the position: "Please coordinate internally, and then let's confirm the change in writing along with any fee implications." In some cases, the freelancer simply needs to give the client contact time to complete that internal negotiation.

Responding to Force Majeure

When a force majeure event occurs, begin by documenting the factual impact and reporting it to the client. Then open a discussion about what response is reasonable for both parties.

Even when a delay is caused by force majeure, the freelancer's credibility depends on proactive communication and the offer of alternatives. "I'm waiting, please be patient" is far less effective than "Here is the current status, and I'm considering the following alternative approach."

For cost claims, when force majeure genuinely creates additional expenses — extra lodging, equipment rental, and so on — present an itemized breakdown and open a discussion. Claims without supporting documentation are likely to be rejected, so gathering receipts and evidence before the conversation is essential.

Each time an unforeseen situation is handled, the experience points toward something that should be in the next contract. Logging these experiences and systematically updating the contract template leads to meaningful long-term risk reduction.

Building a Log of "What the Contract Didn't Cover"

Create a simple log for each project recording "what this project surfaced that wasn't in the contract." Any tool works — a spreadsheet, a note-taking app, whatever fits your workflow. Five fields are enough: project name, situation encountered, response taken, outcome, and proposed improvement for next time.

After ten or so entries, patterns emerge — the types of unforeseen events you repeatedly face. Translating those patterns into contract language is what transforms a generic template into one that fits your actual practice.

Priority Clauses to Add

For frequent additional work requests: attach a detailed scope definition document as an exhibit to the contract and state explicitly that work outside the exhibit is subject to additional fees.

For frequent specification changes: add a "Change Control" clause requiring that changes be submitted in writing, and that they take effect only after the contractor provides an estimate and the client approves it.

For frequent third-party intervention: add a clause identifying the authorized decision-maker by name and title, and stating that instructions from others will not be acted upon without written confirmation from that person.

For frequent force majeure exposure: add a force majeure clause with illustrative examples, a notification deadline, and a clear default rule for cost allocation.

Version Control for the Contract

Record a version number and revision date on every updated contract, and preserve prior versions. Managing templates with labels like "2026 Edition" or "Web Design v3" makes it possible to track which version was used for which project — and to trace the evolution of your practice over time.

---

A contract is not a document that prevents problems. It is a document that provides a starting point for resolving them. No matter how carefully it is drafted, real work will always reach beyond its terms.

What matters is being able to respond calmly when that happens — following the three steps of documentation, interpretation, and negotiation without panic. Each time this process is repeated, the quality of response improves, and that improvement feeds back into the next contract. The ability to handle unforeseen situations is itself one of the core competencies of a working freelancer.