Fractional Integrator Job Description: Template, Duties and Success Measures

What Should a Fractional Integrator Job Description Actually Define?

A Fractional Integrator job description should define five things clearly: the business outcomes the person owns, their recurring responsibilities, their authority, the leadership relationships they must coordinate, and the measures used to judge success. It should describe an accountability seat, not become a miscellaneous list of operational tasks.

The distinction matters because founders often hire an Integrator when the business has already reached a point of operating strain.

Priorities exist, but they compete with each other. Department heads are capable, but cross-functional work still comes back to the founder. Meetings generate actions, but somebody has to keep chasing them. Important issues remain open because nobody owns resolution across departments.

The natural response is to write every one of those frustrations into the job description.

That is usually the wrong approach.

Write the seat around outcomes, not founder frustrations

“Follow up with everyone” is a task.

“Create a consistent accountability rhythm where leadership commitments have one owner, a deadline, and a review point” describes an operating outcome.

“Attend all meetings” is a task.

“Ensure leadership meetings produce clear decisions, assigned actions, and resolved cross-functional issues” describes an outcome.

The job description should prioritize outcomes because they give the Integrator room to operate rather than turning the role into an executive assistant with a larger title.

Make cross-functional ownership explicit

The Integrator seat becomes useful where work crosses normal department boundaries.

A sales leader can own sales.

An engineering leader can own engineering.

A finance leader can own finance.

Problems emerge when an important company priority requires all three functions to move together and nobody owns the coordination.

The Integrator should not take those functional responsibilities away from the leaders. The role should make sure the leaders agree on the outcome, understand their commitments, resolve dependencies, and surface problems before the founder has to intervene.

Define what the founder is delegating

A founder cannot hire accountability while retaining every meaningful operating decision.

The job description should therefore make clear which responsibilities move into the Integrator seat.

Depending on the business, these may include:

• maintaining the leadership execution rhythm;
• tracking company priorities and commitments;
• escalating missed or blocked priorities;
• coordinating work that crosses departments;
• ensuring agreed decisions are converted into owned actions;
• bringing unresolved operating issues back to the correct leaders;
• keeping the founder informed without routing every normal operating decision back to them.

If none of these responsibilities are genuinely delegated, the business may be hiring a coordinator rather than an Integrator.

State the part-time nature of the seat clearly

A fractional role is not simply a full-time job compressed into fewer hours.

The company must decide which recurring responsibilities deserve the person's limited operating time.

A good brief should clarify:

• expected weekly availability;
• required leadership meetings;
• scheduled founder or CEO check-ins;
• response expectations for urgent operating issues;
• whether work is remote, onsite, or mixed;
• what information the Integrator can access;
• which decisions require founder approval.

These details prevent an ambiguous arrangement where the company expects full-time responsiveness from a deliberately part-time seat.

Do not confuse the seat with general administration

Scheduling meetings, formatting notes, updating documents, and chasing routine administrative tasks may support the role, but they should not define it.

An Integrator should spend their limited time on operating leverage: priorities, ownership, cross-functional coordination, issue resolution, accountability, and the rhythm that keeps leadership execution moving.

If the job description does not tell the candidate what they are expected to make happen, it is not yet ready to publish.

Copy-and-Paste Fractional Integrator Job Description Template

The template below is designed for a founder-led company of roughly 10 to 50 people that needs part-time operating leadership. Copy it, remove anything that does not apply, and replace broad responsibilities with the actual priorities and authority of your business before sharing it with candidates.

Treat the template as a seat definition, not a finished vacancy post

The template is deliberately operational.

Before publishing it, founders and HR or operations leads should adjust four areas:

1. Priorities: Name the types of company-level outcomes this person will coordinate.
2. Authority: State which decisions the Integrator can make, challenge, or escalate.
3. Cadence: Define the actual weekly time commitment and required meetings.
4. Success: Replace vague expectations with observable 90-day changes.

The job description becomes much more useful when a candidate can read it and understand not only what they will do, but what will be different in the company if they perform the role well.

Avoid making the first 90 days a list of projects

An Integrator may help with projects, but project completion alone is a weak measure of whether the seat is working.

The first 90 days should primarily establish an operating system that survives from week to week:

• priorities stay visible;
• commitments remain owned;
• issues have a route to resolution;
• functional leaders know what is expected;
• founder intervention becomes more intentional.

Later sections will turn those outcomes into specific 30-, 60-, and 90-day success measures rather than relying on subjective descriptions such as “improve accountability” or “help the team execute better.”

The template should make the seat clear enough that both the founder and candidate can tell, within the first quarter, whether the engagement is creating the operating discipline the company hired for.

Weekly Duties That Belong in the Integrator Seat

The weekly duties of a Fractional Integrator should concentrate on keeping priorities visible, turning decisions into owned actions, coordinating cross-functional work, reviewing commitments, surfacing blockers, and maintaining the leadership operating rhythm. The role should spend less time administering activity and more time ensuring that agreed work actually moves.

This is especially important in a fractional engagement.

When the person may only be working with the business for a limited number of hours each week, the job description needs to protect that time from low-value administrative work.

Review company priorities before the leadership meeting

The Integrator should begin the weekly cycle by checking the priorities leadership has already agreed to.

