Founder support role scope checklist

Start with the real operating need

Founder support roles become unstable when the title is chosen before the work. A founder may need calendar and inbox ownership, project follow-through, leadership cadence, personal logistics, or a strategic operating partner. These needs can coexist, but they require different judgment, capacity, access, and management. Inventory a representative month and identify work only the founder can do, work that can be delegated, and work that should belong to another function.

Set authority and boundaries

Group needs into executive assistance, project coordination, leadership administration, and chief-of-staff work. Define outcomes, frequency, sensitivity, time window, authority, and consequence for each. Decide whether one person can safely cover the mix or whether a managed team, specialist, or staged hire is better. Name excluded personal or professional work and the owner for priority conflicts.

Build the first control

Run a two-week demand capture without requiring invasive surveillance. The founder records recurring friction, delayed decisions, missed follow-up, context switching, and after-hours administration. Add calendar and workflow evidence where approved. Focus on patterns rather than a minute-by-minute productivity judgment.

Make ownership visible

Translate tasks into outcomes. Scheduling becomes protected decision and customer time; reminders become accepted leadership commitments; document formatting may become decision-ready meeting materials. Outcome language reveals the judgment and context the role actually needs.

Test the workflow

Map authority and access before recruiting. Specify what the role may decide, draft, send, spend, disclose, and escalate. Start with least privilege and company-controlled systems. Broad trust language is not an operational permission model.

Protect judgment and access

Model capacity under normal and peak demand. Include waiting, coordination, quality review, meetings, documentation, improvement, and backup. If board, fundraising, travel, or hiring peaks overlap, decide what pauses or receives coverage before the person starts.

Create reliable follow-through

Choose a reviewable first phase. Set thirty- and sixty-day workflows, acceptance, management cadence, and a decision about expansion. Avoid advertising a strategic role and then measuring only administrative speed, or hiring an assistant while expecting unspoken organizational authority.

See the approach in practice

A founder asks for a chief of staff because priorities are slipping. Demand mapping shows that calendar fragmentation, meeting preparation, and unrecorded follow-up consume most time, while department heads already own strategy. The company starts with senior executive assistant support plus a weekly commitment review. It reserves a later chief-of-staff decision for evidence that cross-functional operating design is still missing.

Review evidence and improve

Measure founder direction time, accepted outputs, delayed decisions, workload outside scope, access exceptions, recurring corrections, and work that still depends on private founder memory. Review whether the role's title, authority, and daily work remain aligned. Change scope deliberately and adjust capacity or compensation through the appropriate process instead of allowing success to create unlimited responsibilities.

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. Bureau of Labor Statistics administrative assistant overview 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 founder operations support. Include the intended outcome, trigger, inputs, source of truth, authority, service window, exception path, completion evidence, backup, and review date. Connect it to founder operations support and chief of staff versus executive assistant 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 founder operations 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

• founder operations support
• chief of staff versus executive assistant
• executive support capacity planning