research

Measuring how often password reset requests pass identity verification

A method for sampling password reset requests, scoring the identity checks recorded in each ticket, and finding where the desk departs from policy.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

UnitOne reset requestStudy protocol
Minimum sample30 requestsStudy protocol
Spot check10 per monthStudy protocol

Key takeaways

A password reset is the most common helpdesk request and one of the easiest places to skip a check. The person asking may be the account owner, a manager in a hurry, or an attacker with a name and a phone number. A verification routine only works if the desk follows it under pressure. This study measures how often reset requests pass the documented identity checks and where the process breaks.

Question and scope

The study asks what share of completed password reset requests include evidence that the requester's identity was verified before the reset. The unit is one reset request. The population is every request completed by the support desk during the study window. The result describes the recorded practice, not the intent in the policy. Record the systems covered and the channels through which requests arrived.

Include requests that arrive by phone, chat, email, and walk-up. Exclude self-service resets that the user completed without contacting the desk, but record how many occurred. Note the identity provider and the applications that use it. A study that counts only email tickets will miss the phone calls where verification is hardest to observe. Record the channel mix in the report so a change in the sample can be explained.

Define verification

Write the acceptable verification methods before scoring any request. Examples include a callback to the number in the directory, a video check against a photo ID, an in-person check, or a successful multi-factor challenge on a registered device. Record which method was used and who performed it. A request that only asks for a date of birth or an employee number does not meet the same standard.

Decide whether one method is enough or whether high-risk accounts need two. Define high-risk accounts in advance, such as finance, executive, and administrator accounts. Note the evidence that must appear in the ticket, not only in a chat thread. The definition should be specific enough that two reviewers reach the same verdict. Write the two-factor rule for high-risk accounts in the scoring sheet before the first review.

Build the request sample

Export the reset tickets from the helpdesk for the study window. Filter by the category or subject used for password resets and check the filter against a manual search. Record the total count and the number that could not be classified. Draw a random sample of at least thirty requests, or include every request when the volume is lower. Save the filter query with the export so another reviewer can reproduce the sample.

Add the requests that were handled outside the ticket system, such as chat messages that were never converted. Ask the desk lead whether those channels exist and how often they are used. Record the channel and the time of day for each sampled request. A sample that covers only office hours will miss the riskiest requests. Ask the desk lead to log those requests in the ticket system during the study window.

Score each request

For each request, record whether verification was documented, which method was used, and who performed it. Use three outcomes: verified, partial, or not recorded. A partial result means a check appears in the conversation but not in the ticket or the approved method. Keep the evidence link or quote beside the score. Use the same scoring sheet for every request so the outcome does not depend on the reviewer.

Have a second reviewer score a subset independently and compare the results. Discuss every disagreement and refine the definition rather than forcing agreement. Record the agreement rate and the changes made. A scoring sheet that only one person understands cannot support a repeatable measure. Aim for agreement on the definition rather than on the individual verdict. Record the revised definition and rerun the subset that caused the disagreement.

Interview the desk

Ask three agents to describe the last reset they handled and how they verified the caller. Ask what happens when the caller cannot use the approved method. Record the answers without attributing them to individuals. The interview explains the score and reveals the pressure points that the ticket data cannot show. Ask each agent what they would do if the caller could not answer any approved question.

Ask the desk lead how the policy is trained and where the approved scripts live. Check whether the scripts are current and easy to reach during a call. Note the tools that slow the check, such as a directory that requires a separate login. A verification step that takes five minutes will be skipped on a busy morning. Record the name of the script and the date it was last updated.

Separate policy from practice

Read the reset policy and list the checks it requires. Compare each requirement with the sampled evidence. Mark the clauses that cannot be verified from the ticket system. A policy that requires manager approval but has no place to record it is a policy that depends on memory. Add the policy reference and the approval date to the report so the comparison is reproducible.

Check whether the helpdesk tool has a required field for verification. If the field is optional, measure how often it is filled. Note whether the field records the method or only a yes or no. The tool shape tells you what the desk can prove after the call. Check whether the field is visible to the agent during the call or hidden behind a menu.

Report the share

