Source Code and Design File Handover Obligations

This section clarifies typical examples of production data handover disputes and the recognition gaps underlying them.

Freelance designer A completed a website project and received a request from the client two weeks after delivery: "We need all PSD files and source code for future updates." The contract states "copyright transfers to the client," but nothing is written about production data handover. Designer A was confused: "I delivered the completed site, but do I have an obligation to hand over production process files?"

Meanwhile, Company B's representative thinks, "We purchased the copyright, so naturally we should receive all data." This difference in recognition leads to future disputes.

The reason such troubles frequently occur is the confusion between "finished product delivery" and "production data handover." Many parties mistakenly believe "copyright transfer of deliverables = handover of all related data," but legally these are completely separate contract matters.

Specifically, delivering a website's finished product (final versions of HTML, CSS, JavaScript) and handing over Photoshop files (PSD), Illustrator files (AI), development environment source code, and design documents used in the production process are treated as different obligations.

What further complicates the problem is that the scope of "source code handover" and "design data delivery" varies greatly by project. Even within web development, static sites, CMS construction, and e-commerce site development require completely different types and volumes of data to be handed over.

Contractors tend to think "delivering the finished product is sufficient," while clients expect "all data necessary for future operation and updates is included." This gap in expectations creates dissatisfaction of "this is different from what we expected" after project completion.

Particularly among freelancers and small production companies, contract preparation is often inadequate, with work beginning based only on verbal agreements or simple work orders. As a result, differences in mutual recognition surface at the final stage, developing into problems such as relationship deterioration and additional cost claims.

This section organizes the legal relationship between copyright transfer and production data handover, providing practical judgment criteria.

Under copyright law, copyright transfer and handover of materials and data used in creating copyrighted works are treated as completely separate legal relationships. Transferring copyright does not automatically create an obligation to hand over all files generated during the production process.

To explain with a concrete example, when transferring copyright of a logo design, what the client acquires is "the right to reproduce, modify, and distribute that logo." However, this alone does not create an obligation for the creator to hand over the original file (AI file) created in Adobe Illustrator.

This legal structure follows the same thinking as physical product manufacturing. Purchasing a car doesn't automatically grant access to its blueprints or manufacturing process data. The same principle applies to digital creations.

However, the situation is different when explicitly agreed upon in a contract. "PSD AI handover obligations" have legal binding force when specified as contract clauses. Conversely, when not stated in the contract and verbal agreements cannot be proven, it's generally judged that the creator has no handover obligation.

What's important in practice is to distinguish between copyright transfer consideration and production data handover consideration. Copyright transfer fees are "consideration for rights," while data handover fees are "consideration for services."

For example, even if copyright transfer fees are set at 500,000 yen for website development, this often doesn't include costs for "additional work necessary for data handover" such as source code organization, documentation creation, and handover explanations. These tasks typically cost an additional 100,000-200,000 yen.

Production data also distinguishes between "final versions" and "working versions." Final version source code is relatively organized, but handing over massive working files created through trial and error in the production process can cause confusion for recipients.

Legally, unless specifically stipulated in the contract, creators fulfill their obligations by delivering "deliverables agreed upon in the contract." Providing additional data should be treated as paid services under new contracts.

This section explains specific methods for writing contract clauses regarding source code and design data handover, along with operational considerations.

When defining production data handling in contracts, five elements must be clarified: (1) handover scope, (2) file formats, (3) handover timing, (4) cost allocation, and (5) support scope.

Example of Clearly Defining Handover Scope

"Party B (creator) shall hand over the following data files to Party A (client) in addition to transferring copyright of the created work:

• Final version HTML files, CSS files, JavaScript files
• Final version PSD files of design mockups (with organized layers)
• AI files of logos and icons (editable format before outlining)
• List of fonts used and license information However, working files generated during production, test data, and development environment configuration files are not included in handover targets."

The key point of this clause example is clearly distinguishing between "what to hand over" and "what not to hand over." Ambiguous expressions become breeding grounds for future troubles.

File Formats and Version Management

What's often overlooked in production data handover is file format compatibility. Files created with the latest Adobe Creative Cloud may not open in older versions.

"PSD files shall be saved in Photoshop CC 2019 format with layer names in Japanese. AI files shall be in Illustrator CC 2019 format, providing both outlined versions and text-editable versions of fonts used."

By specifying concrete software versions and save formats like this, post-handover troubles can be prevented.

Handover Timing and Acceptance

Production data handover timing is also an important point. In most cases, handover after completion of deliverable acceptance is appropriate, but depending on project nature, parallel processing may occur.

"Production data handover shall be implemented within 10 business days from completion of final acceptance by Party A. Party A shall verify data content within 30 days after handover and notify in writing of any deficiencies."

Cost Clarification

Since production data organization and handover requires considerable labor, clarifying cost allocation is important.

"Party A shall bear a separate cost of 150,000 yen (excluding tax) for organization work, documentation creation, and handover explanations required for production data handover."

This cost often includes file organization and renaming, README creation, simple handover documentation creation, and one online explanation session (2 hours).

