A worker with no expiry on its mandate will eventually treat yesterday's exception as tomorrow's policy.
A scope lease defines exactly what an agent may do, why it may do it, when the right expires, and who must renew it.
Machine workers do not ask for promotions. They absorb adjacent work because teams reward throughput and forget to retire exceptions.
Operators can move fast without letting successful edge-case handling become unmanaged organizational design.
Bad agent behavior gets noticed. Useful agent behavior gets copied. That is the trap. A worker that routes inbound leads well gets asked to enrich records. A support triage worker starts drafting replies. A RevOps worker that fixes missing fields begins changing lifecycle stages. Nobody announces a reorg. The mandate simply grows.
This is how autonomous companies accumulate invisible power. The machine worker did not break a rule. The team kept adding reasonable exceptions until the original rule stopped describing reality.
A scope lease makes that growth explicit. It says: this worker may own this action, for this customer segment, under this evidence standard, until this date, unless the human owner renews the right with proof.
Name the exact objects, channels, queues, customer types, and systems the worker may touch. Anything outside that surface is blocked.
Define whether the worker may recommend, draft, route, write, approve, send, refund, suppress, escalate, or override.
Attach a short renewal window. High-risk rights expire faster than low-risk research or internal classification rights.
Require evidence before extension: clean samples, incident count, owner review, customer impact, rollback test, and drift check.
Most teams treat agent scope as configuration. It is not. Scope is organizational power expressed in software. When a machine worker can change a CRM field, route a lead, send a message, suppress a campaign, or recommend a commercial action, it is participating in management.
The common failure mode is not a rogue agent. It is a helpful agent holding rights nobody remembers granting. A campaign exception survives after the campaign. A pilot segment becomes the default. A human override becomes a learned workflow. A borrowed data source becomes trusted evidence.
Example: a prospecting worker gets temporary permission to use conference attendance data during an event week. The event ends, but the permission remains. Two months later it still scores accounts with stale event intent and quietly distorts outbound prioritization. The error is not hallucination. The error is an expired mandate that never expired.
The agent, workflow, model, toolchain, or queue owner receiving temporary authority.
The exact systems, object types, segments, channels, and action classes covered by the lease.
The operating need that justifies the expanded mandate: campaign spike, owner absence, incident response, data cleanup, or measured throughput gain.
The date, volume threshold, campaign end, owner return, incident count, confidence drop, or policy change that forces review.
The sample quality, error rate, customer impact, rollback readiness, and owner sign-off required before the lease continues.
The point is not to slow every agent down. The point is to prevent accidental permanence. Fast teams need a way to say yes now without donating authority forever.
That is why leases should be short, visible, and tied to real operating proof. A low-risk research worker can keep a broad surface for longer. A worker that writes customer-facing messages, changes revenue records, or changes prioritization should renew frequently. The more the action affects trust, money, or workload, the shorter the lease.
Heads of Growth should like this control because it protects speed. When scope expires automatically, teams can run bolder experiments. They know the permission will be reviewed before it hardens into shadow policy.
Pick a new permission the worker wants: send, write, route, enrich, approve, suppress, score, or escalate.
Constrain it to a named segment, queue, system, campaign, or workflow. No vague “GTM support” mandates.
Set a renewal date or event trigger before the permission becomes normalized.
Require samples, incidents, reversibility, and owner judgment before the right continues.
Before giving any autonomous worker a broader mandate, write a one-page scope lease.
The blunt rule: no permanent agent mandate without a renewal decision.