01
Check the boundaries
Separate the requested outcome from assumed or excluded work. Cover implementation, review, testing, rollout, monitoring, and cleanup as one estimate checklist.
Made for Engineers
Before You Commit to an Estimate
Also useful for: people in Software Engineering
15 min
Beginner
Decisions
Build Professional Skills
Need to Make a Decision
Check whether a work request is clear enough to estimate, then choose a range, a conditional estimate, or a short investigation first.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Catch hidden effort before an estimate becomes a promise.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Rank what could move the estimate
Find the few unknowns and dependencies that could materially change effort or timing instead of treating every open question as equally important.
03
Choose the responsible commitment
Decide whether the available information supports an estimate, a conditional range, or a short investigation before estimating.
Make Your Play
Before You Commit to an Estimate
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Paste or summarize the work you're being asked to estimate, including the intended outcome.
0/10000
List confirmed requirements, boundaries, existing components, and assumptions already being used.
0/10000
List open questions, unfamiliar systems, outside teams, approvals, data concerns, or blocked decisions.
0/10000
Describe expected reviews, testing, rollout steps, deadlines, release limits, and competing work.
0/10000
Select the kind of estimate being requested.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Check the boundaries
Separate the requested outcome from assumed or excluded work. Cover implementation, review, testing, rollout, monitoring, and cleanup as one estimate checklist.
02
Rank what could move the estimate
Find the few unknowns and dependencies that could materially change effort or timing instead of treating every open question as equally important.
03
Choose the responsible commitment
Decide whether the available information supports an estimate, a conditional range, or a short investigation before estimating.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the request as written, then add what is already known. It’s fine to list uncertainties without solving them. Use the recommendation to decide whether to estimate now or ask for investigation time.
Advanced instructions
Replace broad unknowns with concrete failure modes, affected systems, dependency owners, and release constraints. Compare the result with similar completed work before sharing the final range.
Use this when
You're being asked for an effort estimate or delivery date, but the request still contains unclear scope, technical unknowns, or outside dependencies.
You'll need
- Work request
- Known scope
- Unknowns and dependencies
- Delivery context
- Estimate request
You'll get
- Scope boundaries checked
- Unknowns and dependencies labeled
- Review, testing, and rollout effort covered
- Estimate confidence stated
- Estimate range or investigation plan selected
- Caveats ready to share
By the end of this playbook
You will have:
- Scope boundaries checked
- Unknowns and dependencies labeled
- Review, testing, and rollout effort covered
- Estimate confidence stated
- Estimate range or investigation plan selected
- Caveats ready to share
Examples
Progress 1 of 3