Plan Screening Days From a Daily Minute Budget
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.
1 · applicant batch | applications to screen | minutes to screen one application
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.
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.
Perspective: 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.
2 · Read the screening queue stub
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.
Paid layer: screening queue stub print and history
one-time step · the free reading above stays complete
Free tier
- one complete screening queue stub run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the screening queue stub with its row workings
- CSV of screening days and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the screening queue stub, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
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.
- Method: 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.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Mechanism: competence-autonomy-loop
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.