How Should Teams Detect Scope Creep in Executive Support Work?

Research question and scope

This review asks: How should a team detect scope creep in executive support work before it becomes an unmanageable role? Scope creep is the quiet accumulation of duties that were never formally agreed. In executive support it rarely arrives as a dramatic request. It arrives as a favor, a temporary cover during a colleague's leave, or a task that is easier to do than to explain. Six months later the role no longer resembles the one that was hired.

The scope covers the definition of an agreed duty baseline, the logging of changes, and the periodic comparison of planned and actual work. It excludes performance evaluation of an individual assistant and excludes employment-law questions about role changes, which belong to human resources and counsel. The focus is on a measurement method an executive support team can operate.

The review separates verified source claims from analysis and inference. Project and workforce guidance supports documented scope and change control; it does not specify an acceptable growth rate for a support role. The method proposed here is an inference, labeled as such.

Methodology

This review was prepared and fact-checked on 18 September 2026. Sources were selected for authority in project scope, accountability, workforce definition, and communication: the Project Management Institute and the Association for Project Management for scope and change control, NIST SP 800-53 for accountability and audit concepts, the U.S. Office of Personnel Management for how duties are classified, the U.S. Digital.gov plain-language guide, and SHRM for the human-resources context. Each was checked on 18 September 2026.

The unit of analysis is one recurring duty, not one task. A one-off request is excluded from the baseline unless it recurs. For each recurring duty, the method records the agreed source, the observed frequency, the average effort, the owner, and whether it is inside or outside the original role. A four-week observation window is used so that occasional spikes do not dominate.

Transfer limits apply. Project management methods assume a defined deliverable and a change-control process. Executive support work is less structured, so the method must be light enough to survive a busy week.

What authoritative sources establish

The Project Management Institute describes project management as the application of knowledge, skills, tools, and techniques to meet requirements, and it treats scope definition and change control as core practices. The Association for Project Management similarly frames scope as something that must be defined and managed, with changes assessed rather than silently absorbed. These sources support writing down the agreed duty set and reviewing changes against it.

NIST SP 800-53 includes accountability and audit concepts that support recording who owns a duty and when it changed. The U.S. Office of Personnel Management's classification guidance shows how duties are described and grouped for a role, which supports a documented baseline rather than a verbal understanding. The Digital.gov plain-language guide supports writing duty descriptions that a reader can act on. SHRM's human-resources guidance provides context for how role expectations and workload are managed in employment relationships.

Source	Publisher	What it supports	Transfer limit
What is Project Management?	Project Management Institute	Scope definition and change control	Project, not support-role, context
Association for Project Management	Association for Project Management	Managing scope and assessing change	Principle-level guidance
NIST SP 800-53 Rev. 5	National Institute of Standards and Technology	Accountability and audit evidence	Information-system oriented
Classification and qualifications guidance	U.S. Office of Personnel Management	Describing and grouping duties	Public-sector classification context
Plain Language Guide	U.S. Digital.gov	Reader-centered duty descriptions	General writing guidance
Human-resources guidance	SHRM	Role expectations and workload context	Advisory, not binding

Analysis: the baseline is the missing control

The first analytical point is that scope creep cannot be measured without a baseline. Most support roles have a job description, but the description is often written once and never compared against actual work. The practical fix is a short duty baseline: the recurring duties the role was expected to perform, each with an agreed source. Without it, every new duty can be described as "part of the role," and the drift is invisible.

The second point is that temporary cover and permanent absorption look identical in the moment and differ only with time. A domain that distinguishes them at the point of logging prevents the common pattern where a two-week favor quietly becomes a permanent responsibility. The log should record the expected end date of temporary work and require a decision when that date passes.

The third point is that scope creep has a measurable cost, but not the one usually cited. The direct cost is the hours absorbed, and the indirect cost is the rework created when responsibilities become ambiguous. When two people both believe they own a duty, the work may be duplicated, and when neither believes they own it, the work may be dropped. Tracking rework caused by unclear ownership is often more informative than tracking total hours.

A fourth, more cautious inference is that scope creep can be a signal of success rather than failure. When an executive delegates more over time because trust has grown, the role legitimately expands. The review should distinguish an agreed expansion, documented and resourced, from an unagreed accumulation that is neither documented nor resourced. The difference is not the size of the change but whether it was a decision.

A reproducible scope review

Write the duty baseline from the role description and the last quarter's actual work, then confirm it with the executive and the assistant. Keep it to the recurring duties that consume meaningful time. For each duty, record the agreed source, the owner, and whether it is inside or outside the original role.

For four consecutive weeks, log new recurring duties as they appear. For each, record the date first seen, the request source, the estimated recurring effort, whether it is a temporary cover with an end date, and whether it was added to the baseline. One-off requests that do not recur are excluded, but if the same one-off recurs three times, it is a candidate for the baseline.

At the end of the window, compute three local measures: the count of duties permanently absorbed without a documented decision, divided by all duties reviewed; the count of recurring work items not present in the baseline; and the count of rework events attributed to unclear ownership. Report each with its denominator and the observation window. Preserve the baseline version when it changes so that a trend is not compared against a moving definition.

Operating implications for remote executive support

Remote support can maintain the duty baseline, log changes, and surface the decision when temporary cover is about to become permanent. It should not decide whether a role should expand; that is a decision for the executive and the people owner, and it may have employment implications. Support should also avoid normalizing unlogged work simply because it was completed.

A useful escalation names the duty, its origin, the recurring effort, the current owner, and the decision required: add to the baseline, reassign, automate, or stop. It should state when a temporary arrangement has passed its end date without a decision, because that is the moment scope creep becomes structural.

Limitations

This review transfers project and workforce concepts to a support role, and the transfer is an inference. The reviewed sources do not set an acceptable growth rate, and effort estimates are subjective. The four-week window may miss seasonal work, and logging itself adds load. A small team's data will not support statistical claims, and local results should not be generalized across organizations with different role designs.

Conclusion

The defensible finding is procedural. Scope creep becomes visible when a documented duty baseline is compared with observed recurring work, temporary cover is time-bounded, and changes require a decision rather than accumulating by default. Public project and workforce guidance supports documentation and review, but the acceptable rate of change remains local policy.

Sources

• What is Project Management? Project Management Institute. https://www.pmi.org/about/what-is-project-management (checked 18 September 2026).
• Association for Project Management. Association for Project Management. https://www.apm.org.uk/ (checked 18 September 2026).
• NIST SP 800-53 Rev. 5, Security and Privacy Controls. National Institute of Standards and Technology. https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final (checked 18 September 2026).
• Classification and Qualifications. U.S. Office of Personnel Management. https://www.opm.gov/policy-data-oversight/classification-qualifications/ (checked 18 September 2026).
• Plain Language Guide. U.S. Digital.gov. https://digital.gov/guides/plain-language/ (checked 18 September 2026).
• SHRM. Society for Human Resource Management. https://www.shrm.org/ (checked 18 September 2026).