Develop credible proposal schedule durations by estimating each activity from defined scope, realistic resources, applicable calendars, historical performance and known external dependencies. Then document the basis for each material estimate and test the resulting network against contractual milestones and the proposed period of performance.
Do not begin with the desired finish date and divide the available time among activities. That approach produces durations that fit the calendar but may not represent the work. Instead, build a supportable schedule model that explains how the proposed team will execute the technical approach.
Start With the Solicitation, Not a Duration Template
No Federal Acquisition Regulation (FAR) provision establishes a universal method or standard duration limit for proposal schedules. The solicitation controls. Under FAR 15.204-5, Section L provides proposal instructions, while Section M identifies the significant evaluation factors and subfactors.
Therefore, first identify every schedule-related instruction, evaluation criterion and contractual date. Review the statement of work, performance work statement, specifications, Contract Line Item Numbers (CLINs), Contract Data Requirements List (CDRL), attachments and assumptions provided by the Government. Also identify proposal-specific requirements such as page limits, required schedule fields, native-file formats or mandated schedule software.
The Government evaluates a proposal against the factors stated in the solicitation. FAR 15.305 does not create a separate schedule-duration standard. However, an unrealistic schedule can weaken the proposed technical approach or increase perceived performance risk when schedule realism relates to an evaluation factor.
For a broader review of solicitation-driven planning, see how to build an integrated master schedule from an RFP and proposal scheduling for government contracts.
Build Proposal Schedule Durations in Seven Steps
1. Define the activity before estimating it
A duration estimate has little value until the team agrees on what the activity includes. Each activity should describe a specific piece of work with an identifiable completion condition.
Before asking for a duration, establish:
- The scope included in the activity.
- The required inputs and predecessor products.
- The person or organization responsible for the work.
- The expected output or completion evidence.
- The technical reviews, approvals or quality checks included.
- The resources, facilities and tools needed.
- Any assumptions that could change the estimate.
For example, “Develop design” is too broad. “Complete preliminary power-supply schematic” gives the estimator a clearer boundary. However, the scheduler must still determine whether the activity includes peer review, revision and approval or only the initial engineering work.
This scope discipline should align with the work breakdown structure and technical narrative. Review how the WBS connects to the statement of work when the proposal schedule and proposal volumes use different structures.
2. Select an estimating method that fits the work
One method will not fit every proposal activity. Use the strongest available evidence and identify the method in the schedule basis of estimate.
- Analogous estimating: Use actual durations from similar completed work. Adjust for differences in complexity, quantity, technology, team experience and review cycles.
- Parametric estimating: Apply a supportable rate to a measurable quantity. Examples include drawings per week, test cases per day or units processed per shift.
- Bottom-up estimating: Break the activity into smaller steps, estimate each step and combine them. This works well when the work is understood but the proposal schedule does not display every detail.
- Expert judgment: Ask the accountable technical lead or Control Account Manager (CAM) to estimate the duration. Challenge the estimate with historical data and clearly stated assumptions.
- Vendor or subcontractor input: Use current quotations, supplier schedules or documented planning input for external work. Confirm whether the estimate includes production, queue time, shipping and acceptance.
- Three-point estimating: Capture optimistic, most likely and pessimistic durations when uncertainty materially affects the plan. Retain the range for schedule risk analysis rather than hiding uncertainty inside an unexplained padded duration.
The GAO Schedule Assessment Guide recommends that activity durations use the same rationale, historical data and assumptions that support cost estimates. The guide also emphasizes reasonably short, meaningful activities that allow objective progress measurement. These are recognized scheduling practices, not universal solicitation requirements.
3. Separate work from duration
Work and duration are related, but they are not interchangeable. Work represents effort, often expressed in labor hours. Duration represents the working time between an activity’s start and finish under the applicable calendar.
An engineer may need 80 hours to complete an analysis. That does not automatically create a ten-day duration. If the engineer can devote only half of each day to the activity, the duration may approach 20 working days. Conversely, two qualified engineers may reduce the duration, but only if the work can be divided efficiently.
Use a simple planning relationship as a starting point:
Duration = estimated work ÷ effective resource capacity
Effective capacity must reflect actual availability, not nominal headcount. Account for other assignments, shift coverage, security restrictions, learning curves, coordination time and work that must occur sequentially. Adding people does not always reduce duration proportionally, especially for design decisions, integrated reviews and specialized testing.
4. Apply the correct calendars and availability
State whether estimates use working days, calendar days or elapsed time. Then configure the schedule calendar consistently. Holidays, planned shutdowns, alternate workweeks and facility operating hours can materially affect calculated finish dates.
Use special calendars only when the work genuinely follows a different pattern. For example, a thermal cycle may continue around the clock, while technicians supporting the test work scheduled shifts. Similarly, shipping may span weekends even though receiving and inspection occur only on working days.
Also distinguish resource availability from the task calendar. A laboratory may operate five days per week, but the required chamber may be available only during a reserved two-week window. In that case, facility access can control the duration or start date more than labor effort.
5. Model reviews, procurements and external dependencies explicitly
Do not bury supplier lead time, Government review or facility queues inside engineering durations. Represent material external steps as separate activities or milestones so reviewers can understand the execution plan.
Use a Government review duration stated in the solicitation, CDRL or applicable attachment when one exists. Otherwise, identify the proposed duration as an assumption. Do not present a customary review cycle as a contractual commitment.
Likewise, model long-lead material using documented supplier input. Include purchase authorization, fabrication, inspection, shipment and receiving when those steps affect the delivery path. For customer-furnished items, identify the need date and analyze the consequences of late availability. See Government-furnished equipment and schedule risk for additional planning considerations.
Data-item preparation also requires more than a finish milestone. Where schedule detail permits, include draft development, internal review, approval and submission. The schedule treatment should reflect the actual requirement described in the CDRL. For examples, review how contract deliverables should appear in an IMS.
6. Document a schedule basis of estimate
A proposal schedule basis of estimate explains why the team selected each significant duration. It can be a separate narrative, an estimating workbook or coded activity attributes. The format should fit the proposal instructions and internal review process.
At a minimum, capture the following for high-value, high-risk or driving activities:
- Activity identifier and description.
- Responsible estimator or activity owner.
- Estimating method.
- Historical source, productivity rate or vendor input.
- Estimated work and assumed staffing.
- Calendar and resource-availability assumptions.
- Most likely duration and, when useful, uncertainty range.
- Included and excluded scope.
- External dependencies or customer actions.
- Date of estimate and approval status.
The NASA Schedule Management Handbook recommends documenting the basis for schedule estimates and revisiting durations as better information becomes available. Although NASA guidance does not automatically govern a DoD contractor proposal, the documentation practice helps teams defend estimates during color reviews, negotiations and post-award planning.
7. Reconcile duration, resources and cost
The schedule, staffing plan and cost estimate must describe the same execution approach. If the schedule assumes four engineers for three months, the cost volume should contain compatible labor loading. If the basis of estimate funds one engineer, the scheduler should not use four-person capacity to achieve the proposed date.
The Department of Energy’s Cost Estimating Guide describes schedule and cost development as iterative and interrelated. In proposal practice, the scheduler, cost estimator and technical lead should repeatedly reconcile activity timing, labor hours, material need dates and escalation assumptions.
This reconciliation also improves the transition from proposal to execution. If the awarded program uses earned value management, the proposed plan may influence work-package planning, budget time phasing and the Performance Measurement Baseline (PMB). For more detail, see schedule-to-cost integration.
Handle Uncertainty Without Hiding Padding
Do not add unexplained contingency to every duration. Hidden padding makes estimates difficult to defend and can distort the critical path. It also prevents the proposal team from understanding which risks drive the finish date.
Instead, identify uncertainty explicitly. A technical lead might estimate an activity at 20 working days most likely, with a range of 15 to 35 days because of an unresolved interface. Record that range for schedule risk analysis and connect the uncertainty to the applicable proposal risk.
The deterministic schedule may use the most likely duration, an expected value or another approved value. No universal rule requires one choice for every proposal. Follow the solicitation, company estimating procedure and proposal risk strategy. If the team uses visible schedule margin, define its purpose and ownership rather than distributing it invisibly across unrelated activities.
Fictional Example: Estimating a Prototype Test Sequence
Consider the fictional Orion Ridge sensor prototype proposal. The offeror must deliver a qualified prototype within 18 months after contract award.
The engineering lead initially estimates “Conduct environmental qualification” at ten working days. During the estimate review, the scheduler separates the scope into test readiness preparation, chamber setup, vibration testing, thermal-vacuum testing, anomaly disposition and test-report approval.
Historical actuals show that thermal-vacuum testing requires five elapsed days. However, the facility manager confirms that chamber setup and teardown require four working days. The technical lead also identifies three working days for data review. Finally, the draft test report needs five working days, followed by a customer review period whose duration is not specified in the solicitation.
The revised network does not replace the original ten-day activity with an arbitrary longer duration. Instead, it exposes the sequence and identifies the customer review period as a proposal assumption. It also shows that chamber availability, not technician labor, controls the test start.
As a result, management can decide whether to reserve the chamber earlier, qualify a second facility or accept the schedule risk. The cost team can also price the correct facility window and test-support labor.
Test the Durations Against the Complete Network
After estimating activities, calculate the schedule and inspect the driving and near-critical paths. Check whether the network meets required delivery dates and remains inside the proposed period of performance. For additional context, review how the contract period of performance affects the IMS.
If the schedule misses a required date, do not simply shorten activities until the milestone fits. First, determine why the plan fails. The solution may involve changing the technical approach, adding a shift, increasing qualified staffing, performing work in parallel, using a different supplier or negotiating an assumption.
Next, confirm that any acceleration remains technically credible and matches the cost proposal. Fast-tracking can create rework risk, while crashing can increase cost without producing a proportional schedule gain.
Common Proposal Duration Mistakes
- Working backward from the desired date: The team assigns durations based on available time rather than executable scope.
- Using unsupported round numbers: Every design activity receives 20 days even though complexity varies.
- Confusing labor hours with duration: The schedule ignores part-time availability, parallel work and serial workflow.
- Ignoring calendars: The estimate omits holidays, shutdowns, shift limits or facility windows.
- Assuming Government turnaround times: The proposal treats an undocumented assumption as a contractual fact.
- Hiding risk inside durations: Padding masks the activities and assumptions that threaten the delivery date.
- Using optimistic supplier lead times: The schedule relies on informal estimates that exclude queues, shipping or inspection.
- Disconnecting schedule and cost: The schedule assumes resources that the proposal does not price.
- Leaving long activities unmeasurable: The post-award team cannot assess objective progress during normal status cycles.
- Cutting durations during executive review: Management changes dates without changing scope, resources or execution strategy.
Final Review Questions
Before proposal submission, ask the technical leads, cost team and proposal manager:
- Does each material duration trace to defined scope and a completion condition?
- Did the activity owner review and accept the estimate?
- Does historical performance support the duration, or did the team document why the work differs?
- Are labor, facilities, suppliers and calendars realistically available?
- Do the schedule and cost volumes assume the same staffing and execution approach?
- Are Government actions and external deliveries shown rather than hidden?
- Are uncertain durations supported by ranges and risk statements?
- Does the calculated network meet every required milestone without unsupported constraints?
- Can the team explain the basis for a driving duration during evaluation or negotiations?
A strong proposal schedule does more than show compliant dates. It demonstrates that the offeror understands the work, has considered the resources and dependencies, and can explain how the proposed plan will become an executable schedule after award.