Before You Accept: A Role Due-Diligence Workbook

01

Set your conditions before the offer sets them for you

Write what you need from the next role and why. Separate hard constraints from strong preferences and negotiable trade-offs. Examples might include a location requirement, a sustainable schedule, enough support to do the work responsibly, or an opportunity to develop a specific capability. Do not let a prestigious title quietly replace the reason you began looking.

Include staying, continuing the search, or accepting a smaller change where those are feasible. Not everyone has equal time, bargaining power, or financial flexibility. The goal is an informed choice within real constraints, not a perfect offer or a demand that every condition be negotiable.

02

Investigate the ordinary work

Ask for concrete examples of the role's normal week, difficult periods, and recent deliverables. Compare these with the job description. A role can sound strategic while mostly requiring coordination, troubleshooting, or repetitive delivery. None of those is inherently bad; the question is whether the work fits what you want and can do.

• What did the person in this role spend most of their time on last month?
• What is the most difficult recurring handoff, and who helps resolve it?
• Why is the role open? What has changed in the team or mandate?
• Which parts of the job are fixed, and which would I genuinely be able to shape?
• What tends to surprise people after they join?

03

Test whether the mandate has support

Clarify what the manager expects at the first meaningful review and what success would look like in observable terms. Ask what resources, authority, relationships, and learning time are available. Responsibility without a way to influence the work is a risk to understand, not something enthusiasm alone can solve.

Where appropriate, ask to speak with a future colleague or cross-functional partner. Seek examples rather than confidential information or gossip. A recruiter, manager, and teammate may see different parts of the role. Conflicting answers are a reason to clarify; they are not automatic proof that someone is dishonest.

• Which two or three outcomes matter most, and what would be deprioritized if they compete?
• What can this role decide independently, and what requires approval?
• Which promised resources are already available, and which depend on future approval?
• How does the manager give feedback, handle disagreement, and respond when priorities change?
• What support would a new person receive before being expected to deliver independently?

04

Keep promises, evidence, and unknowns separate

For each important claim, record what was said, when, by which role, and what supports it. A specific account of a recent working week is different from a slogan about flexibility. An approved resource is different from a plan to request one. An unanswered question remains an unknown; it should not become either a reassuring assumption or an invented red flag.

Use the evidence grid to plan follow-up. Prefer questions that could materially change your decision. If you cannot obtain an answer, record the remaining exposure and whether you can accept it. Do not ask for private employee assessments, customer details, or internal documents that the organization cannot appropriately share.

05

Clarify the trade-offs before committing

Compare the opportunity with your constraints and realistic alternatives. A role may offer learning with less predictability, or stability with a narrower scope. Name the trade-off plainly and decide whether it is acceptable to you; do not hide it inside a total score. Strong performance on one dimension does not erase an unacceptable hard constraint.

Ask the appropriate person to clarify important expectations and confirm agreed changes in the relevant written offer or other appropriate record. Do not assume an informal conversation changes formal terms. For employment terms, benefits, immigration, compensation, or financial consequences you do not understand, obtain qualified advice suited to your situation.

06

Illustrative example: the attractive operations title

A hypothetical candidate receives an offer to lead operations at a growing organization. The job description emphasizes process improvement. Conversations reveal that the immediate priority is covering daily escalations, while hiring additional support is only a proposal. A colleague describes frequent after-hours handoffs that the candidate had not anticipated.

The candidate asks the manager to clarify the initial priorities, decision authority, available support, and schedule expectations. The manager confirms a narrower improvement scope but cannot promise the proposed hire. The candidate records that uncertainty instead of treating the future team as secured. If the confirmed role breaches a hard constraint, declining is reasonable. If the trade-off is acceptable, acceptance can be deliberate rather than based on a different imagined job.

07

Make a decision you can explain

Choose accept, clarify or negotiate, decline, or defer where possible. Record your rationale, the unresolved risks you are knowingly accepting, and the next action before the actual deadline. If you accept, carry the clarified expectations into an early alignment conversation with your manager; the workbook is a starting point for that conversation, not an employment agreement.

• Do not equate a compelling interviewer with a supportive operating environment.
• Do not assume budget, headcount, flexibility, or advancement that has not been confirmed.
• Do not use one negative anecdote as a verdict on the entire organization.
• Do not average away a hard constraint or let urgency erase it without acknowledging the trade-off.
• Do not keep researching questions that cannot change the decision while avoiding the one that can.

Continue with a related resource

• Thirty-Day Field Learning Sprint
• Career Portfolio Audit
• Pivot Distance Diagnostic