At this present moment tagging is a real challenge.

A) - I cant add tags on the fly, which means that every time I come across a candidate with a new skill I wish to code.. I have to leave the record & visit the back end every time.

B) - The field for adding tags in the back end is just a short free text field on ONE line, that you must separate with a comma. Nightmare to manage when you have 100's of verticals or skills.

C) - The Tags / Verticals should be united across all records. At this present time it would be a tall order to keep 3 lists correlated in the back end on each record type.

Tags are used by any recruiter to group together candidates by what we have told the system that they are, not simply by what words they happen to have in their resume.

For Example: 'BPM - Pega' or 'IBM BPM'

If I coded someone with that, it would be telling me the the candidate is a 'Business Process Management' Consultant who specifically uses Pega or IBM.

The issue is that if I was to use a boolean to search for Pega or IBM for that matter the search would be very poor as it would bring back candidates that worked on an IBM mainframe 10 years ago or did their work experience at Pega. or worked for a company called 'Pega Post'

Tagging for Candidates, Contact and ideally companies needs a drastic overhaul as I don't want to have to do this for 20,000 records twice