Limiting Support Scope

Without clarifying post-handover support scope, there's risk of being asked for free technical support indefinitely.

"Party B shall respond to technical questions from Party A via email for 30 days after production data handover. However, support for data modification and customization is outside the scope of this contract."

By combining these clauses, a production data handover system that both parties can accept can be established.

This section shows problem points that both parties tend to overlook regarding production data handover and actual trouble examples that can occur.

Contractor Pitfalls

The most common is "underestimating the labor required for handover work." There's a tendency to think finished files can simply be handed over as-is, but considerable organization work is actually required.

For example, in a 3-month website development project, hundreds of files are generated during production. Selecting "files to be handed over" from these, organizing them into understandable folder structures, and renaming files according to unified rules takes 1-2 days even for experienced creators.

What's further overlooked is "organizing licenses for libraries and fonts used." When web fonts and JavaScript libraries used during production require commercial licenses, separate license acquisition becomes necessary on the client side. This information organization and explanation is also included in handover work.

Cases where "agreeing to free handover but actually requiring a week's work, affecting other projects" are not uncommon.

Also, "requests for free support" after handing over production data is a major pitfall. Requests like "please do this small modification for free" come frequently, compressing actual production work.

Client Pitfalls

The most common misunderstanding on the client side is the assumption that "receiving data means immediate in-house operation is possible." Even after receiving source code or PSD files, considerable skill is needed to understand and properly update them.

In an actual case, a company that received e-commerce site source code handover had their internal engineer attempt customization, but the site stopped working, ultimately requiring external specialists for recovery. Recovery costs reached half the original production cost.

Cases of budget overruns from additional costs claimed by creators after demanding handover believing "PSD AI handover obligations" exist are also common. Especially when production data handover costs aren't included in budgets, approval processes take time, delaying project completion.

"Version management" of handed-over data is also an important challenge. When requesting additional modifications from the original creator after modifying files received from them in-house, confusion arises over which version to use as reference.

Common Pitfalls for Both Parties

Most dangerous is "ambiguous agreements through verbal promises." Light conversations during projects like "We can get the data too, right?" "No problem" create a sense of agreement without working out detailed conditions.

As a result, conflicts of "different from expected scope" and "didn't think costs would be this high" arise at the handover stage.

"Inadequate security considerations" are also easily overlooked. Production data may contain production environment configuration information or API keys, creating information leakage risks with inappropriate handover methods.

Methods like attaching production data to emails or sharing through cloud storage without password protection are security problems. Appropriate handover methods with proper encryption and access control need to be predetermined.

This section shows specific improvement measures applicable from the next project and review points for existing contracts.

Immediately Effective Contract Improvements

Adding just the following item to currently used contracts can dramatically reduce troubles:

"Regarding production data handover: Deliverable delivery under this contract does not include handover of source code and design data (PSD, AI files, etc.) used in the production process. When requesting handover of such data, separate consultation and additional contracts shall be concluded."

Adding just this sentence clarifies "no handover obligation" and provides basis for responding to subsequent requests.

For more detailed clauses, use the following template:

"Article ○ (Production Data Handling)

1. Party B shall hand over the following data to Party A: [list specific file types]
2. As handover costs, Party A shall pay Party B ○○,000 yen
3. Handover timing: Within ○ business days after deliverable acceptance completion
4. Handover method: Encrypted USB memory or secure file transfer service
5. Post-handover support: Respond to technical questions via email for ○ days"

Pre-Project Start Checklist

Before starting new projects, always confirm the following items:

□ Whether production data handover is desired □ Specific scope if handover is desired □ Budget securing status for additional costs accompanying handover □ Technical level and operational system of recipients □ Security requirements (encryption, access control, etc.)

Confirming these in advance prevents troubles in late project stages.

Items Clients Should Prepare

When desiring production data handover, client-side preparation is also necessary:

1. Establishing reception systems: Secure personnel and systems capable of properly managing and utilizing handed-over data
2. Advance budget securing: Include handover costs (approximately 10-20% of production costs) in budgets
3. Security policy organization: Consider handover methods matching internal security standards

Emergency Response Protocol

Response procedures when production data handover is requested without contract specification:

1. First check contracts: Clarify scope covered by current contracts
2. Organize handover possibilities: Identify files without technical or legal problems
3. Propose additional contracts: Calculate necessary work hours and costs, propose additional contracts
4. Agree on handover conditions: Confirm scope, costs, timing, and methods in writing

Maintaining Ongoing Relationships

Production data handover issues don't end with one-time arrangements. For maintaining long-term relationships:

• Regular contract reviews (approximately once yearly)
• Rule updates matching industry standard changes
• Accumulation of past trouble cases and improvement measures

Particularly when new file formats or development methods emerge due to technological progress, contract content must also follow suit.

Contractors should use improved contracts from the next project, and clients should consider necessity and costs of production data handover in advance. With this basic preparation, troubles over "source code handover" and "design data delivery" can be significantly reduced. Let's realize production data handover under conditions both parties can accept and build long-term trust relationships.