← Go back

Guide // MandateGuard

How does the reviewer card decide within, needs approval, or outside mandate?

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

The reviewer card is where a spend envelope meets a real request: one screen showing the vendor, amount and reference against the envelope's approved vendors, period, conditions and remaining total, with MandateGuard's computed verdict — within mandate, needs approval, or outside mandate. Within proceeds and is receipted; needs approval waits for a human deciding with full context; outside mandate cannot be waved through — the spend is declined or the envelope is deliberately redefined. The card's completeness is the control: decisions made from full context, preserved in the hash-chained receipt trail.

What is the reviewer card?

The reviewer card is MandateGuard's single-screen presentation of a spend request evaluated against a spend envelope. It shows the request (vendor, amount, reference) against the envelope's terms — approved-vendor membership, period validity, approval conditions, spent-versus-maximum position — and the engine's computed decision in one of three states: within mandate (may proceed), needs approval (a human decides), or outside mandate (does not fit the envelope).

One card, because fragmented decisions fail

Approval quality collapses when the decider must assemble context: the request in one system, the budget in a spreadsheet, the conditions in a chat thread, the vendor list in someone's memory. Under that friction, reviewers either slow to a crawl or start approving from the amount alone. The reviewer card is designed against that failure: a single screen carrying the request and every mandate fact it must be judged against. The design premise is that most spend decisions are easy when the context is complete — vendor in or out, dates valid or not, conditions met or not, this much of the envelope already consumed — and hard only when the context must be gathered. Gather it once, in the product, forever.

Within mandate: the quiet state

A within-mandate verdict means the request fits every term of the envelope: approved vendor, live period, conditions satisfied, envelope total not exceeded. No human action is required and the spend proceeds under the envelope's authority, receipted like any decision. Reviewers still benefit from seeing these on the envelope's record, because the pattern of within-mandate spends is the task's financial story forming in real time: burn rate against the period, vendor split, batch sizes. A task consuming its envelope far faster than its timeline predicts will show it here first, while there is still time to ask whether the task or the estimate was wrong.

Needs approval: judgement with the facts attached

The needs-approval state fires when a request fits the envelope's hard terms but crosses a written condition — classically the per-spend approval level. The card then waits for a person, and the person decides with the full context in view: not just 95 dollars, but 95 dollars from an approved vendor, inside the period, taking the envelope to a stated position, for a stated task reference. That context is what separates a decision from a reflex. Reviewers should treat repeated needs-approval items as calibration data: if every second purchase needs approval, the level was set below the task's natural batch size; if none ever does, the condition may be decorative. Tune the next envelope accordingly.

Outside mandate: a boundary, not a rejection form

Outside mandate is the card's most valuable state precisely because it cannot be waved through. It means the request does not fit the envelope as written — wrong vendor, dead period, total exceeded — and therefore the honest options are only two: decline the spend, or change the mandate deliberately by redefining the envelope with eyes open. What it prevents is the quiet third option that plagues approval systems: approving anyway and letting the record imply the mandate covered it. When outside-mandate requests recur for the same task, read them as the task telling you its true shape: perhaps a vendor was genuinely needed, perhaps the total was under-estimated. Redefine the envelope in a considered act, and let the redefinition itself be part of the record.

Card decisions inside the evidence trail

Every card outcome extends the workspace's hash-chained receipts, so an envelope's history can be replayed decision by decision: the mandate as written, the requests as they arrived, the computed states, the human decisions on the middle state. For client-billed or grant-funded tasks, that replay is the accountability artefact — it shows not only that spending stayed inside a total, but that each step was inside the terms or visibly escalated when it was not. Reviewers internalise this quickly: deciding on the card feels consequential in the right way, because the decision's context and outcome are preserved together rather than scattered across an inbox and a bank feed.

Designing envelopes the card can judge

The card is only as decisive as the envelope behind it. Conditions written vaguely (large spends need approval) force the engine and the reviewer to improvise; conditions written numerically (single spends over 80 dollars) evaluate cleanly. Vendor lists that name the actual charging entities spare reviewers a class of false outside-mandate verdicts. Periods with real dates let the card catch stale-task spending automatically. When you review a closed envelope, grade the envelope itself: how many decisions were mechanical, how many needed interpretation, how many outside-mandate states were really drafting errors? That grading is how an organisation's envelopes get sharper quarter by quarter, and it starts with taking the card seriously as the mandate's moment of truth.

Five actions to take now

  1. Judge the card as presented: vendor status, period, conditions, envelope position
  2. Approve inside the envelope's terms; anything outside them is a mandate change, not an approval
  3. Use needs approval as a real decision point, not a queue to clear
  4. If outside-mandate requests recur, the envelope was mis-scoped — redefine it deliberately
  5. Close reviews by reading the envelope's full decision list, not just its total

Worked example: three cards on a Wednesday

An envelope funds a data-cleaning task: maximum 300 dollars, vendors A and B, period ending Friday, condition that single spends over 80 dollars need approval. Three requests arrive on Wednesday. Forty-five dollars from Vendor A: within mandate — vendor approved, period valid, under the approval level, envelope at 120 of 300 dollars spent. It proceeds with its receipt.

Ninety-five dollars from Vendor B: needs approval — everything fits except the amount crosses the written condition, so the card waits for a person, who approves after checking the batch size. Sixty dollars from Vendor C: outside mandate — a fine price and a valid day, but the vendor is not the envelope's. Three cards, three different correct actions, each decidable in under a minute because everything the decision needs is on the card.

Frequently asked questions

Who is the reviewer?

Whoever the workspace designates for envelope decisions — typically the task's owner or budget holder, working from the envelopes surface.

Can a reviewer approve an outside-mandate request from the card?

Outside mandate means the request does not fit the envelope's terms. Proceeding requires changing the mandate — a deliberate redefinition — not an approval click.

What does needs approval depend on?

The envelope's conditions: commonly a per-spend approval level written into the envelope, applied by the engine's evaluation.

Are card decisions receipted?

Yes — envelope evaluations join the same hash-chained receipt trail as policy decisions.

How is this different from the approval inbox?

The inbox supervises standing-policy requests against thresholds. The card judges a request against one task's full written mandate — vendors, period and conditions included.

Keep reading

Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides