Skip to main content

​
What Are Tags?

Tags are customizable labels that you can apply to jobs in your collection to organize, categorize, and track them. They serve as a flexible organizational layer on top of Recruitier’s built-in attributes (match score, experience level, job type, etc.), allowing you to create a system that matches your personal workflow. Common uses for tags include:
  • Pipeline stages — “Shortlist,” “To Review,” “Follow Up,” “Submitted”
  • Priority levels — “High Priority,” “Medium,” “Low”
  • Candidate assignments — Tags named after specific candidates
  • Geographic grouping — “Amsterdam,” “Rotterdam,” “Remote”
  • Specialization — “Frontend,” “Backend,” “DevOps,” “Data”
  • Time-sensitive tracking — “Contact by Friday,” “Interview scheduled”
Tags are shared across your agency team. When you create a tag, all team members can see and use it. This makes tags an effective tool for team coordination — for example, tagging a job as “Claimed by [Name]” to prevent duplicate outreach.

​
Creating Tags

Before you can tag a job, you need to create the tag itself. Tags are created from the tag management section or on-the-fly when tagging a job.

​
From Tag Management

Navigate to Organization > Tags to access the full tag management interface. Here you can:
  1. Click Create Tag
  2. Enter a tag name (keep it short and descriptive — 1-3 words)
  3. Choose a color to visually distinguish the tag
  4. Optionally enable time-based expiration (see below)
  5. Save the tag

​
On-the-fly During Tagging

When applying a tag to a job, the tag selector shows a “Create new tag” option. Enter the name and color, and the tag is created and applied in a single step. This is the fastest way to create a tag when you realize you need a new category during your review.

​
Tag Properties

PropertyDescription
NameA short, descriptive label (e.g., “Priority,” “Follow Up,” “Amsterdam”). Keep it to 1-3 words for best readability.
ColorA color that visually identifies the tag in the UI. Choose colors that contrast well against the white table background and are easily distinguishable from each other.
Time-basedOptional. When enabled, the tag has an expiration period.
Days DurationIf time-based, the number of days before the tag expires after being applied to a job.
Tag names should be concise and meaningful. Long tag names get truncated in the UI and are harder to scan in a filtered view. Prefer “Shortlist” over “Jobs I Want to Review More Closely.”

​
Applying Tags to Individual Jobs

To tag a single job:
1

Open the Tag Selector

On the job detail page or in the results table row, click the Tag button or tag icon. A dropdown appears showing all available tags.
2

Select a Tag

Click on one or more tags to apply them. Each selected tag appears as a color-coded chip on the job. You can apply multiple tags to the same job — there is no limit on how many tags a single job can have.
3

Confirm

Tags are applied immediately when selected. There is no separate save step. The tag chip appears on the job instantly in the results table and on the detail page.
Applied tags are visible in:
  • The results table as color-coded chips in the Tags column
  • The job detail page in the tags section
  • The all-jobs view across all your searches

​
Batch Tagging Multiple Jobs

One of the most powerful tag features is the ability to apply tags to multiple jobs at once. This is essential for efficiently organizing large search result sets.
1

Select Jobs

Use the checkboxes in the results table to select the jobs you want to tag. You can select them individually or use “Select All” to select all visible jobs (after applying any filters).
2

Open Batch Tag

With one or more jobs selected, click the Tag button in the batch action toolbar that appears above the table.
3

Choose the Tag

Select the tag to apply from the dropdown. The tag is applied to all selected jobs simultaneously.
Typical batch tagging workflow:
  1. Open a search with 100+ results
  2. Sort by match score (highest first)
  3. Review the top 20 results quickly
  4. Select the 8-10 most promising ones
  5. Batch-apply a “Shortlist” tag
  6. Continue reviewing the next batch
  7. Apply “Maybe” to borderline results
  8. Batch-delete poor matches
This workflow lets you process large result sets efficiently and creates a tagged pipeline you can filter and act on later.
Develop a consistent tagging workflow within your team. Agree on a standard set of tags (e.g., “Shortlist,” “Contacted,” “Waiting for Reply,” “Rejected”) so everyone uses the same labels and filtering is consistent across team members. This is especially important in agency settings where multiple recruiters work the same pipeline.

​
Using Tags as Filters

Once you have tagged your jobs, tags become powerful filters:

​
In Search Results

  1. Click the Tag Filter dropdown above the results table
  2. Select one or more tags
  3. The table shows only jobs with the selected tags

