Candidate sourcing teaches a recruiter the most in the week a finalist accepts the offer. By then they know which line of the brief the hiring manager rewrote after the first profiles, and which finalists nearly said yes. The week after, they are sourcing for another role, and what they learned sits in a Slack thread until someone archives the channel.
I think that week decides whether a team has a sourcing system or a series of unrelated searches. My answer is a one-page close-out written that week and filed under the role family, so the next similar req opens from it and the work carries between roles instead of leaving with the recruiter.
What a candidate sourcing search loses when the req closes.
A search produces more than a hire. By the time the offer is signed, the recruiter knows things no job description says, and most of it is gone within a week of the close:
- The brief as it ended, with every correction the hiring manager made after seeing real profiles, and the dealbreakers that only came up in the second batch of feedback.
- The people who got close, such as finalists who chose another offer and strong candidates who said “not now,” along with what might bring each of them back.
- Where the finalists were found: the employer and the channel behind each one.
- The first lines of the messages that drew replies, and the ones that drew silence.
Most of it was written down somewhere, in the hiring manager’s Slack thread or the recruiter’s inbox, which the next person to source for that role will never open.
Reqs move between recruiters as workloads shift, so that next person is often someone else, and the second search for a role can open a year after the first. So record it at the close, in one document the next recruiter for that role family will be handed.
Write a close-out before the req is marked filled.
The close-out is a one-page document the recruiter writes the week an offer is accepted, before the req is marked filled in your company’s applicant tracking system (ATS). To write it, book a short close-out call with the hiring manager that week, while both of you still remember why the team passed on the profile that looked perfect on paper.
Use the call to fill in these rows, one each:
| What the close-out records | What the next search does with it |
|---|---|
| The brief as it ended, with each correction the hiring manager made and why | Opens the next intake call, where the hiring manager edits a page instead of describing the role again |
| The dealbreakers that surfaced after the first profiles went to the hiring manager | Goes into the first search, so profiles that failed on those points last time stay off the list |
| The finalists who nearly said yes, and what might bring each one back | Gives the recruiter the first people to write to when the role opens again |
| The employer and the channel behind each finalist | Points the first open-market search where the strongest candidates were found last time |
| The opening lines of the messages that drew replies | Gives the next recruiter a first draft for the first message, to rewrite for the new role |
| What the recruiter would do differently | The one row that is pure judgment, and often the one the next recruiter reads twice |
Send the draft to the hiring manager before you file it, and ask them to correct anything they remember differently.
Keep it to a page. A close-out that takes an afternoon gets skipped in the busy weeks, and those are the weeks with the most to record.
Keep one brief per role family, and date every change.
File close-outs by role family, such as backend engineering or account executives, and never by req number. The next backend engineering req has a new number and the same open questions, and a library sorted by req makes the recruiter hunt for an answer the system could have handed them.
Keep one current brief per family. Whenever a close-out changes the brief, edit it in place and put a dated note beside the change saying why, for example: “Added in March: has sold to a finance buyer, because the hiring manager turned down the finalists who hadn’t.” A dated reason lets the next hiring manager argue with a requirement instead of inheriting it without knowing where it came from.
Retire a line once no one can say why it is there. Old briefs collect requirements the way old job descriptions do, and each one left in place shrinks the pool for a reason the current hiring manager may not hold.
Open the next search from what the last one kept.
When a req opens in a family you have hired for before, the close-out sets the order of the first week. Send the hiring manager the current brief a day before the intake call, and spend the call on what has changed in the team and on anything they would reject that the brief doesn’t say yet.
I think a hiring manager edits a page more carefully than they describe a role from memory. Their edits are what the new search needs most, and a fresh description buries them among the things that stayed the same.
Before the open-market search runs, write to the finalists first, starting from what the close-out says might bring each one back. Their full records belong in your candidate database. Shaping those records so a later search can find them is its own job, which this candidate database guide walks through.
Then aim the open-market search at the employers and channels the finalists came from, and widen it once the first batch shows whether those places still hold the people you want. Draft the first messages from the lines that drew replies last time, and have the new hiring manager read each one before it goes out under their team’s name.
Where Metaview fits in candidate sourcing.
A close-out written from memory quotes the hiring manager loosely, and the next search reaches only what someone typed into the ATS. Metaview works at both ends: the intake call the close-out draws on, and the search that opens the next req.
When everyone on an intake call agrees to be recorded, the Metaview Notetaker attends as a named participant everyone on the call can see, and from its recording and transcript it writes structured notes of the call. Your team decides how it asks for that agreement.
On an intake call Metaview captures every spoken word. That record lets the close-out quote a dealbreaker in the hiring manager’s own words and lets the next intake call be read side by side with the last one.
Intake meetings are one of the most outcome-defining moments of the hiring process.”
Quote that call in the close-out, and the next hiring manager for the role starts from what this one said rather than from a recruiter’s summary.
When the role reopens, an intake call recorded with Metaview is enough to start AI Sourcing: from that call, the sourcing agent kicks off a web search, and you can upload a job description, sample resumes, or past interviews to give it more to work from. The search also reaches the candidates synced over from your ATS and the conversations your team recorded in Metaview, so people your team spoke to on recorded calls can come back in it, each with the sourcing agent’s reasoning.
Contacting and assessing those candidates stays with the recruiter, because the agent does neither on its own. So check each returned name against the close-out’s dated dealbreakers before anyone writes to them.
The date windows in this clip are the kind of detail a close-out should keep. Metaview’s chief executive asks the sourcing agent for product designers who were at fintech companies while those companies had fewer than a thousand employees, and the agent works out when each company passed that size before it searches.
When a hiring manager names a requirement like that on an intake call, add it to the role family’s brief with its date and reason. It is the hardest kind of line to rebuild from memory a year later.
Reports covers the interview data your own recruiting team holds in Metaview, which helps when you sit down to write a close-out and want to know what the finalists’ interviews covered.
- 1Derek L.’s interview with the hiring manager, where “Problem Solving” got “0 questions” and “Culture” got nine.
- 2Jo T.’s technical interview, with seven questions under “Coding.”
- 3A saved “Punctuality” report in the row of report cards below the table.
Note a zero like Derek’s in the close-out: if a dealbreaker went unasked in the finalists’ interviews, the next search inherits a requirement no one tested.
- 1A salary figure plus equity, from Marc S.’s screen with the hiring manager.
- 2Gemma B. on two rows, one for each of her calls.
- 3The column’s header, with the AI icon beside it.
Kept in the close-out, what each finalist said they expected to be paid spares the next recruiter an awkward first call with them.
Questions to put to the next repeat req.
When a repeat req lands, these five questions show whether the last search left anything behind. Start with the fix in the last column wherever the answer comes back badly:
| Question | A bad answer | Fix first |
|---|---|---|
| What does the intake call open with? | The hiring manager describes the role from scratch | Write a close-out for the last search in that family, even a late one rebuilt from the ATS record |
| Who hears about the role first? | Strangers from a new open-market search | Write to the finalists the close-out names before that search runs |
| Can someone say why each line of the brief is there? | Lines no one can explain | Date each change with its reason, and retire the lines no one will defend |
| Who wrote the last close-out? | No one, or a recruiter who has since left | Book the close-out call for the week the offer is accepted |
| What do the first messages start from? | Each recruiter writes from a blank page | Keep the lines that drew replies in the close-out, beside the ones that drew silence |
Of everything the close-out holds, I’d protect the last row, what the recruiter would do differently, because no tool and no record can write it for them. Make it the first row of the next close-out you file. When the role family reopens, the next recruiter reads that lesson first, the one the last search paid for.
Build a sourcing system that carries into the next role.
Bring the brief from your last close-out to a demo, and watch the sourcing agent search with it, including the conversations your team recorded in Metaview.
Frequently asked.
What if the recruiter leaves before writing the close-out?
Rebuild a shorter one from the ATS record of who reached which stage, and ask the hiring manager why each finalist stopped. It will be thinner than one written at the time, and it still gives the next search more than a job description does.
When should you rewrite a role family’s brief from scratch?
When the hiring manager changes, or the role moves to a different level. Otherwise edit the kept brief at each intake call, and let the new hiring manager strike any line whose reason they don’t share.
What about roles your team only hires for once?
Close the search out anyway and file it under the nearest family. A one-off search for a staff accountant still tells the next finance hire which employers produced finalists and what that hiring manager would not accept.
How do you keep a list of near-miss candidates useful between reqs?
Get back in touch when each person asked you to, such as the spring they said they might move, even if no role is open. Take a name off the list once they tell you they are settled or ask not to be contacted.
Should a recruiting agency write a close-out too?
Ask for one whenever an agency works a role, and agree in the contract which of its candidates you may approach later. An agency’s finalists can be the most useful names for the next search, and those terms decide whether you can contact them yourself.
