When you need bulk operations

Bulk operations are not a nice-to-have. They become a necessity the moment the volume of candidates is larger than you can sensibly handle one profile at a time. These are the situations where they earn their keep.

High-volume hiring. Roles in customer support, sales, retail and operations can each pull in hundreds of applications. Handling every one individually, open the profile, review, move a stage, send an email, can swallow hours of your day. Bulk operations run the same actions across an entire selection in seconds.

Careers fairs and campus recruiting. After an event you come back with dozens or hundreds of CVs to process. They all need to get into the ATS, be reviewed quickly and be triaged. Bulk CV upload and bulk tagging are exactly the tools for this stage.

Closing out a filled role. When you hire someone, every other candidate still in the pipeline deserves to hear back. For a role with 80 candidates across various stages, rejecting each one with an individual email would take the best part of an hour. With bulk reject it takes a couple of minutes, and everyone gets a proper, personalised note.

Quarter-end reporting. At the end of a quarter your HR team needs the numbers: how many candidates were processed, how many hired, how many rejected, and from which sources. Bulk export pulls that data out in one go, with none of the manual copying.

Restructuring a pipeline. Sometimes the stages of a pipeline need to change, one stage removed, another added. Candidates sitting in the old stage need to be moved across to the new structure together rather than dragged one by one.

Bulk operations in Treegarden

Treegarden provides a full set of bulk operations covering the actions you repeat most. The one that saves the most time at the very start of the funnel is bulk CV upload, so we will begin there.

Bulk CV upload and parsing

Drag in a batch of CVs and Treegarden imports and parses them together, reading out the candidate's name, email, phone and experience into structured records so you are not retyping anything. Treegarden accepts up to 50 CV files per upload, up to 20MB each, in common formats such as PDF and DOC. Where parsing cannot read a field cleanly, the candidate is still created so nothing is dropped, and you can fix the detail later. This is the fastest way to clear a pile of CVs from a careers fair or an inbox campaign and get every applicant into the pipeline ready to triage.

Bulk move to stage

Tick several candidates, choose the target stage and confirm. They all move at once, each with its own timestamp and history entry. Any automations set on the target stage, such as a stage-entry email or a notification, fire for each candidate individually. This is ideal for reorganising the pipeline or advancing a group after a first-pass screen.

Bulk reject

Select the candidates, pick a rejection reason from your pre-set list (not enough experience, skills mismatch, role filled, and so on), and optionally send a rejection email using a template. Each person receives an individual message with their own name inserted, never a visible group send. The reason is recorded on every profile for later reporting. This is the clean way to close out a filled role or tidy up a pipeline.

Bulk tag. Add or remove tags across every selected candidate at once. Tags are flexible labels: "March careers fair", "senior", "open to relocation", or any category you find useful. Bulk tagging is especially handy straight after importing a batch of CVs or after a themed screening pass.

Bulk email. Send one message to a whole selection, with automatic personalisation. Variables such as {{candidate_name}} are replaced with each candidate's name, and every email is sent individually, so recipients never see each other's addresses. Use it for status updates, event invitations or follow-ups.

Bulk export. Download the selected candidates as a structured CSV: full name, email, phone, role applied for, current stage, application date and tags. Useful for reporting, outside analysis, or sharing a shortlist with colleagues who do not have ATS access.

How to select candidates for bulk operations

Bulk operations are only as efficient as your ability to select exactly the right candidates, quickly. Treegarden gives you a few ways to do that.

Individual checkboxes. Every row in the candidate table, and in the candidate database, has a checkbox. Tick the candidates you want. This is the most precise method and the right one when you are picking out a small, specific set.

Select all. A checkbox in the table header selects everyone currently shown. If you have filters active, Select all picks only the candidates that match those filters. That behaviour is deliberate: it stops you accidentally acting on people who fall outside your criteria.

Practical tip

Pair filters with Select all for powerful, safe selections. For example, filter to the "Received" stage with an Edera AI match score below 30%, then use Select all and bulk reject with the reason "skills mismatch". In a few seconds you have cleared the lowest-fit applicants and freed up your time for the ones with real potential. Always glance at the selected count before you confirm.

Selecting from the candidate database. Bulk operations work from your central candidate database too, not just from a single job's pipeline. That lets you act across roles, for instance adding a "suitable for role X" tag to candidates who applied to several different jobs, or exporting everyone carrying a particular tag.

How bulk emails are sent: the queue

When you send email to a large group, whether through bulk email or bulk reject, Treegarden runs it through a send queue to protect deliverability and keep things responsive.

Why a queue exists. Firing 100 or more emails off at the same instant is a deliverability risk. Receiving mail servers can flag an unusual burst from one sender as spam. The queue spaces the sending out over time, staying within the rate limits mail servers expect.

How it works. Emails enter the queue and are processed in order. For small batches (under 50) it is nearly instant. For larger batches (50 to a couple of hundred) it can take up to around half an hour. Each message goes out individually, correctly personalised, from your configured company email address.

Rough processing times

Under 20 emails: a few seconds. Between 20 and 50: roughly one to five minutes. Between 50 and 100: roughly five to fifteen minutes. Over 100: roughly fifteen to thirty minutes. You do not have to sit and wait. The sending happens in the background while you carry on working, and each email is logged in the relevant candidate's history.

