the change request workflow is the bit i needed most. i have been absorbing way too many "quick additions" without logging them, and then wondering why projects feel exhausting even when the client is lovely. the 30-minute threshold for when to absorb vs log vs formal-request is really practical — i am going to steal that. also the exclusions section in the scope doc is genius, most of my scope creep comes from things i never explicitly said were not included.

the change request form is genuinely underrated. i started using something similar about six months in and it completely changed how clients talk about "just one more thing." the trick for me was making it feel collaborative rather than bureaucratic, like a shared google doc where we log changes together rather than a formal approval process. way less friction and they still think twice before adding stuff.

the exclusions section in the scope doc is the thing i keep forgetting and it bites me every time. listing what you WON'T do is honestly more important than listing what you will — clients fill in their own assumptions otherwise. that landing page story at the start is painfully relatable, had almost the exact same thing happen on a project last year. saving the post-project audit template idea for sure