Chief of staff first 90 days: an operating plan

Start with the real operating need

A chief of staff should not spend the first ninety days creating a private layer between the executive and organization. The opening period should clarify decisions, priorities, forums, information flow, and ownership. Begin with the sponsor's mandate, the leadership team's current commitments, recurring meetings, major deadlines, stakeholder expectations, and the few operating failures that most constrain execution. Publish how the role will help and what it will not control.

Set authority and boundaries

Define the sponsor relationship and authority map early. State which meetings the chief of staff convenes, which information they may request, which commitments they may negotiate, and which decisions stay with functional leaders. Select two or three outcomes for the first quarter, each with current evidence, target behavior, adoption owner, and review date.

Build the first control

In the first thirty days, listen and map. Review priorities, decision records, meeting flow, recurring reports, and stakeholder dependencies. Observe before redesigning. Return a concise current-state map to the leadership team so errors can be corrected openly.

Make ownership visible

Establish a sponsor cadence with decisions at its center. Use a short brief covering choices needed, risks, stakeholder commitments, and upcoming events. Keep notes and actions in company-controlled systems. The cadence should reduce ad hoc updates rather than create another reporting burden.

Test the workflow

During days thirty-one through sixty, improve one leadership forum and one priority portfolio. Clarify agenda ownership, pre-read timing, decision capture, action acceptance, status definitions, and escalation. Test the new rhythm for two cycles before expanding it.

Protect judgment and access

During days sixty-one through ninety, transfer routine ownership and address a cross-functional dependency. Functional leaders should still own their outcomes. The chief of staff makes the commitment, dependency, and next decision visible and escalates unresolved conflicts to the sponsor.

Create reliable follow-through

Close the quarter with evidence and a second-quarter proposal. Show which decisions moved faster, which meetings changed, which commitments remain unclear, and where the role consumed unexpected capacity. Ask leaders to confirm or revise the mandate rather than allowing scope to expand silently.

See the approach in practice

A new chief of staff finds six company priorities with different status definitions and a weekly meeting dominated by presentations. In month one, they map decisions and owners. In month two, the meeting becomes a pre-read plus three decision blocks. In month three, department leaders update the common portfolio themselves. The chief of staff owns the system, while executives retain business decisions.

Review evidence and improve

Use adoption and decision evidence rather than document counts. Review decision lead time, overdue owner acceptances, unresolved dependencies, meeting actions, sponsor preparation time, and the number of routines that function without private chief-of-staff memory. If the role becomes the default owner for departmental work, reset boundaries with the sponsor and affected leader.

Check authoritative guidance

Before adopting this approach, review the real workflow with the accountable executive, the person doing the work, and any qualified owner needed for employment, legal, security, privacy, finance, travel, or governance questions. Use U.S. Small Business Administration business planning guidance as a current starting reference, not as a substitute for advice based on the organization's facts and location. Record confirmed facts separately from assumptions, name the decision owner, and identify the safe action while information is missing.

Write the operating brief

Turn the decision into a one-page operating brief for chief of staff support. Include the intended outcome, trigger, inputs, source of truth, authority, service window, exception path, completion evidence, backup, and review date. Connect it to chief of staff support and fractional chief of staff scope so the surrounding service and practical guidance stay easy to find. Walk through an ordinary case and an ambiguous case before applying the rule to consequential work.

Design for continuity

Protect continuity by keeping current records in company-approved systems and limiting access to the work a person performs now. Material changes, approvals, and exceptions should remain visible instead of being rewritten after the fact. A named backup needs to understand what is open, why it matters, which action is permitted, who owns the next decision, and when action becomes too late. Test that handoff with a bounded scenario before relying on it during an absence.

Rehearse the exception path

Run a tabletop review related to chief of staff support. Remove one expected input, introduce a priority collision, and make the usual decision owner briefly unavailable. Ask the team to show how the request enters, where current status lives, which action can proceed, when escalation starts, and what evidence proves completion. Treat confusion as a system defect, assign the correction, and repeat the affected step with the named backup.

Choose the next operating cycle

HireExecutiveTeam helps founders and leadership teams define and staff practical executive support. Apply this guide to the real calendar, inbox, board, travel, meeting, project, and follow-through workload. Keep executive judgment with accountable leaders and specialist decisions with qualified owners. Begin with a bounded operating cycle, review accepted evidence, and preserve the option to revise or stop the arrangement when the facts do not support expansion.

Related resources

• chief of staff support
• fractional chief of staff scope
• leadership decision log