Separate process waiting time from applicant responsiveness using supplied timeline evidence. The download provides a specific review process. It does not make decisions or act in an account.
Download the free skill
One complete Markdown file. No subscription, checkout or fabricated setup files.
Download SKILL.mdWhat to provide
Approved candidate IDs, timeline events, timezone, service windows and documented pause policy.
How it works
- Pair explicit request and response events using the same timezone.
- Separate internal waiting, applicant-requested pauses and unknown ownership.
- Calculate elapsed time on the approved calendar. Do not invent weekend exclusions.
- Return process bottlenecks. Do not reject candidates, send nudges or collect health details.
The output
stage | start/end evidence | elapsed | wait owner | pause rule | unknown | reviewer
Worked fictional example
Fictional request Monday 10 AM, response Monday 1 PM: 3 hours elapsed. Panel review Wednesday 1 PM is 48 hours of internal wait, not 51 hours of candidate delay.
Checks and limits
Preserve source versions and original values. Unknowns stay unknown. Use a qualified reviewer for regulated, legal or hiring decisions. No send, share, account change, schedule, ledger update or payment is authorized. No live account test is claimed.
More recruiters workflows · How-to guides
Method: reviewed source. Demand lead: GSCrecruitmentpipeline/sourcing;distinctfromschedulingconflictmap. These are site-query cluster impressions and method evidence, not exact new-topic monthly search volume or a traffic promise. Checked October 3, 2026.