That review should answer:

• Which priorities are moving as expected?
• Which are at risk?
• Which are already overdue?
• Which are blocked by another person or department?
• Which no longer have a clear owner?
• Which require a leadership decision before progress can continue?

The Integrator is not expected to complete every delayed priority personally.

The responsibility is to make the execution condition visible and ensure that the correct owner is engaged.

Prepare the meeting around decisions rather than updates

A leadership meeting can easily become a sequence of status reports.

The Integrator should separate information that can be read beforehand from issues that genuinely require leadership attention.

Before the meeting, that may involve:

• gathering current scorecard information;
• identifying priorities that need discussion;
• confirming unresolved issues from the previous week;
• checking that responsible leaders are ready to report outcomes;
• identifying decisions that cannot be made at department level;
• removing routine updates that do not require leadership time.

This preparation gives the meeting a defined purpose before everyone joins it.

Turn discussion into one owner and one next action

During the meeting, the Integrator should continuously distinguish discussion from commitment.

If an issue is discussed but nobody can answer who owns the next action, the issue is still open.

The Integrator should help leadership leave each material decision with:

• one accountable owner;
• a clear expected outcome;
• an agreed deadline or review point;
• any dependencies that could prevent completion;
• an escalation path when additional authority is required.

The role should also challenge vague commitments such as “we'll look into it,” “the team will handle it,” or “someone needs to follow up.”

Those phrases describe intent, not ownership.

Keep the founder from becoming the default action owner

Founder-led companies often develop a predictable pattern.

When a discussion becomes difficult, unclear, or cross-functional, the founder eventually says, “I'll handle it.”

That may solve the immediate problem while weakening the operating system.

A Fractional Integrator should help determine whether the issue genuinely requires founder authority or whether another leader should own the outcome.

The job description should make this responsibility explicit because reducing founder dependency is difficult if every unresolved issue automatically returns to the founder.

Track commitments after the meeting

The Integrator's work does not end when the meeting closes.

Between meetings, the role should maintain visibility into important commitments.

That may include:

• recording decisions;
• updating agreed actions;
• following up with owners on material commitments;
• identifying overdue actions;
• surfacing blocked work;
• carrying unresolved issues into the correct next discussion;
• preparing accountability information for the next weekly review.

This is different from repeatedly reminding everyone about every task.

The objective is to maintain a reliable execution loop in which significant commitments do not disappear simply because the meeting ended.

Coordinate work that crosses departments

Cross-functional work is one of the strongest reasons to create an Integrator seat.

Consider a customer launch that requires sales, operations, finance, and technology.

Each functional leader may perform their own part well while the total initiative still slips because:

• dependencies were not identified;
• one team assumed another team owned the next step;
• a decision was waiting for approval;
• deadlines were never aligned;
• nobody was responsible for the outcome across functions.

The Integrator should not become the functional owner of sales, finance, operations, or technology.

The role should own the coordination required to keep the shared company outcome moving.

Review the operating scorecard

A useful weekly rhythm should include a small number of measures that show whether the business is operating as expected.

The Integrator may help gather and review this information, but should not automatically become responsible for producing every metric.

Functional leaders should still own the accuracy and performance of the measures related to their areas.

The Integrator's responsibility is to make sure leadership can see material deviations and decide what action follows.

Maintain one focused founder or CEO check-in

A Fractional Integrator needs access to the founder or CEO, but that relationship should not become a second operating system running privately beside the leadership team.

A focused check-in can cover:

• decisions reserved for the founder;
• blocked priorities requiring executive authority;
• recurring accountability problems;
• sensitive leadership issues;
• changes in company priorities;
• areas where the Integrator's authority is unclear.

Routine operating updates should remain inside the normal leadership system whenever possible.

A practical weekly rhythm

The exact schedule will vary by company, but a part-time Integrator brief can describe the rhythm in practical terms.

The weekly duty list should describe the operating rhythm the Integrator maintains, not every task the company might eventually ask them to perform.

What Should a Fractional Integrator Own — and What Should Stay With the Team?

A Fractional Integrator should own the execution system around shared priorities, accountability, cross-functional coordination, and follow-through. Functional leaders should continue owning their departments, specialist decisions, team performance, and functional outcomes. The Integrator strengthens ownership across the company rather than collecting everyone else's responsibilities into one new role.

This boundary is one of the most important parts of the job description.

Without it, a capable Integrator can quickly become the person who receives every task that does not fit neatly somewhere else.

The Integrator can own the execution system

The execution system includes the structures that keep company-level commitments moving.

The Integrator may reasonably own:

• the leadership meeting rhythm;
• the company-level priority tracker;
• the action and commitment review process;
• the unresolved-issue list;
• cross-functional dependency visibility;
• escalation discipline;
• accountability follow-through;
• coordination between functional leaders on shared priorities.

These responsibilities create one operating layer across the leadership team without requiring the Integrator to run every department.

Department heads should continue owning functional performance

The sales leader should still own sales performance.

The operations leader should still own the operating function.

The technology leader should still own technology decisions within their authority.

The Integrator should not automatically:

• approve every department decision;
• supervise every employee;
• replace functional planning;
• personally complete overdue department work;
• become the project manager for every initiative;
• make specialist decisions outside their competence.

