What belongs in a software copyright registration dossier?

A software copyright registration dossier needs the application form, a copy of the program, and documents identifying the author and owner. The exact ownership papers differ where the software was created personally, by employees, or by contractors, so verify ownership before filing.

A software copyright dossier consists of the application form, a copy of the program, and documents proving who the author and owner are. The difficult part is usually not the source file but ownership where employees, co-authors or contractors contributed. Settle that relationship before signing the form.

Preparation checklist

  1. Application form using the correct computer-program category and applicant.
  2. Copy of the software in the format required by the receiving authority, with enough description to identify the work.
  3. Author and owner details consistent across the form and supporting documents.
  4. Proof of the right to apply where the applicant is not also the author: an employment agreement, commission, assignment or co-author agreement as the facts require.
  5. Power of attorney where a representative files.
  6. Consents from relevant parties where there are several authors or owners.

Check the protected categories of works before choosing the category. Where employees or freelancers wrote the code, read author and copyright owner before collecting documents.

Preparing the source code

Prepare a copy that identifies the program, removing access secrets, API keys and personal data before producing the filing copy. Do not treat this post as a fixed page-count rule: filing specifications can change, so check the published form and guidance when you submit.

Cost and timing

This post does not reproduce a fee or processing period. Use the cost estimator for the current fee data and the protection-term tool for the relevant protection timeline. Legal figures remain in the source articles and YAML rather than this checklist.

Self-file or seek help?

A dossier with one author, one owner and a clear creation history is often manageable without assistance. Consider support where several contributors, layered commissioning contracts, assignments or an investment transaction complicate ownership.

Sources