Executive search
A headhunter's daily workflow review: choose the next useful action
A daily review for independent headhunters: recover live commitments, separate blocked work from actionable tasks and define the evidence needed to close the next action.
A headhunter's working day can begin in several places: the calendar, a client message, a research note or a reminder from yesterday. Each shows part of the work. None necessarily explains which commitment needs attention first or which task is waiting for a decision elsewhere.
A daily workflow review brings those questions together. It is a short working decision about the next useful action, grounded in actual commitments, available inputs and the purpose of the assignment. It should not become a competition to complete the largest number of small tasks.
The method works with existing tools. It does not require a new CRM, an automated priority score or a universal schedule for every headhunter. Its usefulness depends on whether the resulting plan reflects the work that can responsibly be done now.
Copyable daily workflow review
| Question | Working answer |
|---|---|
| What is already promised? | Named commitment, recipient, due point and current owner |
| Which assignment question matters next? | Decision or uncertainty the work should help resolve |
| What can I do now? | Concrete action with the necessary inputs and authority |
| What is blocked? | Missing dependency and the person or route responsible |
| What would completion establish? | Reviewable output, communication or recorded decision |
| Where does the result belong? | Correct assignment or relationship record |
| What could interrupt the plan? | Genuine time-sensitive dependencies and a reassessment trigger |
| What remains at close of review? | Accepted next actions, unresolved items and next check |
Do not attempt to recreate the whole firm in one daily list. Link each action to its relevant source record, and keep enough context to understand the next step. The daily view can then stay small without discarding the wider record.
The client update template is one source of live promises. If an update committed to return with a particular clarification, that commitment should be visible in the daily review even if no new email has arrived.
Recover obligations before selecting priorities
Begin with existing commitments and decisions awaiting action. Check the calendar, assignment records and relevant communications for work already promised to clients, candidates or colleagues. A new request should be considered alongside those obligations, rather than replacing them merely because it is recent.
Record the source of a deadline. A client-agreed update point, an internally chosen target and a reminder you set for yourself can all be useful, but they have different meanings. If the source is unclear, resolve it rather than describing the date as a firm promise.
Task tools can help make the record visible. Clockwork's task-panel documentation describes tasks in the context of people, projects and deals. That supplier-specific structure illustrates the value of context; it does not establish that a task entry contains every relevant commitment.
The question is not whether the task exists somewhere. It is whether you can explain who expects what, why it matters and what you are responsible for doing next.
Distinguish a daily view from the underlying work
A daily list is a selection of work, not the complete record of obligations. Moving an item out of the view should not make its underlying commitment disappear.
Microsoft's My Day guidance for Outlook says the view clears at midnight while tasks remain in their other lists. That is a useful product distinction: resetting a planning view is different from completing or deleting the work.
Use the same distinction when reviewing yesterday's unfinished items. Ask whether they still matter, whether their next action changed and whether someone needs an update. Avoid copying them into a fresh list without thinking, but do not remove them merely to start with a clean page.
A deferred item should have a reason and an appropriate next check. It should not remain indefinitely in a daily list whose repeated appearance makes it easy to ignore. Where the underlying commitment must change, communicate and record that through the proper route.
Separate actionable work from waiting work
An action is available when you have the necessary information, authority and conditions to perform it. A task can be important and still not be actionable. Repeatedly starring it will not supply the missing client instruction.
Write the dependency specifically. “Waiting on client” is less useful than “the agreed company boundary is awaiting confirmation from the designated client owner.” The latter identifies what would change the work and who can help resolve it.
Choose an appropriate next action for the dependency itself: request clarification through the agreed route, check whether a response has arrived, or explain which work is affected. Do not substitute an invented assumption to make a blocked task appear complete.
The mandate kickoff checklist helps recover the assignment's agreed boundaries. If the daily task conflicts with the brief, treat that as a question to resolve rather than silently expanding the search.
Choose work by the decision it supports
A useful next action has an identifiable purpose. Reviewing a source may help establish a candidate's actual scope of responsibility. Preparing a client question may resolve an ambiguity that affects several research tasks. The value is in the uncertainty addressed, not the number of clicks involved.
Write the output before starting: a sourced note for review, an agreed client question, or a completed check against a defined instruction. This makes it easier to stop when the action is complete and avoid drifting into unrelated research.
Do not turn this into a score that pretends unlike tasks are directly comparable. You can reason about urgency, consequence and available capacity without assigning an unsupported numerical value to every client or person.
If an interruption changes the plan, make the tradeoff visible. Ask which previous action moves and whether its recipient needs an update. A calendar full of intentions is less useful than a smaller set of commitments that can be understood and managed.
Worked example: seven actions and a limited day
This invented morning list belongs to one independent headhunter. The times and commitments are fictional and explicitly use Hong Kong time; they are not a prescribed schedule or quota.
| Item | State at the morning review | Next action and closure evidence |
|---|---|---|
| A: add a proposed company group | Waiting for the designated client scope decision | Retain the current boundary; consultant checks the agreed decision route |
| B: use a reference account | Waiting for the responsible person to confirm the permitted next step | Hold that use; record the unanswered question without contacting a new source |
C: promised update at 11:00 HKT | Existing commitment supported by yesterday's client note | Prepare the update with A and B visible as dependencies; record the reviewed communication |
| D: verify one operating-remit statement | Available research using a permitted source | Produce an attributed note stating which unit and period the source actually covers |
| E: reconcile an expense item | Available administration | Check the receipt against the assignment record and record the disposition |
| F: prepare tomorrow's client question | Available preparation | Draft the exact unresolved question and have the assignment owner review it |
| G: organize a closed research folder | Available, no external due commitment established | Defer with a next check if C and D use today's capacity; retain the underlying task |
The initial plan protects C and starts D. A and B remain visible with their decision owners; E, F and G do not become three more promised completions merely because they are available. The seven rows comprise two waiting items, one existing due commitment and four other available actions.
At 10:00 HKT, imagine A's answer arrives. The headhunter checks its consequence before changing the plan: does the new boundary affect C's update, and must D's source review change? They record the tradeoff rather than silently abandoning the promised update. Receiving an answer makes work actionable; it does not supply a universal priority rule.
Make ownership clearer than assignment buttons
When another person is involved, distinguish assigning a task from their accepting the responsibility and understanding its output. A name in a tool can be helpful while leaving those questions unresolved.
Microsoft Planner supports assigning a task to multiple people, and completion by one marks it complete for the others. That documented behavior belongs to Planner. It shows why your working meaning of completion must be clear when a tool shares a task across people.
For a headhunter working with a researcher or colleague, agree who produces the output, who reviews it and who returns an answer. Avoid a shared task whose apparent completion conceals an outstanding review.
Use the assignment handover guide when responsibility changes. The next owner needs the live instruction and unresolved points, not merely access to a task list.
Check time assumptions before communicating them
An agreed meeting time, a task reminder and a client's local working day may involve different time zones. Record the intended zone where confusion would matter, particularly when setting a promise with an external person.
Google Calendar's time-zone guidance describes how events are displayed across time zones. Correct calendar display still does not establish that a person accepted a new meeting or that a message will be answered before the next task starts.
For work whose duration is uncertain, state the dependency and next review point. Do not convert an optimistic plan into a guaranteed completion time. If the dependency changes, update the affected commitment rather than leaving a stale date to explain the assignment's state.
Close the review with evidence and a next check
At the end of a working period, record what was completed, what it established and where it belongs. A source-review action should leave an attributed note, including relevant uncertainty. The candidate research-note method offers a structure for that output.
For unfinished work, decide whether the next action is unchanged, revised, blocked or no longer appropriate. If another person is affected, record and communicate the change through the normal route. The purpose is continuity, not a perfect completion percentage.
Over time, examine recurring reasons the plan changes. Repeated missing inputs may call for a clearer briefing process. Repeated uncertainty about ownership may call for better receiving-team confirmation. A daily review can reveal those questions without proving a particular productivity or hiring outcome.