When a department repeatedly misses a commitment, the Integrator's role is to make that failure visible, clarify ownership, challenge the gap, and escalate appropriately.

It is not to quietly absorb the work.

The founder should keep vision and reserved executive decisions

A Fractional Integrator does not replace the founder's role in setting direction.

The founder or CEO normally retains responsibility for matters such as:

• company vision;
• major strategic changes;
• significant capital commitments;
• ownership decisions;
• senior leadership decisions that remain CEO responsibilities;
• other matters explicitly reserved for executive approval.

The Integrator's value is not in taking over those decisions.

It is in reducing how often ordinary operating work reaches the founder simply because nobody else is coordinating it.

The role should not become a meeting facilitator

Running a structured meeting can be one responsibility of the seat.

It is not the seat itself.

A meeting facilitator improves the structure and participation of a meeting.

A Fractional Integrator carries execution continuity beyond the meeting by tracking commitments, coordinating dependencies, challenging missed ownership, and maintaining the operating rhythm between leadership sessions.

If the brief ends when the meeting ends, the company may be defining facilitation support rather than an Integrator role.

Do not make the Integrator responsible for fixing structural problems they cannot control

Some job descriptions quietly assign outcomes to the Integrator without giving the role the authority or organizational conditions required to achieve them.

For example, the role cannot reasonably be expected to create accountability when:

• the founder routinely overrides agreed ownership;
• department heads can ignore commitments without consequence;
• leadership priorities change constantly without being reset formally;
• decision rights remain undefined;
• the Integrator has no visibility into performance or commitments;
• leadership refuses to use the agreed operating system.

The job description should therefore define both responsibility and authority.

Do not make the Integrator the automatic owner of every stalled project

A common failure pattern appears when leadership says:

“This is stuck. Give it to the Integrator.”

That response teaches the organization that missed ownership results in reassignment to one central person.

Over time, the Integrator becomes another bottleneck.

A stronger operating rule is:

The Integrator owns clarity and accountability around the work. The appropriate functional or project owner still owns delivery unless leadership deliberately changes ownership.

Avoid assigning problems outside the role's purpose

A Fractional Integrator should not be expected to solve every problem in a growing company.

The seat does not automatically:

• fix product-market fit;
• repair poor hiring decisions;
• replace undefined leadership roles;
• create authority when the founder refuses to delegate;
• substitute for missing specialist expertise;
• guarantee growth or immediate operational improvement.

Those issues may affect execution, but they require different interventions.

Use a simple ownership test before adding a duty

Before adding another responsibility to the job description, ask:

“Does this duty strengthen cross-functional execution and accountability, or are we assigning it to the Integrator because nobody else currently owns it?”

If the answer is the second one, leadership should first decide where the responsibility logically belongs.

A strong Integrator seat creates clearer ownership throughout the company. It should not become the place where unclear ownership goes to hide.

Define Decision Rights Before You Hire

A Fractional Integrator cannot be accountable for execution if the job description gives them responsibility without authority. Before hiring, define what the Integrator can decide independently, what they can challenge or coordinate, what requires founder approval, and which decisions remain with functional leaders.

This is where many otherwise strong Integrator briefs become vague.

They describe outcomes such as “improve accountability,” “keep priorities on track,” or “ensure departments execute,” but never explain what the person is allowed to do when a leader misses a commitment, two departments disagree, or a priority is blocked.

Without decision rights, the Integrator becomes a messenger.

Responsibility and authority must travel together

Consider a simple example.

A sales leader commits to delivering pricing inputs by Thursday. Operations needs those inputs before a customer rollout can proceed.

Thursday passes.

The Integrator can see the dependency and the missed commitment, but what are they authorized to do?

Can they:

• challenge the missed commitment directly;
• request a revised deadline;
• require the blocker to be made visible;
• bring the issue into the leadership review;
• escalate repeated non-ownership to the founder;
• reprioritize another department's work?

The first five may fit the Integrator seat.

The last one may belong to the relevant functional leader or founder unless authority has been specifically delegated.

That distinction should be agreed before the engagement starts.

Give the Integrator permission to challenge unclear ownership

Accountability requires more than recording names beside tasks.

The Integrator needs permission to challenge statements such as:

• “The team is working on it.”
• “We should have that soon.”
• “Operations and sales are handling it together.”
• “We are waiting for more information.”
• “I'll check with everyone.”

Each statement may be reasonable in conversation, but none identifies one accountable owner and a defined next action.

The Integrator should be able to ask:

• Who owns the outcome?
• What exactly must happen next?
• By when?
• What is blocking it?
• Who has the authority to remove that blocker?

This is not interference in department management.

It is the operating discipline the role was created to provide.

Define four levels of decision authority

A practical job description can divide authority into four levels.

1. The Integrator can decide

These are decisions necessary to maintain the agreed execution system.

Depending on the company, they may include:

• structuring the weekly leadership agenda;
• maintaining the company priority tracker;
• requiring one named owner for an agreed action;
• moving unresolved issues into the correct leadership discussion;
• maintaining agreed follow-up and review routines;
• identifying a commitment as blocked, overdue, or at risk.

2. The Integrator can coordinate and challenge

