Fractional COO Authority: Decision Framework Guide

Three weeks into a fractional COO engagement, a pattern emerges that kills more engagements than any other issue: the COO needs to make 15 decisions per week but only has explicit authority over 3 of them. The remaining 12 require the CEO's input, but the CEO is traveling, fundraising, or in back-to-back customer calls. Decisions stall. The team notices. Momentum dies.

This isn't a personality problem or a trust problem — it's a structural one. Most companies hire a fractional COO without defining what that person can actually decide on their own. The result is a $10,000-$20,000/month executive who functions like a project manager, routing every decision through a bottleneck that was the whole reason they were hired in the first place.

The solution is a Decision Authority Matrix — a documented framework that specifies exactly which decisions the fractional COO makes independently, which require input, and which need CEO or board approval. This guide provides the framework, complete with real threshold numbers and clause language you can implement on day one.

Why Authority Boundaries Matter More for Fractional COOs

A full-time COO builds authority gradually over months of daily interaction. They're present for hallway conversations, attend every leadership meeting, and develop relationships that create implicit authority. A fractional COO doesn't have that luxury.

With 2-3 on-site days per week (or fewer), a fractional COO operates in compressed bursts. Every moment spent seeking permission for routine decisions is time not spent on operational improvement. According to a Harvard Business Review analysis, unclear decision rights are the single biggest drag on organizational speed — and the problem intensifies when the decision-maker is only available part-time.

Three specific risks emerge without defined authority:

Decision paralysis. The team waits for the COO, who waits for the CEO, who's unavailable. A vendor contract expires without renewal. A hiring decision stalls for two weeks. A process change gets delayed indefinitely. Authority undermining. Department heads bypass the fractional COO and go directly to the CEO because they know the COO can't make the call. The COO loses credibility, and the CEO gets pulled back into the operational role the COO was hired to fill. Scope ambiguity. Without clear boundaries, every decision becomes a judgment call about whether this one needs approval. Some fractional COOs overreach and create friction; others under-reach and become expensive observers.

The Four-Tier Decision Authority Model

The most effective fractional COO authority frameworks use a tiered model that categorizes decisions by impact, reversibility, and financial magnitude.

Tier 1: Full Autonomous Authority

Decisions the fractional COO makes independently without informing the CEO beforehand. These are routine operational decisions with limited financial exposure and high reversibility.

Decision Type	Examples	Typical Threshold
Operational expenses	Software subscriptions, office supplies, contractor payments	Up to $5,000 per transaction
Process modifications	Workflow changes, SOP updates, meeting structure changes	No capital expenditure required
Team scheduling	Shift assignments, work-from-home approvals, PTO management	Within existing headcount
Vendor management	Day-to-day vendor communication, issue resolution, performance reviews	Within existing contracts
Project prioritization	Sequencing work within approved project list	Within approved scope
Tool configuration	Settings changes, user permissions, dashboard customization	Within existing tools

The rule of thumb: If a decision can be reversed within 48 hours without significant cost, it belongs in Tier 1.

Tier 2: Decide and Inform

The fractional COO makes the decision but notifies the CEO within 24-48 hours. These are moderately impactful decisions where speed matters more than consensus.

Decision Type	Examples	Typical Threshold
Expenses above Tier 1	Equipment purchases, consulting fees, training programs	$5,000-$15,000 per transaction
Hiring (non-executive)	Making offers to individual contributors and managers	Below Director level
Vendor changes	Switching vendors, renegotiating terms, ending vendor relationships	Under $25,000 annual value
Performance management	Formal warnings, performance improvement plans	All levels below executive
Customer escalations	Service credits, refunds, SLA exceptions	Up to $5,000 value
Policy changes	Internal policies affecting operations teams	Non-compensation related

The rule of thumb: If the CEO would want to know about it but wouldn't want to be the bottleneck, it belongs in Tier 2.

Tier 3: Recommend and Decide Together

The fractional COO brings a recommendation to the CEO, but both parties must align before action is taken. These are strategic or high-impact decisions.

Decision Type	Examples	Typical Threshold
Significant expenditures	Capital purchases, annual vendor contracts, system implementations	$15,000-$50,000
Organizational changes	Department restructuring, new reporting lines, role eliminations	Any structural changes
Executive hiring	Director+ positions, new department heads	All executive hires
Compensation changes	Salary adjustments, bonus structures, benefits modifications	Any changes to comp framework
Strategic vendor partnerships	Long-term partnerships, exclusive agreements, co-development deals	Multi-year commitments
Customer pricing	Custom pricing agreements, enterprise deals, pricing model changes	Any pricing deviation

The rule of thumb: If the decision shapes the company's trajectory for 6+ months, both parties should weigh in.

