How to hand over an unfinished software project (complete checklist)
Package your half-built project so a new developer can run, change and deploy it without guessing: accounts, code, setup, known issues and a clean access plan.
ReadA custom web app is software written for one organisation's way of working: a booking system for a clinic, a quoting tool for a manufacturer, a members' portal, a niche marketplace. Stacks range widely, from Django and Laravel to Ruby on Rails, ASP.NET and Node.js with React. What these projects share is a single original builder and business rules that exist nowhere except in the code.
Bespoke builds are often deployed by hand, with files uploaded over SFTP or a script run on the server, and no separate staging environment. Business logic tends to be scattered across controllers, database triggers and front-end code. Configuration values may be hard-coded, and admin features the owner relies on daily are sometimes unfinished or hidden behind a URL nobody documented.
Write down each business process the app must handle, in your own words, including exceptions such as cancellations or refunds. Gather access to the repository, server, database and domain under accounts you control; the handover checklist generator produces a list tailored to your setup. Mention who uses the app today and what would happen if it went offline for an afternoon, because that shapes how carefully a developer must work.
Be the first rescue specialist here
Developers and agencies who finish other people's projects can create a free profile and list this as a specialty.
Package your half-built project so a new developer can run, change and deploy it without guessing: accounts, code, setup, known issues and a clean access plan.
ReadA calm, ordered plan for the day your developer goes silent: protect the domain and email first, then hosting, code, data and money accounts.
ReadSometimes. Your hosting account may hold the deployed code, which a developer can recover. If the app was compiled or bundled, recovery is partial. Check hosting access before posting and describe what you found.
A formal document is not required. A list of the business steps the app should support, from a user's first visit to the final outcome, is usually enough for a developer to plan from.