In these areas, the Integrator does not necessarily own the final decision but has explicit authority to drive clarity.

Examples include:

• challenging missed commitments;
• asking functional leaders to clarify ownership;
• coordinating dependencies between departments;
• requesting an updated deadline when an agreed date is missed;
• surfacing conflicts between company priorities;
• requiring unresolved blockers to be visible to leadership.

3. The Integrator can recommend, but another leader decides

Some matters require functional expertise or executive authority.

The Integrator may identify the issue and recommend a course of action while the responsible leader retains the decision.

These might include:

• staffing changes inside a department;
• significant budget reallocations;
• specialist technology decisions;
• changes to sales compensation;
• major vendor commitments;
• changes to departmental strategy.

4. The Integrator must escalate

The brief should also specify circumstances where the Integrator should not attempt to resolve the issue independently.

Escalation may be appropriate when:

• company priorities conflict and leadership cannot resolve the trade-off;
• a decision exceeds delegated financial authority;
• a department leader repeatedly refuses agreed accountability;
• a significant people issue requires founder or executive involvement;
• strategic direction is unclear;
• the issue affects ownership, major capital, legal exposure, or another reserved executive area.

Put the authority into the job description

Do not rely on the founder telling the candidate privately, “You have my backing.”

Functional leaders need to understand that backing too.

A copy-ready authority section can read:

Founder sponsorship needs to be visible

The founder or CEO should introduce the role to the leadership team with a clear explanation of why the seat exists and what authority comes with it.

The message should not be:

“This person is here to help me.”

It should be closer to:

“We are creating a clearer execution system. This person is responsible for maintaining that system, and all of us are expected to work within it.”

That distinction matters.

The first description creates an assistant to the founder.

The second creates an operating seat.

Do not give authority without boundaries

Clear authority does not mean unrestricted authority.

A Fractional Integrator should not automatically:

• overrule every department leader;
• approve spending without delegated authority;
• change company strategy independently;
• make specialist decisions outside their role;
• hire or terminate employees without the agreed process;
• become the founder's proxy for every executive decision.

The objective is enough authority to enforce the execution system, not unlimited authority over the company.

90-Day Success Measures for a Fractional Integrator

A Fractional Integrator's first 90 days should be measured by observable operating changes rather than broad promises. Priorities should become clearer, commitments should have owners, leadership follow-up should become consistent, recurring cross-functional blockers should be visible, and routine execution should depend less on the founder personally chasing the team.

These measures should not imply that every company problem will be solved in one quarter.

The first 90 days are better used to determine whether a functioning execution system is being established.

Days 1–30: establish visibility before changing everything

The first month should help the Integrator understand how execution currently works.

That means identifying:

• the company's current priorities;
• who owns each priority;
• the existing leadership meeting rhythm;
• which commitments are already overdue or blocked;
• recurring cross-functional dependencies;
• which issues repeatedly return to the founder;
• what operating metrics leadership currently reviews;
• where decision rights are unclear.

The Integrator should resist redesigning every process immediately.

A 10-to-50-person company may have informal systems that work well in some areas and poorly in others. The first month should distinguish between the two.

Useful 30-day success evidence

By the end of the first month, leadership should be able to see evidence such as:

• a current list of company-level priorities;
• one named accountable owner for each priority;
• a documented weekly leadership cadence;
• a visible list of unresolved cross-functional issues;
• agreed escalation rules;
• initial clarity on which decisions belong to the founder, functional leaders, and Integrator.

These are foundational measures.

They show that the company can now see the execution system it is trying to improve.

Days 31–60: make ownership and follow-through consistent

The second month should move from visibility into repeatable behavior.

The Integrator should be helping leadership use the same operating rules each week:

• priorities are reviewed consistently;
• important actions receive one owner;
• agreed deadlines remain visible;
• blocked work is identified before it becomes an emergency;
• unresolved issues return to the correct decision forum;
• functional leaders are expected to report outcomes rather than activity alone.

At this stage, the role should also begin identifying recurring patterns.

If the same type of problem appears repeatedly, leadership should ask whether the root cause is unclear ownership, weak process, conflicting priorities, insufficient resources, or a decision that has never actually been made.

Useful 60-day success evidence

By around the second month, reasonable evidence may include:

• leadership meetings consistently ending with documented decisions and owners;
• overdue commitments being reviewed rather than forgotten;
• recurring cross-functional blockers having named owners or escalation paths;
• leaders using the same priority and accountability system between meetings;
• the founder receiving more focused escalations instead of routine follow-up requests;
• the initial operating scorecard being used consistently enough to reveal meaningful exceptions.

These measures are more useful than counting how many meetings the Integrator attended.

Days 61–90: test whether the operating rhythm can hold

By the third month, leadership should be able to evaluate whether the new rhythm is becoming part of how the company operates.

The key question changes from:

“Has the Integrator created the system?”

to:

“Are leaders actually using it?”

The Integrator should now be able to show where accountability is improving and where structural problems remain.

Useful 90-day success evidence

By the end of the first quarter, leadership should look for observable changes such as:

