How to write a CAO job description (with a template)

Five questions to settle first

• What administrative functions report to this role on day one?
• Where is the boundary with the COO, CFO, CHRO, and chief of staff?
• What does success look like at the end of year one?
• What is the reporting line — to the CEO, to the COO, to a board?
• What decisions does this role make alone, and which require partnership?

Common patterns of confusion

• Treating the JD as a wishlist instead of a contract about scope.
• Borrowing language from a prior CAO whose actual scope was different.
• Describing the person you want instead of the role you need.
• Leaving the boundary with adjacent executives implicit, then defending it post-hire.

Chief Administrative Officer — template

Role summary. The Chief Administrative Officer reports to the [CEO / President / Board] and leads the administrative functions that let [organization] deliver its strategy. The role will be judged primarily on [one outcome, e.g. "a stable, measurable shared-services model across all business units"].

Context. This is a [new role / backfill / redesigned role]. It exists now because [one or two sentences on the trigger: growth, consolidation, a reorganization, a leadership transition].

Scope. The CAO leads [list named functions, e.g. HR operations, IT operations, facilities, procurement, and the enterprise PMO]. The CAO partners with, but does not lead, [e.g. finance, legal, and clinical or academic leadership].

Reporting line and team. Reports to [title]. Direct reports: [number and titles]. Budget responsibility: [operating and capital budgets in scope, described in a way you are comfortable sharing].

Template, continued

Decision rights. Decides: [e.g. administrative policy, vendor selection within approved budget, service-level standards]. Decides jointly with [title]: [e.g. capital priorities, headcount plans]. Recommends to [CEO / board]: [e.g. major contracts, organizational redesign].

First-year outcomes.

• [Outcome 1 — specific and reviewable, e.g. "service-level agreements published for every shared service".]
• [Outcome 2 — e.g. "a single operating dashboard reviewed monthly by the executive team".]
• [Outcome 3 — e.g. "procurement consolidated under one policy and one system".]

Qualifications. [Three to six capabilities, e.g. "has led several administrative functions at once", "has run a regulated or audited operation", "has redesigned a service model without disrupting delivery".] Credentials: [only those that are genuinely required, with the reason].

Compensation philosophy. [Base, annual incentive, and long-term incentive structure, or the band if your policy or local law requires publishing one.]

Treating the JD as marketing

Glossy language about "transformation" and "innovation" attracts applications but does not recruit the right candidates. Strong CAOs read past the marketing copy looking for scope, reporting line, and authority. Lead with substance.

Listing every possible responsibility

A bullet list of every administrative function the role might touch reads as confused rather than expansive. List only what the CAO owns or co-owns. Functions the CAO may interact with but does not lead belong in a separate "partners with" line.

Confusing CAO with COO or chief of staff

JDs that read like a COO or chief-of-staff role with the wrong title produce mismatched candidate pools. If the role is really a COO or a chief of staff, use that title. The CAO vs COO and CAO vs Chief of Staff guides cover the distinctions.

Hiding the regulated parts of the role

In healthcare, government, and higher education the regulatory load is part of the job. Pretending otherwise to broaden the pool produces mis-hires. Sector context is part of the role; see the healthcare, government, and higher-education sector guides.