Manual copy-paste at this point is not just slow. It is a confidentiality risk. One wrong attachment to the wrong committee member and the candidate relationship is damaged before the process starts. In retained search, where fees are paid upfront and expectations run high, that kind of error does not get forgiven.
What makes candidate dossier distribution different from other bulk email
Executive search is not marketing. You are not broadcasting a message. You are sending a confidential document about a specific person to a specific client stakeholder. The stakes are different because the content is personal.
A candidate dossier contains compensation data, reference feedback, assessment results, and career history. If the wrong dossier reaches the wrong person, the candidate's current employer could learn they are exploring opportunities. The search firm's reputation for discretion is the entire business model.
Standard Outlook mail merge tools were not designed for this. They treat every recipient the same. They cannot handle per-recipient attachment mapping. Cloud-based mail merge add-ins require uploading candidate data to a third-party server, which creates a data custody trail that complicates confidentiality agreements with both clients and candidates. Most retained search agreements include clauses requiring the firm to control access to candidate data throughout the engagement. Uploading dossiers to a marketing platform's infrastructure is hard to reconcile with that obligation.
The confidentiality problem with cloud-based recruitment tools
Most recruitment technology platforms operate as cloud CRMs. You upload candidate profiles, log outreach, and manage pipelines inside their database. For the sourcing and tracking phases of a search, this works fine. The problem starts when you need to send a dossier to a client.
Exporting a dossier from your CRM and emailing it manually bypasses the CRM entirely. There is no audit trail connecting the send event to the candidate record. If a client later asks which candidates were presented and when, the answer lives in someone's Sent Items folder, not in the system of record.
Some firms try to work around this by attaching files through the CRM's email integration. But these integrations typically use cloud relays that process your attachments through the vendor's mail servers. For a confidential candidate dossier containing compensation data and reference feedback, that adds a data custodian that the client did not authorize.
FlowDrafts avoids this by keeping everything local. The candidate list stays in your spreadsheet. The dossier PDFs stay on your drive. The VSTO add-in reads both, drafts the emails through your local MAPI connection, and never transmits a byte to any server. The audit log maintains the connection between candidate and send event without any external data processing.
How the workflow works for a retained search firm
The operational question is whether local-first processing can handle the volume of a busy search practice. It can, but the workflow needs to be structured correctly.
Start with a clean Excel sheet. One row per recipient. Columns for name, email, firm, and the candidate assigned to their review. The column headers become personalization tags you insert into your email template.
Paste the sheet into the add-in. The interface reads your columns and makes them available as tags. You write one email template and the add-in personalizes it for each recipient through your local Outlook session.
Map dossiers to each recipient row. The add-in opens a file dialog per row. You select the PDFs for that specific recipient. Each row can hold multiple files. The interface displays every mapping so you can visually confirm nothing is crossed before execution.
Generate the emails as drafts first. Spot-check a few. Verify the attachments, confirm the greeting, check that the dossier matches the candidate assigned to that reviewer. Then send. The drafts-first step catches the errors that manual processes miss because you are reviewing rendered emails, not spreadsheet rows.
Secure Your Dossier Distribution
Send confidential candidate profiles to clients directly from Outlook.
What changes when a search firm automates dossier distribution
The time savings are real but they are not the main benefit. The main benefit is that the workflow becomes auditable. Every send gets logged locally with recipient, timestamp, attachment list, and delivery status. If a client asks what was presented and when, the answer is an export, not a reconstruction from Sent Items.
Error elimination is the second benefit. Manual attachment mapping produces mistakes. Not every mistake gets caught. A dossier attached to the wrong email is usually discovered when the wrong person opens it. Automated row-level mapping prevents this by making every attachment pairing explicit and visible before execution.
For firms operating under AESC standards or similar professional guidelines, the audit trail alone justifies the switch. Retained search agreements require demonstrable control over candidate data distribution. A local audit log that captures every send event satisfies that requirement. A cloud relay that processes candidate data through a third-party mail server does not.
Distributing candidate dossiers is one of the highest-stakes workflows in executive search. A single misdirected file can cost a candidate placement and a client relationship. Automating the mechanical part of that workflow does not reduce the judgment required. It removes the clerical errors that distract from it.