• company priorities have stable, visible ownership;
• leadership commitments are reviewed on an agreed cadence;
• major unresolved issues remain visible until a decision is made;
• cross-functional dependencies are identified and coordinated earlier;
• repeated missed commitments trigger a defined accountability conversation;
• leaders understand the escalation path when normal ownership cannot resolve an issue;
• founder involvement is concentrated more heavily on strategic or genuinely executive decisions;
• the business can identify which parts of the execution system still require improvement.

Use a 30-60-90 scorecard rather than subjective feedback alone

Add numeric targets only after you know the baseline

A job description can include measurable targets, but avoid inventing numbers simply to make the role appear more accountable.

For example, a company may eventually decide to track:

• percentage of company priorities with a named owner;
• percentage of leadership actions completed by their agreed review date;
• number of overdue company-level commitments;
• number of unresolved cross-functional blockers;
• number of priority changes made during the quarter;
• number of routine operating decisions escalated to the founder.

But the target should be set after leadership understands the current baseline and the business context.

Writing “95% of actions completed on time” into a job description without knowing current performance may produce a neat metric but a poor measure.

Measure the system, not just the person

Some success measures depend on the leadership team as much as they depend on the Integrator.

The Integrator cannot force accountability if:

• the founder changes priorities without resetting expectations;
• functional leaders ignore agreed commitments;
• the role is denied access to required information;
• leadership bypasses the operating rhythm;
• the Integrator lacks authority to challenge or escalate.

The 90-day review should therefore assess both the person's performance and whether the company has created the conditions required for the seat to work.

Copy-ready 90-day success section

A strong 90-day measure describes evidence that the operating system is becoming clearer and more reliable. It does not promise that one fractional leader will solve every execution problem in a quarter.

What Should Go on the Fractional Integrator Scorecard?

A Fractional Integrator scorecard should measure whether the company's execution system is becoming more reliable. Useful measures include priority ownership, overdue commitments, action follow-through, unresolved cross-functional blockers, escalation patterns, and how often routine execution still requires founder intervention. The scorecard should measure operating discipline, not simply activity.

This is different from the company's normal financial or departmental scorecard.

Sales may already track pipeline and revenue. Finance may track cash and margin. Operations may track delivery, capacity, or service performance.

The Integrator scorecard should answer a different question:

Is the leadership team reliably turning agreed priorities into owned, reviewed execution?

Measure whether priorities have clear owners

Every company-level priority should have one person who is accountable for moving it forward.

The Integrator does not need to own every priority personally.

The scorecard can instead track whether priority ownership is clear.

Useful measures may include:

• company priorities with one named accountable owner;
• priorities without a clear owner;
• priorities that have changed owner during the period;
• priorities currently blocked by another function;
• priorities requiring executive escalation.

The purpose is not to create more reporting.

It is to make unclear ownership visible before it becomes a founder problem.

Track commitments that are overdue or repeatedly moved

A leadership team can appear busy while the same commitments move from one week to the next.

The Integrator should be able to see:

• how many important commitments are overdue;
• which commitments have been rescheduled repeatedly;
• whether the delay has a known blocker;
• whether ownership is still correct;
• whether the issue needs escalation or reprioritization.

A missed deadline is not automatically an accountability failure.

Priorities change. Dependencies appear. New information can make an original date unrealistic.

The stronger measure is whether the change is visible, owned, explained, and deliberately reset rather than quietly ignored.

Measure decision-to-action clarity

The Integrator should help leadership ensure that significant decisions produce an executable next step.

For selected company-level decisions, the scorecard can review whether each one has:

• one clear owner;
• an expected outcome;
• an agreed review date;
• identified dependencies;
• a clear escalation route if progress stops.

This gives the Integrator a practical way to measure the difference between a decision that was discussed and a decision that entered the execution system.

Keep unresolved cross-functional issues visible

A founder with 10 to 50 people may not need a large portfolio-management system.

They do need visibility when important work is stuck between functions.

The Integrator can track:

• open cross-functional blockers;
• how long material blockers have remained unresolved;
• which leader currently owns the next action;
• whether the issue requires a leadership decision;
• whether the same type of blocker keeps returning.

Repeated blockers are particularly useful.

They often indicate a structural issue such as unclear roles, conflicting priorities, weak handoffs, missing process, or insufficient decision authority.

Track founder escalations carefully

Reducing founder dependency does not mean preventing issues from reaching the founder.

Some decisions should reach the founder or CEO.

The useful distinction is between:

• genuine executive decisions;
• strategic trade-offs;
• major people or capital decisions;
• routine execution issues that reached the founder because ownership was weak.

Over time, the Integrator should help leadership recognize whether normal operational questions are being resolved at the correct level.

This is more useful than setting an arbitrary target that the founder should never be involved.

Do not score the Integrator on activity volume

Weak measures can make an active Integrator appear effective without showing whether execution improved.

Avoid using activity measures such as:

• number of meetings attended;
• number of reminders sent;
• number of documents created;
• number of Slack or Teams messages posted;
• number of tasks added to a project-management tool.

These activities may support the job.

They are not evidence that the business is executing more reliably.

Use baseline, direction, and evidence

A practical scorecard does not need aggressive targets on day one.

For each measure, define:

1. Baseline: What does the current situation look like?
2. Direction: What should improve, reduce, or become more consistent?
3. Evidence: What observable information will show that change?

For example:

