What belongs in the first client note?
Start with what is happening now, who feels the friction, what has already been tried, and any real constraint. This gives the conversation more signal than a premature feature list.
- Describe current reality.
- Name the affected people.
- List prior attempts.
- State the constraint and decision date.
Write a four-paragraph discovery note using one sentence for each step.
How do you protect the proof boundary?
Separate delivered scope from claimed outcomes. A live website, a private dashboard, and supplied client feedback are different forms of evidence and should be described differently.
- List visible deliverables.
- Label private work as private.
- Attribute supplied proof.
- Remove unsupported metrics.
Audit one portfolio description and underline every sentence that needs a source or attribution.
What makes a handoff durable?
Ownership must survive the project. Record who controls the domain, repository, hosting, analytics decisions, content, and operational recovery before the work is called complete.
- Map account ownership.
- Document the release path.
- Record rollback and recovery.
- Teach the next operator.
Make an ownership table with one accountable person for every system the work depends on.