Guide // MandateGuard
How do per-period budgets and authority windows pace an intent?
By the Ingenious AI team · Published 2026-11-14 · Reviewed 2026-11-14
▸ Run the free live demo See pricing
Free covers 1 agent and 1 policy with the full authorize flow, signed receipts and the approval inbox — no card required to start.
Short answer
Per-period budgets pace an intent — a cap on spend inside each period, such as 200 dollars per 30 days — while the authority window bounds the intent's whole life, after which the mandate simply ends. Together with the cumulative budget they bind pace, total and time: an authorisation must satisfy all three, plus the agent's own policy. Set the period figure from a normal period's real spend with modest headroom, choose the window to match the arrangement's true lifespan, and review period and cumulative gauges together at each period close.
What are per-period budgets and authority windows?
A per-period budget caps spend within each recurring period (for example 200 dollars per 30 days) inside an intent; the authority window is the date range during which the intent is alive at all. MandateGuard shows period spent against period budget alongside the cumulative figures, and intent detail displays the window's start and end. Period budgets govern pace; the window governs existence; the cumulative budget governs total commitment.
Pacing: the failure mode period budgets prevent
Without pacing, a mandate's budget is available at its fastest possible burn rate. Agents do not experience months; a quarter's budget can be consumed in a week of enthusiastic purchasing that is individually legal and collectively absurd — the stock bought for a season, the credits bought for a year, in the mandate's first days. A per-period budget converts the total into a rhythm the principal actually agreed to: this much per period, every period, for the window's length. It also smooths the relationship's cash reality for merchants and issuers, who can forecast mandate-backed volume period by period instead of bracing for arbitrary spikes.
Choosing the period and the figure
Pick the period from the underlying commerce: monthly billing cycles suggest 30 days; a fortnightly operations rhythm suggests 14. Then set the figure from a normal period's real spend, with headroom for a busy one — commonly a quarter to a third above normal. Set it at the busiest period's level and pacing stops meaning anything; set it at the average and ordinary variance will exhaust it mid-period regularly, training everyone to treat exhaustion as routine. The intent's period gauge (spent against period budget) makes the tuning empirical: after two periods you will know whether the figure describes the work or fights it, and successor intents can be registered with the corrected rhythm.
The authority window: a mandate with a lifespan
The authority window answers when the mandate exists. Registration can set a window in days (with intent detail showing the resulting valid-from and valid-until); outside it, the intent confers no authority. Windows matter because mandates otherwise default to immortality: a permission granted for a project quietly survives the project, the team and sometimes the relationship. A window forces the healthiest question in authorisation management — should this still exist? — to be answered by default rather than by memory. For arrangements that genuinely continue, registering a successor intent at renewal is a small ceremony that re-confirms scope, budgets and merchants against current reality.
How period, cumulative and window compose
The three controls bind different dimensions and an authorisation must satisfy all of them, along with the agent's policy. The window says the mandate is alive. The period budget says this period has room. The cumulative budget says the arrangement has room. An intent can therefore pause for three different reasons — out of period, out of total, or out of time — and the intent's displayed state (period spent, cumulative spent, window dates) tells every party which one applies. That legibility is the shared-state dividend: nobody needs to ask the issuer why a purchase stopped, because the mandate's own figures answer, identically for agent, merchant and issuer.
Operational rhythms around periods
Build two habits. At each period close, glance at period consumption beside cumulative consumption: a mandate consuming periods fully while its cumulative gauge crawls may be over-paced or under-totalled; one barely touching period budgets while the window ages may be over-scoped. And calendar the window's end when the intent is registered, not when it surprises you — renewal decisions deserve the same lead time as the original registration. Suspensions inside the window (for investigations or pauses) do not extend it, so a long suspension late in a window is effectively an early end; plan accordingly if the mandate's work must complete.
When pacing is the wrong tool
Not every mandate needs a period budget — it is optional at registration for a reason. One-off purchases with a hard total, short windows where the whole budget is expected to move quickly, or arrangements where the merchant relationship itself paces delivery may be cleaner with cumulative and window alone. The test is front-loading risk: if spending the whole total in week one would be a genuine harm (cash flow, stock timing, programme design), pace it. If it would merely be unusual, the cumulative budget plus human oversight is probably the proportionate control, and simpler mandates get read more carefully by everyone who must honour them.
Five actions to take now
- Set the period budget from the mandate's natural rhythm (a normal month, not its best month)
- Choose period days that match the commercial cycle — 30 is a sane default
- Set the authority window to the arrangement's real lifespan, with margin for settlement
- Review period consumption beside cumulative consumption at each period close
- Use suspend for pauses inside a window rather than letting a stale mandate sit live
Worked example: pace and lifespan on a 12-month intent
A charity registers a 12-month intent for an agent that buys translated materials monthly: cumulative budget 3,600 dollars, per-period budget 400 dollars per 30 days, authority window 365 days. Most months spend 260 to 330 dollars. In month four a conference doubles demand: the agent spends the period's 400 dollars by day 19, and further authorisations under the intent wait for the next period — the annual total was never at risk, because pace and total are separate controls.
The window matters at the other end: when the programme ends at month twelve, the intent expires with 410 dollars unspent. The unspent remainder lapses with the mandate rather than lingering as live authority — the window closed it automatically, with the full event history preserved for the charity's auditors.
Frequently asked questions
What happens when the period budget is spent early?
Authorisations under the intent pause until the next period. Needs that cannot wait are a renegotiation — usually a successor intent — not an override.
Can periods be shorter than a month?
Period days are set at registration (30 is the common shape). Choose the period that matches the commercial rhythm you are pacing.
Does the authority window auto-close the intent?
The window bounds validity; intent detail shows valid-from and valid-until. Treat expiry as the mandate ending, with history preserved.
What if no per-period budget is set?
It is optional. The cumulative budget and window still bind. Add period pacing when front-loading is a real risk.
How do windows interact with suspend?
Suspend pauses inside the window, reversibly. The window keeps running; when it ends, the intent's life ends regardless of suspensions.
Keep reading
- How do cumulative budgets work on an agent intent?
- When should you suspend, resume or revoke an agent intent?
- What is an AP2-style intent mandate for agent payments?
Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides