Skip to content
Ashish Kumar AgnihotriOperating Partner

The template

Fractional COO Job Description & Scope of Work (With Template)

A fractional COO should not be hired against a full-time job description with the days cut down. The document you need is a scope of work: mandate, responsibilities, decision rights, cadence, deliverables, measures and term. This page contains the full template, section by section, ready to adapt — and explains why each clause is there.

Most fractional COO hires that fail were briefed wrong, not hired wrong. The buyer takes a full-time COO job description — run all operations, build the team, own the P&L, report to the CEO — trims the salary line, and expects the same coverage in two days a week. It cannot work, and the failure is structural: a full-time JD describes a permanent owner of everything, while a fractional engagement buys senior judgement applied to specific problems for a defined period. The document that makes fractional work is narrower, sharper and more measurable than any JD — closer to a contract’s schedule than to a careers-page posting.

The template on this page is organised the way I structure real engagements: a mandate stating the two or three problems being bought; responsibilities split into owns, directs and advises; decision rights and spend authority made explicit; a cadence that fits the fee; deliverables named as artefacts — scorecards, cadences, playbooks — rather than activities; measures agreed against baseline numbers; and a term with a proper exit. Each section below gives you the clause language and the reasoning behind it, so you can defend every line in negotiation rather than delete what you cannot explain. Nothing in it is exotic; all of it is regularly missing.

It is written from the operator’s side of the table, which is where scope documents get stress-tested. Nineteen years in operations — most recently Senior Director, Business Excellence at Publicis Groupe, across 500+ clients and 2,000+ teams — taught me that ambiguity in scope is where engagements go to drift: unclear decision rights stall everything behind the founder, unnamed deliverables become attendance, unmeasured mandates become atmosphere. A page of precision before signing prevents most of it. Use the template as a working draft, not a sacred text; the thinking transfers even where the wording will not. Every clause below earned its place by being absent somewhere expensive.

In depth

What you need to know.

Why a full-time JD fails for a fractional role

A full-time COO job description is a coverage document: it lists everything operations touches, because a permanent executive absorbs whatever arises. Hand that to a two-day-a-week operator and you have guaranteed disappointment — the scope is infinite and the time is not. A fractional scope of work inverts the logic: instead of listing everything the person might touch, it names the few things they must change, the authority they carry to change them, and the evidence that will show the change happened. The practical test: every line of a fractional scope should be checkable at the end of a month. “Owns operational excellence” is a JD line, checkable never. “Installs a weekly operating cadence and a leadership scorecard by day sixty” is a scope line — checkable on day sixty.

Template: the mandate statement

Open the document with three or four sentences, not a list. Template language: “The Fractional COO is engaged to address the following operating priorities: (1) [problem with number — e.g. billing approvals currently take approximately N weeks]; (2) [problem — e.g. delivery quality is inconsistent across teams, with error rates rising under load]; (3) [problem — e.g. operational decisions route through the founder, delaying execution]. The engagement is judged against measurable movement on these priorities, per the Measures section.” The discipline is the numbering and the numbers: three priorities at most, each stated as a current fact rather than an aspiration. If a fourth priority appears mid-engagement, it displaces one of the three or extends the scope formally. A mandate that quietly grows is how retainers become attendance.

Template: responsibilities — owns, directs, advises

Flat responsibility lists cause the classic fractional failure: the client expected execution, the operator planned direction. Split every responsibility into three verbs. Owns — the fractional COO is personally accountable for the artefact: “owns the design and installation of the operating cadence and leadership scorecard; owns the diagnostic and the resulting priority sequence.” Directs — the client team executes under the operator’s direction: “directs the process owners in documenting and improving the billing and delivery workflows; directs the weekly operating review.” Advises — input without accountability: “advises on organisation design, senior operations hires and vendor selection.” Three short lists, none longer than five items. The test of a good split: when something stalls, one glance at the document says whether the operator, the team or the founder was supposed to move.

Template: decision rights and spend authority

This is the section most scope documents omit and most engagements break on. Template language: “The Fractional COO may decide without prior approval: changes to process design, meeting cadence, reporting formats and operating metrics within the mandate. The Fractional COO may approve expenditure up to [amount] per item within the approved operations budget. The following require [CEO/board] approval: hiring and termination, compensation changes, customer- and investor-facing commitments, expenditure above the threshold, and changes to strategy or pricing.” The amounts matter less than the existence of the clause. An operator with zero authority is a consultant renamed, and will queue behind the founder like everyone else — often the exact problem they were hired to remove. Set thresholds low if trust is young; widen them at review. Silence here guarantees friction.

Template: cadence and availability

Define the rhythm, not just the volume. Template language: “Engagement cadence: [two] days per week, of which [one] day on-site, or in overlap hours where the team is remote. Fixed commitments: the weekly operating review [day, time], a monthly review with the [CEO/board], and availability for decisions requiring the Fractional COO’s input within [one business day]. Cadence is reviewed at each term review and may be scaled by written agreement.” Two subtleties earn their place here. Response time matters more than day-count — an operator reachable for a decision inside a day at two days a week beats three silent days. And name the fixed meetings in the document itself: the weekly operating review is not a diary entry, it is a deliverable, and pinning it in the scope makes it one.

Template: deliverables and artefacts

Deliverables are the difference between buying an operating model and renting a presence, so write them as artefacts with dates. Template language: “By day 30: a written diagnostic — where the operating model strains, what it costs, sequenced priorities — and a baselined draft scorecard. By day 60: the weekly operating cadence installed and running; the leadership scorecard live on a single source of truth; ownership of the [two or three] critical processes mapped to named roles. By day 90: documented playbooks for those processes; the governance rhythm — measures, escalation, review — operating without the Fractional COO chairing every session.” Adjust the contents to your mandate; keep the structure. Every item is a thing that exists and can be inspected, not an activity that was performed. Activity reports are what scope documents look like after they fail.

