Rough Order of Magnitude (ROM) Estimate
What is a Rough Order of Magnitude (ROM) Estimate?
A rough order of magnitude (ROM) estimate is an early, high-level estimate of a project's cost or duration, given as a wide range. It is used to decide whether an idea is worth exploring before detailed planning.
Updated November 2026 · 2 min read
How accurate is a ROM estimate?
A ROM estimate is deliberately rough. It is made when little is known, so it comes with a wide range. Project management guidance from PMI describes a typical ROM range of -25% to +75%, meaning a project estimated at $1 million could reasonably cost anywhere from $750,000 to $1.75 million. As more is known, estimates narrow.
| Estimate type | When it is made | Typical accuracy range |
| Rough order of magnitude (ROM) | Idea or initiation stage | -25% to +75% |
| Budget estimate | Early planning | -10% to +25% |
| Definitive estimate | Detailed planning, before execution | -5% to +10% |
This narrowing is often shown as the "cone of uncertainty": estimates are least reliable at the start and become more accurate as requirements, design and risks become clear.
How ROM estimates are made
- Analogous estimating: comparing with similar past projects and adjusting for size and complexity
- Expert judgment: asking experienced people for a range
- Parametric estimating: using simple rules of thumb, such as cost per user or per integration
- Relative sizing, such as t-shirt sizing, converted to cost ranges
Whatever the method, the output should be a range plus the main assumptions behind it.
An example
A logistics firm is considering a new customer portal. Within a week, the delivery team produces a ROM estimate of $600,000 to $1.4 million and 6 to 12 months, based on two similar portals it has built and an assumption of three integrations. That is enough for the portfolio governance board to decide the idea is worth a funded discovery phase, but not enough to approve the full build. After discovery, a budget estimate narrows the range to $850,000 to $1.1 million, and the board approves at the go/no-go decision.
Where ROM estimates are used
ROM estimates are most useful at the front of the funnel: in project intake, early portfolio prioritization, annual planning and the first version of a lean business case. They let leaders compare many ideas quickly and decide which deserve more detailed work, without spending weeks estimating options that will be rejected anyway.
Common pitfalls
The biggest danger is that a ROM estimate becomes a commitment. Someone quotes the low end of the range in a meeting, it ends up in the budget, and the project is "over budget" from day one. Always present ROM estimates as ranges, state the assumptions, and label them clearly. Another pitfall is skipping the refinement step: approving a full project on a ROM estimate without any further estimation. Finally, teams often underestimate systematically; comparing ROM estimates with actual outcomes over time helps calibrate future ranges and reduces the impact of optimism bias.
Frequently asked questions
What is the accuracy range of a ROM estimate?
PMI guidance describes a typical range of -25% to +75% for a rough order of magnitude estimate. Some organizations use other ranges, such as -50% to +100%, especially for very early ideas. The key point is that a ROM estimate is wide by design and should always be presented as a range, not a single number.
What is the difference between a ROM estimate and a budget estimate?
A ROM estimate is made at the idea stage with little information and has a wide range. A budget estimate is made later, once scope is better understood, and is more accurate, typically -10% to +25%. The ROM estimate decides whether an idea is worth exploring; the budget estimate supports a funding decision.
Who prepares a ROM estimate?
Usually the delivery team, project manager or architect most familiar with similar work, often with input from finance, and often as part of project intake. It should take days rather than weeks. Estimators should record their assumptions, the comparable projects they used and the main uncertainties, so decision-makers understand how reliable the range is.
Related terms
Portfolio Governance
Who decides what gets funded, how the portfolio is balanced and held to account.
Go/No-Go Decision
A formal checkpoint to decide whether a project goes ahead.
Project Intake
One front door for new project requests, so they can be compared fairly.
Portfolio Prioritization
Ranking initiatives against agreed criteria so money goes where it counts.