Report the verified share, the partial share, and the not-recorded share with the sample size. Split the results by channel, by hour, and by account risk. Do not publish a single percentage without the denominator. A share from twenty tickets is a starting point, not a benchmark for the industry. Report the count of requests that had no verification at all as a separate line.

Add one example of a well-documented reset and one that failed the check, with names removed. Show the evidence that made the difference. Send the report to the desk lead and the technical owner. Ask them to confirm the numbers before the report is shared more widely. Remove the example from the shared version if it could identify the user.

Set a verification rule

Agree a rule that names the approved methods, the evidence field, and the escalation path when no method works. Require the field before the reset is completed rather than after. Name the person who reviews exceptions and the time limit for the review. The rule should be short enough to fit on the desk's quick reference card. Give the desk a one-page card with the methods and the escalation number.

Add a spot check of ten resets per month to the desk routine. Record the result with the same three outcomes and the same definitions. Share the monthly result with the team and fix the tool or the script when the same gap repeats. A rule that is measured is more likely to survive a busy week. Record the name of the person who completed the spot check.

Repeat the measure

Rerun the study after a tool change, a new script, or a staff turnover. A new agent may not know the approved method, and a new tool may change where the evidence is stored. Compare the new share with the previous result and check whether the sample is comparable. Keep the previous sample so a change in the share can be compared with a change in the desk.

Keep the scoring sheet and the sample export with the helpdesk documentation. Set a quarterly review and a monthly spot check. Record the date and the reviewer. The trend is more useful than a single result because it shows whether the rule is holding. Review the spot-check results with the desk lead before the quarterly report is written. Note the date of the review and the changes agreed with the desk.

Limits of the study

The study sees what the desk recorded, not every check that happened on the call. A good verification that was never written down will score as not recorded. The sample may also miss requests that were resolved by a manager outside the queue. State these limits so the report is read as an evidence review. Note whether the ticket system records the method or only the outcome.

The result describes one desk and one period. Do not generalise it to other teams or to the whole industry. Repeat the study with the same definitions before comparing periods. Use the findings to improve the process, not to rank individual agents. Share the report with the desk lead before anyone outside the team sees it. If the desk disagrees with a finding, record the reason and check the evidence again.

Check the reset tooling

Review the helpdesk form the agent uses during a reset. Confirm that it shows the approved methods and requires an evidence field before the ticket can be closed. Test the form as an agent would, including the case where the caller cannot use the first method. Record any step that forces the agent to leave the form and lose the call context.

Check the identity provider logs for the reset event and confirm that the ticket can be linked to the log entry. Note whether the log records the agent and the method. If the tools do not connect, the reviewer has to rely on memory. A small integration that writes the method into the ticket is often the most useful fix.

Use the result in training

Turn the common gaps into two or three short scenarios for the next desk meeting. Use a caller who cannot remember the registered number and a manager who demands an immediate reset. Ask the agents to walk through the approved response and the escalation. Keep the scenarios practical and free of blame. Record which scenarios were used so the next session can avoid repeating them.

Add the scenarios to the onboarding pack for new agents and review them after the first month. Record who completed the training and when. Recheck the same measures after the training to see whether the share changed. A training session without a follow-up measure is only an intention. Add the training date and the measured share to the same report.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the local administrator, password reset, vendor case, file restore, and browser credential measures discussed here. The NIST SP 800-63B digital identity guidance supports the verification and credential checks, NIST SP 800-34 contingency planning guidance supports the restore measure, and the GAO data reliability guidance supports the sampling approach. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the local administrator audit and the file restore timing study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the measuring how often password reset requests pass identity verification data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to measuring how often password reset requests pass identity verification, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
UnitOne reset requestStudy protocol
Minimum sample30 requestsStudy protocol
Spot check10 per monthStudy protocol

Sources

  1. NIST SP 800-63B, Digital Identity GuidelinesAuthentication and authenticator lifecycle guidance used to frame identity checks.
  2. NIST SP 800-53 Rev. 5, Security and Privacy ControlsIdentification and authentication control language for the verification rule.
  3. CISA Cross-Sector Cybersecurity Performance GoalsBaseline identity and access controls for small organisations.
  4. CISA: Avoiding Social Engineering and Phishing AttacksContext for attacker requests that target the reset process.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review