The Schedule Is Technical Points, Not a Checkbox
On most progressive design-build and CMAR evaluations, technical criteria account for 50–70% of the total score before price is considered. The schedule exhibit — labeled "Project Approach," "Construction Schedule," or "Proposed CPM Schedule" in the technical requirements section — is typically scored against 5 to 10 specific evaluation criteria drawn from the schedule specification.
A GC who submits a bar chart created in PowerPoint is not just losing schedule points. They are signaling to the evaluation panel that they do not understand what they are building or how they intend to build it. A GC who submits a compliant, logic-driven P6 schedule signals the opposite — and that signal carries through the entire technical evaluation.
The 5 Criteria Evaluators Score Most Consistently
1. Critical Path Continuity
Evaluators want to see a clear, unbroken critical path from Notice to Proceed through Final Completion. Activities on the critical path should be connected with Finish-to-Start relationships where logic supports it, and the critical path narrative should identify the key controlling work sequences explicitly.
The failure mode: A schedule where the critical path jumps between unrelated scopes with no logical connection, or where the critical path terminates and restarts — indicating open ends or logic gaps that would not survive a DCMA review.
2. Owner Milestone Compliance
Every milestone listed in the RFP must appear in the schedule, properly constrained or logic-driven to meet the required date. Evaluators compare the submitted milestone dates against the RFP's required dates and score compliance directly. A missed required milestone — even if the overall duration is technically achievable — can result in the schedule being scored non-compliant.
The failure mode: Required milestones appear in the schedule but are not on the critical path, meaning the schedule provides no logic guarantee that they will be achieved by the required date.
3. Logic Density and Relationship Diversity
A well-built P6 schedule has a high density of logical relationships between activities. Most relationships should be Finish-to-Start, with Start-to-Start and Finish-to-Finish relationships used where the actual construction logic requires them. Lags should be minimized and where used should be documented with a rationale.
The failure mode: A schedule with a high percentage of Start-to-Start relationships with lags — often used to create a schedule that looks dense but is actually a bar chart with decorative logic links. Experienced evaluators recognize this pattern immediately.
4. Float Distribution
Total float should be distributed reasonably across the schedule. Activities with very high float (60+ days) on a 12-month project signal that logic relationships are missing or that the duration estimates are inflated. Negative float on non-critical activities signals constraint abuse.
The failure mode: A schedule where all float accumulates in one or two activity chains — indicating that the logic structure is incomplete and the schedule cannot accurately predict what is truly critical.
5. Schedule Narrative Quality
The written schedule narrative is evaluated alongside the Gantt. It should describe the critical path in plain language, explain the phasing approach, identify key assumptions embedded in the schedule logic, and confirm milestone compliance. Evaluators look for evidence that the person who wrote the narrative is the same person who built the schedule — not a generic boilerplate inserted after the fact.
The Most Common Scoring Failure We See
The single most common reason GC proposal schedules lose technical points is the absence of a continuous, logic-driven critical path. Proposal teams under deadline pressure build activity lists and connect them loosely — or build the Gantt first and add logic afterward. The result is a schedule that looks complete in a Gantt view but fails the first DCMA open-end check.
Evaluators at transit authorities, hospital systems, and major airport programs run the DCMA check on every submitted schedule as a matter of standard practice. A schedule with more than 5% open ends is often scored non-compliant on logic requirements before any other criteria are evaluated.
CPM Pros builds RFP schedule exhibits by reading the spec first, scoring the evaluation criteria, and building the schedule to those criteria — not by modifying a previous project's schedule to fit the new RFP. Our RFP exhibit service includes the XER, formatted Gantt, narrative, and milestone matrix in 2–3 business days.