Skip to content
Calcrivo

Access Review Calculator

Size an access certification campaign: decisions to make, reviewer hours, elapsed days and the annual effort across campaigns.

Inputs

identities
entitlements
minutes
%
reviewers
hours
days
campaigns

Reviewer Hours per Campaign

468.0hours

Decisions in Scope

28,800

Decisions Needing a Human

18,720

Hours per Reviewer

11.7hours

Elapsed Days Needed

7.8days

Reviewer Hours per Year

1,872hours

Assessment

Fits inside the campaign window

Step by step

  1. Values used

    Identities in scope = 3,200 identities; Entitlements per identity = 9 entitlements; Minutes per approve or revoke decision = 1.50 minutes; Decisions auto-approved by policy = 35 %; Reviewers taking part = 40 reviewers; Hours per day a reviewer can give = 1.50 hours; Days allowed for the campaign = 14 days; Campaigns per year = 4 campaigns

  2. Access Review

    effort = identities × entitlements per identity × minutes per decision, less whatever policy auto-approves.

  3. Campaign duration

    elapsed days = hours per reviewer ÷ hours per day each reviewer can actually give.

  4. Reviewer Hours per Campaign

    = 468.0 hours

  5. Decisions in Scope

    = 28,800

  6. Decisions Needing a Human

    = 18,720

  7. Hours per Reviewer

    = 11.7 hours

  8. Elapsed Days Needed

    = 7.8 days

  9. Reviewer Hours per Year

    = 1,872 hours

How it works

Certification effort is a straight product, which is why it grows alarmingly: doubling entitlements per identity doubles the campaign. Auto-approving low-risk decisions by policy and reviewing only exceptions is the only lever that changes the shape of the curve rather than its slope. Reviews that cannot finish inside their window get rubber-stamped in the last two days, which produces a clean audit artefact and no actual reduction in access.

Formulas

Access Review

effort = identities × entitlements per identity × minutes per decision, less whatever policy auto-approves.

identities
Users, contractors and service accounts being certified
entitlements
Roles, group memberships and permissions attached to each identity
minutes per decision
Realistically 1–3 minutes once the reviewer has to think

Campaign duration

elapsed days = hours per reviewer ÷ hours per day each reviewer can actually give.

hours per day
Reviewers have day jobs — 1–2 hours is a realistic ceiling

Frequently Asked Questions

How is Access Review calculated?

effort = identities × entitlements per identity × minutes per decision, less whatever policy auto-approves. Certification effort is a straight product, which is why it grows alarmingly: doubling entitlements per identity doubles the campaign. Auto-approving low-risk decisions by policy and reviewing only exceptions is the only lever that changes the shape of the curve rather than its slope.

Why does Access Review matter?

Reviews that cannot finish inside their window get rubber-stamped in the last two days, which produces a clean audit artefact and no actual reduction in access.

What values do I need to enter?

This calculator takes 8 inputs: Identities in scope, Entitlements per identity, Minutes per approve or revoke decision, Decisions auto-approved by policy, Reviewers taking part, Hours per day a reviewer can give, Days allowed for the campaign, Campaigns per year. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

How long does one access decision really take?

Between roughly 30 seconds for a familiar group membership and several minutes when the reviewer has to work out what an entitlement grants. One to three minutes is the planning range, and the average rises sharply when entitlement names are technical rather than business-readable.

How do I cut access review effort?

Reduce what is in scope rather than speeding up reviewers: auto-approve unchanged low-risk entitlements, review by role rather than by individual permission, certify privileged and data-sensitive access more often and everything else less often, and remove orphan and dormant accounts before the campaign starts instead of certifying them.

You might also need