Audits rarely go wrong all at once. They drift. A deadline slips quietly, a request goes unanswered a little too long, a new name appears on the auditor's emails. Each sign on its own looks minor. Together, they are usually visible weeks before the problem becomes expensive.
Across responses involving a range of vendors and organisations, the same signals come up again and again. These are the ones worth watching for.
1. Deadlines move without anyone deciding to move them
An agreed date passes and nobody formally asks for more time. A request is "nearly ready" for a second week running. When dates drift silently, it usually means nobody owns the plan, or the plan no longer reflects reality. The fix is unglamorous: reset the dates explicitly, agree them with the auditor in writing, and resource them properly.
2. Scope creeps in conversation
An extra subsidiary, a second product, a longer lookback period. Each expansion tends to be requested informally and accepted informally. Ask anyone on the response team what the agreed scope of the audit is. If nobody can point to a written answer, scope is already drifting. Every change should be raised, assessed with your licensing specialists, and either agreed in writing or challenged.
3. The auditor starts talking to other people
Direct emails to a system administrator. A meeting request sent to a manager who was never part of the response. Sometimes this is innocent. Sometimes it is a sign the auditor is not getting what they need through the agreed channel. Either way, it fragments your response, and it is worth understanding why it is happening and closing the gap.
4. The same question gets asked twice
If the auditor asks for something you are sure you already provided, there are two possibilities. Either it was never sent, or it was sent and did not answer the question. Both point to gaps in how requests are logged and reviewed. Repeated questions are also an early sign that the auditor's working dataset and yours are diverging, which is how surprising draft findings happen.
5. Key people go quiet
The infrastructure lead stops attending the weekly call. The person who knows the contract history is suddenly unavailable. Audit fatigue is real, and it shows up first as absence. Left alone, it slows evidence gathering and pushes work onto whoever is left. Visible progress, a realistic plan, and sometimes a direct conversation with line management are what bring people back.
6. Leadership hears about it from somewhere else
If an executive learns something about the audit from the vendor's account team, from finance, or from a colleague before hearing it from the response team, reporting has broken down. That tends to trigger exactly what nobody wants: senior intervention, ad hoc meetings, and decisions made without the full picture.
What to do when you spot them
None of these signs is a crisis on its own. The mistake is treating them as noise. A short reset, often no more than a fresh look at the plan, the request log, the scope, and the stakeholder list, is usually enough to bring a drifting response back under control.
The harder question is who notices. In most organisations, the people doing the audit work are too close to it, and too busy, to see the pattern forming. That is one of the clearest arguments for having someone whose job is to watch the whole response, not just their part of it.