Chasing is a job description, not a task
Audit preparation fails in the gaps between asks. Someone requests the access review, the owner is busy, four days pass, and now the deadline math is against you. The work is not hard; it is relentless, and relentless is exactly what humans are worst at sustaining.
The compliance employee opens a loop per piece of evidence: ask the owner in Slack, wait, nudge in the same thread with the context intact, and escalate to the manager with the deadline arithmetic spelled out when waiting stops being safe. Each loop knows whether the person replied. There is no blind every-two-days reminder; a loop that got its evidence closes itself.
The permission ladder did the trust work
Nothing about chasing is risky, so it runs at the act-and-log level. Filing evidence links is similarly reversible. The one action that touches the compliance system of record sits at the approval level: the employee prepares it, a human clicks Approve, and the audit trail shows exactly who decided what. The founder described their remaining job as reading well-prepared requests.
Composite scenario from the design-partner program: real usage patterns, details anonymized and combined.