Acceptance Disputes: When 'Done' Can't Be Agreed On

Freelance designer A has completed the third "final review" for a website renewal project. The client continues to respond with "It's almost finished, but we need a bit more internal discussion." Two weeks have already passed since the contractual delivery deadline, and the schedule for the next project is being compressed.

Meanwhile, project manager B at the ordering company is struggling with "continuous feedback from executives about the design direction, preventing approval." There's no budget to pay for additional modifications, yet the current state cannot be considered complete from an internal perspective.

These acceptance disputes occur daily in freelance and outsourcing work environments. Situations where "acceptance never ends" or "delivery completion can't be determined" create not only time and economic losses for both parties, but also serious problems that damage trust relationships.

This section organizes specific patterns of situations where acceptance cannot be finalized and the actual damage this causes to both contractors and clients.

Typical "Endless Acceptance" Patterns

Pattern 1: Infinite Modification Loop In a system development project, modification requests continue with "There are no operational issues, but we'd like to improve usability a bit more." The initial requirements definition specified "basic function implementation," but the scope of "basic functions" wasn't clear, and the client considers additional features within the scope of free modifications.

Pattern 2: Internal Approval Confusion In logo design creation, approval was obtained at the staff level, but upper management opinions aren't unified. Abstract instructions like "make it more elegant" or "needs more impact" are repeated, resulting in 15 design modifications over 3 months.

Pattern 3: Third-Party Opinions Added Later In a video production project, at the final stage, acceptance is postponed because "we want to hear opinions from an external advertising agency." Significant modifications become necessary based on agency feedback, but there's no agreement on who bears the additional costs.

Impact on Contractors

Cash Flow Deterioration For contracts where payment occurs only after acceptance completion, acceptance delays directly cause cash flow problems. For sole proprietors especially, when month-end acceptance is delayed to the following month, it means payment delay until the month after that.

When acceptance for a medium-scale system development project (contract value 2 million yen) is delayed by 2 months, the contractor is effectively providing a 2-month interest-free loan. This represents an opportunity cost equivalent to 24% annual interest.

Schedule Management Collapse Delays in starting the next project disrupt annual ordering plans. Particularly in seasonal industries (like e-commerce site construction for year-end shopping), delays of several weeks can impact plans until the following year.

Mental Stress and Motivation Decline Endless modification work severely diminishes creators' motivation. When situations continue where "no matter how many modifications are made, satisfaction isn't achieved," contractors become reluctant to engage in future transactions.

Impact on Clients

Overall Project Delays Website creation acceptance delays can cause planned marketing campaign launches to be postponed, missing sales opportunities. This is particularly fatal for time-dependent projects like event announcement sites.

Internal Resource Waste Prolonged acceptance processes prevent staff from focusing on other duties. A vicious cycle emerges where middle management is tied up with acceptance work, neglecting their primary management responsibilities.

Additional Cost Generation Acceptance delays worsen relationships with contractors, making future continued transactions difficult. Selecting and contracting new outsourcing partners requires considerable time and cost.

This section analyzes the fundamental mechanisms that create acceptance disputes and the vicious cycle structure that emerges when these issues are left unaddressed.

Vague Acceptance Criteria

Absence of "Completion" Definition Many outsourcing contracts specify "completion and delivery of deliverables" as payment conditions, but don't specify concrete "completion" criteria.

For example, with contract content like "website creation package," it's unclear how many pages are included, what level of dynamic functions will be implemented, or which browsers require testing confirmation.

Subjective Judgment Standards For deliverables containing subjective elements like "design quality" or "usability," client satisfaction becomes the acceptance criterion. Contractors cannot clearly object to modification requests based on reasons like "somehow unsatisfactory."

Lack of Technical Quality Standards Even in system development, abstract standards like "operates normally" are insufficient. Technical quality standards like response speed, concurrent user limits, and security levels aren't numerically defined.

Inadequate Internal Approval Systems

Unclear Decision-Making Authority While project managers may say "I'll make the final decision" at project start, actual decision authority often lies with supervisors or executives. Staff themselves sometimes don't accurately understand their own authority scope.