If leadership does not currently know how many strategic commitments are overdue, the first success measure is visibility.

Once a reliable baseline exists, leadership can set a sensible improvement target.

Copy-ready scorecard section for the job description

The scorecard should tell leadership whether execution is becoming more dependable, not whether the Integrator looks busy.

What to Leave Out of the Job Description

Leave out responsibilities that turn the Fractional Integrator into the founder's assistant, the manager of every function, the owner of every stalled project, or the person expected to solve unrelated business problems. A narrower brief creates stronger accountability because the candidate can see exactly what the seat owns and where its authority ends.

More responsibilities do not automatically create a stronger job description.

They often create the opposite.

Leave out “own all operations”

This phrase is too broad for most fractional Integrator briefs.

It can imply responsibility for:

• finance;
• HR;
• IT;
• customer support;
• vendor management;
• project delivery;
• facilities;
• procurement;
• every internal process.

If the business genuinely needs broad executive ownership of company operations, it may be defining a different role.

The Integrator brief should specify the cross-functional execution responsibilities the company actually wants this person to own.

Leave out responsibility for every project

The Integrator may coordinate company-level priorities and help unblock important projects.

That does not mean every project should be transferred to them.

A job description that says “manage all company projects” can create several problems:

• functional leaders stop owning delivery;
• the Integrator becomes overloaded;
• important and low-value work receive the same attention;
• the role becomes a centralized project-management office;
• the company creates a new execution bottleneck.

Keep ownership with the person or function closest to the outcome unless leadership deliberately assigns the Integrator as the project owner.

Leave out executive-assistant duties unless they are intentionally part of the engagement

Calendar management, travel booking, meeting scheduling, inbox management, routine note formatting, and administrative coordination are legitimate responsibilities.

They simply belong to a different type of role unless the engagement explicitly combines them.

Mixing them into the Integrator brief can consume the limited fractional capacity that was supposed to be used for:

• priority management;
• accountability;
• issue resolution;
• decision follow-through;
• cross-functional execution.

Leave out “make sure everyone does their job”

This is not a useful accountability statement.

Functional leaders should manage their teams.

The Integrator can make commitments visible, challenge missed ownership, coordinate company priorities, and escalate persistent accountability problems.

They should not become the direct manager of the entire organization merely because leadership wants stronger follow-through.

Leave out ownership of the founder's vision

The Integrator helps translate direction into coordinated execution.

The role should not be described as the person responsible for defining the founder's vision, replacing strategic leadership, or making every major executive decision.

A clearer distinction is:

• the founder or CEO determines strategic direction;
• leadership agrees on priorities;
• functional leaders own their areas;
• the Integrator maintains the cross-company execution rhythm.

Leave out problems the role cannot reasonably solve

Avoid making the Integrator accountable for outcomes such as:

• fixing product-market fit;
• correcting every poor hiring decision;
• solving chronic understaffing;
• creating leadership authority that the founder refuses to delegate;
• repairing undefined executive roles without leadership participation;
• guaranteeing revenue growth;
• eliminating all internal conflict;
• ensuring every company target is achieved.

An Integrator can improve execution around many of these issues.

That is different from having unilateral control over their outcome.

Leave out arbitrary performance promises

Statements such as “increase productivity by 50%,” “eliminate missed deadlines,” or “remove the founder from operations within 90 days” may sound measurable, but they are weak job-description measures without verified baselines and clear control over the result.

Replace them with observable operating changes.

For example:

• establish one visible company priority list;
• assign accountable owners to company-level priorities;
• create a consistent weekly accountability review;
• maintain visibility into overdue commitments and blockers;
• establish an agreed escalation path.

These outcomes can be evaluated without inventing a performance promise.

Be careful with “other duties as assigned”

A flexible role needs room to respond to changing business needs.

But an unrestricted catch-all clause can undermine the entire seat definition.

A more useful version is:

This gives the business flexibility without turning every unowned task into Integrator work.

Do not write a full-time expectation into a fractional seat

A part-time Integrator cannot reasonably be expected to attend every meeting, respond instantly to every issue, manage every initiative, and remain continuously available throughout the working week.

The job description should instead identify:

• required recurring meetings;
• expected weekly availability;
• agreed communication windows;
• urgent escalation expectations;
• responsibilities that happen asynchronously;
• work that remains with internal leaders.

A fractional model works when scope and availability are designed together.

Run one final test before publishing the brief

Read every responsibility and ask:

“Does this belong to the Integrator because it strengthens company-level execution, or because we currently do not know who else should own it?”

Anything in the second category deserves another ownership discussion before it stays in the job description.

A strong Integrator brief makes ownership clearer across the company. A weak one transfers unclear ownership into a single overloaded role.

Build the Part-Time Role Around a Weekly Operating Rhythm

A fractional Integrator role works best when the job description defines a repeatable weekly operating rhythm rather than expecting continuous availability. The cadence should create enough structure to review priorities, prepare leadership decisions, run accountability conversations, coordinate cross-functional work, and follow up on significant commitments between meetings.

This matters because “part-time” can mean almost anything unless the operating expectation is written down.

One company may need concentrated leadership support one day each week. Another may need shorter blocks spread across several days. A third may require a scheduled meeting day plus asynchronous follow-up.

The exact model can vary.

