Are Verbal Instructions Contract Changes? How to Document

This section analyzes typical patterns where additional work from oral agreements develops into contract disputes and structural causes.

In a web development project with an initial estimate of 500,000 yen, the client called mid-project requesting "please add 5 more product pages." At the time, you answered "understood" and proceeded with the work, but when billing an additional 150,000 yen after delivery, the client refuses payment saying "I didn't hear about such a high additional cost. I thought it was included in the original amount." This type of case is a typical trouble that any freelancer or creator encounters at least once.

Why do such problems occur frequently? The biggest factor lies in the nature of oral agreements in outsourcing contracts. Unlike employees, there's no hierarchical relationship between freelancers and clients - it's an equal contractual relationship, so additional work instructions should be treated as "new contract proposals." However, in actual practice, clients often make additional work requests as "instructions/orders," while contractors often give ambiguous responses due to the psychology of "difficulty refusing."

Furthermore, the "ambiguous boundaries of work" characteristic of the creative industry complicates problems. For design modifications, feature additions, and specification changes, it's difficult to judge what falls within the original contract scope and what constitutes additional work. What clients consider "minor modifications" may actually require several days of work.

Additionally, many freelancers being unaccustomed to "keeping records" is a major contributing factor. While they may have had habits of confirming supervisor instructions via email during their employee days, after going independent, verbal exchanges via phone or video conferences become central, creating situations where no reviewable records remain.

This section explains from a legal perspective the conditions under which oral agreements become legally valid contract changes and the importance of evidence.

To conclude, verbal contract instructions can constitute legally valid contract changes. Under civil law, contracts are established when parties reach agreement, and document creation is not generally a required condition. This means even verbal exchanges like "please create 5 additional pages" "understood" can potentially establish contract changes legally.

However, contract change establishment requires the following elements. First is specificity of change content. Abstract instructions like "please make it better" cannot be considered contract changes. Specific work content must be identified, such as "add 5 product pages" or "change from 3 to 5 logo design proposals."

Second is agreement on compensation. There must be clear determination of payment for additional work, or at least shared recognition between both parties that it's "paid additional work." Starting work while it remains unclear whether additional support is free or paid, and if paid, how much, creates major sources of dispute later.

Third is agreement on performance deadlines and impact on delivery dates. There must also be alignment in both parties' recognition of work prerequisites, such as whether additional work extends the original deadline and what quality level is required.

The problem is that proving "whether agreement existed" after the fact is extremely difficult with oral agreements. Even if contract changes occurred, parties often have different memories and perceptions of the content. When claims like "we didn't discuss additional fees" or "I didn't hear it was such demanding work" arise later, proving whether agreement actually existed becomes necessary.

In court cases, judges make decisions based on objective evidence. Without physical evidence like email/chat history, recorded data, or work instruction documents, it becomes a "he said, she said" argument. Therefore, even with oral agreements, keeping records that can prove them later is practically essential.

This section introduces specific steps for documentation, confirmation, and consensus building when additional work is requested verbally.

The basic principle for responding to additional freelance instructions is "not giving ambiguous responses on the spot." No matter how simple the additional work seems, when requested verbally, answer "I'll consider it" or "let me confirm the details" and create time to take it back and organize.

Step 1 is documenting the additional work content. When receiving instructions by phone, immediately after the call ends, send an email or chat message stating "Let me confirm what I heard on the phone just now" and organize the following items:

Specific example of work content description: "Additional creation of 5 product pages (Products A-E), each page created with the same layout and functionality as existing product pages, assuming product images and descriptions will be provided by the customer"

By putting the work scope into specific text and sending it to the other party, you can discover recognition gaps early. If they reply "that's not right," you can correct it to the proper content at that point.

Step 2 is presenting estimates for work period and costs. The most important evidence for additional work is agreement records about costs and timeframes. Present clearly with statements like "For the above additional work, we expect a work period of 5 business days and additional cost of 150,000 yen (excluding tax)."

Step 3 is organizing impacts on the existing contract. When additional work delays the original deadline, changes priorities of other work, or modifies originally planned specifications, you must also communicate those impacts.

Step 4 is obtaining clear approval from the other party. State "If you approve the above content, we will begin work. Please confirm" and wait for their response. Even if they say "that's fine" by phone, always send a confirmation message via email or chat stating "As you approved by phone, we will start work tomorrow."

Step 5 is recording work start and completion. Record the date/time when additional work actually began, completion date/time, and detailed work content as time logs. This becomes counter-evidence when later told "I didn't think it was work that would take so much time."

The important thing is not making clients feel this series of procedures is "troublesome red tape." Use positive expressions like "to confirm details so we can accurately meet your requirements" or "to organize details so we can deliver high-quality deliverables," positioning it as work that benefits clients too.

This section organizes evidence capabilities of various recording media and characteristics of evidence likely to be recognized as valid in actual disputes.

Documents where both parties agreed on content have the highest evidence capability. Email and chat histories are very powerful evidence because transmission date/time, sender, recipient, and content are objectively recorded. Especially when the other party's replies record expressions of consent like "understood" or "please proceed," they become decisive evidence proving contract change agreement existed.

