Human Resources Outsourced research
How old are open leave of absence requests?
A proposed protocol for measuring the age and ownership of open leave requests.

Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how old open leave requests are at review. The result would describe the leave queue. Ask whether a new reviewer could act on the record without a conversation.
The protocol does not measure whether the leave was approved. It measures whether the request was owned. Ask whether a new reviewer could act on the record without a conversation. Record the exception and the person who approved it.
Population and unit of analysis
Define the population as leave requests open on a stated date. The unit is one request, with the dates, approver, and next step recorded. Update the template when the same question appears twice. Keep the boundary visible in the place where the work is assigned.
Link the request to the employee so the same request is not counted twice. Ask whether a new reviewer could act on the record without a conversation. Keep the boundary visible in the place where the work is assigned. Record the exception and the person who approved it.
Definitions and measures
Define age as the time between the request and the review date. Define ownership as a named approver and a next action. Record the date and the source so the next reviewer can repeat the check. Review the first few notes together before the process expands.
Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it.
Evidence standard
Use the leave record and the approval log. A pending note without a date is weak. If the source is unclear, route the question instead of guessing. Review the first few notes together before the process expands.
Record the date and the approver. Review the first few notes together before the process expands. Keep the boundary visible in the place where the work is assigned. Keep the original note beside the corrected version.
Sampling and collection
Use a census of the open requests. If sampling is necessary, stratify by leave type. Separate what was observed from what was assumed. Test the rule on one real file before applying it to the team.
Pilot the review on a few requests and compare the reviewers. Clarify how a partial approval is treated. Record the date and the source so the next reviewer can repeat the check. Use the same format for every handover so the next reader can scan it.
Analysis and reporting
Report the age distribution and the ownership rate by type. Show the requests without a next date. Separate what was observed from what was assumed. Update the template when the same question appears twice.
Present the results as a description of the queue, not a judgment about the employee. Name the owner in the same line as the action. Record the exception and the person who approved it. If the source is unclear, route the question instead of guessing.
Limits and sources of error
The request may be in a different system. State the systems included. Keep the boundary visible in the place where the work is assigned. Ask whether a new reviewer could act on the record without a conversation.
The medical detail may be restricted. Record only what the process requires. Name the owner in the same line as the action. A control that depends on memory is not yet a control.
Review cadence
Repeat the review after a policy change or at the same interval each month. Compare the same leave types. Write the deadline as a date and a local time. Update the template when the same question appears twice.
Assign the follow-up to the HR lead and set a date. The protocol should produce a specific decision about the leave queue. Ask whether a new reviewer could act on the record without a conversation. If the source is unclear, route the question instead of guessing.