Software Project Contract and Delivery Checklist

Most disputes in software projects do not begin with broken promises. They begin with things nobody wrote down clearly. This checklist comes from a software engineer’s point of view and does not replace legal advice. For the final contract, especially on large projects, talk to a lawyer.

Scope

• List the first version’s features or scenarios. A clear project brief can be attached to the contract.
• State what is not included, such as content writing, logo design, or server costs.
• Describe how changes work: how is a new request reviewed and priced?

Ownership and access

Never postpone this part.

• Who owns the code after final payment?
• Keep the repository on your account from the start, or at least transfer it at delivery.
• Register domains, servers, payment gateways, and service accounts in your own name.
• Note which libraries or existing code are used, and under what licences.

Schedule and payment

Tie payments to visible deliveries, not to the passing of time.

1. A deposit to begin
2. Payment after each stage is delivered and approved
3. A final amount after testing and the handover of access

Give each stage a date and a defined output. Also state how late feedback or information from the client affects the schedule.

Delivery criteria

“Done” must have a precise meaning.

• Main scenarios are tested on the final version in the real environment.
• The review period and the way to report bugs are defined.
• Setup, installation, and backup documentation is delivered.

If the system cannot be brought up on a new server without the current developer, delivery is not complete.

After delivery

• How long is the free bug fix period, and what exactly does it cover?
• What do support and response times cost after that?
• Who handles backups and security updates?

Confidentiality and ending the work

Consider a non disclosure agreement for your idea and data. State how completed work is valued if the collaboration ends early, and how code and access are handed over.

For each clause in depth, read 12 clauses that prevent disputes. If you have not chosen a developer yet, read the guide to outsourcing a software project. To talk about your project, get in touch.