What should remain consistent is the purpose of the time.

Start the week by reviewing what changed

The Integrator should enter the leadership cycle already knowing which company-level commitments need attention.

A pre-meeting review may cover:

• progress against current company priorities;
• overdue leadership commitments;
• blocked actions;
• new cross-functional dependencies;
• scorecard exceptions;
• unresolved issues carried forward from the previous week;
• decisions that require leadership attention.

This prevents the leadership meeting from becoming the first time anyone discovers that an important commitment is off track.

Separate reporting from decision-making

A part-time Integrator should protect leadership time aggressively.

Information that can be reviewed asynchronously should not consume most of the meeting.

Before the meeting, the Integrator can help separate:

• updates that only need visibility;
• exceptions that need discussion;
• issues that need a decision;
• commitments that need accountability;
• items that belong in another forum.

The meeting can then spend more time on work that genuinely requires the leadership team.

Use the leadership meeting as the accountability anchor

The weekly leadership meeting should provide a regular point where company-level execution becomes visible.

The Integrator may help the team:

• review the small set of measures that require leadership attention;
• check progress on company priorities;
• surface commitments that are late or blocked;
• resolve issues requiring several functions;
• clarify decisions;
• assign one owner to each resulting action;
• agree on a deadline or review date;
• identify what requires escalation.

The Integrator should keep asking whether the discussion has produced an executable outcome.

If five people understand the problem but nobody owns what happens next, the meeting has not completed the work.

Follow up selectively between meetings

A fractional role should not spend the rest of the week asking every employee whether every task is complete.

Follow-up should concentrate on commitments that are:

• strategically important;
• cross-functional;
• approaching a critical deadline;
• already blocked;
• dependent on another leadership action;
• repeatedly slipping.

Routine departmental management should remain with the relevant leader.

This protects the Integrator's limited time for company-level execution rather than turning the role into a centralized reminder service.

Use a founder check-in for exceptions, not duplicate reporting

A regular founder or CEO check-in can be useful, but it should not duplicate the leadership meeting.

The conversation is better used for:

• decisions reserved for the founder;
• sensitive leadership concerns;
• priority conflicts that need executive judgment;
• repeated accountability failures;
• changes in strategy;
• clarification of the Integrator's authority.

If every normal operating update still needs a separate founder discussion, the company has not yet reduced founder dependency.

Leave capacity for cross-functional intervention

Do not schedule every fractional hour in advance.

The role needs some capacity to deal with important issues that emerge between planned sessions.

For example, a product launch may suddenly be blocked because sales committed to a date that operations cannot support.

The Integrator may need to bring the relevant leaders together, clarify the trade-off, identify the decision owner, and make sure the revised commitment is reflected in the execution system.

That is higher-value work than filling the entire weekly schedule with recurring meetings.

Define the cadence in the job description

Founders do not need to prescribe every hour, but the brief should give candidates enough information to judge whether the engagement is realistic.

A copy-ready section can read:

Avoid defining the role by hours alone

Weekly hours matter commercially, but they do not explain whether the engagement is designed well.

Two candidates may both offer eight hours per week.

One may spend most of that time sitting in meetings.

The other may use the same capacity to review execution before the meeting, focus leaders on decisions during it, coordinate critical dependencies afterward, and escalate only what needs executive attention.

The second model creates more operating leverage without requiring more hours.

Watch for a cadence that depends on constant founder access

A fractional Integrator should work closely with the founder, but should not need founder approval for every routine next step.

If the weekly rhythm contains repeated messages such as:

• “Can I ask the team about this?”
• “Can I move this issue onto the agenda?”
• “Can I follow up with this leader?”
• “Can I mark this commitment overdue?”

the decision-rights section probably needs more work.

A well-designed fractional cadence gives the Integrator enough structure to maintain continuity and enough authority to operate without turning the founder into a permission checkpoint.

How Do You Interview Someone Against the Integrator Seat?

Interview a Fractional Integrator against the operating situations they will actually face. Test how they clarify ownership, challenge missed commitments, handle cross-functional conflict, work with a founder, distinguish execution from administration, and operate with limited weekly capacity. Strong candidates should explain how they create accountability without taking every responsibility onto themselves.

A generic executive interview is not enough.

The role depends heavily on judgment.

A candidate may have impressive operations experience and still be a poor fit if they solve every execution problem by taking personal control of the work.

Ask for examples of turning unclear work into clear ownership

A useful question is:

“Tell us about a situation where an important initiative involved several departments but nobody clearly owned the overall outcome. What did you do?”

Listen for whether the candidate:

• identified the required outcome;
• clarified decision authority;
• assigned or confirmed ownership;
• mapped dependencies;
• created a review rhythm;
• escalated only where necessary.

Be cautious if the answer is mainly:

“I took the project over myself.”

That can solve one initiative while creating the wrong operating pattern for the Integrator seat.

Test how the candidate handles a missed commitment

Give the candidate a realistic scenario:

“A department head committed to an important action for Friday. It is now Monday. The work is incomplete, and another team is blocked. What do you do?”

A strong answer should normally investigate:

• what changed;
• whether the commitment is still valid;
• what is blocking completion;
• whether the owner needs another decision;
• what revised commitment is realistic;
• whether the issue needs escalation.

