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.
Free template for designers
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.
The script
“Good idea. It is outside the current scope, which covers [summary from the proposal]. Two options: I write it up as a change request with a price and timeline, or we put it on the phase two list for after launch. Which works better for you?”
Agree with the idea, name the scope, offer two paths and let the client choose. Start nothing until approval is in writing, even small items.
Change request
- Project: [name]. Request: [CR-01]. Date: [date]. Requested by: [name].
- The change: [what will be built or changed, in plain language].
- Reason: [the business goal behind it].
- Estimate: [hours] hours at [rate] = [total]. [Fixed price, or estimate with a range.]
- Timeline impact: launch moves from [date] to [date], or “no change”.
- Dependencies: [content, access or decisions needed from the client, and by when].
- Not included: [what this change does not cover].
- Billing: [added to the next invoice, or deposit due before work starts].
- If not approved by [date]: the original scope and timeline stand, and this moves to phase two.
- Approved by: [name], signature: ________, date: [date]. Work starts on receipt.
Prevent the next one
- List inclusions, exclusions and revision rounds per phase in every proposal.
- Set one channel for requests, so nothing gets agreed in passing on a call.
- Log every request, even free ones, and show them on invoices as no-charge lines.
More templates
The rest of the kit
Launch day runbook and DNS cutover checklist
A timed launch plan from T minus 48 hours to the first week, including a DNS cutover that leaves email alone.
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.
Vulnerability report replies
Two replies for unsolicited security reports: a polite decline for beg bounty emails, and a professional acknowledgement for a genuine, detailed disclosure.
Website project contract outline
The topics a website design contract usually covers, from scope and payment to ownership, licenses, warranty and termination. An outline for your lawyer, not legal advice.
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.