Running an audit committee when the auditor is new to the firm

A new auditor arrives with fresh eyes and no institutional memory. That sounds like an advantage. Often it is. But it changes the audit committee's role in ways that matter more than most chairs recognise. The committee cannot lean on the shorthand that built up over years with the previous firm. No one knows which questions are the old ones, asked because they used to matter, and which ones genuinely test the business. The committee has to think again about what it is auditing for.

The first task is not to educate the new auditor about the firm. It is to ask the new auditor what they see that the previous firm missed. This is not a rhetorical courtesy. A new firm will have worked with dozens of competitors and peers. They will have spotted patterns in your operation that looked normal to you because they were normal to you. Bring that out early. Ask them what surprised them in the planning phase. Ask what they expected to find and did not. The answers shape the season's work.

The second task is to clarify the audit committee's own remit with precision. Many committees find that the previous auditor had gradually taken on work that was not technically audit work. They had become a sort of quasi-internal function, flagging operational issues that belonged to management or internal audit. A new firm will not assume this. You have to decide whether you want it. Sometimes you do. If you do, say so explicitly in the engagement letter or in an amendment to it. Make it a scope decision, not a drift.

The third task is to reset the pace of reporting and escalation. How frequently does the committee need to see the auditor. What is the threshold for an issue to come to the committee chair outside the formal meetings. What constitutes a finding versus a query versus a recommendation. The previous auditor had a rhythm with your board. The new one does not. You have to build it. Do this in writing. Document the standard. It feels pedantic. It is not. It removes ambiguity when something goes wrong.

Where new auditors often stumble is in understanding the firm's tolerance for friction with management. Every audit involves points of debate between the auditor and the finance team. Previous auditors knew where your leadership would push back and where they would yield. New auditors do not. They may come to the committee with a finding they think is material, when the firm's culture is to treat it as immaterial. Or they may soften a recommendation, when the committee would prefer directness. Use the first six months to establish this. Tell the new auditor where you stand. Tell management where the committee stands. Be explicit about the trade-offs.

A regulated firm is watched more closely on its audit relationship than on most other things. The FCA expects the audit committee to engage rigorously with the external auditor. That engagement looks different when the auditor is new. The committee needs to show it has asked harder questions, not softer ones. The committee also needs to show it has not simply adopted the new auditor's framework without testing it. Use the first year to build a relationship that is collegial but not deferential. That distinction matters in the file.

The most useful thing an audit committee can do in the first year with a new firm is to set a standard for the second year. If the first year is reactive, the second year is reactive. If the first year establishes what good looks like, the second year can build on it. Do not assume the new auditor will remember what you discussed informally in September. Document the decisions. Confirm the scope. Then in the second year, hold both the auditor and the committee to that standard. That is when the relationship becomes genuinely useful.