Tracking & audit

“Who approved this?” answered in ten seconds.

Every action against every request is timestamped and tied to a person — including the ones taken by guests and agents. Above that sits the reporting that tells you where your process is actually slow, and a public tracker so submitters stop asking.

Free plan, no card required. Submitters are always free.

Audit log

FIN-284
  1. Request submittedSarah K.
  2. Routed to FinanceAutomatic
  3. Question askedMark T.
  4. AnsweredSarah K.
  5. Reminder sentAutomatic
  6. Approvedexternal:cfo@acme.com
01Day to day

Six surfaces, each answering one question

A dashboard that tries to answer everything answers nothing. Each of these has a single job, and the command palette gets you between them.

Overview

What needs you and what's moving, with an AI ask-bar for the question the dashboard didn't anticipate.

My Tasks

Reviews waiting on you, sorted by urgency, with a card queue, bulk actions, and questions directed at you.

My Requests

Everything you submitted, with live status and the approver avatars — so nobody has to ask “any news?”

Inbox

The workspace activity feed, with archive and restore, for the things you want to know about but don't own.

Saved views

Save a filter combination you keep rebuilding. Admins can share a view workspace-wide.

Command palette

⌘K to jump to any request, template, team, or member without navigating there.

02The record

Evidence, not recollection

Audit log

Actor, timestamp, IP, user agent — on everything

Not just decisions. Member changes, team changes, template edits, group edits, status changes, workspace settings, and every approval or rejection, including those made by external guests.

  • External decisions attributed as external:<email>, never anonymised into “someone”
  • Agent runs emit audit events like any other participant
  • Manual status overrides are visibly marked, with a return-to-automatic path
  • Workflow restarts are recorded, so a re-run can't quietly rewrite history

audit_event

actor
member:sarah.k@acme.com
action
request.decision.approved
target
FIN-284
at
2026-08-06T11:27:04Z
ip
203.0.113.42
user_agent
Mozilla/5.0 … Safari/605.1

Decision narratives

The history, written as a paragraph someone will actually read

When a request closes, the AI turns the raw event trail into a readable account of how it was decided — who raised what, what changed, and what finally settled it. The raw log stays underneath it, untouched.

  • Generated from real events, not from a template
  • Sits alongside the audit log rather than replacing it
  • Makes a two-month-old decision legible without reconstructing it
How the AI layer works

Decision record — FIN-284

Sarah K. requested a replacement laptop on 4 August, citing a 2019 unit failing CI builds. Mark T. asked which cost centre it should land against and Sarah confirmed ENG-04 the following morning. After a reminder on 6 August, the CFO approved it externally by email at 11:27. Total time to decision: two days, three hours.

2 days to decision1 question resolved1 reminder sent1 external approver
03Analytics

Twelve measures, and one that matters most

Slowest workflow steps is the one people act on. Everything else tells you whether the process is healthy; that one tells you exactly where to go and fix it.

Resolution rate
Median time to first review
End-to-end cycle time
Deadline-risk count
Request volume trends
Reliability trends
Status breakdown
Deadline compliance monitor
Slowest workflow steps
Response time by team
Reviewer activity
Decision-level reporting

Basic analytics on Pro, advanced on Business. Compare plans →

04Shareable status

Package tracking, for approvals

Submitters chase because they can't see. Give them a link and the chasing stops — without exposing anything that isn't theirs to see.

Public tracker

A read-only link the submitter can forward to their own stakeholders

Branded, revocable, and view-counted. Deliberately limited to reference, title, status, and milestones — the projection is a security boundary, not a convenience.

  • Never shows reviewers, comments, or the answers on the form
  • Revoke at any time; revoked and invalid links render identically
  • View count tells you whether anyone is actually watching
  • White-labelled on Business, without the Requester mark

getrequester.com/status/…

FIN-284

Purchase request — MacBook Pro

  1. Submitted
  2. In review
  3. Approved
  4. Closed

No reviewers, comments, or form answers are ever exposed here.

14 viewsRevocable
05Getting told, getting out

Notifications in, data out

16 notification types

Assignment, decisions, changes requested, mentions, nudges, workflow status, role changes, invitations — each per-user configurable.

Push & PWA

Install it to a home screen and get web push, so an urgent approval isn't waiting on someone opening a laptop.

Digest emails

A cron-driven roll-up with per-user preferences, for people who'd rather have one email than fourteen.

Export everything

One JSON file with the entire workspace, plus CSV for request lists. No lock-in, no support ticket required.

The projection is the security boundary. A status page shows a reference, a status, and a milestone — and structurally cannot show anything else.
On what a public status page is allowed to contain
06Questions

On the record and the reporting

What exactly does the audit log record?
Who did what and when, with actor, IP address, and user agent. It covers members, teams, templates, groups, statuses, requests, decisions, workspace settings, and external-approver decisions — the last recorded as external:<email> so a guest decision is as traceable as a member's.
Can I share a request's progress with someone outside the workspace?
Yes, with a shareable status page: a read-only public tracker link, like package tracking. It's branded, revocable, and view-counted, and it deliberately shows only the reference, title, status, and milestones — never reviewers, comments, or the answers on the form.
Can I get our data out?
Any time, and completely. The full workspace export is one JSON file containing teams, templates, fields, requests, answers, comments, history, decision narratives, members, and guest approvers. There's also CSV export for request lists and single requests.
How do I find where requests are actually getting stuck?
The slowest-workflow-steps report ranks steps by how long requests sit in them, and response time by team shows which group is the bottleneck. That's usually a staffing or rule problem rather than a tooling one — but you can't fix it until you can see it.
Are analytics available on the free plan?
No — analytics and audit logs start on Pro, with advanced analytics on Business. The free plan covers the full approval lifecycle; reporting on it is where paid begins.

Make the next audit a search, not an archaeology project.

Every decision recorded against a person, every stalled step visible, and the whole workspace exportable in one file. Start free and see what your current process has been hiding.