You need an MS Project schedule when the contract, the owner, or the permitting authority requires a CPM network in Microsoft Project format — not a bar chart in Excel. We build .mpp files that survive review: a WBS tied to CSI MasterFormat divisions, activity durations backed by crew and quantity assumptions, and logic ties that show the critical path. If your project also requires Primavera P6 or a pure CPM analysis, we cover that under CPM Scheduling Services and Primavera P6 Scheduling Services.
- Deliverable
- Excel estimate + marked-up PDF plans
- Organized by
- CSI MasterFormat section
- Turnaround
- 24–48 hours for most projects
- Pricing
- ZIP-code-adjusted material and labor pricing
- Software
- Bluebeam Revu, PlanSwift, RSMeans data
Most of our MS Project work starts from a quantity takeoff, because durations without quantities are guesses. We measure the work by division — concrete (CY), steel (tons), MEP rough-in (LF/EA), finishes (SF) — then apply productivity rates from RSMeans data and your crew assumptions. The result is a schedule where every activity has a traceable basis, with activity sequencing, duration estimating, and free float you can defend. That matters when you are defending a time extension or updating a baseline for a pay application. For delay events after the fact, see Schedule Delay & Time Impact Analysis.
Deliverables arrive as .mpp, PDF, and Excel, organized by CSI MasterFormat division, with marked-up plan sets showing where quantities came from. Turnaround is 24–48 hours for most projects, with rush available. We serve contractors and owners nationwide, including Texas, California, Florida, New York, and North Carolina.
What our MS Project scheduling services include
We build the schedule from your drawings, specs, and contract milestones. Every activity carries a duration basis, and every logic tie is checked for open ends. You get a working .mpp file plus PDF and Excel reports you can issue.
WBS Development
Build work breakdown structure mapped to CSI MasterFormat divisions and spec sections, with activity codes for phase, area, and responsible party.
Divisions · SectionsQuantity-Based Durations
Derive activity durations from measured quantities (CY, tons, LF, SF, EA) and productivity rates from RSMeans data and crew assumptions.
CY · Tons · LF · SF · EAResource & Cost Loading
Assign labor crews, man-hours, and cost codes to activities; load costs for resource leveling and cash flow analysis.
Man-hours · Cost codesLogic Ties & Lags
Establish FS, SS, FF relationships with lags for cure, form-stripping, procurement, and submittal review periods.
FS · SS · FF · LagsBaseline & Critical Path
Set baseline schedule with total float and critical path identified; assign calendars for 5-day, 6-day, and 7-day work weeks.
Float · CalendarsProcurement & Submittals
Incorporate procurement and submittal review durations for long-lead items such as switchgear, elevators, and structural steel.
Days · WeeksInspection & Permit Holds
Add inspection and permit hold points per local building department requirements; coordinate with utility companies for tie-ins.
Hold pointsMonthly Updates & Reporting
Update schedules monthly with actuals, remaining durations, and float tracking; provide PDF and Excel reports with marked-up plan sets.
Monthly · PDF · ExcelWhat every ms project scheduling takeoff includes
- WBS mapped to CSI MasterFormat divisions and spec sections
- Activity durations derived from quantity takeoff and productivity rates
- Resource and cost loading by crew, man-hours, and cost codes
- Baseline schedule with total float and critical path identified
- Logic ties (FS, SS, FF) with lags for cure, procurement, and submittals
- Calendar assignments for 5-day, 6-day, and 7-day work weeks
- Procurement and submittal review durations for long-lead items
- Inspection and permit hold points per local building department
- Monthly update cycles with actuals, remaining durations, and float tracking
- Schedule of values tie-in for pay applications (01 29 00)
- PDF and Excel schedule reports with marked-up plan sets
- Narrative report explaining critical path and near-critical activities
How we handle project schedule development in MS Project
- Document review and WBS setupWe review the full plan set, specifications, and contract milestones. The WBS is mapped to CSI MasterFormat divisions — 01 32 16 for the schedule itself, 03 for concrete, 05 for steel, 22/23/26 for MEP. We set the project calendar (5-day, 6-day, or 7-day) and define activity codes for area, phase, and responsibility. We also check for any owner-mandated schedule specs, such as 01 32 16.01, and incorporate those requirements into the WBS structure and reporting format.
- Quantity takeoff by divisionWe measure quantities from the drawings: concrete CY from foundation plans, steel tons from framing plans, MEP LF from riser diagrams, finishes SF from floor plans. Each quantity is tagged to a sheet number and spec section. This takeoff is the basis for every duration — no activity is scheduled without a measured quantity or a stated allowance. We also note any assumptions, such as waste factors, and record them in the activity notes for traceability.
- Duration and resource loadingWe apply productivity rates from RSMeans data, adjusted for ZIP code and your crew assumptions. Durations are calculated as quantity divided by daily output, then loaded with crew size and man-hours. Long-lead procurement activities — switchgear, elevators, curtain wall — get durations from your supplier quotes or typical lead times. We also load non-labor resources, such as crane time and concrete pump hours, to support resource leveling and cost loading.
- Logic ties and critical pathWe link activities with finish-to-start, start-to-start, and finish-to-finish relationships, adding lags for concrete cure (ACI 301/347), submittal review, and inspection hold points. We check for open ends and near-critical paths. The CPM calculation identifies total float and the critical path, which we document in the narrative. We also run a schedule health check to flag activities with excessive lags, negative float, or missing predecessors.
- Baseline and reviewWe save the approved schedule as a baseline. You get the .mpp file, a PDF bar chart, and an Excel activity list. We walk you through the critical path, float values, and any assumptions. Revisions are made until the schedule meets your contract requirements. We also provide a baseline comparison report if you have an existing schedule, highlighting changes in durations, logic, and float.
- Monthly updatesFor ongoing projects, we update the schedule with actual start/finish dates, remaining durations, and percent complete from your field reports. We track float consumption, near-critical activities, and any logic changes. Each update includes a revised baseline comparison and a short narrative on schedule health. We also flag any activities that have slipped and provide a recovery plan if needed, such as adding shifts or re-sequencing work.
What we need from you
- Plan setArchitectural, structural, civil, and MEP drawings in PDF. Marked-up sets help us trace quantities.
- SpecificationsProject manual with CSI sections, especially 01 32 16 for schedule requirements and 01 29 00 for payment procedures.
- Contract milestonesStart date, substantial completion, owner occupancy, and any phased turnover dates.
- Crew assumptionsTypical crew sizes and shifts for each trade, so resource loading matches your means and methods.
- Procurement lead timesSupplier quotes or historical lead times for switchgear, elevators, curtain wall, and other long-lead items.
- Calendar requirementsWork week (5-day, 6-day, 7-day), holidays, and weather allowances for your region.
- Existing scheduleIf you have a draft .mpp or P6 file, send it so we can align WBS and activity IDs.
Sample MS Project activity list and durations
This is the format we use for activity lists and schedule reports. Durations are derived from quantities and productivity rates.
| Section | Line item | Qty | Unit | Ref. |
|---|---|---|---|---|
| 01 32 16 | Mobilization and temporary facilities | 1 | LS | C-100 |
| 31 23 16 | Excavation and backfill, including haul-off | 1,850 | CY | C-101 |
| 03 30 00 | Concrete foundations and slab-on-grade, 4000 psi | 12,400 | SF | S-101 |
| 05 12 00 | Structural steel erection, including connections | 185 | TON | S-201 |
| 22 11 16 | Plumbing rough-in, domestic water and waste | 2,400 | LF | P-101 |
| 23 31 13 | HVAC ductwork rough-in, galvanized | 3,200 | LF | M-101 |
| 26 05 19 | Electrical rough-in, conduit and wire | 4,800 | LF | E-101 |
| 09 29 00 | Drywall, tape, and finish, Level 4 | 28,500 | SF | A-301 |
| 01 32 16 | Substantial completion and punch list | 15 | wd | — |
| 01 32 16 | Final inspection and closeout | 10 | wd | — |
Units and how we measure them
We measure quantities in the units your spec and crew understand, then convert to durations using productivity rates.
| Item | Unit | How it's measured |
|---|---|---|
| Work days (wd) | wd | Calendar days minus weekends and holidays per project calendar |
| Calendar days (cd) | cd | Total elapsed days including weekends and weather allowances |
| Crew-days | crew-day | One crew working one full shift; used for resource leveling |
| Man-hours (MH) | MH | Labor hours from RSMeans or your historical rates |
| Linear feet (LF) | LF | Measured along centerline or specified run on plan |
| Square feet (SF) | SF | Area from plan dimensions, adjusted for openings |
| Cubic yards (CY) | CY | Volume from plan dimensions divided by 27 |
| Each (EA) | EA | Counted items: fixtures, equipment, connections |
| Lump sum (LS) | LS | Allowance items without measured quantities |
| Percent complete (%) | % | Physical progress at update date, verified against field reports |
| Float days | float day | Total float from CPM calculation; tracked at each update |
Worked example: scheduling concrete foundation and slab-on-grade
This worked example shows how we derive durations for a concrete scope from a quantity takeoff. All dimensions are illustrative; your project will have different quantities.
Step 1: Measure the area. From the foundation plan, the building footprint is 100 ft × 60 ft = 6,000 SF. The slab-on-grade covers this area. The perimeter strip footings are 2 ft wide × 1 ft deep, with a total length of 320 LF. Interior column pads: 12 pads, each 3 ft × 3 ft × 1 ft deep.
Step 2: Calculate concrete volumes.
- Slab: 6,000 SF × 0.5 ft (6 in.) = 3,000 CF. Convert to CY: 3,000 ÷ 27 = 111.1 CY.
- Strip footings: 320 LF × 2 ft × 1 ft = 640 CF = 23.7 CY.
- Column pads: 12 × (3 × 3 × 1) = 108 CF = 4.0 CY.
- Total concrete = 111.1 + 23.7 + 4.0 = 138.8 CY.
Step 3: Add waste. Typical waste for concrete is 5–10%. Use 7%: 138.8 × 1.07 = 148.5 CY. Round to 149 CY.
Step 4: Determine formwork area. Strip footing forms: 320 LF × 2 sides × 1 ft high = 640 SF. Column pad forms: 12 pads × 4 sides × 3 ft × 1 ft = 144 SF. Total formwork = 784 SF.
Step 5: Calculate reinforcement. Assume #4 rebar at 12 in. on center each way for slab: 6,000 SF × 2 directions × (1 lb per 2.67 LF?) Actually, standard estimating: #4 rebar weighs 0.668 lb/LF. For 12 in. OC each way: total length = 6,000 SF × 2 = 12,000 LF. Weight = 12,000 × 0.668 = 8,016 lb = 4.0 tons. Add 10% for laps and waste: 4.4 tons. For footings: 4 continuous #5 bars (1.043 lb/LF): 320 LF × 4 = 1,280 LF × 1.043 = 1,335 lb = 0.67 tons. Add 10% = 0.74 tons. Total rebar = 4.4 + 0.74 = 5.14 tons.
Step 6: Apply productivity rates. From RSMeans data (adjusted for ZIP code):
- Concrete placement and finishing: 0.8 crew-days per CY for slab, 1.2 crew-days per CY for footings. Slab: 111.1 CY × 0.8 = 88.9 crew-days. Footings: 27.7 CY × 1.2 = 33.2 crew-days. Total = 122.1 crew-days.
- Formwork: 0.05 crew-days per SF. 784 SF × 0.05 = 39.2 crew-days.
- Rebar: 0.02 crew-days per ton? Actually, typical: 0.5 crew-days per ton for installation. 5.14 tons × 0.5 = 2.6 crew-days.
Step 7: Calculate durations. Assume a crew of 6 workers (3 finishers, 2 laborers, 1 equipment operator) works 8-hour days. For concrete: 122.1 crew-days ÷ 6 = 20.4 days. Round to 21 work days. Formwork: 39.2 ÷ 4 (carpenters) = 9.8 days, round to 10 days. Rebar: 2.6 ÷ 2 (ironworkers) = 1.3 days, round to 2 days.
Step 8: Sequence and logic. Rebar and formwork can overlap with excavation and backfill. Concrete placement follows formwork and rebar inspection. Cure time per ACI 301: 7 days before form stripping. Add 7-day lag. Total foundation duration: 21 + 10 + 2 + 7 = 40 work days. This becomes the activity duration in the MS Project schedule, with predecessors and successors linked.
This method ensures every duration is traceable to a quantity and a productivity rate. For your project, we would use your actual dimensions, crew sizes, and local pricing.
What drives the schedule duration
Relative impact on a typical estimate for this trade, based on estimator judgment. Select a bar for details.
Procurement lead times
Switchgear, elevators, and curtain wall can take 20–40 weeks. If these are not on the schedule as activities with float, the project will stall. We include submittal review, fabrication, and delivery windows as linked activities. We also add a procurement log to track shop drawing approvals and release dates, and we update it at each schedule update to reflect actual lead times.
Switchgear, elevators, and curtain wall can take 20–40 weeks. If these are not on the schedule as activities with float, the project will stall. We include submittal review, fabrication, and delivery windows as linked activities. We also add a procurement log to track shop drawing approvals and release dates, and we update it at each schedule update to reflect actual lead times.
Concrete cure times per ACI 301 and 347 affect when formwork can be stripped and subsequent trades can start. We add lags for cure and strength testing, not just a generic 7-day wait. We also consider ambient conditions and mix design, and we schedule cylinder breaks as milestones that must be met before stripping or loading. This prevents premature removal and potential rework.
Local building department inspections — footing, framing, MEP rough, fire sprinkler — are mandatory hold points. We schedule them as zero-duration milestones with predecessors and successors. We also include the inspection request lead time (often 24–48 hours) and the possibility of re-inspection if the work fails. This keeps the schedule realistic and avoids surprises during construction.
Concrete placement and roofing are sensitive to temperature and rain. We add weather allowance days based on your region, or use a 6-day work week to recover time. We also consider the impact of cold joints, curing compound, and temporary heat. For projects in northern climates, we may include winter conditions as a separate calendar with reduced productivity rates.
If your crews are shared across projects, leveling may extend the schedule. We model crew availability and show the impact on total float and critical path. We also consider equipment constraints, such as crane availability, and trade stacking, where multiple crews work in the same area. The goal is to produce a schedule that matches your actual means and methods, not an ideal scenario.
Near-critical paths can become critical after a few updates. We track float at each update and flag activities with less than 5 days of total float. We also analyze the trend of float consumption over time to predict potential delays. If float is being consumed faster than planned, we recommend corrective actions, such as resequencing or adding resources, before the critical path is impacted.
Permit approval and utility company coordination can add weeks to the schedule. We include activities for permit application, plan review, and utility design, with durations based on local agency typical turnaround. We also schedule coordination meetings and meter set as milestones. These are often overlooked but can delay foundation and MEP work if not tracked.
Common gaps we catch in construction schedule review
Most schedule problems come from missing activities or wrong logic, not from bad software. Here are the gaps we see most often.
- Procurement and submittal review durations for long-lead items are often omitted. They hide in the specifications under 01 32 16 and 01 33 00. We add them as activities with submittal, review, fabrication, and delivery steps. We also include a procurement log to track each step and update it with actual dates.
- Cure time and form-stripping durations per ACI 301/347 are frequently ignored. We add lags based on mix design and ambient conditions, not a default 7 days. We also schedule cylinder breaks and require them as predecessors to form stripping, ensuring that concrete has reached sufficient strength before loads are applied.
- Inspection and permit hold points from the local building department are missing. We list them as milestones and link them to the work they release. We also include the inspection request lead time and the possibility of re-inspection, which can add days if corrections are needed. This prevents the schedule from showing work starting before inspections are passed.
- Utility company coordination and meter set lead times are not scheduled. We add activities for coordination meetings, trenching, and meter set, with durations from the utility. We also track the utility's design review and approval process, which can take several weeks. This is critical for projects that require new or upgraded service.
- Seasonal weather allowances for concrete and roofing are left out. We add weather days based on historical data for your ZIP code, or adjust the calendar. We also consider the impact of extreme temperatures on productivity and material performance. For example, concrete placed in hot weather may require retarders and additional curing, which we reflect in durations.
- Testing and balance of MEP systems (TAB) is often a single activity. We break it into pre-functional checks, TAB, and commissioning, each with its own duration. We also include the time required for re-testing if systems do not meet specifications. This ensures that the schedule reflects the actual sequence and duration of commissioning activities.
- Punch list walk and re-inspection cycles are underestimated. We add separate activities for owner walk, contractor correction, and re-inspection, with realistic durations. We also include the time for the owner's consultant to review and approve the corrections. This prevents the schedule from showing substantial completion before the punch list is actually closed.
- Temporary facilities and site logistics are often missing. We add activities for temporary power, water, offices, and storage, as well as site security and cleaning. These are necessary for the work to proceed and can impact the critical path if not available when needed. We also consider the sequencing of site utilities and access roads.
- Closeout documentation and as-built drawings are not scheduled. We add activities for collecting warranties, O&M manuals, and as-built markups, and for the final inspection and certificate of occupancy. These are often on the critical path because they must be completed before the owner will release final payment. We include them as milestones with predecessors.
Scheduling platform comparison: MS Project, P6, and Excel
The choice of platform affects deliverable format, resource loading, and update workflow.
| Platform | File format | Resource loading | Update cadence |
|---|---|---|---|
| Microsoft Project | .mpp | Yes, by crew and man-hours | Monthly or as required |
| Primavera P6 | .xer | Yes, with roles and cost codes | Monthly or weekly |
| Excel / PDF schedule | .xlsx / .pdf | Limited to summary level | As needed for reporting |
| Microsoft Project with cost loading | .mpp | Yes, tied to cost codes | Monthly with pay applications |
| Primavera P6 with earned value | .xer | Yes, with BCWP/BCWS | Monthly for progress reporting |
Codes and standards that affect MS Project schedules
Model codes
Model codes such as the IBC, IRC, IECC, NEC, IPC, and NFPA 13 influence schedule durations by imposing inspection hold points, testing requirements, and material standards. For example, the IBC requires special inspections for structural steel and concrete, which must be scheduled as milestones. The NEC mandates electrical inspections before energization. The IPC requires pressure testing of plumbing systems. Each of these adds activities and lags to the schedule. The adopted edition varies by jurisdiction, so confirm with the local building department which edition applies to your project.
Industry standards
Industry standards from ACI, ASTM, SMACNA, GA, and NRCA provide the technical basis for durations. ACI 301 and 347 define concrete cure times and form-stripping criteria, which become lags in the schedule. ASTM standards for soil compaction and concrete testing dictate inspection and testing frequencies. SMACNA guidelines for duct installation affect HVAC rough-in durations. GA-216 for drywall installation sets sequencing and cure times between coats. NRCA recommendations for roofing affect weather allowances and sequencing. These standards are referenced in specifications and must be reflected in activity durations.
Specification sections
CSI MasterFormat sections that an estimator must read for scheduling include 01 32 16 (Construction Schedule), 01 32 16.13 (Network Analysis Schedules), 01 29 00 (Payment Procedures), and 01 33 00 (Submittal Procedures). Section 01 32 16 defines the required schedule format, update frequency, and reporting. Section 01 29 00 ties the schedule to the schedule of values for pay applications. Section 01 33 00 sets submittal review times, which become lags. Also review division-specific sections for testing and commissioning requirements, such as 23 05 93 (Testing, Adjusting, and Balancing) and 26 08 00 (Commissioning).
Local amendments
Local amendments to model codes can change inspection requirements, permit processing times, and even work hours. For instance, some cities require additional inspections for fire sprinkler systems or seismic bracing. Others have noise ordinances that restrict night work, affecting shift scheduling. Utility company coordination and meter set lead times are also locally determined. Because adopted editions and amendments vary by jurisdiction, you must confirm with the local building department and utility providers the specific requirements that affect your schedule.
Who uses our outsourced scheduling services
General contractors
You need a contract-compliant schedule for the owner and for pay applications. Our .mpp file ties activities to cost codes and supports monthly updates with actuals and remaining durations.
Owners and developers
You want to see the critical path and float before you approve the baseline. Our narrative report explains what drives the schedule and where the risks are, so you can make informed decisions.
Construction managers
You coordinate multiple primes and need a master schedule that shows interface points. We build logic ties between trades and flag near-critical paths that could delay turnover.
Subcontractors
You need to know when your crew is needed and how much float you have. We provide activity lists with start/finish dates and predecessors, so you can plan your own resources.