As a result, it is the norm to get several copies of an applicant's resume if a number of similar jobs are posted in a large job board. When those resumes are transported into the Recruiter's database, each one incurs some element of tracking cost. Although the language remains unclear, we think it might be a good idea to begin making a distinction between applicants and candidates. A database of applicants doesn't need the same attention to maintenance and procedure as the database of candidates. Rather than spending tons of time cleaning up the database of applicants, why not let it grow.
Storage space is cheap, duplicates are easy to spot.
By dedicating a single machine to all incoming applicants, lots of current tracking costs could be eliminated. When its time to find a candidate, just dip into the easy to use search interface. Problems of document standardization and relevance disappear if the applicant pool is fished rather than farmed. We'd love to talk about your project.