A chief of staff resume needs to explain the principal you supported, the work you coordinated and the decisions within your authority. The title can cover different responsibilities, so give context without treating support work as a lesser contribution.

A scope line can help: one concise statement of the function, project or process you handled. Counts and company size are optional and must be accurate and permitted to disclose. The aim is clarity, not replacing “supported” with “owned” when ownership belonged elsewhere.

Fictional example: Ingrid Solberg, the employer, college, project, training and recognition below are invented. Contacts are placeholders. The document has two experience entries, with an earlier combined analyst/manager title; it does not display three separately dated promotion entries. The dates show work since 2017, not verified company growth or board results.

Use the structure as an option. Add actual role dates when presenting promotions rather than inventing a continuous progression.

The sample describes executive preparation, decision records and planning support without claiming the executive’s approval authority. “Coordinated” and “prepared” are appropriate where those were the tasks performed.

Keep recommendations, approvals, implementation and outcomes distinct. A memo can be useful even if its recommendation was not adopted. A support role does not need a company-wide performance figure to demonstrate value.

Chief-of-staff responsibilities vary across organizations and principals. The following are possible work areas, not an exhaustive five-type classification or a ranking of career value. Executive assistance and coordination also require judgment and should not be dismissed as lesser work.

State the actual mix in plain language. Fictional example: “Chief of Staff to the CEO, coordinating leadership planning, decision preparation and cross-functional follow-up.” Add approved context where useful, but do not imply that the whole company reported to you.

If your experience centers on executive assistance, present it accurately; see the executive assistant example. A target-role summary can explain a transition without changing historical titles.

Scope can be described through deliverables, interfaces and decision boundaries even without direct reports or budget approval. Explain what you prepared, coordinated, recommended or implemented.

The table contains fictional wording examples, not verified outcomes or instructions to upgrade an activity into ownership. Use only the version that matches your actual work.

A cycle count shows activity volume, not automatically influence, quality or seniority. A board-cycle count can also be confidential. Use the verb matching your contribution and distinguish an action log from formal approved minutes.

A specific judgment example might explain how you surfaced conflicting assumptions for an executive decision. You need not claim to have made that decision. See action-verb guidance; no verb guarantees an interview.

Internal promotions can be grouped under one employer or shown as separate entries. Either can be clear when titles and dates are accurate. Separate entries do not inherently look like job hopping, and internal promotion is not the only credible path into the role.

Give each materially different role its actual dates where possible. Do not merge gaps or overlapping assignments into a falsely continuous tenure. Add company-stage or headcount context only when accurate and authorized; company growth is not automatically your achievement.

Allocate detail by relevance, not a mandatory progression from analyst to manager to chief of staff.

Select projects that demonstrate relevant responsibility and that you may discuss. An offsite, internal communication program or presentation can be useful evidence when the task matters to the target role; it does not become worthless because it lacks a financial result.

Combine related projects when that improves clarity, but preserve distinct roles, periods and outcomes. Do not add a claim that every initiative met its deadline unless the records support it. A concise specific example is often more useful than a count with no context.

Choose length based on relevant evidence and instructions; eight years does not automatically require two pages. See length guidance.

There is no universal wording technique that makes confidential work safe to disclose. Ranges, rounded figures, growth multiples, counts and unnamed project descriptions can still reveal protected information. WIPO notes that confidential financial and commercial information, including combinations of information, can qualify for trade-secret protection.

Follow applicable agreements and information-sharing rules. Use already authorized public information or a description approved for external use. When permission is unclear, omit the sensitive detail and describe a nonconfidential responsibility. This article cannot determine whether a particular disclosure complies with your NDA.

For board support, distinguish agenda coordination, assembling pre-reads, drafting material, recording action items and formal governance duties. Preparing a board deck does not make you a director or corporate secretary, and tracking an action does not mean you approved its closure.

For OKR or planning work, explain your contribution and how progress was reviewed. On-time submission is a process measure, not evidence that goals were achieved or that the business improved. A shorter meeting schedule can release calendar time without proving greater productivity.

These prompts help identify genuine responsibility. Complete only those that apply, using details you are permitted to share. A qualitative description is sufficient when no suitable number is available.

An optional summary can combine the principal supported, your main responsibilities and a relevant contribution. Avoid claiming a corporate outcome merely because you drafted a memo about it.

Fictional example: “Chief of Staff to the CEO, coordinating leadership planning and cross-functional follow-up. Prepares decision materials, tracks agreed actions and supports transitions to permanent function owners.” See summary guidance.

You may be applying for another chief-of-staff role, operations, strategy or general management. Select evidence against the actual vacancy rather than assuming everyone should leave the role for a particular career destination.

For operations, relevant examples may include planning and handoffs. For strategy, describe analysis and decision support without implying every recommendation was implemented. For general management, show actual decision and financial authority; headcount modeling or pricing input does not equal P&L ownership. The COO example offers a different scope to compare.

Keep a factual base and tailor emphasis. A Roleframe match assessment is an editing aid, not the employer’s ATS score. Similar phrases do not universally fail an exact-match filter.

Consulting: distinguish analysis, recommendations and implementation. A recommendation remains valid work even when the client chose not to implement it; do not rewrite it as delivered change. See consulting guidance.

Military: retain accurate rank and role, explain unfamiliar responsibilities in plain language and follow release restrictions. Unit size is not necessarily direct-report count. Do not assert equivalence to a civilian executive title merely from a headcount comparison.

Government or political staff: describe actual coordination, analysis and responsibility. Keep factual employer and role history while choosing relevant detail. Policy advice and operational implementation are different contributions.

Across these backgrounds, remove restricted information rather than assuming that generalization makes it publishable.

Use clear headings, accurate dates and readable text. A skills section can help when it adds relevant information; not every skill needs a repeated bullet. Follow the accepted file type and inspect exported text, links and application fields.

PDF does not guarantee correct parsing in every system. A resume check may identify problems, but cannot certify compatibility with an employer’s private setup.