GratisAIcareer · field guide · local-first · no account
screening queue stub

Plan Screening Days From a Daily Minute Budget — Free

A hundred applications and a full calendar produce the same result: a silent backlog. Price each batch’s screening minutes against the minutes you can actually set aside and book the days before the queue starts to rot.

The proof surface

Application pipeline gauges track how long a job search can run on open leads. This converts a recruiter’s or hiring manager’s screening queue into the working days it needs.

Inputapplicant batch | applications to screen | minutes to screen one application; screening minutes available per day
Rare deviceApplication pipeline gauges track how long a job search can run on open leads. This converts a recruiter’s or hiring manager’s screening queue into the working days it needs.
Output artifactscreening days per row with transparent workings
Cost$0 · local-first · one free run · samples labelled
Sample, not your facts: Illustrative sample: Retail cluster | 12 | 25; Agency shortlist | 6 | 40. With screening minutes available per day set to 90, total screening days is 7.00 screening days.

Why the flat version breaks

Screening in the gaps between meetings

Interrupted screening produces inconsistent shortlists; booked minutes produce defensible ones.

Using the average screening time for every role

Portfolio, technical and senior roles take several times longer per application.

Screening the largest batch first

A small high-priority batch often decides the hire; order by decision value, not by queue size.

How to work the screening queue stub

Group applications into batches

Split the queue into the batches you will screen together — one posting, one agency shortlist, one referral group — so priorities stay visible.

Enter applications per batch

Use the number waiting now, not a running total for the quarter.

Time one screening pass honestly

Include opening the CV, checking against must-haves and writing the shortlist note: 25 minutes for a role with a short criteria list, 60 minutes where a portfolio or task must be reviewed.

Book the days the stubs demand

Ten applications at 45 minutes each is 450 minutes — five screening days at 90 minutes a day. Any batch needing more than five days is flagged so it is either split, delegated or descoped before it blocks the hiring decision.

What the screening queue stub replaces

QuestionBeforeVisible working
Screening in the gaps between meetingsInterrupted screening produces inconsistent shortlists; booked minutes produce defensible ones.Enter applications per batch
Using the average screening time for every rolePortfolio, technical and senior roles take several times longer per application.Time one screening pass honestly
Screening the largest batch firstA small high-priority batch often decides the hire; order by decision value, not by queue size.Book the days the stubs demand

A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.

Run it on the samples, right here

FIRST-LOAD

Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.

Throughput arithmetic on queue sizes and screening minutes you enter. Not HR compliance, equal-opportunity or employment-law guidance; follow your organisation’s recruitment policy and record-keeping rules, and do not use queue pressure to skip required review steps.

Data note: Everything runs in this browser tab on the screening queue stub: your applicant batch | applications to screen | minutes to screen one application stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.

Go deeper: the companion app files the same reading as a punched ticket stubs

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the screening queue stub reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.

The screening queue stub reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.

Open the plan screening days from a daily minute budget companion

Boundary

Throughput arithmetic on queue sizes and screening minutes you enter. Not HR compliance, equal-opportunity or employment-law guidance; follow your organisation’s recruitment policy and record-keeping rules, and do not use queue pressure to skip required review steps.

What this is built on

Before: Interrupted screening produces inconsistent shortlists; booked minutes produce defensible ones. After: the screening queue stub shows the working beside each named row so the reader can change the assumption and inspect the consequence.

Optional AI formatting, not calculation

For this screening queue stub, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.

Format my non-sensitive notes for a screening queue stub. Return plain rows only: applicant batch | applications to screen | minutes to screen one application. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.

Accepted schema: applicant batch | applications to screen | minutes to screen one application. No AI response is executed as code.