Onboarding Plan
90-Day Plan for a New Chief Administrative Officer
The first 90 days set the tone for administrative leadership. This plan breaks the period into three phases and thirteen weeks, shows who to meet and why, and lists the deliverables a new CAO should have ready at day 30, day 60, and day 90, so you build trust, understand the operating model, and deliver early wins without disrupting core services.
Updated 2026-10-0210 min read
90-day goals
- Build stakeholder trust
- Map service delivery
- Establish cadence
- Deliver quick wins
Before day one
Preparation before you start
The plan works best if the groundwork is laid between accepting the offer and the first day. A few hours of reading and two or three conversations save weeks later.
What to read
- The current budget and the most recent budget presentation.
- Recent audit reports, management letters, and open findings.
- The strategic plan and the latest board or council materials.
- Organization charts for every function you will own.
- Any existing service catalog, SLA reports, or satisfaction surveys.
What to agree with the CEO
- The top two or three problems you were hired to solve.
- Which functions report to you, and which are shared.
- Decisions you can make alone versus those that need sign-off.
- How and how often the CEO wants to be updated.
- How your arrival will be announced, and by whom.
Days 1-30
Discovery and alignment
Focus on understanding the administrative landscape and building trust with key stakeholders. The goal of month one is a clear, evidence-based picture, not a new structure.
Stakeholder conversations
- Meet executive peers, department heads, and your direct reports one to one.
- Identify service pain points and priorities in their words.
- Clarify what each stakeholder expects from the CAO role.
- Use the onboarding-questions guide as the diagnostic input for these conversations.
Operational assessment
- Inventory all administrative services and who delivers them.
- Review SLAs, backlogs, and service metrics where they exist.
- Assess risk, compliance, and audit status.
- Map the budget by function and identify committed spend.
Days 31-60
Operating model clarity and quick wins
Align on decision rights, service ownership, and early improvements that build credibility.
Operating model alignment
- Publish a draft service catalog and ownership map.
- Define decision rights for service changes.
- Establish governance forums and cadence.
Quick wins
- Resolve a visible service backlog issue.
- Standardize intake and escalation paths for one service.
- Launch or simplify a single service request entry point.
Days 61-90
Execution cadence and long-term plan
Lock in sustainable rhythms, metrics, and a roadmap for the next 12 to 18 months.
Execution cadence
- Launch weekly service delivery reviews.
- Establish monthly portfolio performance reviews.
- Align quarterly with the CEO and CFO on priorities.
Roadmap planning
- Define multi-year operating model priorities.
- Build a resource and budget plan.
- Communicate the roadmap and success metrics.
Week by week
The 90-day plan, week by week
Use this as a starting template and adjust the pace to the organization. If you arrive mid-crisis or mid-budget cycle, some items will move earlier; protect the listening weeks regardless.
| Week | Focus | Key actions |
|---|---|---|
| 1 | Arrive and orient | Meet the CEO to confirm priorities; meet each direct report; learn current escalations and any live crises. |
| 2 | Peer listening | One-to-ones with executive peers; ask what works, what frustrates them, and what they expect from you. |
| 3 | Front-line listening | Meet department heads and front-line staff; walk through request processes as a customer would. |
| 4 | Assess and synthesize | Review budget, audits, and service data; draft findings; agree a written mandate with the CEO. |
| 5 | Share findings | Play back what you heard to your team and peers; test priorities; choose two or three quick wins. |
| 6 | Map services | Build the draft service inventory and ownership map with your direct reports. |
| 7 | Clarify decision rights | Agree who decides what for service changes, spending, and escalations; resolve obvious overlaps with peers. |
| 8 | Deliver quick wins | Complete the first visible fix; communicate it plainly and credit the team that did it. |
| 9 | Set up governance | Schedule the service review, leadership team meeting, and customer forum; define agendas and inputs. |
| 10 | Define metrics | Choose a small set of service and financial metrics; set baselines from current data. |
| 11 | Assess the team | Confirm whether the leadership team has the right roles and capacity; plan any changes carefully. |
| 12 | Draft the roadmap | Write the 12 to 18 month roadmap with budget implications; review with the CFO and key peers. |
| 13 | Present and launch | Present the roadmap to the CEO and, if appropriate, the board or council; start the regular cadence. |
Stakeholder map
Who to meet, and what to learn from each
A balanced stakeholder map covers people who fund the CAO's work, people who depend on it, and people who deliver it. Plan to meet everyone below in the first month, and keep notes in a consistent format so patterns emerge.
| Stakeholder | What they need from you | What to learn from them | Ongoing cadence |
|---|---|---|---|
| CEO or chief executive | Delivery on the mandate, no surprises, a clear view of risk | Priorities, decision style, the problems behind your hire | Weekly one-to-one |
| CFO | Budget discipline, credible cost data, coordinated planning | Budget constraints, allocation methods, audit concerns | Biweekly, plus budget cycle |
| COO and CHRO | Reliable services and clear boundaries between roles | Where internal services slow down delivery or hiring | Biweekly or monthly |
| Board, council, or audit committee chair | Confidence in controls and transparent reporting | Governance expectations and past concerns | As set by the governing body |
| Department heads | Faster, simpler administrative support | Pain points, workarounds, shadow teams | Quarterly customer forum |
| Your direct reports | Clear direction, support, and air cover | Constraints, morale, what has been tried before | Weekly team meeting and one-to-ones |
| Front-line administrative staff | Recognition and workable processes | How work actually gets done, day to day | Periodic site visits and town halls |
| Key vendors and unions, where relevant | Continuity and early notice of change | Contract terms, service issues, upcoming negotiations | As contracts and agreements require |
Deliverables
What to have ready at day 30, 60, and 90
Concrete deliverables turn the plan into something the CEO and peers can see and react to. Keep each one short; a few pages beats a long report nobody reads.
| Milestone | Deliverables | Who sees it |
|---|---|---|
| Day 30 | Listening summary with themes; written mandate covering scope, success measures, and decision rights; initial risk and audit register; shortlist of quick wins | CEO first, then a version for your team and peers |
| Day 60 | Draft service catalog and ownership map; decision-rights matrix; governance calendar; first quick win completed and communicated; metric baselines | Leadership team and department heads |
| Day 90 | 12 to 18 month roadmap with budget implications; first dashboard of service and financial metrics; leadership team assessment; running operating cadence | CEO, executive team, and the board or council where appropriate |
Completion indicators
Confirm each area with your leadership team before calling the 90 days done.
- Stakeholders aligned on the CAO mandate
- Service catalog and ownership established
- Governance cadence in place
- Quick wins delivered and communicated
- 12 to 18 month roadmap approved
Adapting the plan
How the plan changes with your situation
The structure holds in most settings, but the emphasis shifts depending on how you arrived and where.
Internal promotion
You already know the organization, so discovery can be shorter. The harder work is resetting relationships with former peers and showing you now speak for the whole administrative portfolio, not just your previous function. Hold the listening meetings anyway; people will tell a new CAO things they never told a colleague.
External hire
You bring fresh eyes but lack context and relationships. Protect the first month for listening, find a trusted insider who can explain history, and avoid comparing everything to your previous employer.
Public sector
Budget calendars, public meetings, and elected officials shape the timing. Learn the council or board cycle early and plan the day-90 roadmap around it. The CAO in government guide covers the specifics.
Turnaround or crisis
If services are failing or an audit finding is urgent, stabilize first and compress discovery. Still schedule the listening meetings; they simply run alongside the fix instead of before it.
Pitfalls
Common 90-day pitfalls
New CAOs often arrive with a strong appetite for change and discover, a few weeks in, that early action has produced quiet resistance. The patterns below are the ones most likely to derail an otherwise good first ninety days.
Overhauling before listening
Announcing a new operating model in the first month rarely lands well. The new CAO has not yet seen a full operating cycle, so any redesign is based on incomplete information. Use month one to listen, document, and ask precise questions; reserve structural changes for month two onward, once you have evidence.
Solving for the loudest stakeholder
The peer who calls most often is not necessarily the one whose service problem matters most. A balanced stakeholder map, including the quiet ones, keeps your early decisions calibrated to organizational priority rather than to whoever has your ear that week.
Quick wins that cost trust
A "quick win" that forces the existing team to drop committed work, or that embarrasses the previous leadership, can cost more political capital than it earns. Pick wins that are visible to the wider organization and that build on what the team already does well.
No documented mandate
Verbal alignment with the CEO drifts as soon as priorities change. By the end of month one, get the mandate in writing: scope, success metrics, and decision rights. The conversation it forces is more useful than the document itself.
Indicators
Signals you are on track
By the end of the ninety days the right signals are visible without you needing to point them out. Three indicators are worth watching, because their absence tends to predict trouble in the back half of year one.
Other executives bring you problems
A working sign of trust is when peers route real, ambiguous problems to you instead of formal escalations. If the CFO, COO, or CHRO calls early to think out loud, the partnership is forming the way it should. The CAO vs CFO and CAO vs COO guides cover the boundary work behind that signal.
Your team can answer "what good looks like"
Ask three direct reports what good service delivery looks like in this organization. If the answers converge, the clarity work is paying off. If they diverge, the operating-model conversation needs more time before any redesign moves forward.
Departments use the front door
When department heads start sending requests through the agreed intake channel instead of calling you directly, the new operating model is taking hold. Track this alongside the metrics dashboard rather than relying on impressions.
The calendar runs without you
Governance forums that happen on schedule, with prepared inputs, even when you are away, show the cadence is real. The operating model guide covers how to design those forums.
FAQ
First 90 days as CAO: common questions
What should a new CAO do in the first 30 days?
Listen and assess. Meet the CEO, executive peers, department heads, and your team; review the budget, audits, and service data; and agree a written mandate with the CEO covering scope, success measures, and decision rights. Avoid announcing structural changes in this period.
What should be in a 90-day plan for a Chief Administrative Officer?
A good plan covers three phases: discovery and alignment in days 1 to 30, operating model clarity and quick wins in days 31 to 60, and execution cadence and a 12 to 18 month roadmap in days 61 to 90, with specific deliverables at each milestone.
How do you choose quick wins as a new CAO?
Pick problems that many people notice, that your team can fix without dropping committed work, and that build on what the team already does well. Fixing a visible backlog or simplifying one request process are common examples.
Who should a new CAO meet first?
Start with the CEO to confirm priorities, then your direct reports, then executive peers such as the CFO, COO, and CHRO. Follow with department heads, front-line administrative staff, and, where relevant, the board or council chair, key vendors, and union representatives.
Should you present a 90-day plan in a CAO interview?
Often, yes. A short draft plan shows how you think about listening, priorities, and governance. Keep it high level, label it as a starting hypothesis, and be clear that you would refine it after meeting stakeholders.
Download the operating cadence checklist
Use the checklist to formalize your governance rhythm. The operating model guide shows what to put into the cadence once it is running.
Get the checklist