Late-Appearing Stakeholders New stakeholders (advertising agencies, external consultants, other department staff) emerge during projects to voice opinions. These third parties often demand major changes without understanding the background or constraints.

Inefficient Decision-Making Processes Large corporations require approval through multiple approvers via ringi systems, but each approver provides feedback from different perspectives, sometimes contradicting previous approvers' opinions.

Differing Perceptions About Cost Responsibility

Different Interpretations of Modification Scope Even with contract clauses stating "minor modifications are free," the definition of "minor" is vague. While clients expect "color changes," contractors may need major modifications requiring overall balance adjustments.

Unconscious Additional Requests Requests that clients claim they "wanted from the beginning" are often additional functions not in the original specifications. Clients themselves often don't recognize these as additional requests.

Lack of Understanding About Time Costs Work requested casually with "please take a quick look" or "quick modifications" often actually requires several hours to days. Clients don't understand the complexity of creation processes and underestimate time costs.

Vicious Cycle Structure

When these causes combine, the following vicious cycle emerges:

1. Start creation with vague standards
2. Modification requests based on subjective dissatisfaction
3. Interpretation conflicts over free modification scope
4. Prolonged internal approval and confusion
5. Contractor fatigue and motivation decline
6. Quality deterioration leading to further dissatisfaction
7. Relationship deterioration and trust loss

Breaking this cycle requires structural countermeasures.

This section presents specific procedures for freelancers and individual business owners to prevent acceptance disputes and respond appropriately when they occur.

Formalizing Acceptance Criteria During Contracting

Detailed Deliverable Specifications In contracts or specification documents, specify the following elements with numerical values and concrete examples:

• Website creation: page count, responsive screen size range, supported browsers, display speed standards
• System development: function list, performance requirements, test items, security requirements
• Design creation: delivery format, maximum modification count, approval authority identification

Setting Acceptance Deadlines Clearly define the period from delivery to acceptance completion in contracts. Generally appropriate periods are:

• Simple design creation: within 7 days
• Website creation: within 14 days
• System development: within 21 days

Include "deemed acceptance clauses" where acceptance is considered complete after the period expires.

Pre-defining Modification Scope Specifically list the scope of free modifications and specify that additional fees apply for changes beyond that scope. For example:

• Minor text/color modifications: up to 3 times free
• Layout changes: one time free (within 2 hours work)
• Function additions/specification changes: all subject to additional fees

Risk Reduction Through Project Management

Thorough Staged Approval For large projects, avoid bulk delivery and obtain staged approvals:

1. Wireframe/design document approval
2. Design comp/prototype approval
3. Final deliverable acceptance

Obtain written approval at each stage to prevent backtracking.

Pre-confirmation of Approvers and Decision Authority Confirm the following in writing before project start:

• Who has final approval authority?
• What is the staff member's decision-making scope?
• Will there be involvement from external parties (agencies, consultants, etc.)?

Regular Progress Reporting Conduct weekly or bi-weekly progress reports to detect misalignments early. Include the following in reports:

• Completed work content
• Planned work until next time
• Concerns and risk factors
• Confirmation and request items for clients

Staged Response to Acceptance Delays

Stage 1: Reminders and Cause Confirmation Within 3 business days after the acceptance deadline passes, send written reminders (email acceptable). Simultaneously confirm delay causes and expected timeline.

At this stage, use cooperative tone with expressions like "Sorry to bother you during busy times" while maintaining relationship consideration.

Stage 2: Consider Additional Fee Requests At 2 weeks past acceptance deadline, notify about requesting additional fees for storage and management costs. Appropriate amounts are generally 5-10% of contract value.

Cite Article 413-2 of Civil Code (delayed acceptance) as legal basis, explaining it's legitimate rights exercise.

Stage 3: Contract Termination Warning At 1 month past acceptance deadline, warn of contract termination due to performance delay. Specify the following:

• Termination notice period (usually about 2 weeks)
• Settlement method upon termination (compensation for completed portions)
• Reservation of damage compensation claims

Practical Communication Techniques

Modification Request Response Flow Standard response procedure when receiving modification requests:

1. Detailed confirmation of request content (require written documentation)
2. Present work time and cost estimates
3. Propose additional contracts for work exceeding free scope
4. Begin work after obtaining approval

