30-60-90 day plan for financial analysts
On this page
A financial analyst is judged on two things: whether the numbers are right and whether anyone uses them. A new analyst can build an impressive model in the first month and still fail on both counts if it does not tie to the ledger or answers questions nobody in the business is asking. A 30-60-90 day plan for financial analysts should start with reproducing the existing numbers, move to owning a regular piece of reporting, and end with a forecast or analysis that a business partner actually used to make a decision.
This plan is for the FP&A manager, finance director or CFO hiring an analyst who will support budgeting, forecasting and management reporting for a set of departments, products or locations. If the role is mainly about the close and the team, see the 30-60-90 day plan for finance managers. The general structure is in the 30-60-90 day plan template for new hires.
Tie to the ledger before building anything
The fastest way into a new finance team is to reproduce what it already reports. Ask the new analyst to rebuild last month's results for their area from source data and reconcile the differences. It surfaces most of what they need to know.
| What they reproduce | What it teaches | Common surprises |
|---|---|---|
| Actuals by department or product from the general ledger | Chart of accounts, cost centers, mapping to reporting lines | Accounts mapped to the wrong line; manual reclasses each month |
| Allocations | How shared costs are spread and why | Allocation keys nobody has updated in years |
| Headcount and payroll costs | Link between HR data and the ledger | Open roles in the plan that were filled or cancelled |
| Last forecast against actuals | Where the model has been wrong before | The same line missed in the same direction every month |
The 30-60-90 day plan
30-60-90 day plan — [Name], Financial Analyst, [team]
Reports to: [FP&A manager / finance director] Start: [date]
Supports: [departments / products / regions]
Systems: [ERP], [planning tool], [BI tool]
Calendar: close day [N], forecast [monthly / quarterly],
budget cycle starts [month]
DAYS 1-30 — Reproduce and understand
Goals:
- Reproduce last month's results for their area from the ledger;
write up every difference and its cause
- Walk through the forecast model with its owner; list inputs,
assumptions and known weaknesses
- Meet each business partner they support; ask what decisions
they use finance numbers for and what is missing
- Prepare one monthly report with full review by the manager
Deliverables by day 30:
- Reconciliation memo with differences explained
- Model notes: inputs, owners, weaknesses
Check-in: day 30, with manager
DAYS 31-60 — Own the monthly cycle for their area
Goals:
- Own the monthly variance commentary for their area, with
explanations confirmed with business partners
- Update the forecast for their area on the calendar
- Fix one model weakness agreed with the manager
(example: a hard-coded input or a broken link)
Deliverables by day 60:
- Two monthly packs delivered on time, review notes falling
- Model fix documented and reviewed
Check-in: day 60
DAYS 61-90 — Analysis that changes something
Goals:
- Complete one analysis a business partner asked for
(example: pricing, a hiring plan, a vendor change)
- Compare the first forecast they owned with actuals and
explain the gaps
- Prepare their area's inputs for the next budget cycle
Deliverables by day 90:
- Analysis presented, with the decision it informed
- Forecast accuracy review for their area
Check-in: day 90 — full reviewWhat to measure
Most of a new analyst's output can be checked directly. Use these measures in the weekly one-to-one and look at examples, not only counts. The standards are examples; set your own.
| Measure | Why it matters | Example standard (example only) |
|---|---|---|
| Deliverables on the calendar | Leadership plans around them | Every monthly pack on its due date |
| Review notes per deliverable | Accuracy and attention to detail | Falling month over month, none on numbers that do not tie |
| Variance explanations accepted | Shows they understand the business, not only the spreadsheet | Business partners confirm the explanation |
| Forecast against actuals | The forecast is only useful if it is roughly right | Gaps explained each month; judged over several months |
| Requests from business partners | A sign the numbers are used | Growing, and handled through an agreed intake |
A filled example
Financial analyst: Ben Hartley (invented), two years in audit, joining the FP&A team of a multi-site physical therapy group to support operations.
Day 30: Reproducing last month's clinic results showed one clinic's rent posted to a corporate cost center, which made that clinic look more profitable than it was. The forecast model had a hard-coded visit rate that had not changed in a year. Three regional directors told him they wanted visit volume and labor cost on the same page.
Day 60: Owned the monthly commentary for the operations region. The accounting team fixed the rent mapping, and he replaced the hard-coded visit rate with a trailing average, documented in the model notes.
Day 90: Built a staffing analysis for a clinic with a long waitlist, showing the visit volume needed to cover an additional therapist. The regional director used it to approve the hire. His forecast for the region missed actuals mainly on cancellations, which he added as a separate input.
What "on track" looks like
| Checkpoint | On track | Worth a direct conversation |
|---|---|---|
| Day 30 | Numbers reproduced and differences explained; partners met | Builds new templates before understanding the existing ones |
| Day 60 | Monthly cycle owned on time; review notes falling | Commentary that restates the numbers without causes |
| Day 90 | An analysis used for a decision; forecast gaps explained | Business partners still go to the manager for answers |
What the manager owes the new analyst
- System access before day one to the ledger, planning and BI tools.
- The real model, with its known problems, not a cleaned-up version.
- Introductions to business partners with a clear statement that the analyst now supports them.
- Specific review notes rather than silent rework of their files.
Common mistakes
| Mistake | Result | Fix |
|---|---|---|
| Building a new model in month one | Two versions of the truth | Reproduce and document the existing model first |
| Reporting without business context | Commentary nobody reads | Meet partners and confirm explanations with them |
| Manager fixes errors quietly | The same errors repeat | Logged review notes discussed weekly |
| Forecast judged on one month | Noise mistaken for skill or failure | Review accuracy over several months with causes |
Questions for each check-in
The check-ins work best when the analyst brings evidence rather than a status update. Ask the same questions each time so progress is easy to compare.
- Day 30: Which numbers could you not reproduce, and why? Which model input do you trust least? What did each business partner say they need from finance that they are not getting?
- Day 60: Which variance explanations did a business partner correct? What review notes came up more than once, and what did you change to stop them? How long does the monthly cycle take you, and where does the time go?
- Day 90: Which decision did your work inform, and what would you do differently? Where was your forecast wrong, and is the cause in the model or in the business? What should finance stop producing because nobody uses it?
The last question is worth asking every new analyst. People who have just arrived notice reports that exist only because someone once asked for them, and removing one frees time for the analysis the business actually wants.
Adapting the plan
- Corporate finance or investor-facing roles: add the board and lender reporting calendar, covenant calculations and the review process for anything shared outside the company.
- Senior analysts: shorten the first phase and add ownership of the budget process or a planning tool.
- Analysts in small companies: add close tasks such as accruals or reconciliations, and coordinate with the controller or bookkeeper.
If the role is still open, the financial analyst phone screen questions help separate analysts who own models from those who update them. For analysts whose work is mainly SQL and dashboards rather than finance models, see the 30-60-90 day plan for data analysts.
Questions people ask
What should a new financial analyst do in the first week?
Get access to the ledger, the reporting tool and the models, then reproduce last month's reported results for their area from the source data. Tying the numbers back to the general ledger teaches the chart of accounts, the allocations and the adjustments faster than reading documentation, and it shows the manager how carefully the analyst works.
Should a new analyst rebuild the existing forecast model?
Usually not in the first 30 days. They should learn the existing model well enough to explain every input and to find its errors. A rebuild makes sense later if the model cannot be maintained or audited, and it should be agreed with the manager with the old and new versions run side by side.
How do you measure a financial analyst's first 90 days?
By the reliability and usefulness of what they deliver: reports on time, numbers that tie to the ledger, review notes falling over time, variance explanations that business partners accept, and a forecast that holds up when the actuals arrive. Forecast accuracy should be tracked from the start but judged over several months.
How is this plan different from a finance manager's?
A finance manager's plan centers on running the close and the team. A financial analyst's plan centers on models, reporting and business partnering for a set of departments or products. In small companies the roles overlap, and the plan should include close tasks the analyst will own.