Every agency has a version of this story. The client approves a direction on a call. The team builds it. Three weeks later, in the review, the client says "we never agreed to that". Nobody in the room can prove otherwise, so the agency eats the rework, the timeline slips, and the relationship gets a little more guarded.
It is rarely bad faith. The client's memory is honestly different: they remember the concern they raised, not the yes that followed it. The agency's memory is different too, and it is no better as evidence. What is missing is a record both sides would accept.
This post follows one approval on a made-up project, from the call where it was given to the review where it was questioned. Then it shows what changes when the approval is kept with its source.
The usual way it goes wrong
The project is a brand refresh for a client we will call Kestrel. Dana is the client's marketing lead. Ana runs the account at the agency, and Jonah is the designer.
On 9 October, on a video call, Jonah shows two cuts of the launch film: 30 seconds and 45 seconds. Dana worries the short one loses the product shot, Jonah shows how the shot moved earlier, and Dana says: "Okay, that works. Let's go with the 30-second cut for the launch."
Here is what usually happens next:
- Ana writes "Dana OK'd 30s" in her notebook.
- Jonah starts the edit that afternoon.
- The follow-up email says "Great call today, we'll move ahead with the film as discussed".
- Dana's colleague in sales, who was not on the call, still has the 45-second version in the retail plan.
On 30 October, the sales colleague asks why the film is shorter. Dana does not remember saying yes to 30 seconds; she remembers worrying about the product shot. The email says "as discussed". Ana's note says "OK'd" but not what was said. The agency re-cuts the film.
Nothing here was careless. Each step is how most teams work. The gap is that the approval only existed in the conversation, and conversations don't keep.
Step 1: the call is captured
Now the same call, with Velkri's notetaker in it. Ana added it from her calendar, and it joined the call as a participant. It records and transcribes the call, then picks out what sounds like decisions and actions.
Shortly after the call there is a recap with the decision and the actions, each with the time in the call it came from. Nobody had to stop and write.
Step 2: someone on the team confirms it
A recap is not a record yet. Velkri shows the decision as a proposal, and a person decides what happens to it. Ana was on the call and knows what Dana meant, so she is the right person to confirm it. She can confirm it as it is, edit it first (for example to add "with the product shot at 0:04"), or dismiss it if it was only an idea.
Confirming is deliberate. The software noticed that something sounded like an approval; a person who heard it says that it was one. Only what someone confirms goes on the project's record.
The confirmed decision now sits on the project's timeline. The timeline shows what was decided, who confirmed it and when, and the decision links back to the call. Ana spent about ten seconds on it.
Step 3: the client can see it too
Agencies often keep the client out of their workspace, which means the record is something only the agency can see, and it is easy for a client to doubt a record they have never seen.
In Velkri, Dana can be a guest in the Kestrel project. Guests see that one project and nothing else in the workspace. They can read, chat in the project channels they are invited to and upload files, and they are not billed as seats. They cannot confirm proposals: that stays with your team.
So Dana can see the decision the day it is confirmed, with the link to the call. If she remembers it differently, the moment to say so is now, while the edit is a day old, not three weeks later.
Step 4: three weeks later
On 30 October the question comes up again. This time Ana does not search her notebook. She asks the project.
The answer quotes what was decided and footnotes where it came from. The first footnote opens the recording of the 9 October call at the point Dana said yes. Ana sends the link to Dana and her colleague in sales.
The conversation that follows is short and friendly. Dana listens to the twenty seconds, remembers, and tells sales the 30-second cut is the one. Nobody had to win an argument, because there was nothing to argue about.
What changed, and what didn't
It is worth being clear about what made the difference, because most of it is habit rather than software.
The approval was captured where it happened. The call was the source, so the record links to the call. A summary written afterwards would have been one more memory.
A person who was there confirmed it. That is what makes the record something a client accepts. "The tool thinks you said yes" would start a different argument.
The client could see it early. A record a client sees on the day is one they can correct on the day.
Changes add a row, they don't erase one. If Dana later asks for the 45-second cut after all, that is a new decision with its own date and source. Velkri proposes it as replacing the first one, and once someone confirms it, the first one stays in the history instead of being deleted. Scope changes become visible instead of silent.
If you want to start without new software
You can get most of the way with discipline and a shared document:
- At the end of every client call, read the decisions back out loud: "So we're agreed: 30-second cut for launch, product shot moved to 0:04."
- Send them in writing the same day, one line per decision, with the date of the call. Our free client call notes template has a section for exactly this.
- Ask the client to reply if anything is wrong. Silence after a clear list is far stronger than silence after "as discussed".
- Keep one running list per client project, so the decisions don't live in twenty email threads.
The hard part is doing it after every call, including the rushed ones. That is the part Velkri does for you: the notetaker takes the notes, the team confirms, the client can see it, and the link to the call is there when the question comes back. See how it fits an agency's week on the agency page.