Accountability should not automatically mean confrontation.

But it should not mean accepting indefinite vagueness either.

Ask how they would work with the founder

The founder relationship is critical because the Integrator needs sponsorship without becoming dependent on constant founder direction.

Ask:

“What do you need from a founder or CEO in order to make this role work?”

Strong responses may include:

• clear priorities;
• visible sponsorship;
• defined decision rights;
• willingness to delegate;
• access to relevant information;
• support when agreed accountability is ignored;
• discipline around changing priorities.

A candidate who says they can make the system work regardless of founder behavior may be underestimating the role's dependency on executive sponsorship.

Test whether they can distinguish execution from administration

Ask the candidate:

“You have limited fractional capacity. Which tasks would you refuse or delegate so you can protect the purpose of the role?”

The candidate should be able to distinguish between necessary operating work and lower-value administration.

They should also be comfortable saying that some responsibilities belong with:

• the founder;
• a functional leader;
• a project manager;
• an executive assistant;
• a specialist;
• another internal owner.

A strong Integrator creates ownership rather than collecting it.

Ask how they would structure their first 30 days

Avoid telling the candidate the full answer before asking.

Use a question such as:

“You join a 30-person founder-led company where priorities change often, leadership meetings are inconsistent, and the founder follows up personally on most important work. What would you do during your first month?”

Look for a sequence that begins with understanding before redesign.

The candidate may reasonably want to:

• understand company priorities;
• meet functional leaders;
• map current commitments and blockers;
• understand the existing meeting rhythm;
• identify where founder dependency occurs;
• clarify decision rights;
• establish a simple first operating cadence.

Be cautious when the first answer is to introduce a large new framework before understanding the business.

Test cross-functional conflict directly

Another practical scenario is:

“Sales wants to commit to a customer deadline. Operations says the date is unrealistic. Both leaders believe their position is correct. What is your role?”

The Integrator does not need to personally choose the commercial or operational answer.

A stronger response should clarify:

• the business outcome;
• the facts each leader is using;
• the trade-off being made;
• who has the decision right;
• what must happen after the decision;
• how the resulting commitment will be tracked.

The role coordinates decision and execution discipline without pretending to be the specialist owner of every issue.

Ask what they would measure

Ask:

“After 90 days, what evidence would you show us to demonstrate that the Integrator seat is working?”

Strong candidates should move beyond vague answers such as “the team will communicate better.”

Useful evidence may include:

• clearer ownership of company priorities;
• visible leadership commitments;
• a consistent operating cadence;
• fewer unresolved cross-functional dependencies;
• clearer escalation paths;
• more focused founder involvement.

Test whether they know when not to intervene

One of the strongest interview questions is:

“Give us an example of a problem you would deliberately leave with a functional leader instead of taking ownership yourself.”

This tests whether the candidate understands the boundary between accountability and takeover.

A candidate who feels responsible for personally solving every visible problem can become the company's next bottleneck.

Score the interview against the role, not personality alone

After the interview, assess the candidate against the same criteria used in the job description.

A practical hiring scorecard can include:

• ability to translate priorities into owned actions;
• cross-functional judgment;
• accountability without unnecessary control;
• comfort challenging senior leaders;
• understanding of escalation;
• ability to operate within fractional capacity;
• founder communication;
• ability to distinguish operational symptoms from ownership problems;
• practical approach to the first 90 days.

Use the same scenario with finalists

When comparing several strong candidates, give each person the same short operating scenario.

For example:

There is no single perfect answer.

The exercise reveals how the candidate thinks about ownership, authority, prioritization, coordination, founder dependency, and operating discipline.

Hire for the ability to create clarity and sustained execution across leaders—not simply for the ability to run a polished meeting or manage a large task list.

A Clear Job Description Still Fails Without Real Authority

A well-written Fractional Integrator job description will not create accountability by itself. The role only works when the founder or CEO visibly supports the seat, delegates appropriate authority, gives the Integrator access to priorities and results, and expects functional leaders to participate in the same operating system.

Before hiring, confirm that the Integrator will be allowed to challenge unclear ownership, surface overdue commitments, coordinate cross-functional dependencies, maintain the agreed leadership rhythm, and escalate issues that cannot be resolved at the normal operating level.

At the same time, keep the boundaries clear. The Integrator should not replace the founder's vision, take specialist decisions away from functional leaders, or become the owner of every unfinished initiative.

External fractional support may also be unnecessary when a capable internal operator already owns company-level execution, when the problem is limited to one poorly structured meeting, or when leadership can correct the issue by clarifying roles and decision rights internally.

Conversely, the role is unlikely to succeed when the founder continues changing priorities informally, refuses to delegate authority, or allows leadership commitments to be optional.

Before publishing the job description, take one final step: review every responsibility beside the authority required to perform it. If the candidate will be accountable for an outcome but has no legitimate way to challenge, coordinate, decide, or escalate around that outcome, fix the seat before you hire into it.

Once the role is defined, the next question is how to turn the brief into the first quarter of actual execution. The 90-Day Fractional Integrator Roadmap provides a practical next view of that transition.

The best Integrator job description does more than describe a person. It defines an operating seat that the company is prepared to let someone genuinely own.