Video conference recordings can also be effective evidence. If you record meetings on tools like Zoom or Teams and have records of discussing additional work, you can prove verbal agreement content. However, recording requires obtaining the other party's consent in advance, and unauthorized recording can cause problems later.

The same applies to audio recordings - recording calls without the other party's consent carries legal risks. On the other hand, notes you keep for your own records (content written immediately after calls) have no evidence capability by themselves but help explain situations when combined with other evidence.

Often overlooked is the evidence capability of work deliverables themselves. Additionally created pages or designs usually record file creation dates and revision history. Even if the other party claims "no additional work was done," files clearly created after the original contract serve as evidence that some additional work occurred.

Invoices and estimates are also important evidence. When the other party doesn't object to invoices sent after additional work completion and a certain period passes, it may be interpreted as tacit recognition of compensation for additional work.

Conversely, records with much ambiguous expression are difficult to use as evidence. Exchanges like "please make some more modifications" or "we'll handle what we can" make it impossible to determine specifically what work occurred and whether it was paid or unpaid.

Unilateral records also have limited evidence capability. Memos created only by yourself, emails sent only by you (without replies from the other party), and work logs managed only by you are difficult to accept as evidence when the other party denies the content.

Exchanges on SNS like LINE also require caution. Since message deletion and editing are possible, evidence capability may be questioned from a completeness perspective. For important agreements, it's safer to keep records in more formal email or business chat tools rather than SNS.

As a practical tip for evidence preservation, recording the same content in multiple media is recommended. Confirming verbally agreed content via email and additionally recording it in project management tools - by recording the same facts through different methods, evidence reliability increases.

This section specifically shows contract clause settings to prevent troubles from verbal instructions and advance agreement items with clients.

The fundamental solution is clearly defining additional work handling rules in the initial contract. Including the following types of clauses in contracts can prevent most troubles.

Example "Specification Change/Additional Work Clause": "When the client requests specification changes or additional work after contract conclusion, the contractor shall receive formal written change request submissions (including email), then consider change content, additional costs, and delivery date impacts, and respond in writing. Changes/additional work will only be implemented when the client agrees to the contractor's response content."

This clause creates a system where work doesn't begin with verbal instructions alone. To avoid clients thinking it's "troublesome procedures," explain the reason as "for quality improvement and trouble prevention" when concluding contracts and gain understanding.

As more detailed provisions, also define additional cost calculation standards. Clauses like "Additional work costs will be calculated based on this contract's hourly rate (XX yen/hour), with estimates presented before work begins" can reduce risks of cost disputes later.

Also establish advance agreements about delivery date impacts. A clause stating "When additional work requires changing the original delivery date, the contractor will propose a new delivery date and continue work after obtaining client agreement. The contractor bears no responsibility for delivery delays due to additional work" legitimizes delivery delays caused by additional work.

In addition to contract-level responses, re-confirming "change/additional work rules" at project kickoff meetings is also effective. While contracts have legal binding force, in actual project management it's important that all stakeholders understand the rules.

As a practical prevention measure, "scope confirmation" in regular meetings is also effective. During weekly or monthly progress reports, confirm "is the current work scope as per the original contract" and "are there any newly arising requirements," taking formal procedures early when changes are needed.

Client education is also an important prevention measure. Many clients don't fully understand that freelancer contracts are "equal outsourcing relationships" rather than "employment relationships." At project start, carefully explain additional instruction procedures and seek cooperation with the stance "let's conduct transparent project management for both of us."

Also consider creating "Project Management Rules" documents separate from contracts and sharing them with clients. Clarifying daily interaction rules like communication methods, meeting frequency, deliverable confirmation methods, and change request procedures in writing makes entire projects run smoothly.

The important thing is positioning these mechanisms not as "defensive measures" but as "cooperative systems for project success." Habitualizing appropriate records and procedures without damaging client trust relationships leads to long-term business stability as a freelancer.

Verbal additional instructions can constitute legally valid contract changes, but they often lead to disputes later due to lack of evidence. The actions freelancers and creators should take are clear.

First, develop the habit of not giving ambiguous responses on the spot to any additional requests, no matter how minor, and always confirming content in writing. Use email or chat to state "confirming the matter we just discussed," specifically record work content, costs, and timeframes, and only begin work after obtaining clear approval from the other party.

Next, establish additional work rules in contracts in advance. Building mechanisms at the contract level to prevent troubles - like written change requests, advance cost agreements, and delivery date impact confirmations - can significantly reduce risks from verbal instructions.

Finally, position these responses not as "troublesome procedures" but as "project quality improvement" and implement them while building cooperative relationships with clients. Appropriate records and procedures ultimately lead to transparent project management that benefits clients too.

As an action you can implement starting today, when there are verbal exchanges in currently ongoing projects, make sure to confirm the content via email within that day. And when contracting with new clients next time, consider including clauses about additional work in contracts. These small accumulations strengthen your business foundation as a freelancer.