Support models

Fractional support capacity boundary

How to define the boundary between a useful fractional scope and an always-on expectation.

4 min readHireExecutiveTeam editorial
Fractional support capacity boundary article illustration
Table of contents
  1. Name the workflows included, expected response windows, peak periods
  2. Review requests that fell outside the agreement and identify
  3. Set a review date with one decision owner on each side
  4. Frequently asked questions

Name the workflows included, expected response windows, peak periods

Name the workflows included, expected response windows, peak periods, exclusions, and backup path. Capacity should be described through work and timing, not a vague availability promise.

Review requests that fell outside the agreement and identify

Review requests that fell outside the agreement and identify whether the answer is a priority decision, a new boundary, or a different support model.

Set a review date with one decision owner on each side

Set a review date with one decision owner on each side. A visible boundary protects both the executive relationship and the quality of the work.

Frequently asked questions

Should one assistant support the whole executive team?

Sometimes. It works when priorities are clear and executives share one operating rhythm.

What should happen before a consult?

List the meetings, inbox rules, recurring reports, and decisions that need support.

Ready to define the role?

Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.

Book a consultation