Three weeks into a search for a finance director, the client asks a simple question in the progress call: “Did you speak to anyone at our two main competitors?” The consultant thinks so, but the research sits in a spreadsheet on the laptop of a researcher who is on leave this week. Nobody can say who was approached, who declined, or why. A week later the client widens the brief, and the team contacts two people again who had politely said no only a fortnight earlier. The search was done properly; it was just not recorded where everyone could see it. This article explains why every search assignment in your Applicant Tracking System needs a documented longlist: why longlists get lost, what a longlist is and is not, what to record, how to agree the target list with the client, how to move from longlist to shortlist and how to check with your own data whether your research is really visible.
A documented longlist matters most for executive search firms, where the research is a large part of what the client pays for. Recruitment agencies that headhunt for specialist or senior roles work the same way. Secondment firms that search the market for scarce consultants, and in-house recruitment teams that run direct search for leadership or hard-to-fill roles, face the same question: who did we look at, and what happened?
Why longlists get lost
- Research is done in a spreadsheet or document next to the system, one file per assignment, saved on someone’s own drive
- Names are kept as bookmarks or private notes, so only the researcher knows who they are
- Target companies are agreed with the client in a meeting, but the agreed list is never written down
- There is no status per name, so “approached”, “not interested” and “not yet contacted” look the same
- When the assignment closes, the file is archived and the knowledge of who was interested disappears with it
None of this is careless work. Research is often treated as preparation for the real process, while in a search assignment it is the process.
What a documented longlist is, and what it is not
A documented longlist is the list of target companies and named potential candidates for one search assignment, kept in the same system as the vacancy, with a status, a date and an owner for every name. It shows at any moment which part of the market has been covered and what the outcome was.
It is not a shortlist, and it is not permission to present anyone. People on a longlist have usually not applied; many do not yet know they are being considered. Nobody is shared with the client by name until the candidate has agreed. A longlist is also personal data that you mostly did not receive from the person themselves, so record only professional information you need for the search, and handle it under the same privacy rules, such as the GDPR, as the rest of your records, including telling people about it in the way your privacy policy describes. This article is not legal advice; what applies is what your own policy, contracts and privacy rules say.
What to record
Keep the structure simple enough that the whole team fills it in the same way:
- Target companies — the companies or sectors where you search, each checked against the off-limits agreements with your other clients before anyone is approached
- Named potential candidates — a person, their current role and company, linked to one candidate record rather than a copy per assignment, so you do not create duplicates
- How you found them — research, referral, your own database or an application, recorded as the candidate source
- Approach status — not yet approached, approached, in conversation, not interested, not suitable or moved to shortlist; one value at a time
- Approached on and by — the date of first contact and the named colleague who made it
- Outcome reason — a short standard reason when someone declines or is not suitable, chosen from a fixed list like your rejection reasons, without personal details
- Next step — a next action date for every name that is still open
Agree the target list with the client
The target list is part of the structured brief. Record which companies and sectors the client wants included, which ones must be left out, who agreed and on which date. When the client adds or removes a company later, record the change with its date rather than overwriting the old list. That protects both sides: the client sees that the search follows what was agreed, and your team can show why a certain company was or was not approached.
Keep the longlist moving
A longlist is a working list, not a report that is written once. Review it at a fixed moment, for example in your weekly pipeline review: which names have had no status change, which approaches are waiting for an answer, and which target companies have not been covered yet. Progress reports to the client can then come straight from the longlist: how many target companies have been covered, how many people have been approached and how many are in conversation, based on your own records rather than on impressions.
When a colleague takes over an assignment, the longlist is what makes the handover possible. Without it, the new consultant starts again from zero, and candidates hear from the same firm twice.
From longlist to shortlist
Moving someone from the longlist to the shortlist is a stage change like any other, so use the same written entry criteria for that stage. A few rules keep it honest:
- The candidate has been interviewed by your team and the outcome is recorded
- The candidate has agreed to be presented, in line with your consent before submission
- You have checked that the candidate has not already been presented to the same client by a colleague
- The longlist status is set to moved to shortlist on the same day, so the longlist and the pipeline tell the same story
After the assignment closes
Record a close reason for the assignment, and do not throw the longlist away. People who were interested but not chosen are valuable for the next search, and you can re-engage them from the talent pool if they agree to stay in touch. People who said they were not interested should not be approached again for the same kind of role within a period you agree as a team. Give every name on the longlist a retention date, so research data does not stay in the system longer than your policy allows.
Let the system help
Several longlist steps repeat in every assignment and suit automation: a reminder when a name has had no status change for a set number of days, an off-limits check when a target company is added, and a progress overview for the client built from the statuses. An artificial intelligence helper can suggest companies with similar roles, summarise call notes or draft a first approach message. The researcher and the consultant still decide who is approached and how; artificial intelligence does not replace recruiters or researchers and does not contact anyone on its own.
Common mistakes to avoid
- A longlist outside the system — a spreadsheet per assignment cannot be searched, reviewed or handed over
- Names without a status — a list without status cannot tell you which part of the market is covered
- Personal opinions in notes — record professional facts and standard reasons, not remarks you would not want the candidate to read in an access request
- Sharing names too early — share target companies and progress with the client, not names, until the candidate has agreed
- Forgetting the off-limits check — approaching someone at a company you agreed not to search in costs more than one missed candidate
Questions teams ask
- Should every name on a longlist get a full candidate record? — Give them one record with the information you need for the search, linked to the assignment; add more only when someone is in conversation with you
- Can the client see the longlist? — Share the agreed target companies and the progress per status; share names only with the candidate’s agreement
- How long should a longlist be? — As long as the market for that role requires; the point is not the number of names but that each one has a status
- Does this also apply to internal candidates? — Yes, in-house teams can put internal colleagues on the same longlist, with the same care about who sees their name
Check it with your own data
Count from your own records, per assignment: how many names are on the longlist, how many have no status or no next action date, how many were approached more than once for the same kind of role, how many target companies agreed with the client have not been covered, and how many shortlist candidates came from research compared with applications or your own database. Look at the time from the start of the assignment to the first shortlist alongside your time-to-fill. Report the number of assignments and names behind each figure. Do not compare with industry averages; the gap between the research you did and the research anyone can see is the number that matters.
A practical start
- Agree the approach status values and a short list of outcome reasons with your consultants and researchers
- Link every new search assignment to a longlist in the system, and stop starting new research spreadsheets
- Record the target companies and the client’s agreement as part of the brief
- Run the off-limits check every time a target company is added
- Review open longlist names and uncovered target companies once a week
Research you can show
A search is only as good as the research behind it, and research only counts when your team and your client can see it. Keep the longlist in the same system as the assignment, give every name a status, a date and an owner, agree the target companies with the client, check off-limits before every approach and keep the outcome for the next search. Explore the product or book a demo — we show how longlists, approach statuses and target companies are set up in BoldATS for your segment.