A schedule basis of estimate explains why an activity has its planned duration. It records the scope, estimating method, historical basis, resource assumptions, calendars, constraints and risks that support the estimate. A strong schedule BOE turns a duration from an unsupported number into a traceable planning decision.
For a proposal, the BOE should also reconcile with the technical approach, labor estimate and contract period of performance. It does not need to become a separate narrative for every minor task. However, reviewers should be able to trace significant durations and schedule-driving assumptions to credible source data.
What a schedule basis of estimate should answer
A useful BOE allows another qualified planner or technical lead to understand and reproduce the estimate. At a minimum, it should answer the following questions:
- What work does the activity include, and what does it exclude?
- Which Statement of Work (SOW), Work Breakdown Structure (WBS), deliverable or technical requirement does it support?
- How was the duration calculated?
- What labor, equipment, facility or supplier capacity does the estimate assume?
- Which project calendar applies?
- Does the duration include work, waiting time or both?
- What historical data, productivity rate or expert judgment supports it?
- Which assumptions and risks could change the duration?
- Does the estimate agree with the proposal’s cost and staffing plan?
The GAO Schedule Assessment Guide recommends supporting activity duration estimates with documented methods, assumptions and historical or analogous data. It also connects the schedule basis to the cost-estimating basis for the same WBS scope.
Is a schedule BOE a contractual requirement?
There is no universal Federal Acquisition Regulation requirement that every contractor proposal include a task-level schedule BOE. The controlling requirements come from the solicitation, including proposal instructions, evaluation criteria, the SOW or Performance Work Statement, data item descriptions, contract clauses and customer-specific scheduling guidance.
For example, FAR 11.402 directs the Government to consider factors such as production time, transportation, industry practice and Government-furnished property when establishing delivery or performance schedules. It does not prescribe a standard contractor format for documenting every proposed activity duration.
Likewise, the DFARS proposal adequacy checklist, when applicable, addresses supporting labor basis-of-estimate data such as labor categories, hours, task descriptions, rationale, history and time phasing. That requirement concerns proposal cost support. It does not automatically establish a separate schedule-duration BOE requirement. However, the labor BOE and proposal schedule should tell the same execution story.
Therefore, first follow the request for proposal. Then use the schedule BOE as a planning and review practice wherever the solicitation does not specify the level of documentation.
How to develop a schedule basis of estimate
1. Define the activity scope before estimating time
Duration estimating starts with scope. A technical lead cannot provide a reliable duration for an activity named “Complete Design” if the activity’s completion criteria remain undefined.
First, identify the required output. Then define the work needed to produce it and the event that marks completion. For proposal schedules, trace the activity to the applicable SOW, WBS, Contract Line Item Number (CLIN), Contract Data Requirements List (CDRL) item or technical review.
This traceability also helps prevent missing scope and duplicate scope. See how the WBS connects to the Statement of Work for a deeper treatment of that relationship.
2. Select the estimating method
Use the strongest method available for the maturity of the work. Common duration estimating techniques include:
- Bottom-up estimating: Decompose the activity into steps, estimate the effort or production quantity for each step and calculate the required duration.
- Analogous estimating: Compare the activity with similar completed work and adjust for differences in scope, complexity, resources or conditions.
- Parametric estimating: Apply a validated productivity relationship, such as drawings per week, test cases per engineer-day or units produced per shift.
- Expert judgment: Use the knowledge of a subject matter expert, supported where possible by records, assumptions or comparison points.
- Supplier or external estimate: Use a vendor lead time, subcontractor schedule, Government review period or facility commitment.
- Three-point estimating: Develop optimistic, most likely and pessimistic durations for schedule risk analysis.
The method should match the available data. Near-term engineering work may support a detailed bottom-up estimate. Meanwhile, an activity several years into the future may rely on an analogy until rolling-wave planning provides better information.
3. Convert effort or quantity into duration
Effort and duration are not interchangeable. Effort measures the labor required. Duration measures the working time between an activity’s start and finish under the assigned calendar.
A practical calculation is:
Duration = effort ÷ effective daily resource capacity
Effective capacity depends on the number of resources, their availability and the working hours in the calendar. It may also reflect a supportable productivity rate.
For example, an activity requires 240 engineering hours. Two engineers will each spend 60 percent of an eight-hour workday on the activity. Their effective capacity is 9.6 hours per day. Therefore, the calculated duration is 25 working days.
That estimate assumes both engineers remain available and can perform the work concurrently. If one engineer must complete the initial analysis before the other begins, the scheduler must reflect that sequence in the activity breakdown or logic. Adding people does not always reduce duration proportionally.
4. Separate active work from waiting time
Do not hide every turnaround period inside one long duration. Instead, model significant waiting periods as separate activities or logic when they represent distinct responsibility, risk or performance.
For example, separate “Prepare Draft Test Plan” from “Government Review of Draft Test Plan” and “Resolve Review Comments.” This structure clarifies accountability and exposes the effect of a delayed customer response.
However, decomposition should remain useful. A two-day internal peer review may reasonably remain part of a larger drafting activity if separate visibility adds no management value. The schedule’s required detail, reporting cycle and customer instructions should guide that decision.
5. Document calendars and availability
A 20-day duration does not have a single meaning unless the BOE identifies the calendar. Twenty working days on a five-day calendar differ from 20 days on a seven-day test calendar.
Document planned shifts, holidays, shutdowns, overtime assumptions and part-time availability when they materially affect the estimate. Also identify specialized resources that support several activities. A laboratory, test chamber, range or security-cleared reviewer may drive duration even when sufficient labor hours exist.
The NASA Marshall Space Flight Center Project Planning and Control Handbook describes schedule BOE development as a collaborative process. Its suggested content includes task descriptions, durations, logic, estimate sources, resource assumptions and risks on the projected critical path.
6. Reconcile the schedule with cost and staffing
A proposal schedule should not assume three full-time engineers while the cost BOE funds one half-time engineer. Similarly, the cost estimate should not phase labor before the schedule authorizes the associated work.
Reconcile at a practical control point, such as the WBS element, work package or major proposal task. The schedule may contain more detail than the cost model, so one-to-one mapping at every activity is not always necessary. Still, the scope, staffing profile, timing and estimating assumptions should align.
For more detail, see schedule-to-cost integration and how to develop schedule durations for a proposal.
7. Identify uncertainty without burying contingency
The planned duration should represent the execution estimate under stated assumptions. Do not quietly add untraceable padding to selected activities. Hidden contingency makes the network harder to analyze and prevents reviewers from understanding the actual uncertainty.
Instead, document the risk drivers. Where the proposal requires schedule risk analysis, develop supportable optimistic, most likely and pessimistic values. Risks may include resource competition, immature requirements, supplier variability, facility availability or uncertain Government review cycles.
A duration range should describe uncertainty in the activity, not compensate for incomplete logic or omitted scope. Therefore, correct structural problems before running a Monte Carlo simulation.
A realistic proposal example
Assume the fictional Falcon Ridge program must develop and deliver an Interface Control Document within 90 calendar days after contract award. The proposal team creates three linked activities:
- Develop draft Interface Control Document — 25 working days.
- Conduct internal and customer review — 15 working days.
- Resolve comments and deliver final document — 10 working days.
The first duration comes from 240 labor hours divided by the planned capacity of two engineers at 60 percent availability. The review duration comes from the proposal’s assumed ten-working-day customer response plus five days for internal processing. The final activity uses historical results from three comparable documents, adjusted for a larger interface count.
The BOE also records two assumptions. First, the customer will provide interface data at contract award. Second, both engineers will have access to the required development environment. The schedule models late customer data as an external dependency rather than adding padding to the drafting activity.
Finally, the proposal manager confirms that the labor BOE funds 240 hours during the planned drafting period. This simple reconciliation makes the duration, staffing and cost estimate defensible as one integrated plan.
Recommended schedule BOE fields
A spreadsheet, schedule note field or controlled basis document can hold the BOE. The format matters less than consistent, accessible content. Useful fields include:
- Activity ID and activity name
- WBS, SOW, CLIN or deliverable reference
- Scope and completion criteria
- Planned duration and calendar
- Estimating method
- Effort, quantity or productivity calculation
- Resource count and availability
- Historical source or analogous activity
- Assumptions and exclusions
- External dependencies and review periods
- Risk drivers and three-point values, when used
- Estimator, reviewer and estimate date
For a large Integrated Master Schedule (IMS), maintain detailed BOEs for critical, near-critical, high-risk and unusual activities. Standard production activities can reference an approved estimating standard rather than repeat the same narrative hundreds of times.
The Department of Energy Integrated Project Schedule Guidance also describes a schedule basis document that records the overall scheduling approach, key dates, assumptions, external constraints, procurement durations, resource limitations and reasons for unusual schedule features.
Common schedule BOE failures
- Accepting an unsupported expert estimate: “Engineering says 30 days” identifies a source but provides no rationale.
- Confusing hours with duration: Eighty labor hours do not automatically equal ten working days when several resources or part-time assignments apply.
- Estimating to a required date: Compressing durations until the schedule meets the desired finish date hides the execution gap.
- Ignoring calendars: Vendor shutdowns, holidays, shifts and facility schedules can invalidate an otherwise reasonable estimate.
- Combining work and external delay: Long activities can conceal customer reviews, procurement lead time and supplier dependencies.
- Using inconsistent proposal assumptions: The technical volume, schedule, labor BOE and staffing plan describe different execution strategies.
- Applying historical data without adjustment: An analogy loses credibility when the team ignores differences in quantity, complexity, tooling or personnel.
- Failing to preserve the basis: Reviewers cannot explain later why the baseline duration was selected or whether changed conditions justify replanning.
Reviewing the BOE before proposal submission
Review the duration basis alongside the logic, resource plan and proposal narrative. Challenge activities that drive contractual milestones, require scarce resources, contain unusual calendars or rely on aggressive external assumptions.
Then confirm that the schedule fits within the proposed period of performance without relying on unexplained constraints. The schedule should calculate from scope, durations, logic and calendars. It should not merely display the requested dates.
Teams building the first proposal network may also use the guides on building an IMS from an RFP and proposal scheduling for government contracts.
Final scheduler interpretation
A schedule BOE is successful when it makes the plan easier to challenge, integrate and update. It should reveal how the team expects to perform the work, not create paperwork after the schedule has already been built.
Focus the documentation on material durations and assumptions. Use traceable calculations, align them with the cost estimate and expose uncertainty instead of hiding it. As a result, the proposal schedule becomes more than a compliance graphic. It becomes a credible model of contract execution.