I spent an afternoon reading feature pages. Not ours. Everyone else's. And somewhere around the fourth one I noticed that nearly everything on them is about the past.
A budget alert fires after the hours are spent. A profitability report tells you a project lost money after it did. An AI summary condenses a thread after the conversation happened. An automatic check-in asks the team what changed, after it changed. A dashboard shows you drift once it's large enough to show up in a chart. None of these are bad. They are autopsies.
Why every tracker is a rear-view mirror
It isn't laziness on anyone's part. A tracker can only know what someone typed into it, and people type things in after they happen. That's the whole design. The information that would have predicted the problem was never in the tool. It was in a sentence on a call, or the fourth paragraph of a client email, or a hallway conversation somebody meant to write up.
So the tool is honest about the past and blind to the present. Which is fine for work that goes wrong slowly and visibly, like a schedule slipping a day at a time. It is not fine for advisory work, where the things that go wrong are quiet.
What actually goes wrong on an engagement
Not capacity. Not the critical path. In fixed-scope client work, three things cause almost all the damage:
Scope moves in a sentence. Someone on the client side says "while you're in there, could you also look at..." and everybody nods. Nobody calls it a change. Three weeks later it's a workstream.
Decisions get made and never land. The sponsor answers a question in an email reply. It's a real decision. It also lives in one inbox, unlinked to the plan, and the person who made it will not remember making it.
The sponsor changes. A new stakeholder arrives, and every sign-off that came before them turns into "I wasn't part of that." If you can't show when it was agreed and by whom, it wasn't agreed.
None of those show up in a budget alert until months later. By then the argument is not about the work. It's about whose memory is right.
The earlier warning
The moment to catch all three is the same day, and it is not complicated. Read your own transcript or notes within a day of the call and look for exactly three things: anything that changes scope, anything that is a decision, and anything anyone committed to. Write them down in the same place the plan lives. Then ask for sign-off on the ones that matter, that week, while everyone still remembers the conversation.
This works with a notebook. It works in any tool on our compare page. The problem is not that consultants don't know to do it. The problem is that it is admin, and admin loses to client work every single time. That's the honest reason plans drift.
The record
Now the second half, which almost nobody talks about on a feature page: what happens when something goes wrong anyway.
Every consultant has had the conversation. "You never told us that." "We didn't agree to that." "That wasn't in scope." The strength of your position in that conversation depends entirely on what you can show, and a Slack scrollback is not a record. Neither is a task marked done.
A record that holds up has four things in it. When the information was provided. What was actually said. Who signed off, and on what. What was scoped, against a baseline set at the start. And ideally a fifth: the line in the transcript or the email it came from, so nobody has to take your word for it.
If you keep that, the "you never told us" conversation takes about a minute, and it tends to be a polite one. If you don't, it takes a week and a discount.
The part underneath both
Prevention and the record are the same discipline. You can only notice that scope moved if you wrote down where it started. You can only flag an unclosed decision if you logged it as open. The record is not paperwork you keep in case of a dispute. It's the thing that makes the early warning possible.
That's the job we built Willie to do. She reads the transcript and the email the day they arrive, flags the scope move and the open decision before they become a problem, and keeps the log: who said what, when, and why, with every entry linked back to the line it came from. Every scope change, every decision, every status update goes through you first. Nothing enters the record you didn't approve, which is exactly what makes the record worth having.
But the discipline works without us. Read the transcript the same day. Write down the three things. Get the sign-off this week. Start there.