June 2026 Organization

Tags Library

ATZ CRM introduced a centralized Tags Library so teams can create and manage tags more consistently across candidates, clients, and related records.

Create and manage tags from one library

Reduce duplicate or inconsistent tag names

Improve candidate and client organization

Support cleaner filtering and team handoffs

Quick answer

What changed for recruiters?

Tags Library gives recruiters and admins a central place to manage tags. It helps teams keep labels consistent, reduce duplicate tag names, and organize candidates, clients, jobs, contacts, and other records with cleaner shared terminology.

What changed

What this update changes

ATZ CRM added a centralized Tags Library in June 2026. Instead of every recruiter creating slightly different labels, teams can manage tags from one place and keep naming more consistent.

Tags are useful when recruiters need flexible labels for skills, campaigns, priority groups, client categories, sourcing sources, or follow-up themes.

A central library gives teams a better foundation for filtering, reporting, cleanup, and shared workflows.

Why it matters

Why it matters to recruiters

Recruiters are often measured on speed, quality, and follow-through. This update is designed to reduce manual work, protect useful context, and help teams keep hiring activity moving with fewer handoffs.

Cleaner record organization

Recruiters can use consistent tags to group records without relying on scattered naming habits.

Better team alignment

A shared library helps teammates understand what each tag means and how it should be used.

Easier cleanup

Admins can reduce duplicate tags and keep the tag system useful as the database grows.

Before and after

How the workflow changes

Before

Tag names could vary by recruiter, creating duplicate or confusing labels.

After

Teams can manage tags centrally and use cleaner shared terminology.

Before

Candidates and clients could be organized inconsistently across desks.

After

The Tags Library gives teams a more controlled organization layer.

How recruiters use it

How the workflow works

The exact setup depends on your workspace and permissions, but the core workflow is built to keep recruiters closer to the record, the next action, and the right team context.

1

Audit existing tags

Review which tags the team already uses for candidates, clients, campaigns, and workflows.

2

Create standard labels

Build tags that are clear, reusable, and easy for recruiters to understand.

3

Apply tags during daily work

Use tags when sourcing, importing, reviewing, or segmenting records.

4

Clean up over time

Merge habits around preferred tags and remove unnecessary variations when possible.

Feature-specific details

Extra context for this update

Some releases affect more than one recruiting workflow. These notes explain the practical details recruiters, admins, or managers may want to review before rolling the update out to the team.

Data hygiene

A practical tagging approach for recruiting teams

Tags work best when the team agrees on clear labels before everyone starts creating their own variations.

  • Use tags for flexible context such as campaign source, niche skill group, availability theme, priority pool, or client-specific shortlist status.
  • Avoid creating multiple tags with the same meaning, such as “Java Dev,” “Java Developer,” and “Java Engineer,” unless your team has a clear distinction.
  • Review the library regularly after imports, sourcing projects, and outreach campaigns so the tag list stays useful instead of noisy.

Quick answers

Common questions

What is the Tags Library?

It is a centralized place to create and manage tags so teams can organize records with more consistent labels.

Why does tag consistency matter?

Consistent tags make filtering, segmentation, cleanup, and handoffs easier across the recruiting team.

Are tags the same as folders?

No. Folders group records into working lists, while tags label records with flexible attributes or themes.

Who should manage the Tags Library?

Usually admins, operations leads, or senior recruiters should manage the library so tags stay consistent across teams.

Can tags help after a bulk import?

Yes. Tags are useful for marking imported records by campaign, source, event, niche, or cleanup status after a large upload.

How many tags should a team create?

Create only tags that recruiters will actually use for filtering, follow-up, segmentation, or reporting. A smaller clean library is better than a large confusing one.

See it in context

Review this update inside your recruiting workflow

Book a walkthrough with the ATZ CRM team to see how this update supports your jobs, candidates, and shortlist process.

Book a demo