​
In the All-Jobs View

The same tag filter is available on the all-jobs page, but here it works across your entire collection — not just a single search. This lets you see, for example, all jobs tagged “Priority” regardless of which search produced them.

​
Combining Tag Filters with Other Filters

Tag filters can be combined with attribute filters (experience level, job type, etc.) and the active-only toggle. For example:
  • Tag: “Shortlist” + Active only = Your top picks that are still open
  • Tag: “Follow Up” + Experience: Senior = Senior roles that need follow-up
  • Tag: “Amsterdam” + Flexibility: Hybrid = Hybrid jobs in Amsterdam that you tagged
When you select multiple tags in the filter, the result shows jobs that have any of the selected tags (OR logic), not all of them. If you need to find jobs with multiple specific tags, apply one tag filter and then visually scan for the second tag in the results.

​
Tag Colors

Colors serve as quick visual identifiers in the results table. When you scan a long list of jobs, color-coded tag chips help you spot patterns without reading each tag name. Recommended color conventions:
ColorSuggested Use
GreenPositive status: shortlisted, approved, ready to submit
RedUrgent or blocked: needs immediate action, deadline approaching
BlueInformational: location-based tags, category labels
Yellow/OrangePending: awaiting response, under review
PurpleSpecial: VIP candidate, premium opportunity
GrayNeutral: archived, low priority
These are suggestions, not rules. Choose colors that make sense for your workflow and are easy to distinguish from each other. Avoid using similar shades for different tags (e.g., light blue and sky blue) as they become hard to distinguish in a table view.

​
Removing Tags

To remove a tag from a job:
  1. Open the job detail page or click on the tag chip in the results table
  2. Click the X icon on the tag chip you want to remove
  3. The tag is removed immediately
Removing a tag from a job does not delete the tag itself. The tag remains available for future use. To delete a tag entirely (removing it from the system and from all jobs it was applied to), use the tag management page under Organization.
Deleting a tag from the tag management page removes it from all jobs across your entire agency that have this tag applied. This is a system-wide action. If you just want to remove a tag from specific jobs, remove it from those jobs individually rather than deleting the tag definition.

​
Time-Based Tags (Expiration)

Time-based tags have a built-in expiration mechanism. When you apply a time-based tag to a job, it starts a countdown:
  • Days duration — Set when creating the tag (e.g., 7 days, 14 days, 30 days)
  • Expires at — Calculated from when the tag is applied to a specific job
  • Days left — A countdown displayed on the tag chip

​
How Expiration Works

When a time-based tag expires:
  • The tag chip changes appearance to indicate expiration (visual dimming or strikethrough)
  • The job can be filtered to show expired tags specifically
  • The tag is not automatically removed — it remains applied but marked as expired
This means expired tags serve as visual reminders rather than automatic actions. You still need to manually review and act on jobs with expired tags.

​
Use Cases for Time-Based Tags

  • “Follow up in 7 days” — Apply this tag when you send outreach. After 7 days, the tag expires, reminding you to follow up if you have not heard back.
  • “Interview next week” — A 5-day tag that expires before the interview date, prompting you to prepare.
  • “Vacancy closing soon” — A 14-day tag for jobs with known application deadlines.
  • “New hire onboarding” — A 30-day tag for tracking the onboarding period after a successful placement.
Time-based tags are particularly useful for managing a high-volume outreach pipeline. They create automatic visual reminders without requiring you to set calendar events or external reminders. The countdown is always visible on the tag chip, giving you an at-a-glance view of your time-sensitive tasks.

​
Best Practices

  • Start with 5-7 standard tags — Too many tags creates confusion. A small, well-defined set covers most workflows.
  • Use consistent naming across your team — Agree on tag names and meanings so everyone can filter reliably.
  • Tag during first review — Apply tags as you first scan through results, not as a separate step later. This saves time and ensures nothing falls through the cracks.
  • Combine tags with batch operations — Use “Select All” with filters to batch-tag efficiently.
  • Review and clean up periodically — Remove tags from completed or irrelevant jobs to keep your filtered views useful.
  • Use time-based tags for follow-ups — They create automatic visual reminders in your pipeline.
  • Avoid tag proliferation — Resist the urge to create a new tag for every scenario. Instead, use a combination of existing tags (e.g., “Priority” + “Amsterdam” instead of “Priority Amsterdam”).
For the full tag management documentation, including creating, editing, and deleting tags at the system level, see Organization > Tags.

​
Advanced

