6.4Toolbox
The essentials in 30 seconds
- A checklist protects you from memory: the same critical points come back on every project.
- Three key moments: before launch, every month, before a migration.
- A living toolbox: you adapt it after every incident, otherwise it becomes decoration.
Samir thread — the everyday toolbox
Samir has gathered his reference points into a small toolbox: a launch checklist, a monthly routine, a migration checklist and a handover sheet. Nothing spectacular, but everything that saves him from reinventing the wheel and discovering a problem at the client's end.
A toolbox only has value if it is used: four applied reference points are better than twenty forgotten ones.
Why a toolbox
The same questions come back on every project: is the domain active? does the form really receive messages? is the backup tested? A checklist avoids depending on memory and on the mood of the day.
Three moments, three lists
Before launch, you check that everything is ready. Every month, you maintain. Before a migration, you secure and prepare the rollback. Three different moments, three different lists — mixing them makes you forget the essentials.
Keeping the lists alive
After every incident, Samir adds a point to the relevant checklist. The toolbox becomes the project's memory: it improves with experience instead of ageing.
Before launching a site
- Domain and HTTPS active, www redirect chosen
- Key pages proofread, responsiveness checked on mobile
- Form tested with real receipt
- Basic SEO: titles, descriptions, sitemap
- Automatic backup enabled and restoration tested
- Access documented and client trained
Every month
- Full backup and disk space check
- Minor updates applied, major ones tested
- Abandoned plugins identified
- Form and checkout journey tested
- Administrator accounts and permissions checked
- Simple report sent to the client
Before a migration
- Full backup and site export
- URLs and permalink structure noted
- DNS and TTL prepared
- HTTPS and emails checked on the destination
- Key journeys tested after import
- Old site kept until validation
Ready-to-say script — presenting your method (25 s)
“I have three checklists: launch, monthly maintenance and migration. They prevent critical points from being forgotten and let me tell you exactly what has been checked.”
Keep this to reassure a client about the rigour of the follow-up.
Ready-to-say script — explaining maintenance (20 s)
“Every month, I back up, test the updates and check the form and the shop. You receive a simple report.”
Link the checklist to a concrete benefit for the client.
Copy-paste template — monthly report
MONTH: _______________
BACKUP: OK / to review
UPDATES: core ____ theme ____ plugins ____
TESTS: form ____ shop ____ login ____
INCIDENT: _______________
ACTION: _______________
NEXT CHECK: _______________Copy-paste template — handover sheet
SITE: _______________
DOMAIN / HOSTING: _______________
ADMIN: _______________
CHILD THEME: _______________
PLUGINS: _______________
BACKUPS: _______________
CONTACTS: _______________
PROCEDURES: _______________Small business / tight budget
A one-page launch checklist and a monthly routine are enough to cover the essentials.
Shop
Add a complete order test to every critical update.
Non-profit
Add volunteer account management and access handover.
Agency
Standardise the checklists for the whole team and attach them to the contract.
48h challenge — apply tomorrow
Create your three checklists (launch, monthly, migration) and apply one to a real site. Note the point that was missing. 25 minutes.
- I have checklists for the key moments.
- I adapt the lists after every incident.
- I can prove what has been checked.
What is a launch checklist for?
A short checklist that is applied is better than a perfect procedure never opened. Start with five points, then build on them.