What a Chief of Staff Does for a Finance Leader

A chief of staff works for one senior person, called the principal. In this course the principal is you: a CFO, controller or finance lead. McKinsey bases its description of the job on forums with more than 200 chiefs of staff, and it says the role exists to make the principal as effective as possible.

Picture the third working day of close. The pack goes to the CFO tomorrow. Two bank reconciliations are still open, the auditors want three items on their request list by Friday, and a lender has asked when the covenant certificate will arrive. A good chief of staff doesn't do the accounting. They make sure you see the right things in the right order and that nothing gets dropped.

Over this course you'll build an AI version of that role. It prepares the work, and you decide and send.

The whole course runs on one rule from the Finance track: sign only what ties out. To tie out a figure is to trace it back to its source and confirm it agrees. AI can produce a number in seconds, but only a person can stand behind it.

McKinsey's research and its 2024 podcast with senior partner Andrew Goodman describe the regular work of a human chief of staff. It comes down to seven duties:

1. Information and paper flow. Preparing and filtering what reaches the principal, including board materials and inputs to key decisions.
2. Air traffic control. Managing the flow of the principal's work and actions. The phrase is Goodman's own.
3. Meeting prep and the record. Making sure the principal arrives prepared, and keeping a record of what was said and agreed.
4. Peripheral vision. Acting as the principal's eyes and ears so there are no surprises. Senior people tend to bring the boss good news, so this also means reporting what is really happening on the front line.
5. Calendar against the business cycle. Lining time up with planning, executive and board cycles, and scanning ahead each week.
6. Priorities and lists. Holding the principal to a small set of priorities.
7. Follow-through and handover. Tracking what was agreed and, when the role changes hands, writing down the key past decisions.

McKinsey also describes the chief of staff as an adviser who gives candid feedback.

Each duty has a direct equivalent in a close and reporting calendar.

• Air traffic control becomes close calendar control. Every close task has an owner, a due date and evidence that it's done.
• Follow-through becomes tracking who owns each reconciliation and each variance explanation, and chasing what's late.
• Meeting prep and the record becomes audit-committee and lender prep, plus a clear record of what was agreed.
• Handover and past decisions becomes a judgment log: the accounting judgments made, who made them and on what evidence.
• Peripheral vision becomes watching for unusual payment requests, such as a supplier suddenly asking to change bank details, or an "urgent, keep this quiet" payment demand.
• Calendar against the business cycle becomes the close kickoff a few days before month-end and the countdown to each quarterly audit committee.
• Information flow becomes filtering what reaches the CFO, so the pack's inputs arrive complete and nobody gets buried.

In later lessons you'll turn each of these into a routine your agent runs.

One chief of staff in McKinsey's forum kept the principal to five or six priorities, split into outward-facing ones (auditors, lenders, the board) and inward-facing ones (the close, the team, systems). Another kept a three-column list: now, soon and never.

The never column is the one people skip, and it's the useful one. It records things that came up but won't be done, so they're written down instead of forgotten.

Here's an example. During a walkthrough, the audit senior mentions in passing that the cost-centre hierarchy could be cleaner. You decide it isn't a priority this year. If nobody writes that down, it comes back in three months as a surprise, or a new controller inherits it without context. On the never list it reads: "Cost-centre hierarchy cleanup. Raised by audit senior during walkthrough. Not pursued this year: no impact on reported figures. Revisit at next year's planning."

The entry protects you. It shows the point was heard and a decision was made on purpose, and that matters at handover.

McKinsey is just as clear about the limits of the role. A good chief of staff:

1. Does not decide for the principal. The scope and decision rights are agreed explicitly at the start and revisited as the role changes.
2. Does not blur whose voice it is. People respond to a chief of staff because of halo authority, the weight they borrow from the boss. So the chief of staff has to be clear about when it speaks for itself and when for the principal.
3. Does not play politics. It sits with the leadership team but stays independent of it.
4. Does not isolate the principal. Guarding the principal's time is part of the job, but their office shouldn't become an island.
5. Does not make itself the story. As one chief of staff put it, the job is to make the principal look good, not yourself.

In finance, imagine Commercial blaming freight for a margin drop while Operations blames discounting. A chief of staff that sides with one team is playing politics. Sending the auditor a line that sounds like the CFO's position is blurring the voice. In both cases the job is to set out the disagreement and leave the call to the principal.

Finance already has a way to keep preparing separate from deciding: segregation of duties. The person who prepares a reconciliation is not the person who approves it. Your AI chief of staff fits into that structure as an extra preparer. It never replaces the approver.

In practice, the agent drafts the close status note, the variance-explanation requests or the audit-committee prep. Someone checks each figure and claim against its source. The approver reviews it. A named person releases it. If a figure in the prep note doesn't trace back to the ledger export or the reconciliation file, it doesn't go in front of the audit committee, however polished it looks.

That's what "sign only what ties out" means in daily work. Every lesson after this one adds a safeguard for it: source tags, "not found" instead of a guess, drafts held for approval, and statuses like "proposed" and "done (claimed)" that only a person can upgrade.

The next lesson splits the work into what you can safely hand to an AI and what stays with people.