Hiring a controller takes months of searching, and then the hard part starts. A new controller walks into a close calendar that is already running, a team they did not hire, systems they did not configure and habits nobody wrote down. If the first quarter is unplanned, one of two things usually happens. Either the controller spends weeks just keeping up with the next close and never gets to the problems you hired them to fix, or they change too much too fast and the team loses confidence in them.

A simple 90 day plan prevents both. This guide is for CFOs, owners and finance leaders who have just hired a controller, or are about to, and want the first three months to produce a clean close, a clear picture of risk and a short list of agreed improvements.

Key Takeaways

  • Prepare access, documents and introductions before day one so the controller can observe a full close in the first month.
  • Give the first 30 days to learning and listening, not to redesigning the close.
  • By day 60, the controller should own the close calendar and have a written view of control gaps.
  • By day 90, agree on a short, prioritized improvement plan with owners and dates.
  • Hold short weekly check ins and a formal review at each 30 day mark so problems surface early.

Before day one: set the controller up to observe a real close

The most useful thing a new controller can do early is watch a full month end close from start to finish. That only works if access and context are ready. Before the start date, line up:

  • System access: the general ledger, AP and AR modules, payroll reports, bank portals in view only mode, the expense tool and the shared drive or document system.
  • The current close calendar and checklist, even if it is informal or out of date.
  • The last three to six months of financial statements, account reconciliations and management reports.
  • The most recent audit or review letter, management letter comments and any open items from your outside accountants.
  • An organization chart for finance, with each person's main responsibilities.
  • A list of key outside contacts: the audit or tax firm, the bank relationship manager, the payroll provider and the benefits broker.

Decide, too, what authority the controller has on day one and what waits. Approval limits, bank signing authority and payment release rights should be deliberate decisions, not something granted by default because a password was shared. Give bank and payment permissions in stages once the controller understands your approval workflow.

Days 1 to 30: learn the business and the close

The goal of the first month is understanding. A new controller who starts rebuilding processes in week two is guessing. Give them a clear assignment instead:

  • Meet one on one with every member of the finance team. Ask what they do each day, where they get stuck and what they would fix first.
  • Meet the operations leaders who generate the numbers. In a construction company, that means project managers and the people who handle job costing, change orders and pay applications. In a professional services firm, it means whoever approves time, billing and collections.
  • Shadow the full month end close and take notes on timing, handoffs, manual workarounds and where reconciliations stall.
  • Walk through the chart of accounts and the main revenue and cost flows, from customer contract to cash and from purchase order to payment.
  • Review the payroll and payroll tax process with whoever runs it. IRS Publication 15 explains whether an employer deposits payroll taxes on a monthly or semiweekly schedule, and a controller should confirm which schedule applies and who watches the deadlines.

A useful deliverable at day 30 is a short written summary: what the controller learned, what is working well, the three to five issues that worry them most and the questions they still have. Keep it to a page or two. The point is to show judgment, not volume.

Days 31 to 60: take ownership of the close and assess controls

In the second month, the controller should run the close rather than observe it. Agree in advance on which steps they own and which still have a backup. Expect some friction. The first close a new leader runs is usually slower than the one before it, and that is acceptable if the result is accurate and documented.

This is also the right time for a structured look at internal controls. Many finance teams use the COSO Internal Control Integrated Framework, first issued in 1992 and refreshed in 2013, as a common reference for how controls should be designed and reviewed. A smaller company does not need a formal framework exercise to get value from this step. Ask the controller to answer practical questions:

  • Who can create a vendor, change vendor bank details and approve a payment? Are any of those held by the same person?
  • Are bank, credit card and payroll accounts reconciled every month, and does someone other than the preparer review them?
  • How are manual journal entries approved, and is support attached?
  • Who reviews payroll changes, new hires and terminations before payroll runs?
  • How are customer credits, write offs and refunds approved?
  • Where are records kept, and for how long? The IRS says employment tax records should be kept for at least 4 years after the tax becomes due or is paid, whichever is later, and other records follow different periods.

The deliverable at day 60 is a written list of control gaps and process pain points, each rated by risk and effort. Keep legal and tax conclusions with your outside advisors. The controller's job here is to find the questions and route them correctly.

Days 61 to 90: agree on an improvement plan

By the third month, the controller has seen at least two closes and has a view of the team and the risks. Now it is time to decide what to change. Ask for a short improvement plan, not a wish list. A practical format:

  • Three to five priorities, each with an owner, a target date and a measure of done.
  • A target close timeline that reflects reality today, not an aspirational number copied from somewhere else.
  • Any staffing gaps, with a clear explanation of the work that is not getting done.
  • System or reporting changes, separated into quick fixes and larger projects that need budget.
  • A revised close checklist with named owners for each step.

Hypothetical example: a controller at a mid sized specialty contractor finds that job cost reports reach project managers two weeks after month end, so change orders are often discovered late. Her day 90 plan proposes a weekly job cost review with the three largest project managers, a cutoff date for change order paperwork and one extra reconciliation step for work in progress. It does not propose a new system yet. That is the kind of focused, testable plan to look for.

If the plan calls for more help, write the new role down before you search. Our guides on hiring a staff accountant and hiring a payroll specialist include practical exercises you can adapt.

How to run check ins during the first 90 days

Structure matters as much as the plan itself. Keep it simple:

  • A 30 minute weekly meeting between the controller and the CFO or owner, with the same three questions: what you learned, what is blocked and what you need from me.
  • A formal review at day 30, 60 and 90 tied to the written deliverables above.
  • Direct feedback in both directions. Ask the controller what the company did not tell them during hiring.
  • Early introductions to the outside accountants so year end planning does not wait for the fourth quarter.

Controller onboarding checklist

  • System access, documents and introductions ready before day one.
  • Bank and payment authority granted in stages, by deliberate decision.
  • One on one meetings with every finance team member and key operations leaders.
  • A full close observed in month one, with a written day 30 summary.
  • Close ownership and a control gap review in month two.
  • A prioritized improvement plan with owners and dates at day 90.
  • Weekly check ins and formal reviews at 30, 60 and 90 days.

A good controller can strengthen how your company closes, reports and makes decisions, but only if the first quarter gives them room to learn before they lead. Career Path Staffing works with employers hiring for accounting and finance roles. If you are planning a controller search or building out your finance team, reach out to our team.

Further Reading

IRS: Publication 15, Employer's Tax Guide

IRS: How Long Should I Keep Records?

COSO: Internal Control Integrated Framework