Avoid emotional responses and always maintain professional, objective stance.

Importance of Evidence Preservation Record all instructions, approvals, and modification requests in writing (email/chat) to prepare for future disputes. For verbal phone instructions, always follow up with email confirmation: "Regarding the matter you instructed by phone..."

This section specifies the internal systems and operational rules that ordering companies and clients should establish to avoid acceptance disputes.

Internal Approval Flow Development

Creating Approval Authority Matrix Establish internal rules that clarify approval authorities by amount and content:

| Contract Amount | Content | Approval Authority | Approval Period | |----------------|---------|-------------------|-----------------| | Under 100,000 yen | Design/light work | Staff member | 3 business days | | 100,000-500,000 yen | Website creation | Manager level | 5 business days | | Over 500,000 yen | System development | Department head level | 10 business days |

Prior Education for Approvers Provide education to management with approval authority on:

• Basic knowledge of outsourcing management
• Risks and impacts of acceptance delays
• Additional cost rules for modification requests
• Obligation to observe approval deadlines

Project Management System Establishment

Appointing Dedicated Project Managers For projects above certain scale, appoint dedicated staff with following authorities:

• Daily progress management and communication
• Approval authority for minor modifications and changes
• Coordination with internal stakeholders
• Acceptance schedule management

Standardizing Internal Review Processes Establish processes to streamline internal confirmation of deliverables:

1. Primary confirmation by staff (2 business days)
2. Approval decision by supervisor (3 business days)
3. Coordination with related departments (5 business days when necessary)
4. Final approval and acceptance completion (1 business day)

Create checklists for confirmation points at each stage to prevent dependency on individuals.

Coordination Systems with External Collaborators

Prior Identification of Stakeholders Before project start, list all parties who might provide opinions on deliverables:

• External consultants and advisors
• Advertising agencies and marketing partners
• Related staff from other departments
• External specialists and supervisors

Pre-scheduling Opinion Collection Incorporate opinion collection timing from these stakeholders into project plans and share with contractors. Prohibit late-stage opinion collection in principle, handling unavoidable cases with additional fees.

Budget Management and Cost Control

Prior Budget Allocation for Modifications and Changes Budget 10-20% of initial contract value as reserve funds for modification and change responses, establishing systems where staff can execute these at their discretion.

Simplified Additional Cost Approval Flow For minor additional work (under 50,000 yen, etc.), establish rapid approval routes that bypass normal ringi procedures. Position this as investment to prevent opportunity losses from acceptance delays.

Quality Management and Satisfaction Improvement

Thorough Requirements Definition Before project start, clarify the following during requirements definition:

• Specific deliverable specifications and quality standards
• Anticipated usage scenarios and target effects
• Internal preferences and NG points
• Reference sites and design examples

Mandatory Interim Confirmations For large projects, always set interim confirmation timing to detect directional misalignments early. Document interim confirmation issues and share understanding with contractors.

This section organizes legal relationships when acceptance disputes become serious and practical response procedures.

Legal Framework of Delayed Acceptance

Delayed Acceptance Under Civil Code Acceptance is the client's "acceptance obligation," and refusing or delaying acceptance without justifiable reason constitutes "delayed acceptance" under Article 413-2 of Civil Code.

Requirements for delayed acceptance:

1. Contractor properly offered performance
2. Client refuses or delays acceptance without justifiable reason
3. No contributory negligence by contractor

Effects of Delayed Acceptance Delayed acceptance creates the following legal effects:

• Client's risk bearing (risk of deliverable loss/damage transfers to client)
• Contractor's right to claim storage and additional costs
• Right to claim delay damages
• Right to terminate contract (after reasonable period passes)

Practical Additional Fee Requests

Calculating Storage and Management Costs Calculate specific costs incurred by contractor due to acceptance delays:

• Data storage/backup costs: approximately 5,000 yen per month
• Inquiry response/management labor: 3,000 yen per hour × actual working hours
• Opportunity costs (impact on other projects): certain percentage of lost profits

Creating and Sending Invoices Additional cost invoices should specify:

• Billing basis (additional costs due to delayed acceptance)
• Cost breakdown and calculation basis
• Payment deadline (usually within 30 days)
• Late payment damages for non-payment (14.6% annual, etc.)

