Lever screening for an HR team of one: a review plan

By Screened · Researched 26 September 2026

You have three hours for recruitment this week and 500 applications in Lever. Payroll and onboarding still need doing. Reading faster will not make those responsibilities disappear.

Plan what those three hours can finish before promising a shortlist. Divide the time between CV reviews, candidate messages and manager decisions. Use it to make a specific request for help and test whether another screening tool would reduce the work.

How can an HR team of one manage a Lever screening backlog?

Start with one vacancy. Separate unread applications from those waiting for a document, a manager's decision or an interview booking. Read the latest activity rather than assume an early-stage application has never been reviewed.

Use replacement CVs already supplied, leave withdrawn applications out of screening and continue interviews already agreed. The catch-up plan should move each person to the right next step, not start everyone again.

Work with the individual job application, called an opportunity in Lever. Check the role as well as the person's name before reading the notes or arranging another interview.

For each outstanding task, keep the relevant Lever opportunity link, next action, owner and agreed date together. Leave the CV and candidate messages in the approved hiring system. The plan should point a colleague to the work, not create a second set of application records to maintain.

Calculate whether the plan fits before promising a deadline

Start with the time to read the CV, check the requirements and write a recommendation. Report-generation speed is not a substitute for that measurement.

The calculation assumes two minutes per review, 500 unread applications and three hours available. Replace the review time with your own before committing to a deadline:

The three-hour block covers 90 applications. The remaining 410 need 13 hours 40 minutes at the same pace, before new arrivals, follow-up replies and interviews. For a queue that is still growing, use our backlog catch-up calculation.

Ninety reviews is the ceiling only if you spend all three hours reviewing CVs. Reserve time for the work those reviews create before making a commitment. A more workable allocation could be:

This plan allows 60 first reviews, with time reserved for requirements and messages. It does not assume every resulting question or interview can also be completed that week.

Take that plan to the manager:

I have three hours for recruitment this week. I propose using two for 60 CV reviews and one for requirements, candidate messages and decisions that need your input.

That leaves 440 of the original applications awaiting review, before new arrivals. Can we arrange additional help or agree a later completion date?

Use your measured timings to agree the commitment. Neither 60 nor 90 clears the backlog; the useful target is work your team can actually finish.

Agree which decisions need the hiring manager

Agree what you can decide independently and what needs the manager. Routine clarifications should not need a fresh approval every time. A disputed requirement or an interview decision outside your authority does.

For an HR coordinator, the unclear requirement might be “onboarding experience.” Does the manager need someone who books induction sessions, or someone who manages everything needed before a new hire starts?

Show two examples. One applicant booked training sessions from a checklist. Another chased missing paperwork, arranged equipment and checked that everything was ready for the person's first day. Ask which responsibilities this job needs. Settle that once rather than asking again for every CV.

Give the manager a decision they can answer, supported by one or two application examples: “Can we train someone on the pre-start checks, or must they already have coordinated them?” Agree a response date and time for any interviews that decision may approve.

Apply the manager's answer consistently across comparable applications. Keep an application awaiting their decision visible as such; another CV review will not provide the approval it needs.

Reserve time to act on the response. Approval to interview creates a booking and a candidate message. It is not the end of the task, and those actions should not depend on an empty inbox you are unlikely to have.

Can Lever's existing resume review help?

Lever's guide to reviewing new applicants describes Fast Resume Review for opportunities in New Applicant. It presents the CV and application answers with options to collaborate through notes and advance or archive.

Review a small group in the current interface and note where you spend time: opening documents, interpreting experience or writing recommendations. Track waiting for the manager separately. Those problems call for different changes.

Compare how long it takes to finish a review in Lever with the proposed new process. Include reading and checking the new tool's summary. Count a time saving only when you can complete a checked recommendation with less work. Better evidence may justify the tool too, but it does not clear this backlog unless the team has time to use it.

Do not move live applications merely to make them appear in a feature. Check what a stage change triggers and whether it fits the actual hiring process.

Decide what Screened should handle, and what stays in Lever

The Lever connection reads the stage selected under Read from. Adding the job queues applications already in that intake stage. Inspect the group before connecting it; a catch-up trial should not accidentally restart applicants who already passed the first screen.

Screened returns the results; stage movement is handled in Lever. Screened's Lever setup offers the read-from control, not the same move-to controls available for some other integrations. Interview invitations are a separate action. Our ATS configuration guide explains the distinction and requires Screened sign-in.

Use one purpose-made CV and an inbox your team controls. Confirm that the report returns without an unexpected stage move or invitation. A job labelled “Test” may still use settings shared with live vacancies.

Ask the administrator or supplier to isolate the test and explain the shared settings. Your job in this trial is to evaluate the review, not learn message automation by experimenting on real applicants.

The trial should address the reading backlog. Add an interview only when a useful answer is missing and a conversation is worth the effort. More candidate activity is not a substitute for finishing the reviews already waiting.

Where do Screened's CV results appear in Lever?

Screened's Lever connection can return a written CV assessment through Screened - CV Results in the feedback area. The feedback includes a summary, match percentage and status. Your update settings control the tags and notes posted. Our guide to reviewing Screened results in Lever explains the outputs and intake-stage behaviour. Screened sign-in is required.

Read the explanation behind the tag, and open Screened for the full requirement details or CV preview. Not a Fit may mean the CV did not establish an essential requirement, not that the applicant confirmed they lack the skill. The reason helps you decide whether to clarify, correct a mistake or decline.

Try completing a review yourself: find the report, check what it says against the CV and write your recommendation. Include any copying or extra screens you must open in the timing.

Then try a CV the tool cannot read. Can you find the application and get it reviewed another way? Failed files still need your time; they should not disappear from the workload.

Give unfinished applications a next action

Replace “later” with the action still needed. A missing CV needs a usable file. An unclear contribution may need one question. A technical assessment needs the right reviewer. An approved interview needs a booking and an invitation.

Keep separate lists of unread CVs, replies awaiting review and decisions waiting for a colleague. Assign each outstanding action and update date. Check these lists during the next review session so candidates who answered your questions don't stay behind newer applications.

Keep response dates realistic. A candidate update can promise contact even when the decision will take longer:

We're still reviewing applications for the role. I'm sorry for the wait. I'll update you by Thursday, even if we have not finished the review. You do not need to send anything else in the meantime.

Replace Thursday with a date your team can meet. Check that no automatic reminder asks for work the message says is unnecessary.

Weekly update: reviews finished and help still needed

Send the manager a small, usable update: reviews completed, decisions they need to make and the next response date. Keep unread CVs and missing information separate. Link to the relevant Lever opportunities rather than send an export for the manager to interpret.

Under the example's assumptions, 60 completed first reviews leave 440 of the original applications awaiting review. In your report, account separately for withdrawals or applications closed without review, then add new arrivals. Include the replies and manager decisions still outstanding; the reserved hour does not guarantee that all of them are finished.

A useful Friday update could say:

We completed 60 first reviews and sent the resulting updates. There are 440 original applications still unread, plus this week's new arrivals. The linked applications need your decision before we can arrange interviews.

Please confirm the review time or help available next week. I will revise the completion estimate once that capacity is agreed.

Report what actually finished, not Monday's target. Use a faster review time in next week's estimate only when the work demonstrates it.

Ask the manager to agree more review time, help or a revised deadline. The 440 applications still waiting need one of those decisions, not an assumption that you will find the hours after work.