​
Tag Architecture and Data Model

Tags in Recruitier are implemented as a many-to-many relationship between Job entities and Tag entities:
  • Tag entity: Contains the tag definition (name, color, time-based flag, days duration). Tags are scoped to the agency, meaning all agency members share the same tag definitions.
  • Job-Tag association: Links a specific Job to a specific Tag, with an applied_at timestamp. For time-based tags, the expiration is calculated as applied_at + days_duration.
This architecture means:
  • Tags are shared definitions at the agency level
  • Tag applications are per-Job
  • The same tag can be applied to jobs from different searches and by different team members
  • Deleting a tag definition removes it from all associated jobs across the agency

​
How Tags Interact with Cloning

When a search is cloned, tags are not copied to the cloned search. This is by design:
  • Tags represent the reviewer’s personal organization, which may not be relevant to the clone recipient
  • The clone recipient starts with a clean slate to apply their own organizational system
  • If both the original and clone owner need the same tags, they can independently apply them since they share the same tag definitions (being in the same agency)

​
Tags and Agency Collaboration

Since tags are shared at the agency level, they enable several collaboration patterns:
PatternHow It Works
Claim preventionTag a job as “Claimed by [Name]” to signal that you are working on it
Pipeline handoffTag jobs in your pipeline stage, and a colleague filters by that tag to pick up where you left off
Quality labelingUse tags like “Verified” or “Company Confirmed” to signal that a job has been manually verified
Candidate mappingTag jobs with candidate names to track which opportunities are being pursued for each candidate

​
Time-Based Tag Calculation

The expiration for a time-based tag is calculated as: 
expiration_date = applied_at + timedelta(days=days_duration)
days_remaining = (expiration_date - current_date).days
is_expired = days_remaining <= 0
The applied_at timestamp is set when the tag is first applied to a specific job, not when the tag was created. This means the same time-based tag can have different expiration dates on different jobs, depending on when it was applied to each one.

​
Power-User Tips

The most effective tag-based pipeline for recruitment agencies:
  1. Shortlist (green) — Promising jobs identified during initial review
  2. Contacted (blue) — Outreach has been sent to the company
  3. Waiting (yellow) — Awaiting response from the company
  4. Interview (purple) — Interview process is active
  5. Placed (dark green) — Candidate has been successfully placed
  6. Rejected (red) — Company declined or role was filled
Filter by each tag to view that pipeline stage. Combine with “Active only” to exclude expired listings. This gives you a real-time pipeline dashboard.
Create a set of time-based tags for your follow-up cadence:
  • “Follow up 3 days” (3-day duration) — For hot leads
  • “Follow up 7 days” (7-day duration) — Standard follow-up
  • “Follow up 14 days” (14-day duration) — For passive opportunities
Apply the appropriate tag when you send outreach. When the tag expires, you see a visual cue that it is time to follow up. This eliminates the need for separate calendar reminders or CRM tools for follow-up tracking.
Tags provide lightweight reporting capabilities. By filtering your all-jobs view by each pipeline stage tag, you can quickly count:
  • How many jobs are in each stage
  • How many “Contacted” jobs have been active for a long time (potential follow-ups)
  • Which candidate-tagged jobs have the most opportunities
  • How your pipeline is distributed across searches
While Recruitier does not provide formal pipeline analytics, tag-based filtering gives you a real-time view of your pipeline composition.
Over time, tags accumulate on completed or irrelevant jobs, making filtered views noisy. Periodically:
  1. Filter by a tag (e.g., “Shortlist”)
  2. Add the “Active only” filter
  3. Review which jobs are expired — remove the tag from expired jobs or batch-delete them
  4. Review which jobs are still active but no longer being pursued — remove the tag
This keeps your tag-filtered views clean and actionable.

​
Business Rules

  • Agency-scoped tags: Tag definitions are shared across all members of an agency. Creating a tag makes it available to all team members. Deleting a tag removes it for everyone.
  • No duplicate tag names: Within an agency, tag names must be unique. You cannot create two tags with the same name.
  • Tag application is per-Job: Each Job-Tag combination is independent. Applying a tag to one Job does not affect other Jobs, even if they share the same ScrapedJob.
  • Tags survive search deletion: If a search is deleted (soft-delete), the tag associations on its jobs are also soft-deleted. However, the tag definition itself remains available for use on other jobs.
  • Batch tag limits: Batch tagging applies a single tag to all selected jobs. To apply multiple tags, perform multiple batch operations or tag individually.