Contract Termination Procedures

Implementing Demand Procedures Contract termination requires prior demand (Civil Code Article 541). Demand letters should include:

• Facts of performance delay (acceptance delay)
• Performance request within reasonable period (usually about 2 weeks)
• Notice of contract termination if not performed within period

Sending Termination Notice After demand period expires, send formal contract termination notice:

• Expression of intent to terminate contract
• Clear statement of termination cause (performance delay)
• Claim for compensation for completed portions
• Reservation of damage compensation claims

Practical Negotiation Strategies

Staged Escalation Legal response should be last resort; take following staged approach:

Level 1: Cooperative Resolution

• Detailed confirmation of delay causes
• Resetting acceptance completion timing
• Proposal for provisional partial acceptance

Level 2: Conditional Continuation

• Request and agree on additional costs
• Strict acceptance deadlines
• Addition of penalty clauses

Level 3: Relationship Dissolution Preparation

• Implementation of demand procedures
• Organization and preservation of evidence documents
• Securing alternative projects

Contract Clauses for Dispute Prevention

Deemed Acceptance Clause "The client shall complete acceptance within ○ days of receiving deliverables, and if no objections are raised within this period, acceptance shall be deemed complete"

Additional Cost Clause for Acceptance Delays "If acceptance is delayed due to client circumstances, the contractor may claim monthly management fees of ○ yen"

Acceptance Criteria Clarification Clause "Acceptance shall be determined according to the following criteria, and subjective satisfaction is not included in acceptance requirements: (list specific criteria)"

These clauses can significantly reduce dispute risks.

Prevention and response to acceptance disputes can be reliably achieved by incorporating them into daily business processes. Here are specific actions that contractors and clients should implement starting tomorrow.

Immediate Actions for Contractors

Contract Template Development Add the following clauses to existing contracts:

• Acceptance deadlines (within 14 days of delivery, etc.)
• Deemed acceptance clauses
• Clear modification count and scope limits
• Additional cost provisions for acceptance delays

This work can be completed in one day and applied to all future projects.

Project Start Checklist Creation Create a checklist of items to always confirm when starting new projects:

• □ Identify and confirm final approver
• □ Confirm decision-making authority scope
• □ Confirm presence of external stakeholders
• □ Agree on acceptance schedule
• □ Obtain emergency contact information

Progress Report Format Standardization Report progress in the same format every time to prevent misunderstandings:

1. Completed work since last report
2. Planned work until next time
3. Client confirmation and request items
4. Concerns and risk items
5. Overall progress percentage

Immediate Actions for Clients

Approval Authority Matrix Creation Document outsourcing project approval authority by amount and content, and notify stakeholders. Summarize on one A4 page and distribute to each department.

Acceptance Checklist Development Create checklists of confirmation points during acceptance by deliverable type:

• Websites: functional operation, display speed, supported browsers
• Design: specification compliance, brand consistency, usability
• Systems: requirement fulfillment, performance standards, security requirements

Internal Coordination Rule Clarification Establish rules for when internal coordination is needed for outsourced projects:

• Maximum coordination period (within 1 week, etc.)
• Decision method when opinions don't align
• Policy for handling late-stage opinions

Common Improvement Actions

Communication Quality Enhancement

• Eliminate verbal instructions/approvals and record everything in writing (email/chat)
• Prohibit vague expressions ("a bit more," "make it nice," etc.)
• Always request confirmations with deadlines

Regular Relationship Maintenance Make post-project review meetings a habit:

• Share what worked well and improvement points
• Consider improvement plans for next projects
• Build long-term partnerships

Industry Standard Learning and Application Research contract conditions and management methods of other companies in the same industry, updating company standards. Acquire latest practical knowledge by participating in industry association study groups and seminars.

Acceptance disputes should not be "handled after they occur" but "prevented from occurring." By accumulating small improvements that can be implemented starting today, situations of "acceptance troubles," "acceptance never ending," and "delivery completion can't be determined" can be reliably avoided, building healthy contractor-client relationships.

The first step to success is for contractors to prioritize contract clause reviews and thorough project management, while clients should prioritize internal approval system development and budget allocation.