Tier 4: CEO/Board Decision with COO Input

The fractional COO provides data, analysis, and recommendations, but the CEO or board makes the final call.

Strategic direction and company vision
Fundraising and investor relations
Acquisitions, mergers, and major partnerships
Expenditures exceeding $50,000
Changes to the business model, pricing strategy, or target market
Executive terminations
Board-level governance decisions
Legal matters with company-wide implications

The rule of thumb: If it would make the news (even in a trade publication), it's a Tier 4 decision.

Building the Decision Authority Matrix

The Decision Authority Matrix should be created during the first two weeks of the engagement and attached as an appendix to the engagement agreement. Here's how to build one.

Step 1: Audit current decision patterns

Before defining authority, understand how decisions actually get made today. During the first week, the fractional COO should track every decision they encounter and note:

What was the decision?
Who made it?
How long did it take?
Did it require escalation?
What was the financial impact?

This audit typically reveals 30-50 decision types that recur weekly or monthly. Most of them (70-80%) should land in Tier 1 or Tier 2.

Step 2: Set financial thresholds

Financial thresholds should scale with company revenue. Here's a guideline:

Company Revenue	Tier 1 (Autonomous)	Tier 2 (Decide & Inform)	Tier 3 (Joint)
Under $2M	Up to $1,000	$1,000-$5,000	$5,000-$25,000
$2M-$10M	Up to $5,000	$5,000-$15,000	$15,000-$50,000
$10M-$30M	Up to $10,000	$10,000-$25,000	$25,000-$100,000
$30M+	Up to $25,000	$25,000-$50,000	$50,000-$250,000

Step 3: Define the escalation protocol

For decisions that fall between tiers or in grey areas, create an escalation framework:

Standard escalation (non-urgent):

Fractional COO sends a written recommendation via email or Slack with supporting data
CEO responds within 48 business hours
If no response within 48 hours, the COO may proceed with the recommendation (except for Tier 4 items)
Decision and rationale are logged in the shared decision register

Emergency escalation:

Fractional COO calls or texts the CEO directly
If the CEO is unreachable within 2 hours, the COO may make the decision if delay would cause material harm
The COO documents the decision and rationale immediately
Full debrief occurs within 24 hours

Step 4: Create the decision register

Maintain a shared document (Notion, Google Sheet, or project management tool) that logs every Tier 2 and Tier 3 decision with:

Date and decision maker
Decision description
Financial impact
Rationale
Outcome (reviewed quarterly)

This register serves three purposes: it creates accountability, builds trust over time, and provides data for expanding or adjusting authority levels at quarterly reviews.

The HR Authority Question

Hiring and firing authority is the most sensitive area in any fractional COO engagement. Here's how experienced practitioners handle it.

What most fractional COOs should own:

Hiring authority below Director level within approved headcount and budget. The COO runs the hiring process, makes the final decision, and extends the offer.
Performance management for all operational team members. This includes setting expectations, conducting reviews, issuing warnings, and managing PIPs (Performance Improvement Plans).
Contractor management — engaging, directing, and terminating contractors and freelancers within budget.

What requires CEO involvement:

Director-level and above hires — The COO sources, screens, and recommends candidates, but the CEO makes the final call on anyone who'll sit in leadership meetings.
Termination of employees — Most fractional COO agreements require CEO approval for any termination, even if the COO has built the case and managed the PIP process. The legal and cultural implications are too significant for a part-time executive to own unilaterally.
Compensation changes — Raises, promotions, and bonus adjustments should be jointly decided, with the COO recommending and the CEO approving.

The authority expansion pattern:

Authority should grow over time as trust develops. A common progression:

Month 1-3: Tier 1 and Tier 2 only. The COO proves their judgment on routine decisions.
Month 4-6: Tier 2 thresholds increase (e.g., autonomous spending moves from $5K to $10K). The COO takes on more Tier 3 decisions independently.
Month 7-12: The COO operates with near full-time COO authority in operational domains, with CEO involvement limited to Tier 4 strategic decisions.

This progression should be formalized in quarterly authority reviews, not left to informal drift.

Common Authority Conflicts and How to Resolve Them

Conflict 1: The CEO overrides decisions after the fact

Scenario: The fractional COO makes a Tier 2 decision (switching a vendor), and the CEO reverses it two days later without discussion. Resolution: Address it directly in the next 1-on-1. If the decision was within the COO's defined authority, the override undermines the framework. If the CEO had information the COO didn't, the issue is communication, not authority. Either way, the solution is the same: improve the information flow so both parties make aligned decisions.

Conflict 2: Department heads bypass the COO

