Practice operations library

Practice operations · checklist

Run an administrative access review

Start with the systems you use and check who has an active account, what role they have, and who is responsible for reviewing it. Record the review date, but no passwords or client details. Technical and regulated questions need qualified review.

Start the guide
01

Understand the work

Before the checklist

What this guide helps you do

Someone needed access quickly, so you added them. Months later, their role has changed and the account is still there. An administrative access review gives you time to check who has access, what it's for, and who can answer the questions you find.

If you are starting a practice

Build the habit while the list is short. Record the system, the account owner, the business reason for access, and the next review date—never the password itself.

If you already run a practice

Compare the accounts shown in the system with the people who work in the practice and their current responsibilities. If you can't explain someone's access, assign a person to check it.

An example of the resultA dated account list showing which active accounts were confirmed, who will arrange removal of unnecessary access through the approved process, and who will answer each open question. The notes contain no credentials or client information.
02

Start here

Start here

Before you start

  • Review ownership, account need, and role fit separately.
  • Never copy passwords, recovery codes, or client information into the worksheet.
  • Record uncertainty and assign follow-up instead of awarding a security score.

Make sure this fits

Use this for a generic administrative review of workforce accounts and roles in systems the practice already uses.

Pause when

  • The task requires vulnerability testing, access to credentials, investigation of an incident, or a legal or compliance conclusion.

Gather before you begin

  • A current system list
  • An accountable owner for the review
  • A safe place for non-sensitive administrative notes

What to have when you finish

  • A dated account-and-role review with owners, exceptions, and follow-up dates
Why this helps

Old accounts and unclear permissions can make day-to-day administration harder, especially when you need to respond quickly to a problem.

03

Do the work

Guided process

Work through the steps

  1. 01

    Choose the systems this review will cover

    Who handles itReview ownerTimingBefore viewing account listsWhyDecide which systems you're reviewing before you start. That keeps the list manageable and unrelated private information out of the notes.Save thisSystem name, business owner, technical contact, and review date
    Pause or get help when

    Pause if no authorized person can access the account list or identify the system owner.

  2. 02

    Compare active accounts with current roles

    Who handles itSystem ownerTimingFor each in-scope systemWhyCheck access against the person's current responsibilities. The reason for an account may have changed since it was created.Save thisUser identifier, role, business need, reviewer, and decision without secrets or client data
    Pause or get help when

    Use the approved offboarding or access-change process; do not disable access based only on this worksheet.

  3. 03

    Assign follow-up and schedule the next review

    Who handles itReview ownerTimingBefore closingWhyGive each unanswered question to someone who can follow up, and agree on when you'll check back.Save thisException owner, action, due date, and next review date
    Pause or get help when

    Route security, privacy, HR, legal, or incident questions to the appropriate qualified reviewer.

04

Finish well

Adapt, record, review

Record what you decided and what comes next.

If your situation is different

  • A solo practice may combine owner roles but should still record who made each decision and when.

Check your work

  • Every in-scope system has an owner
  • Every listed account has a documented role decision or open question
  • No passwords, tokens, recovery codes, client data, or sensitive employee details are recorded
  • Exceptions and the next review have owners and dates

Editable worksheet

Write down who will follow up.

Record who will follow up, where the approved records live, and what still needs an answer. Save the draft in this browser or print a copy. Browser storage is not secure record storage. Do not enter client details, credentials, health information, financial account numbers, or sensitive employee information.

Your draft stays in this browser.

Keep a copy

Download a PDF to keep or an editable Word document to continue working. The file is created on your device.

Removes the answers saved in this browser.

Common mistakes

  • Treating an account-list review as proof that permissions are technically correct or that the system is compliant.
05

Verify the work

Sources and review

Sources and limits

Scope: This administrative checklist does not test security controls or determine legal, privacy, employment, licensing, or compliance status.

Approved claims and boundaries

Does an administrative access review prove that a system is secure or compliant?

No. It can identify accounts, roles, owners, and follow-up work, but it does not test technical controls or establish legal, privacy, security, or compliance status.

Applies to: Generic administrative review of workforce access without recording passwords, secrets, client details, or sensitive employee information.

  • Technical testing and regulated conclusions require the appropriate qualified reviewers.

Source record

  1. Practice Hub research methodologyLudara · Governing project standardChecked 2026-07-23

Last reviewed: 2026-07-30. Information and requirements can change; confirm consequential decisions with the cited authority or an appropriate professional.

Report a possible error or better source