Service Delivery and IP Transfer Affidavit for Agencies

What a good one includes

• A clear identification of both parties and the specific master services agreement or statement of work being finalized.
• An exact technical catalog of the delivered assets, including specific repository URLs, commit hashes, database backups, and design file directories.
• An explicit, irrevocable statement of intellectual property transfer confirming that ownership of the code and digital assets has successfully migrated to the client.
• A formal declaration of completion confirming that all milestones and deliverables outlined in the project scope have been fully met.
• A liability waiver and 'as-is' acceptance clause, establishing a clean cutoff date for your delivery obligations and post-launch support.
• A sworn statement made under penalty of perjury, complete with a standardized notary block for official witness verification.

Common mistakes to avoid

• Writing broad, vague descriptions of the deliverables instead of listing exact code repositories, file paths, or system URLs.
• Forgetting to condition the intellectual property transfer on the receipt of the client's final payment, which can inadvertently surrender your leverage.
• Neglecting to have the document formally notarized, which strips the affidavit of its self-authenticating legal power in court or arbitration.
• Failing to explicitly state that the person signing has direct personal knowledge of the technical delivery and the authority to bind the agency.

Frequently asked questions