Template: measures of success

Tie the engagement to numbers that predate it. Template language: “The engagement is measured against the following baselines, confirmed during the diagnostic: [metric — e.g. billing/approval cycle time, currently ~N days]; [metric — e.g. first-pass quality rate, currently N%]; [metric — e.g. decision latency on operational items, currently N days]. Targets and review dates are set jointly at day 30 and assessed at each term review.” Choose two or three measures, never ten, and prefer numbers the business already trusts — a finance-system cycle time beats a new dashboard nobody believes yet. For calibration, mature operating work moves numbers like these: a quality score from 95% to 99% across 2,000+ campaigns; a billing cycle from roughly two months to fifteen days across 75 entities. Yours will differ; the principle — baseline, target, date — does not.

Template: term, review and exit

Template language: “Initial term: [three/six] months, commencing [date]. Reviews: at day 30 (diagnostic findings and confirmed measures) and at each term end. Renewal: by written agreement, month-to-month or in successive terms. Notice: [30] days either side. On expiry or termination, the Fractional COO completes an orderly transfer: all playbooks, scorecards and process documentation handed over in editable form, and a transition briefing delivered to the [CEO/named successor].” The transfer sentence is the one buyers forget and the one that protects them most — it makes ending the engagement a deliverable in itself rather than an awkward conversation. A fractional operator confident in their work accepts short notice and explicit exit language readily; hesitation on this clause is information. Good engagements are designed, from the first page, to end well.

Questions

Common questions.

Seven sections: a mandate naming the two or three operating problems being bought, with current numbers; responsibilities split into owns, directs and advises; explicit decision rights and a spend-approval threshold; cadence — days per week, fixed meetings, response time; deliverables written as dated artefacts such as a diagnostic, a scorecard, an operating cadence and playbooks; measures tied to baselined numbers; and a term with notice and an orderly-transfer obligation. If a draft cannot be checked against reality at month-end, it is a job posting, not a scope of work.

A full-time JD describes permanent coverage: everything operations touches eventually lands on the COO, so the document lists domains and reporting lines. A fractional scope describes bounded change: the specific problems to move, the authority granted, the artefacts to be delivered by date, and the numbers that will prove it. Coverage versus change is the whole distinction. Handing a coverage document to a two-day-a-week operator produces guaranteed failure — infinite scope, finite time — which is why drafting has to start from the mandate, not from a standard COO template.

Usually not. Job boards are built for employment: salaried roles, full-time availability, careers-page language. Serious fractional operators are rarely browsing them; they take engagements through referrals, their published work, or fractional-executive platforms. A better use of the same document: send the scope of work directly to candidates sourced through networks and platforms and ask each to respond to the mandate. Their response — specific or generic, sequenced or vague — becomes your first vetting filter. The scope of work is a briefing instrument, not a posting.

Enough to change how work moves without touching what the company is. In practice: authority over process design, cadence, reporting formats and operating metrics within the mandate, plus a defined spend threshold inside the approved budget. Reserved to the CEO or board: hiring and firing, compensation, strategy, pricing, and customer- or investor-facing commitments. The exact thresholds matter less than writing them down — an operator with no authority queues behind the founder, which is frequently the bottleneck they were hired to remove. Start conservative and widen at the first review.

Most genuine fractional COO engagements run at one to three days per week. The right number follows from the mandate: a diagnostic-plus-installation phase often needs two to three days weekly, easing to one or two once the cadence and scorecard are running and the team carries more. Specify the rhythm, not just the volume — which meetings are fixed, how much presence is on-site or in overlap hours, and the response time for decisions, which matters more than the day-count. Build in the right to scale cadence up or down at review, by written agreement.

Artefacts, dated. A written diagnostic by roughly day 30 — where the operating model strains, what it costs, what to fix in what order — plus a baselined scorecard draft. The weekly operating cadence installed and a leadership scorecard live on a single source of truth by around day 60, with ownership of critical processes mapped to named roles. Documented playbooks and a governance rhythm that runs without the operator chairing it by day 90. The common thread: each deliverable is a thing that exists and can be inspected, never an activity that was merely performed.

Three to six months, with a review at day 30 and at each term end, then month-to-month or successive short terms by agreement. Ninety days is roughly what it takes a capable operator to diagnose honestly, install the core artefacts and show early movement on at least one measure — a shorter initial term buys only opinions. Pair the term with a modest notice period, thirty days is common, and an explicit transfer-on-exit clause. A confidence signal worth noting: strong operators accept short terms and clean exits readily, because the artefacts argue for renewal on their own.

Judge your draft against five criteria. Specificity: the mandate names real problems with current numbers, not aspirations. Checkability: every responsibility and deliverable can be verified at month-end. Authority: decision rights and spend thresholds are explicit, so nothing silently queues behind the founder. Measurability: two or three baselined numbers, agreed before the fee starts. Exit: term, notice and orderly transfer written in from day one. Then send it to candidates and watch the responses — the best scope of work doubles as a vetting instrument, because generic operators answer it generically.

The next step

A short conversation settles most of this — and a fixed-fee diagnostic settles the rest.

Book a consultationThe diagnostic

Keep exploring

How to hire a fractional COOThe full buyer’s guide this template slots into.25 questions to ask a fractional COOVet candidates against the scope you just wrote.The fractional COO agreementTurning the scope of work into signable clauses.What is a fractional COO?The role in plain language, before you scope it.Fractional COO servicesHow my own engagements map to this scope.Pricing & engagement modelsDiagnostic first, then a retainer scaled to cadence and scope.