“Looks good” can mean several things during a website project. A client may like the colour palette while expecting another round on the mobile layout. If that message becomes the only approval record, development can move ahead on an assumption neither side intended.

A useful approval note answers four small questions: what was reviewed, which revision was shown, who could approve it, and what decision was made. Keep the link to the actual design or staging page alongside the note. A screenshot in a chat thread is difficult to interpret once the live design has changed.

Give the decision a home

Consider a service-page redesign. “Review service page” is too broad to close confidently. A better task might ask the client to approve the content order in revision 3, with the mobile navigation explicitly left for a separate review. The response then closes that decision without quietly approving the entire page.

For freelancers using Notion, a client–project–task structure provides a workable starting point. It keeps tasks associated with the project and the client rather than scattering approval notes across unrelated pages. The linked resource explains how to build the tracker; it should be treated as a setup guide, rather than a finished workspace that automatically manages approvals.

Record requests for changes separately from the decision itself. Each request needs an owner and a next action. “Replace the hero image after the client supplies the licensed file” carries more information than “image pending”. If the request changes the agreed scope, resolve that point before treating it as routine production work.

At handover, read the record from the perspective of someone who missed the calls. Can that person identify the approved revision and the remaining exceptions? If not, add the missing context while it is still easy to confirm.

NotionSolutions, an independent Notion publication, has further guides on connected records, client access and ongoing project reviews. Whatever tool holds the notes, the goal is the same: make the decision understandable without asking everyone to reconstruct the conversation.