--- title: "The Audit That Closes the Gap Between Claims and Reality" url: "https://cooinsider.com/insight/the-audit-that-closes-the-gap-between-claims-and-reality/" author: "Lilach Bullock" published: "2026-09-25" updated: "2026-09-25" --- # The Audit That Closes the Gap Between Claims and Reality ### **Why I stopped trusting a team's own capability rating** One client I advised as fractional CMO, a mid-sized e-commerce business, had rated their own customer fulfilment capability as strong on an internal scorecard. I asked one plain question in the review meeting. What was the actual on-time dispatch rate last quarter? The answer came back at 67 percent. Those two things cannot both be true, and nobody in the room had put them side by side before I asked. That gap is the reason I no longer take a team's self-rating at face value in any audit I run. A label like strong or on track tells me what a department believes about itself. It tells me nothing about what a customer went through that week, and it is usually written by the same team whose performance it describes. ### **The three-column method, claimed capability, measured output, industry benchmark** The fix I use now is simple to describe and slightly uncomfortable to run. Three columns on one page. Column one is the capability as the team itself would describe it, in their own words, taken from whatever they already report upward. Column two is the measured output, the raw number pulled from the system of record, not a summary someone typed up for the meeting. Column three is the industry benchmark for that same metric, so there is something outside the building to compare against, not just last quarter versus this one. With fulfilment, column one said strong. Column two said 67 percent on-time dispatch. Column three, the benchmark for that category, sat well above where they were. Forcing all three onto one page in front of the team is what did the work. Nobody had to be convinced of anything by me. The columns did it, because the gap between column one and column two was the whole argument. ### **What forcing the comparison revealed, and the bottlenecks it let us fix** Once the three numbers sat next to each other, the conversation changed from is fulfilment fine to where exactly it was breaking. We could point at three specific capacity bottlenecks inside the fulfilment process itself, rather than argue about whether there was a problem at all. That is the real value of the method. It does not diagnose anything by itself. It just makes the argument impossible to avoid, which moves a meeting from defending a rating to fixing a process in about the time it takes to read one page. Over the following six months, on-time dispatch moved from 67 percent to 89 percent. That is the number that mattered to the board, and it only moved because the audit made the bottlenecks visible enough to fix one at a time rather than all at once. ### **Turning the audit into a habit, the monthly 30-minute review** In my own business I run a short monthly review, about thirty minutes, looking at which channels are sending traffic, how many of those visitors turn into enquiries, and how many enquiries turn into paying customers. It has saved me from wasting money on channels that looked healthy at the top of the funnel and fell apart further down where nobody was checking. I run the same three-column comparison against any audit I have already closed out, not just once at the start of it. A rating that was accurate in January is not guaranteed to still be accurate in June, and the only way I know that is to keep checking the claim against the number rather than trusting that a fix, once made, stays made. ### **Why the fix only held once we stayed on the account long enough to close it** The audit found the bottlenecks quickly. Closing them took the full six months, not a single fix in week one. I say if you cannot measure it, do not do it, and that rule cuts both ways on an audit like this. It is not enough to measure the problem once at the start. Each bottleneck had to be checked again against the same number before I would call it closed, which is slower than declaring the fulfilment issue solved the day the first change went in, but it is the only version of closed that held past the next quarter. ### **What I now put in front of a COO and board before they ask** I bring the three-column page itself, not a narrative version of it, so claimed capability, measured output and benchmark sit next to each other on paper before anyone asks a question. Alongside it I bring whatever the monthly review has turned up that month, thirty minutes, three numbers, compared against each other rather than against a feeling. Between the two, most of the awkward questions get answered before a board meeting starts, which is a better use of thirty minutes than defending a scorecard nobody had checked. --- [Lilach Bullock](https://www.lilachbullock.com) is an AI implementation consultant and fractional CMO with 21 years in marketing. She helps business owners put AI to work across content, SEO, social media, email marketing, automation and lead generation. Her work has been featured in Forbes, the BBC, The Times, The Guardian, The Telegraph, WIRED, HuffPost and the Content Marketing Institute, and she has worked with Twitter, IBM, Dropbox, monday.com, Hootsuite and Greenpeace. Forbes named her a Top 20 Social Media Power Influencer worldwide. Based in Israel, she works with US, UK and international clients.