Evidence-based schedule development
How to Create a Schedule Basis of Estimate
Document how important schedule durations were estimated, which assumptions support them, what resources and calendars were expected, where uncertainty remains, and what evidence reviewers can use to test the forecast.
Purpose and scope
A duration is a number; its basis is the explanation
A Schedule Basis of Estimate, often shortened to schedule BoE, records the reasoning behind important duration estimates and other schedule characteristics. It allows another informed person to understand where an estimate came from, what conditions it assumes, and how confidently it should be used.
Consider an activity scheduled for 20 working days. The number alone tells a reviewer almost nothing. It might represent four people completing 400 hours of known work, a vendor’s committed delivery time, an analogy with three previous projects, a regulatory waiting period, or an unsupported guess chosen to fit a target date. Each produces the same visible duration, but each has different evidence, flexibility, and risk.
The BoE makes those differences visible. It connects scope, work quantity, productivity, resource availability, calendars, constraints, external commitments, historical evidence, and uncertainty to the duration placed in the schedule. It does not guarantee that the forecast will occur. Its purpose is to make the estimate explainable, reviewable, reproducible where practical, and easier to update when conditions change.
Traceability
Connect the scheduled activity to its scope, work-breakdown element, responsible owner, estimate source, supporting data, and approval.
Transparency
Separate known information from assumptions, imposed constraints, professional judgment, uncertainty, and explicit management decisions.
Maintainability
Preserve enough context to revise the estimate intelligently when scope, resources, productivity, calendars, or external conditions change.
Document architecture
What belongs in a Schedule Basis of Estimate?
The appropriate level of detail depends on schedule complexity and decision consequence. Apply the most documentation to activities that drive commitments, contain significant uncertainty, depend on scarce resources, or rely on unusual assumptions.
| BoE component | Question answered | Example evidence | Weak documentation |
|---|---|---|---|
| Estimate identity | Which activity, milestone, work package, or phase is covered? | Activity ID, WBS reference, owner, version | “Development work” with no traceable identifier |
| Scope description | What must be completed for the activity to finish? | Deliverable description and completion criteria | A title that does not define the output |
| Estimating method | How was the duration calculated or judged? | Bottom-up, analogy, parametric, vendor quote | “Team estimate” without method or reasoning |
| Source data | Which facts or records support the calculation? | Historical performance, quantities, productivity | Untraceable numbers copied from an old plan |
| Ground rules | Which general estimating rules apply? | Working-day units, calendars, normal conditions | Rules understood only by the estimator |
| Assumptions | What uncertain condition is treated as true? | Staff start date, approval turnaround | Hidden optimism embedded in the duration |
| Resources | Which capability and availability support the duration? | Roles, capacity, productivity, equipment | Assuming full-time availability without confirmation |
| Constraints | Which fixed limits influence timing? | Access window, contract date, seasonal restriction | A forced date with no explanation |
| Uncertainty | How much could the duration reasonably vary? | Range, confidence basis, sensitive variables | Presenting one date as certain |
| Risks and opportunities | Which events could change the estimate? | Risk-register reference and schedule consequence | Generic risk language unrelated to the activity |
| Review and approval | Who owns and accepts the estimate? | Preparer, activity owner, reviewer, dates | No accountable owner or review record |
Estimating methods
Select a method that fits the available evidence
No single estimating method is best for every activity. The BoE should name the method, explain why it is appropriate, identify its data, and disclose meaningful limitations.
Bottom-up estimate
Break the deliverable into measurable pieces, estimate the effort or duration of each piece, and combine them according to their sequence and possible concurrency.
This works best when near-term scope is understood. Document work quantities, responsible skills, productivity assumptions, review cycles, and dependencies. Do not simply add effort hours and call the result elapsed duration; calendar availability and parallel work matter.
Analogous estimate
Compare the activity with completed similar work and adjust for meaningful differences in size, complexity, team capability, technology, environment, or acceptance requirements.
Record why the reference is comparable, the original actual duration, adjustments made, and limitations. An analogy is weak when only its convenient result is copied and its operating conditions are ignored.
Parametric estimate
Apply a supportable relationship between a measurable driver and duration, such as units processed per day, area installed per shift, or records reviewed per analyst-hour.
Document the formula, source data, range over which it is considered useful, productivity rate, learning effects, setup time, and adjustments. Avoid using a precise formula with unreliable inputs.
Expert judgment
Use informed judgment where reliable data is limited or the work is genuinely novel. Record the expert’s relevant role, the reasoning discussed, comparable experience, assumptions, disagreements, and how the final value was selected.
“Expert judgment” should not be a label that prevents review. The basis still needs enough explanation for decision-makers to understand what could make the estimate wrong.
Vendor or external commitment
Use a supplier quote, service-level commitment, published processing period, or agreed delivery window when external performance controls the duration.
Capture the quote date, validity, included scope, exclusions, prerequisites, shipping or review time, calendar basis, and whether the commitment is contractual, indicative, or assumed.
Three-point estimate
Record an optimistic, most-likely, and pessimistic duration based on defined conditions. The range helps expose uncertainty that a single point estimate can hide.
Explain what must be true for each value. Do not choose arbitrary percentages around the most-likely value merely to make the estimate appear analytical.
Step-by-step workflow
Create a defensible BoE in twelve steps
Start with the work—not the target date. Build a chain from defined scope through evidence and assumptions to the scheduled duration.
Identify the estimate precisely
Record the project, schedule, activity ID, activity name, work-breakdown reference, accountable owner, estimator, estimate date, and document version. If the BoE covers a group of activities, define that boundary and list the included IDs.
Clear identity prevents a valid explanation from being attached to the wrong schedule item after names or structures change.
Define the completed outcome
Describe what the activity produces and the condition that marks completion. Include relevant quantity, quality, review, handoff, and acceptance requirements. Distinguish completion of work from approval of its output when approval is a separate activity.
An estimate cannot be evaluated when “done” is undefined. A precise finish condition also prevents scope from quietly growing inside an unchanged duration.
Record ground rules
State the time unit, calendar, standard workday, holiday treatment, expected working conditions, estimating cutoff date, and organizational conventions. Identify whether the duration is elapsed time or working time.
Ground rules apply broadly and should remain consistent with the approved schedule-management approach. Refer to a controlled standard where one already exists.
Choose and justify the estimating method
Select bottom-up, analogy, parametric, expert judgment, vendor commitment, three-point estimating, or a documented combination. Explain why the method suits the maturity of the work and the available data.
Near-term defined work usually supports more detail. Distant or uncertain work may require broader planning estimates that are refined later.
Capture source data
List historical records, measurements, productivity observations, quantities, designs, vendor information, team estimates, or operational data used. Record dates, versions, owners, and limitations so the evidence can be located and interpreted later.
Do not imply that data is verified when it is preliminary. Label draft, incomplete, transformed, sampled, or judgment-based inputs honestly.
Convert effort into elapsed duration
Effort and duration are different. Forty hours of effort may take one person five working days, two people more than two and a half days if coordination is required, or several weeks if the needed specialist is available only part time.
Document capacity, productive availability, concurrency, coordination, setup, review, queue, waiting, and rework assumptions. Avoid assuming that doubling people automatically halves duration.
State resource assumptions
Identify required roles, skills, equipment, facilities, systems, and external services. Record assumed availability, onboarding, productivity, shift pattern, competing work, and any named resource whose absence would materially affect the estimate.
Confirm that resource assumptions are consistent with related cost and staffing plans. If they differ, document and resolve the discrepancy rather than preserving incompatible forecasts.
Separate assumptions from constraints
An assumption is uncertain but treated as true for planning. A constraint limits the available choices. “The reviewer will return comments within three days” may be an assumption. “Testing can occur only during the facility’s two-week access window” is a constraint.
For each assumption, describe the consequence if it proves false and identify how it will be validated. For each constraint, record its source, authority, and schedule effect.
Describe uncertainty and sensitivity
Identify the variables most likely to change the duration: quantity, defect rate, productivity, approval cycles, weather, dependency timing, learning curve, supplier performance, or resource availability.
Where useful, provide a range and the conditions behind it. Explain which assumption has the greatest influence so monitoring can focus on the information that matters most.
Connect relevant risks and opportunities
Link specific risk-register items instead of copying generic risk language. Describe how an event could alter the activity, dependency, resource plan, or duration. Record opportunities that could credibly shorten work without assuming they will occur.
Keep normal activity duration separate from management-held contingency where the project’s method requires that distinction.
Calculate and reconcile the estimate
Show enough calculation for another informed reviewer to follow the result. Reconcile the estimate with dependent activities, working calendars, planned resources, costs, external commitments, and relevant historical outcomes.
If the estimate differs substantially from an analogy or earlier version, document why. A justified difference can be credible; an unexplained difference is difficult to review.
Review, approve, and maintain the basis
Have the activity owner validate the scope and operating assumptions. Use technical, resource, schedule, cost, supplier, or independent review according to the significance of the estimate. Record comments, resolution, reviewer, approval, and date.
Update the BoE when its underlying basis materially changes. Preserve prior versions so later reviewers can understand why the forecast moved.
Interactive documentation aid
Schedule BoE Draft Builder
Enter one activity’s estimating basis to generate a structured draft. The tool runs locally in the browser and does not replace review by the responsible project team.
Generated Schedule BoE draft
Validate this draft against the actual schedule, resource plan, risks, cost assumptions, and organizational requirements before use.
Worked example
From unsupported duration to traceable estimate
Weak entry
Activity: Validate migrated records
Duration: 15 days
Basis: Team estimate based on experience.
This entry does not define the quantity, completion rule, staffing, productivity, calendar, source data, review effort, or uncertainty. It cannot be meaningfully challenged or updated.
Improved estimating basis
Scope: Validate 18,000 migrated records using the approved rule set, resolve identified transformation exceptions, and obtain quality-lead acceptance.
Method: Parametric estimate checked against the previous migration rehearsal.
Basis: Two analysts are assumed to complete an average of 900 records per analyst-day under the approved sampling and exception process. The estimate includes ten analyst-days for primary validation, three working days for exception resolution, and two working days for review and acceptance.
Uncertainty: Duration is most sensitive to the exception rate and reviewer availability. A materially higher defect rate or delayed access to the quality lead requires re-estimation.
The improved version is not automatically accurate merely because it is longer. Its value comes from exposing the model. Reviewers can test the quantity, rate, staffing, exception allowance, review period, and completion criteria. If actual productivity becomes 700 records per analyst-day, the team knows which assumption to update.
Example calculation
| Estimate element | Input | Reasoning | Scheduled contribution |
|---|---|---|---|
| Primary validation | 18,000 records; 2 analysts; 900 records per analyst-day | 18,000 ÷ 1,800 records per working day | 10 working days |
| Exception resolution | Expected normal exception workload | Based on rehearsal observations and team review | 3 working days |
| Quality acceptance | One review cycle with available quality lead | Review, response, and acceptance window | 2 working days |
| Total | Sequential execution assumed | 10 + 3 + 2 | 15 working days |
If exception handling can overlap with primary validation, the network schedule may produce a shorter elapsed duration than the simple sum. That sequencing decision must appear in the schedule logic, while the BoE records the assumption enabling the overlap.
Quality control
Common BoE mistakes and how to correct them
Estimating to the imposed finish date
The duration is reduced until the schedule reaches a preferred milestone, without changing the work or delivery method.
Correction: preserve the supportable estimate and evaluate explicit alternatives involving scope, sequence, resources, productivity, risk, or target date.
Confusing effort with duration
Total labor hours are divided by nominal team size without accounting for availability, coordination, waiting, review, or calendar limits.
Correction: show how effort becomes elapsed time and identify tasks that can genuinely occur in parallel.
Using analogy without adjustment
A past duration is copied even though the new work differs in scale, technology, team experience, quality requirements, or operating environment.
Correction: document comparability and quantify or explain every meaningful adjustment.
Hiding contingency inside activities
Durations contain unexplained padding, making it difficult to know how much time represents normal work and how much represents uncertainty protection.
Correction: estimate normal work transparently and manage risk allowance according to the project’s approved method.
Listing assumptions without consequences
The document says that resources or approvals are assumed available but never explains what happens if they are not.
Correction: add validation ownership, decision date, impact, and response for material assumptions.
Using excessive false precision
Immature work is estimated to decimal-level precision that the supporting information cannot justify.
Correction: match precision to evidence maturity and communicate a reasonable range where appropriate.
Ignoring cost and resource consistency
The schedule assumes more people or equipment than the staffing and cost plans support.
Correction: reconcile shared assumptions at a practical work-breakdown level and record intentional differences.
Never updating the basis
The schedule duration changes repeatedly while its original BoE remains unchanged and appears current.
Correction: update the basis after material changes and retain previous approved versions for traceability.
Review standard
Test whether the estimate is ready for use
A review should test the estimate’s reasoning—not merely confirm that all template fields contain text.
Completeness
- Scope and completion are measurable.
- The method and calculation are visible.
- Resources and calendars are addressed.
- Material assumptions are disclosed.
- Uncertainty is not presented as certainty.
Credibility
- Source data is relevant and traceable.
- Adjustments have a rational explanation.
- The estimate reflects normal expected conditions.
- Ranges are tied to defined scenarios.
- Reviewers can challenge the main drivers.
Consistency
- Scope matches the scheduled activity.
- Resources align with staffing assumptions.
- Calendars match the schedule model.
- Dependencies support the intended sequence.
- Costs and durations do not rely on conflicting facts.
Final verification
Schedule BoE completion checklist
0 of 14 BoE readiness items checked.
Questions answered
Schedule Basis of Estimate FAQs
Does every schedule activity need its own full BoE?
Not necessarily. Documentation should be proportionate. Detailed BoEs are most valuable for critical, high-risk, long-duration, expensive, externally committed, unusual, or assumption-sensitive work. Repetitive low-risk activities may use a controlled standard basis referenced by multiple activities.
What is the difference between a schedule BoE and a schedule narrative?
A BoE explains how an estimate was developed and which assumptions support it. A schedule narrative usually accompanies a current schedule update and explains status, changes, significant variances, critical paths, milestones, issues, and the current forecast.
Can expert judgment be a valid estimating basis?
Yes, particularly for novel or immature work, but the judgment should be transparent. Record who contributed, why their experience is relevant, what reasoning and comparisons were used, which assumptions were made, and where uncertainty remains.
Should risk allowance be included inside activity durations?
The treatment depends on the approved scheduling method, but hidden padding reduces transparency. Estimate expected work under stated normal conditions and document how uncertainty, contingency, and schedule risk are represented and controlled.
When should a Schedule Basis of Estimate be updated?
Update it when material scope, quantity, productivity, resource, calendar, technical, dependency, supplier, risk, or operating assumptions change. Preserve earlier versions when they supported an approved baseline or significant decision.
How detailed should source-data references be?
Provide enough detail for an informed reviewer to locate and interpret the evidence: document or system name, relevant version or date, data owner, selected sample or reference activities, adjustments, and known limitations.
What if no reliable historical data exists?
Use the best available method honestly. Combine structured expert judgment, bottom-up decomposition, vendor information, prototypes, pilot work, or a documented range. Label uncertainty clearly and establish when the estimate will be refined.
Can ScheduleFlowLab help create the working schedule?
Yes. After documenting the estimate, appropriate activities can be organized with the Weekly Schedule Builder , Monthly Schedule Builder , or other resources available through Schedule Tools .