ConceptDiscovery layer

Delegation Boundary Map

The Delegation Boundary Map is a framework for deciding which agency tasks a personal assistant should own outright, which it should draft for human approval, and which it should never touch.

By InnovaAI ResearchPublished Updated

What is Delegation Boundary Map?

“Task type → delegation depth → governance tier”

Task risk on one axis, assistant autonomy on the other

The Delegation Boundary Map is a framework for deciding which agency tasks a personal assistant should own outright, which it should draft for human approval, and which it should never touch. The map has three tiers. Tier one covers deterministic, low-context work: scheduling back-and-forth, hold placement, and follow-up reminders. Tier two covers context-heavy drafting that still needs a human signature, such as client correspondence or proposal language. Tier three covers anything touching pricing, scope changes, or relationship repair, where an assistant can prepare inputs but never send. The framework matters because agencies tend to delegate by tool capability rather than by task risk, which is how a calendar secretary ends up negotiating a retainer renewal. Howie, for example, handles multi-calendar availability checks and reply threading across email, iMessage, and SMS, which is squarely tier one work. Jace drafts replies in a user's voice and triggers cross-tool actions, which sits in tier two and needs a review gate before anything reaches a client inbox.

personal-assistants