Incident log and post-incident report
A running incident log to fill in while a site is down or hacked, plus a short post-incident report for the client: timeline, impact, cause, fix and the changes that stop a repeat.
Free template for designers
Website content collection checklist
Everything a client needs to supply for a new website, with ground rules and a deadline: copy, images with usage rights, brand files, legal pages, form settings and old site details.
Ground rules
- One shared folder for everything: [link]. Copy in documents, not emails.
- Content due by: [date]. Launch moves if content is late, day for day.
- One person collects and approves: [name]. Items waiting over a week get a nudge.
Pages and copy
- Final page list, with the sections each page needs: [Home: 6, About: 4, …].
- Copy for each page, with a headline and the action you want visitors to take.
- Service or product details: names, descriptions, prices, options.
- Team bios, hours, address, contact details and the FAQs you answer most.
- Reviews or testimonials you have permission to publish, with names as agreed.
Images and media
- Logo as SVG or a large PNG, plus any icon version.
- Photos as originals, not copies from social media or messaging apps.
- Proof you may use each image: yours, licensed stock or used with permission.
- A short description of each important photo, for alt text.
- Videos on an account you control, captioned if they include speech.
Brand, legal and settings
- Brand colors (hex codes) and font names, with license details for paid fonts.
- Privacy policy and terms from your adviser, or a decision on who supplies them.
- Form fields, where submissions go and who replies.
- Newsletter, booking, payment and map accounts, with access for [designer].
Moving from an old site
- Old site address and access, so nothing is lost: [details].
- Pages to keep, rewrite or drop, how many items move, and URLs still getting visits.
- Analytics and Search Console access, to see what ranks today.
Reminder email
Hi [name], still needed for [project]: [items]. To keep launch on [date], we need them by [date]. Stuck on anything? Reply and we will sort it.
More templates
The rest of the kit
Client leaving: website offboarding checklist
When a client moves on, a calm reply and a checklist for a clean, professional exit: accounts in their name, a tested backup, licenses sorted, your access removed and everything confirmed in writing.
Scope creep script and change request
What to say when a client asks for “one small thing” outside the project, plus a change request form with real fields.
Client access request email
A ready-to-send email asking a client (or a previous developer) for every login and account you need before you start, with safer ways to share each one.
Care plan tier sheet
Turn your care plan prices into tiers a client can compare: what each tier includes, task credits, add-ons and who may buy them, backups and response times.
Website proposal and scope of work outline
The sections a clear website proposal needs: summary, what is in and out of scope, revisions and timeline, client dependencies, price, deposit and milestone payments.