Scenario: A VP of Sales goes directly to the CEO with an operational request, skipping the fractional COO entirely. Resolution: The CEO must redirect the VP back to the COO. This requires the CEO to consistently reinforce the COO's authority — not just in the org chart, but in behavior. The CEO should introduce the COO's authority publicly, in writing, to the entire leadership team within the first week.

Conflict 3: Emergency decisions without authority

Scenario: A critical system goes down on a day the CEO is unreachable. The fix costs $20,000, which exceeds the COO's Tier 2 threshold. Resolution: This is why the emergency escalation protocol exists. If delay would cause material harm (lost revenue, customer impact, safety risk), the COO should act and document. No reasonable CEO will fault a COO for spending $20K to prevent $200K in lost revenue — as long as the rationale is sound and documented.

Technology Access as Authority

Decision-making authority is meaningless without system access. The authority matrix should include a technology access schedule that specifies:

System	Access Level	Rationale
Financial systems (QuickBooks, Xero)	Full read, limited write	Review financials, approve operational expenses
HRIS / Payroll	Read + manager functions	View org data, manage time tracking, process performance reviews
CRM (HubSpot, Salesforce)	Read + reporting	Understand pipeline for capacity planning
Project management (Asana, ClickUp)	Full admin	Manage projects, assign work, set priorities
Communication (Slack, email)	Full access to operational channels	Participate in team communication
Cloud/hosting (AWS, GCP)	Read-only or no access	COOs shouldn't have production deployment access
Banking	View-only	Cash flow visibility without transaction authority

Important: System access should be provisioned during the first week of the engagement, not trickling in over months. Delayed access is delayed authority, and it signals to the team that the COO isn't fully empowered.

The Quarterly Authority Review

Every 90 days, the CEO and fractional COO should conduct a formal authority review covering:

Decisions made — Review the decision register. Were there any Tier 1/2 decisions that should have been escalated? Any Tier 3 decisions that could have been Tier 2?
Threshold adjustments — Based on trust and track record, should financial thresholds increase or decrease?
Scope changes — Has the COO's scope expanded or shifted? Does the authority matrix need to reflect new areas?
Conflict review — Were there any authority conflicts? How were they resolved? What systemic changes prevent recurrence?
Team feedback — How does the team perceive the COO's authority? Are there clarity gaps?

Key Takeaways

Undefined decision-making authority is the number-one cause of fractional COO engagement failure. Define it in writing during the first two weeks.
The Four-Tier model categorizes decisions by impact: autonomous, decide-and-inform, joint decision, and CEO/board-only. Most operational decisions (70-80%) should fall in Tiers 1 and 2.
Financial thresholds should scale with company revenue — a $5M company's Tier 1 threshold of $5,000 would be $25,000 at a $30M company.
Authority should expand over time as trust develops, formalized through quarterly reviews rather than informal drift.
System access is decision-making authority. Delayed access means delayed effectiveness. Provision all necessary systems during week one.
The CEO must actively reinforce the COO's authority with the leadership team — publicly, consistently, and from day one.

Frequently Asked Questions

Should the fractional COO have authority to fire employees?

In most engagements, the COO manages the performance process (setting expectations, delivering feedback, managing PIPs) but the final termination decision requires CEO approval. The exception is contractor termination, which typically falls within the COO's Tier 2 authority. As trust builds over 6-12 months, some engagements expand this authority for non-executive roles.

How do you handle authority when the fractional COO is only on-site 2 days per week?

Asynchronous authority is critical. The COO should be able to make Tier 1 and Tier 2 decisions remotely via Slack, email, or project management tools — not just during on-site days. Build communication protocols that allow decisions to flow regardless of physical presence. Loom recordings, async Slack decisions with documented rationale, and a decision register accessible to all stakeholders make remote authority functional.

What if the CEO and COO disagree on a Tier 3 decision?

The framework should include a tiebreaker mechanism. In most fractional COO agreements, the CEO has final authority on Tier 3 decisions — they're the one with full-time context and ultimate accountability. The COO's role is to present the best recommendation with supporting data. If disagreements become frequent, it signals a deeper misalignment on strategy or values that needs a direct conversation.

How detailed should the authority matrix be?

Specific enough to cover 80% of recurring decisions without being so granular it becomes a bureaucratic burden. A good matrix has 15-25 line items across the four tiers, with clear financial thresholds and a catch-all escalation rule for anything not explicitly listed. Overly detailed matrices (50+ items) signal trust issues rather than organizational rigor.

Can authority be revoked or reduced during the engagement?

Yes, but it should be handled carefully. If the COO made a decision that caused significant harm, a direct conversation about what went wrong is more productive than silently reducing authority. Formal authority changes should happen during quarterly reviews, not reactively. Sudden authority reduction without explanation will damage the relationship and likely end the engagement.

Decision-Making Authority for Fractional COOs: The Framework That Prevents Chaos