What happens if an email fails. If a message cannot be delivered (an invalid address, a full inbox, a temporary server error), Treegarden retries it automatically up to three times. If it still cannot get through, the email is marked as failed in the log so you can see exactly which candidates did not receive it.

Practical scenarios, step by step

Here is how these operations play out in everyday recruiting.

Scenario 1: closing out a filled role

You have hired your ideal Marketing Manager. The pipeline still holds 65 other candidates across stages: 30 in "Applied", 20 in "Screening", 10 in "Interview" and 5 in "Offer".

  • Step 1: move the hired candidate to the "Hired" stage.
  • Step 2: select the remaining 65 with Select all.
  • Step 3: choose "Reject" from the bulk menu.
  • Step 4: set the reason to "Role filled".
  • Step 5: switch on email sending and pick your "Role filled" template.
  • Step 6: confirm. All 65 are marked rejected, the reason is recorded on each profile, and every candidate gets a personalised email.

Total time: a couple of minutes. Done one by one, the same task would have taken an hour or more.

Scenario 2: restructuring a pipeline

You decide to add a "Technical test" stage between "Screening" and "Interview" for a developer role. You have 15 candidates sitting in "Screening" who need to take the test.

  • Step 1: add the "Technical test" stage to the job's pipeline.
  • Step 2: filter to the "Screening" stage.
  • Step 3: select them all with Select all.
  • Step 4: bulk move them into "Technical test".
  • Step 5: optionally, send a bulk email with the test instructions.

Scenario 3: quarter-end reporting

Your HR lead asks for a report on every candidate processed in Q4. Open the candidate database, filter by date (October to December), select all, and run a bulk export. Within seconds you have a complete CSV ready to drop into Excel or Google Sheets for analysis.

Bulk vs. manual: a sense of the difference

The exact numbers will vary with your setup and how fast you work, but a simple back-of-the-envelope comparison shows why bulk operations matter. The figures below are illustrative estimates, not measured benchmarks.

Rejecting 50 candidates by email

  • One at a time: open the profile, reject, choose a reason, enable the email, preview, send, fifty times over. Easily over an hour.
  • In bulk: select 50, reject, choose a reason, enable the email, confirm. A couple of minutes.

Moving 30 candidates to the next stage

  • One at a time: open, move, choose the stage, thirty times. Around half an hour.
  • In bulk: select 30, move, choose the stage. About a minute.

Tagging 80 candidates

  • One at a time: open, add the tag, save, eighty times. The better part of an hour.
  • In bulk: select 80, add the tag. About a minute.

Repeated across a busy quarter, that kind of saving adds up to a meaningful chunk of time. The hours you get back are better spent on the work that actually moves hiring forward: real interviews, building relationships with strong candidates, sharpening your employer brand, and reading what your recruitment data is telling you.

Good practice and precautions

Bulk operations are powerful, which is exactly why they deserve a little care. A wrong action applied to a whole group has consequences in proportion to its size. A few simple rules keep you safe.

Always check the selection before you act. Before confirming, look at the count of selected candidates. If it says 150 and you expected 50, your filters are not doing what you think. Stop and check.

Filter before you Select all. Never use Select all on a table of hundreds without filters applied. Filter first, by job, stage, score or date, then select. This is the single best habit for avoiding accidental actions on the wrong people.

Preview your emails. Before a bulk email or bulk reject, preview the template. Check the personalisation variables, the tone and the facts. A mistaken message sent to a whole group is far harder to walk back than a single one.

Start small. If bulk operations are new to you, try them on a group of five or ten first to get a feel for the flow, then scale up once you are comfortable.

Note the reason for big actions. Treegarden logs every bulk action automatically, with a timestamp and the user who ran it. Even so, it helps to jot down internally why you did something significant, for example "bulk reject 80 candidates, role filled on 15 January".

Used well, bulk operations turn high-volume hiring from an overwhelming slog into a controlled, efficient process. They do not replace careful judgement at the moments that matter, the shortlist, the interview, the offer, but they take the repetitive busywork off your plate. With good filters, precise selections and a careful eye on the confirmation screen, they are the best ally a recruiter has when there are tens or hundreds of candidates to manage at once. To see bulk CV upload and the rest of these operations on your own data, book a demo.

Related reading Helpful calculators

Frequently asked questions

What are bulk operations in recruitment?

Bulk operations let you act on many candidates at once instead of one at a time. In Treegarden that includes bulk CV upload to import and parse many CVs together, plus bulk move, bulk reject, bulk tag, bulk email and bulk export. They become essential whenever the volume of applicants is larger than you can sensibly handle profile by profile.

When do you need bulk operations?

When you are hiring at volume. High-volume roles in customer support, sales, retail or operations can each attract hundreds of applications. Handling every one individually, opening the profile, reviewing, moving a stage and sending an email, can eat hours a day. Bulk operations run the same actions across a whole selection in seconds.

How does bulk CV upload work in an ATS?

After a careers fair or a campaign you often return with dozens or hundreds of CVs. With Treegarden's bulk CV upload you can import many files at once and have them parsed into candidate records automatically, then tag and triage them in bulk. Treegarden supports up to 50 CV files per upload, up to 20MB each.