The first decision in a new project tends to get plenty of attention. The last one often arrives quietly. Work slows down, the person who owned it moves on, and a page stays online because nobody is quite sure what should replace it.
Closing a project is not one switch. Its website, forms, inboxes, accounts, supplier services and stored data can all carry on after the actual work has stopped. A tidy close protects people from stale promises and gives the business a useful record of what happened.
This project closure checklist is for a project, service or brand within a small business portfolio. It is not a substitute for legal, accounting, tax or data protection advice. If the work sits inside a separate company, involves debt or has regulated responsibilities, get the right professional help.
Write down the decision before touching the website
Start with a short closure note. Name the decision maker, the person responsible for the close, the effective date and what the decision means.
A project might be:
- paused with a review date;
- closed to new work while existing commitments are completed;
- absorbed into another service or brand;
- retired, with a historical record kept;
- connected to a company that needs separate legal or accounting action.
Those are different states. Calling all of them closed creates confusion later, especially when somebody finds an old account, invoice or enquiry.
Stop taking new work you cannot fulfil
Public promises need attention before the design does. Check buy buttons, booking links, registration forms, price pages, app listings, contact forms and automated emails. If the project can no longer accept an order or enquiry, do not leave the route open while a polished farewell page is being written.
Give visitors a plain answer. Say whether the project is closed, paused or now part of something else. Add a suitable contact or replacement route only when somebody is responsible for it. Avoid language that makes a historical project sound available.
MightyGroupUK’s live website uses this distinction. Our Brands shows the four current ventures, while Our Story keeps earlier ecommerce and personals work in the group’s history. The history remains useful without sitting in the current shop window.
Find the project in all the unglamorous places
The main website is only the obvious part. Make a list before cancelling or deleting anything, then record who has checked each item.
- website pages, navigation, footers and redirects;
- forms, email sequences and calendar links;
- shared inboxes, telephone routes and voicemail;
- social profiles and directory listings;
- payment services, subscriptions and supplier portals;
- domains, hosting, apps, analytics and advertising accounts;
- templates, proposals and internal documents;
- references on a parent site or another brand’s website.
Keep one closure register rather than relying on memory. A related MightyGroupUK guide explains how clear content ownership helps several business websites stay accurate. The same principle matters during closure because one forgotten copy can keep attracting the wrong enquiry.
Handle personal data by purpose, not habit
Do not keep every export simply because storage is cheap. Equally, do not delete records before checking whether there is a lawful or operational reason to retain them.
Article 5 of the UK GDPR includes the principles of data minimisation, accuracy and storage limitation. A closure record should identify the personal data held by the project, why it is still needed, who owns the decision and when it will be reviewed or deleted. Retention periods depend on the type of record and the reason for keeping it, so a general checklist cannot set them.
Check live forms and integrations too. Closing a front-end form is not enough if data continues to arrive in a mailbox, spreadsheet or third-party tool. Update the relevant privacy information when the handling of personal data changes.
Transfer access and assets without copying secrets into the checklist
A named owner should take responsibility for the accounts and assets that remain. That may include domains, website hosting, files, design source material, software repositories, social accounts and recovery details.
Record where access is managed, not the password itself. Move credentials into an approved secret store, remove access that is no longer required, and check that recovery email addresses and telephone numbers still reach the right person. Domains and paid services also need a deliberate decision: renew, transfer or allow them to end on a recorded date.
Before cancelling a service, export the records or assets that genuinely need to be kept and confirm that the files can be opened. A backup nobody has tested is a hopeful assumption, not a handover.
Finish the money, supplier and legal admin
Prepare a short list of outstanding invoices, credits, refunds, subscriptions, contracts, licences, physical assets and records needed for tax or accounting. Give each item an owner and a completion note.
Closing a project is not the same as closing a legal entity. GOV.UK’s guidance on closing a limited company explains that the route depends on the company’s circumstances, including whether it can pay its bills. It also describes dormancy as a separate option. If a project is tied to a limited company, debt, employees, regulated work or contractual commitments, deal with those duties separately rather than assuming that an archived website finishes the job.
Keep a short, honest history
Closure does not make all earlier work worthless. Keep a factual summary that answers a few useful questions:
- What problem was the project intended to solve?
- Who was it for?
- What was actually built or operated?
- Why was it paused, absorbed or retired?
- Which lessons, records or assets remain useful?
- Where is the authoritative archive?
Write what can be supported. Do not turn a closure note into a success story by adding results, customer claims or reasons that were never recorded. A simple history helps future decisions because people can see what was tried without mistaking it for a current offer.
Check the result after the close
Once the changes are in place, test the old customer journey. Follow links from search results, parent pages, social profiles and saved emails. Submit only safe test forms that are meant to remain active. Check redirects, automated replies and contact routes. Then repeat the review later, because cached search results and forgotten renewals can reveal loose ends after the first tidy-up.
A good close is fairly quiet. Visitors get an honest answer, the business knows what it still owns, and useful history is kept without leaving an abandoned offer online.