Small-business outsourcing research
How often do new-hire account requests wait more than one business day?
A protocol for measuring how long new-hire account and equipment requests wait for approval before the start date.

Research question and scope
This protocol asks how often a new-hire account request waits more than one business day for the approval it needs. The unit is one request line, not one new hire and not one system. The study measures the approval delay, the share of lines still open at the start date, and the equipment lines that arrived late. It does not judge whether the requested access was appropriate.
Set the scope to one business, one hiring process, and one approval rule. Record the request system, the approval matrix, and the definition of a business day. If the rule changes during the window, keep the original rule for requests already opened and analyze later requests separately. A new approval tool can reduce delay without any change in manager behavior.
Define the population as every request line created for a hire with a start date in the window, including lines that were cancelled before approval. State any exclusion, such as a contractor request handled by another team, and apply it to every line. Test the definition on two completed hires before collection begins. The reader should be able to rebuild the population from the request log.
Definitions that make the measure reproducible
Define the clock start as the time the request line was submitted, not the time the hire accepted the offer. Define the clock stop as the time the approver recorded a decision in the request system. A verbal approval is not a stop until it is entered. Record both timestamps to the minute when the system supports it.
Define a business day using the business calendar, excluding weekends and stated holidays. Record the time zone used for the calculation. A request sent late on Friday and approved Monday morning is one business day, not three calendar days. Report both calendar and business-day delays so the reader can see the difference.
Use the same request export for every hire and keep the export timestamp beside the file. Record any line that was approved outside the system and later entered by hand. If a manager delegates approval, record the delegate and the date of the delegation. A delegated approval that is not recorded can look like a delay when it was actually a handoff.
Evidence standard and data dictionary
For each request line, capture the hire identifier, the role, the start date, the system, the access level, the submitted time, the approved time, and the approver. Add the provisioning time and the first successful login when available. Record whether the line was part of a standard bundle or an exception. Keep the request and approval records linked to the same line.
Capture the reason for delay when it is documented: approver leave, a missing manager, a new system, a security review, or an incomplete request. Do not infer a reason from an empty field. If the reason is unknown, mark it unknown and report the count. A guessed reason makes the process look cleaner than the evidence allows.
Record the number of reminders sent and the channel used. A reminder that reaches the approver on the start date is different from one sent at submission. Note whether the business has a written escalation rule and whether it was followed. A policy that exists but is never used is a different finding from no policy at all.
Sampling and collection
Collect every request line in the window rather than a sample, because the approval rule applies to each line. If the business has several locations or entities, collect each separately and record the entity. A combined rate can hide one manager or one system with a persistent problem. Report the number of hires and lines behind every percentage.
Draw times from the request system audit log, not from a spreadsheet the coordinator maintains after the fact. If the audit log is incomplete, say so and reduce the claim. Record the export date, the filters, and any line that could not be matched to an approver. A missing audit trail is itself a finding about the control.
Ask the coordinator to identify hires whose start date moved earlier or later than planned. A moved start date can create delays that have nothing to do with the approver. Record the change and analyze those hires separately. The reader should be able to tell whether the rate reflects the rule or the calendar.
Analysis and reporting
Report the share of lines approved within one business day, the share approved later, and the share still open at the start date. Show the median and range of approval delay in business hours. Present the results by manager, system, and role. Use the same denominator for every rate.
Separate approval delay from provisioning delay. A line approved on time but provisioned late is an information-technology problem, while a line approved late is a management problem. Report both because they lead to different fixes. A business may accept a provisioning delay but should not accept an unapproved account without a documented decision.
Inspect the slowest lines and describe which stage dominated without naming the manager. A missing request detail, an absent approver, and a security review each point to a different repair. Compare the delay with the reminder schedule and the start date. Report lines with incomplete timestamps rather than dropping them from the denominator.
Limits of the evidence
The record can show when an approval was entered, but it cannot show whether the approver actually understood the request. A quick click and a careful review look the same in the audit log. The protocol also cannot capture a verbal approval that was never entered. State that limitation before presenting the rate.
A small business may have too few hires to support a stable trend. Describe the hires and the request lines instead of ranking managers. If one owner approves every request, the result may reflect that person's availability more than the process design. Do not use the rate as a performance score without the context of leave and turnover.
Do not compare a business that holds the start date until approval with one that lets the hire begin and fixes access later. The two operate different controls even when the delay looks similar. Report the start-date rule beside the rate. A target that can be met by delaying every start is not a good target.
What to change
Give the result to the hiring manager and the coordinator and ask them to choose one observable change. The change might be a request deadline, a named backup approver, a standard access bundle, or a daily approval check. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions after the change.
If the approval delay falls but the provisioning delay rises, requests may be approved earlier without reaching the systems any faster. If both fall but exceptions rise, the team may be routing around the approval rule. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.
Ask the coordinator which request was hardest to complete and why. A concrete answer often reveals a missing role definition, a system owner who never responds, or a bundle that does not fit the job. Use that answer to improve the request rather than to blame the manager. The next measurement should test whether the same delay shrank.
Sources
- NIST Cybersecurity Framework, NIST Cybersecurity Framework; checked 2026-11-16
- Cybersecurity and Infrastructure Security Agency, best practices, Cybersecurity and Infrastructure Security Agency; checked 2026-11-16
- U.S. Department of Labor, recordkeeping, U.S. Department of Labor; checked 2026-11-16
- U.S. Small Business Administration, hire and manage employees, U.S. Small Business Administration; checked 2026-11-16
Frequently asked questions
Does a favorable sample prove the routine caused the result?
No. The design is observational and supports a bounded operating decision, not a universal causal claim.
What should an owner review first?
Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.
Related research
How often do vendor tax records arrive with a missing classification?
A protocol for measuring how many vendor tax records reach payment with a missing or mismatched tax classification.
What share of customer deletion requests close within the stated window?
A protocol for measuring how many customer deletion requests close within the business's stated response window and where the delay occurs.
What share of customer estimates go out without a follow-up date?
A protocol for measuring how many customer estimates leave a service business without an owner and a dated follow-up.