Skip to main content

​
What Is Batch Tagging?

Batch tagging lets you apply a tag to multiple jobs in a single action, instead of opening each job individually. When you have a set of jobs that all need the same tag — for example, all the results from a specific search that belong to the same client — batch tagging saves significant time. This feature is particularly valuable when you are organizing a large number of newly saved jobs or preparing a batch of opportunities for a client presentation. What would take 20 minutes of clicking through individual jobs can be done in under a minute with a batch operation.

​
Using the Batch Tagging Panel

The batch tagging panel is available within a search detail view, where you can tag multiple jobs from the same search at once.
1

Open the Batch Tagging Panel

In the search detail page, locate the batch tagging panel. This panel shows all the jobs from the current search with checkboxes for selection.
2

Select Your Jobs

Click the checkbox next to each job you want to tag, or use the “Select All” option to select every job in the search. A counter shows how many jobs are currently selected.
3

Choose a Tag

Select the tag you want to apply from the dropdown. The dropdown shows all your available tags with their names and colors. If you need a new tag, you can create one directly from the panel using the “Create New” option.
4

Apply the Tag

Click the apply button to add the selected tag to all selected jobs. Recruitier processes each job in sequence and shows a progress indicator. Jobs that already have the tag will be skipped automatically.
5

Review the Results

After the operation completes, you will see a confirmation showing how many jobs were successfully tagged. The selections are automatically cleared so you can start a new batch operation if needed.
Batch tagging applies one tag at a time. If you need to apply multiple tags, run the batch operation once for each tag. The process is fast, so applying several tags in succession takes only a few seconds.
Batch tagging only supports adding tags to jobs. To remove a tag from a job, open the individual job and remove it from the tags section on the job detail page.

​
Use Cases for Batch Tagging

After running a job search and saving promising results, you might want to tag all of them with your client’s name or the search project:
  1. Filter your job list to show only jobs from the recent search.
  2. Enter batch mode and select all visible jobs.
  3. Apply the “Client: Acme Corp” tag to the selection.
Now all those jobs are organized under the client’s tag for easy filtering later. When you prepare for the client meeting, one tag filter shows you everything.

​
Preparing for a Client Presentation

When preparing for a client meeting, you might want to curate and tag the best opportunities:
  1. Browse your job collection and identify the most relevant opportunities.
  2. Select them in batch mode.
  3. Apply a tag like “Acme Presentation - March” so you can quickly pull them up during the meeting.

​
Onboarding to a New Client

When you take on a new client and want to tag existing opportunities in your pipeline that might be relevant:
  1. Use skill or location filters to find jobs that match the client’s hiring needs.
  2. Enter batch mode and select the matching jobs.
  3. Apply the new client tag (e.g., “Client: NewCo BV”).
This gives you an instant pipeline for the new client from your existing job collection.

​
Time-Based Tags in Batch Operations

When you batch-apply a time-based tag, the expiration is calculated individually for each job from the moment the tag is applied. Each job gets its own expires_at timestamp computed as current_time + days_duration. In practice, since the batch operation processes all jobs in quick succession, all expirations will be within seconds of each other. For a “7-Day Follow-Up” tag applied in a batch on Monday, all 20 jobs’ tags will expire the following Monday within the same minute.
Batch-applying a time-based tag with a 7-day duration means each job’s tag expires 7 days from the moment of application. If you batch-tag 20 jobs on a Monday at 9:00 AM, all 20 tags expire the following Monday around 9:00 AM. The per-job calculation ensures accurate, individual expiration tracking.

​
Best Practices for Batch Tagging

  • Double-check your selection count. Before applying tags, verify the job count matches your expectations. If you expected to select 15 jobs but the counter says 47, something is off.
  • Use descriptive tags. When creating tags specifically for batch operations (like presentation prep), include enough context in the name to remember the purpose later. “Acme March 2026” is better than “Presentation.”
  • Create tags before batch operations. You can create new tags directly from the batch tagging panel, but it is faster to have your tags ready in advance if you know what you need.
Batch tagging operations are processed immediately. If you accidentally apply the wrong tag, you will need to remove it from each job individually. Take a moment to verify your selection and chosen tag before confirming.

​
Advanced

​
How Batch Tagging Works Under the Hood

When you execute a batch tag operation, Recruitier processes the tag application for each selected job individually but within an efficient loop. For each job in the selection:
  1. The system checks if the job-tag association already exists (duplicate prevention).
  2. If the association does not exist, a new junction record (JobTag) is created with the current timestamp as created_at.
  3. For time-based tags, the expires_at is calculated as created_at + days_duration for each individual job.
  4. The operation proceeds to the next job in the selection.
This per-job processing means that duplicate prevention works correctly even in batch operations. If you select 50 jobs and 30 already have the tag, only 20 new associations are created.

​
Batch Loading After Operations

After a batch tag or batch remove operation completes, Recruitier refreshes the tag display for all affected jobs. This uses the same batch loading mechanism (get_tags_for_multiple_jobs()) as the normal job list display, meaning the refresh is a single database query regardless of how many jobs were affected.

​
Handling Partial Failures

Batch tagging processes each job individually. If some jobs fail while others succeed, the operation continues and reports the results at the end. A summary shows how many jobs were tagged successfully and how many failed. This means you do not need to worry about the entire batch failing because of one problematic job.

​
Connection to Time-Based Expiration

When batch-applying time-based tags, the lazy expiration system applies to each job independently. Since each job’s expires_at is calculated at the moment of application, batch-applied time-based tags all expire at approximately the same time. However, the expiration check at query time evaluates each job independently. If there is a tiny difference in application time (milliseconds apart), the expiration will reflect that difference precisely.

​
Business Rules

  • One tag per batch: Each batch operation applies a single tag. To apply multiple tags, run the operation once per tag.
  • Selection size: There is no hard limit on how many jobs you can select for a batch operation, but very large selections (hundreds of jobs) may take longer to process since each job is tagged individually.
  • Both tag types: You can batch-apply both standard and time-based tags. Each tag type is handled according to its own rules.

Creating Tags

Set up your tag library with custom names and colors.

Tagging Jobs

Apply tags to individual jobs.

Filtering by Tags

Use tags to quickly find and filter your job collection.

Tag Expiration

Set up time-based tags that automatically expire.