Skip to content

Work Acceptance Checklist

Version: 1.0 Purpose: Systematic framework for evaluating whether to accept new work assignments

Should I Accept This Work?

Use this checklist BEFORE committing to new projects, tasks, or responsibilities.

Part 1: Scope Assessment

Basic Information

  • Clear objective: I understand what "done" looks like
  • Success criteria: There are measurable outcomes
  • Timeline: There is a realistic deadline (not "ASAP")
  • Priority: I know how this ranks against my other work

RED FLAG: If you can't check all 4 boxes, ask for clarification BEFORE accepting.

Complexity Check

Is this work appropriate for my current level?

  • Within my domain: I have worked on similar problems before
  • Reasonable stretch: This is 1 level above my current work, not 3 levels
  • Technical feasibility: The required skills exist in the team
  • Reference available: There are similar past projects to learn from

RED FLAG: If this feels like "sink or swim" rather than "challenging growth opportunity," escalate.

Part 2: Support Assessment

Mentorship Availability

  • Named mentor: There is a specific person assigned to help me
  • Response SLA: I know how quickly the mentor responds (hours/days, not weeks)
  • Review cadence: There is a regular check-in schedule (weekly minimum)
  • Technical depth: The mentor has expertise in the relevant domain

RED FLAG: "Ask if you have questions" is NOT a mentorship plan.

Team Support

  • Peer support: There are teammates I can ask for quick questions
  • Code review: Someone will review my work regularly
  • Knowledge sharing: There is documentation or onboarding material
  • Escalation path: I know who to escalate to if blocked

RED FLAG: If you're the only person working on this domain, question whether this is appropriate for your level.

Part 3: Capacity Assessment

Current Workload

Before accepting, review your current commitments:

Current Work Hours/Week Hard Deadline? Can Deprioritize?
Project A ? Y/N Y/N
Project B ? Y/N Y/N
Oncall ? N/A N
Meetings ? N/A Maybe
TOTAL ?/40 - -

Checklist:

  • Total < 40 hours: I have capacity without overtime
  • Clear priorities: I know what I can deprioritize if needed
  • Buffer time: I have at least 10% slack for unexpected work
  • No conflicts: New work doesn't have deadline conflicts with existing work

RED FLAG: Accepting new work when at 100% capacity = setting yourself up for failure.

Energy Assessment (Honest Check)

  • Mental energy: I have cognitive space for new complex work
  • Stress level: I'm not already burned out from current work
  • Interest: I'm genuinely interested or see career growth value
  • Sustainability: I can sustain this workload for the projected duration

RED FLAG: If you're accepting out of compliance pressure ("I should be able to handle this") rather than genuine capacity, STOP.

Part 4: Risk Assessment

What Could Go Wrong?

Evaluate these risk factors:

  • Scope creep risk: LOW (well-defined) vs HIGH (vague requirements)
  • Dependency risk: LOW (self-contained) vs HIGH (depends on other teams)
  • Technical risk: LOW (proven tech) vs HIGH (experimental/new)
  • Timeline risk: LOW (realistic buffer) vs HIGH (aggressive deadline)
  • Review risk: LOW (regular feedback) vs HIGH (hands-off mentor)

Total risk score: - 0-1 HIGH risks = Acceptable - 2-3 HIGH risks = Needs mitigation plan - 4-5 HIGH risks = Reconsider or negotiate

RED FLAG: If multiple HIGH risks exist AND you have no mitigation plan, this is a setup for failure.

Part 5: Career Alignment

Is This Worth Your Time?

  • Skills development: I will learn valuable skills
  • Visibility: This work will be visible to decision-makers
  • Portfolio: I can showcase this in future interviews/promotions
  • Impact: This work matters to the organization

OR (minimum threshold):

  • Pays the bills: Even if boring, it's stable and low-stress

RED FLAG: If this is neither career-building NOR stable/low-stress, why are you accepting it?

Decision Matrix

Accept Immediately

  • All scope/support/capacity checks pass
  • 0-1 high risks
  • Clear career benefit

Action: Accept and document scope/timeline in writing.

Accept With Conditions

  • Most checks pass, but 2-3 yellow flags
  • 2-3 high risks with mitigation possible
  • Career benefit unclear but manageable workload

