## TL;DR
Check three things: is this person who they claim (identity), does the access match their role (need), and is the duration bounded (time). Approve within one business day; delegate approvals when you are out. Most delays come from approvers not knowing what they are checking, not from diligence.

## The error
```text
(Process guidance; no error.)
```

## Steps
1. Verify identity: the request names the right person and you know them or can confirm with HR. Expected: confirmed. Never approve access for someone you cannot identify.
2. Check role fit: does this access match what the person does? Expected: yes or a justification that makes sense. "Marketing needs production database" deserves a question.
3. Check duration: is there an end date, and is it reasonable? Expected: bounded. Open-ended access is how privilege accumulates.
4. Decide within one business day. Expected: SLA met. If you cannot decide, ask one clarifying question rather than sitting on it.
5. Set a delegate for when you are out. Expected: delegate configured. Approvals must not wait for vacations.

## When to use
- Training new approvers
- Fixing slow approval queues

## When not to use
- IT-side provisioning
- Privileged access approvals (stricter process)

## Compatibility
- Any approval workflow; the checklist is universal

## Variants
### Bulk approvals for a new team
Approve the standard bundle once per role, not per person per app.
### Approver is the requester
Route to their manager instead; self-approval is never allowed.

## Why it happens
Approval queues stall because approvers treat every request as a deep investigation or ignore them entirely. The three checks make approval fast AND meaningful.

## Edge cases
- Track approval times; chronic slow approvers need a nudge or a delegate.
- Document approvals; auditors will ask who approved what.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_bDX4cAZiq6xjsqKbuN8VFg