Action: Negotiate conditions BEFORE accepting: - "I can do this IF timeline extends to [X]" - "I can do this IF you provide [specific mentorship]" - "I can do this IF we deprioritize [other work]"

Decline Or Escalate

  • Multiple red flags (scope/support/capacity)
  • 4-5 high risks
  • No clear career benefit AND high stress
  • Already at 100% capacity

Action: Use professional "no" scripts (see below).

Professional "No" Scripts

Capacity Issue

"I'm currently at full capacity with [Project X] and [Project Y]. To take this on, I would need to deprioritize one of those. Which would you recommend?"

Scope Unclear

"This sounds interesting, but I need more clarity on [scope/timeline/success criteria] before I can commit. Can we schedule 30 minutes to align on expectations?"

Support Gap

"I want to make sure I can succeed on this. My understanding is [Mentor X] would support me. Can you confirm their availability for [weekly reviews / 48h response time]?"

Timeline Unrealistic

"Based on [similar past projects], my estimate for this is [X weeks]. If the deadline is firm at [Y weeks], I would need [additional support/reduced scope]. Which would you prefer?"

Level Mismatch

"This looks like [Senior/Staff] level work. I'm excited to stretch, but want to make sure we have realistic expectations. Should we discuss breaking this into phases, with phase 1 appropriate for my level?"

Simply Overloaded

"I'm currently managing [X hours/week] of committed work. Taking this on would put me at [Y hours/week], which isn't sustainable. Can we revisit my current workload or timeline for this new work?"

Notice: None of these say "No." They state reality and ask for decisions.

Emergency Override: When To Say "Yes" Anyway

Sometimes you SHOULD accept risky/unclear work:

Good reasons to accept despite red flags: - Production outage (all hands on deck) - Critical company initiative (visible high-impact work) - Explicit career opportunity ("this is your promotion project") - You negotiated conditions (extended timeline, extra support)

Bad reasons to accept despite red flags: - "I don't want to seem difficult" - "Everyone else is busy too" - "I should be able to handle this" - "If I say no, they'll think I'm not a team player"

If you're accepting for bad reasons, STOP. Re-read the boundary setting guide.

Post-Acceptance: Document Your Agreement

After accepting work, send confirmation email:

Hi [Manager/Lead],

Confirming my understanding of [Project X]:

SCOPE:
- Objective: [What I'm building]
- Success criteria: [How we measure done]
- Out of scope: [What I'm NOT doing]

TIMELINE:
- Expected completion: [Date]
- Major milestones: [Dates]
- I will flag if timeline slips by >1 week

SUPPORT:
- Technical mentor: [Name]
- Review cadence: [Weekly/biweekly]
- Escalation contact: [Name]

CAPACITY:
- Deprioritizing: [Other work]
- Expected hours/week: [X]
- Current total workload: [Y hours/week]

Please confirm this aligns with your expectations.

Why document: - Prevents scope creep - Establishes shared expectations - Protects you if things go wrong - Shows professionalism

Quarterly Review: Am I Accepting The Right Work?

Every 3 months, review your accepted work:

Pattern Check

In the last quarter, how many projects did you accept that: - Were unclear/vague when you started? - Had inadequate mentorship? - Exceeded original timeline by >50%? - You completed successfully? - Advanced your career?

Healthy pattern: - 0-1 failed/problematic projects per quarter - 2-3 successful projects per quarter - Clear career progression

Unhealthy pattern: - 2+ failed/problematic projects per quarter - Constant firefighting - No career progression - Accepting work out of compliance pressure

If you see unhealthy pattern, revisit boundary setting guide.

Summary: The 5-Minute Decision Framework

When offered new work, spend 5 minutes answering:

1. WHAT (Scope Clear?) - Can I describe "done" in 2 sentences?

2. WHO (Support Clear?) - Do I know who will mentor/review me?

3. WHEN (Timeline Realistic?) - Is this achievable without overtime?

4. WHY (Career Value?) - Will this help my growth or stability?

5. CAPACITY (Room For This?) - Do I have space without sacrificing wellbeing?

If you answer NO to 2+ questions, don't accept without negotiation.

Document Version: 1.0 Last Updated: 2026-05-23 Status: Active guidance for work acceptance decisions