BCN4720C: Scheduling

Course Description

BCN4720C Scheduling is the construction management course on planning time — how a project's work is broken down, sequenced, resourced and tracked, and what to do when it falls behind.

The course is offered at approximately five Florida institutions, including Florida Gulf Coast University, the University of Florida, the University of North Florida and the University of West Florida.

The University of West Florida places it in the College of Science and Engineering, Department of Civil Engineering and Construction Management at 3 semester hours, requires BCN 2251C, and describes a course providing fundamental concepts of scheduling techniques, applications and software packages in which students will be provided hands-on experience with appropriate software.

The `C` suffix is meaningful here — it designates integrated lecture and laboratory, and in this course the laboratory is software. You will build real schedules in a real scheduling package, which is the reason the course carries the suffix and the reason it takes more contact time than a lecture.

Scheduling is the discipline that distinguishes construction management from construction. A project consists of hundreds or thousands of activities performed by dozens of trades, many of which physically cannot start until others finish, all competing for the same crews, equipment and space. The schedule is the model of how that fits together, and it is simultaneously a planning tool, a communication document, a resource allocation mechanism, a control instrument and — increasingly — a legal record.

The technical core is the Critical Path Method, which is genuinely elegant. Given a set of activities, their durations and their dependencies, CPM computes the earliest and latest each can start and finish, identifies the float available to each, and finds the critical path — the chain of activities on which any delay delays the whole project. That is a small piece of graph theory with enormous practical consequence: it tells a manager exactly where attention matters and where it does not.

The professional reality that the course must convey alongside the technique is that a schedule is a prediction, and predictions are wrong. Weather, permitting, supply, labour availability, design changes and owner decisions all intervene. The skill is not producing a schedule that turns out to be correct — it is producing one that is realistic enough to plan against, and then updating it honestly as conditions change. A schedule nobody updates is worse than none, because it produces confident wrong decisions.

And there is a dimension students do not anticipate: the schedule is evidence. Construction disputes over delay are common and expensive, and the schedule and its updates are the primary documentary record in a delay claim. That gives schedule quality, update discipline and documentation a legal significance well beyond project management, and it is a substantial part of why this course exists as a separate requirement.

Learning Outcomes

Required Outcomes

• Explain the purposes of a construction schedule and the differing needs of owner, contractor, subcontractors and designers.
• Develop a work breakdown structure and define activities at an appropriate level of detail.
• Estimate activity durations from quantities, crew sizes and productivity rates.
• Establish logical relationships — finish-to-start, start-to-start, finish-to-finish, start-to-finish — with lags, and justify each.
• Construct a network diagram in precedence diagramming notation.
• Perform forward and backward pass calculations by hand and interpret the results.
• Calculate total float, free float and identify the critical path.
• Explain float ownership and its contractual significance.
• Produce and interpret a Gantt (bar) chart and explain its relationship to the underlying network.
• Apply resource loading, levelling and smoothing, and explain the effect on the schedule.
• Apply schedule compression — crashing and fast-tracking — and analyse the cost and risk of each.
• Perform a time-cost trade-off analysis.
• Update a schedule with actual progress and forecast completion.
• Analyse variance between planned and actual performance and recommend corrective action.
• Explain delay analysis methods and the distinction between excusable, non-excusable, compensable and concurrent delay.
• Use scheduling software competently to build, resource, update and report a schedule.
• Communicate a schedule appropriately to technical and non-technical audiences.

Optional Outcomes

• Apply earned value analysis integrating cost and schedule.
• Apply probabilistic scheduling — PERT and Monte Carlo simulation.
• Apply linear scheduling or line-of-balance methods to repetitive work.
• Apply Last Planner and lean construction planning.
• Integrate scheduling with BIM for 4D sequencing.
• Prepare or evaluate a delay claim.
• Apply critical chain methods.
• Analyse schedule risk and contingency.
• Prepare a short-interval or look-ahead schedule for field use.

Major Topics

Required Topics

• Planning before scheduling. The distinction — planning decides what will be done and how; scheduling decides when — and the frequent error of scheduling an unplanned project; project delivery methods and their scheduling implications; the work breakdown structure; activity definition and the level-of-detail judgement, which is the first real skill: too coarse and the schedule cannot be managed, too fine and it cannot be maintained; the audiences a schedule serves and why one document rarely serves all of them well.
• Durations. Estimating from quantity, crew composition and productivity rate, which ties the schedule to the estimate and is the only defensible basis; production rate data and its sources; calendars — work weeks, holidays, and weather days, which in Florida are a substantial and quantifiable allowance; the difference between duration and effort; the systematic optimism in duration estimates and how experienced schedulers correct for it; contingency and where it should sit.
• Logic and network construction. Precedence diagramming and its four relationship types with lags and leads; the discipline of distinguishing hard logic from soft logic — physical necessity (you cannot roof before framing) versus preference (this crew does A before B) — because only hard logic is defensible in a dispute and soft logic is where compression opportunities live; open ends, redundant logic and out-of-sequence progress; constraints and the damage done by hard-coded dates, which override the network's own logic and are the most common way a schedule is silently broken; milestones; activity-on-arrow notation in historical outline.
• CPM calculation — done by hand before the software touches it. The forward pass giving early start and early finish; the backward pass giving late start and late finish; total float as the difference and free float as the delay available without affecting a successor; the critical path as the zero-float chain; multiple critical paths and near-critical paths, which are where projects actually get into trouble; negative float and what it means; the reason hand calculation is required: software produces the answer without showing the reasoning, and a manager who cannot reproduce it cannot tell when the software has been told something wrong.
• ⚠ Float ownership — a contractual question, not a technical one. Who owns float: the owner, the contractor, or the project? The answer determines who may consume it and who is entitled to compensation when it is exhausted, and it is settled by the contract rather than by the schedule. Float suppression and the practice of building in hidden contingency; the difference between float and contingency; why this appears in a scheduling course: it is the point at which a technical quantity acquires money value.
• Presentation. The Gantt chart and its relationship to the network — a bar chart without logic behind it is a picture rather than a schedule, and the distinction matters; time-scaled logic diagrams; milestone and summary schedules for owners and executives; look-ahead and short-interval schedules, typically three to six weeks, which are what the field actually uses; tailoring the presentation to the audience without changing the underlying model.
• Resources. Resource loading the schedule; the resource histogram and the problem of peaks; levelling (extending duration to fit resource limits) versus smoothing (redistributing within available float); crew continuity and why moving a crew on and off site is expensive; equipment and material constraints; long-lead procurement, which is a scheduling activity and is frequently the actual critical path on modern projects; cash flow derived from the resource-loaded schedule; the point that resource levelling can create a new critical path, which surprises students.
• Compression. Crashing — adding resources to shorten an activity — and its cost slope; fast-tracking — overlapping activities that would normally be sequential — and the rework risk it introduces; the time-cost trade-off analysis and finding the least-cost compression; diminishing returns and the point beyond which adding labour slows the work — congestion, supervision limits and trade stacking; the reality that acceleration is frequently directed rather than chosen, and that constructive acceleration is a claim category.
• Updating and control — the half of the course students underrate. The baseline schedule and its approval; progress measurement and percent complete, including the notorious unreliability of self-reported percent complete; the data date and the mechanics of an update; out-of-sequence progress and retained versus progress override logic, which changes the answer and must be understood; schedule updates as a contractual obligation with a required frequency; variance analysis; forecasting completion; recovery schedules; the professional and ethical point that an update must reflect what actually happened, because an update adjusted to look acceptable destroys the document's value as a control tool and as evidence.
• Delay and its analysis. Delay categories — excusable and compensable, excusable and non-compensable, non-excusable — and what each entitles a party to; concurrent delay, which is the hardest and most litigated concept in the field; analysis methods — as-planned versus as-built, impacted as-planned, collapsed as-built, and time impact analysis, which is the method most often specified; the requirement for contemporaneous records, since a delay claim is won or lost on documentation created at the time rather than reconstructed afterwards; notice requirements under the contract, which are strict and are the most common reason a valid claim fails; liquidated damages.
• Software — the laboratory half. Primavera P6, the standard on large and public projects, and Microsoft Project, dominant on smaller ones; building a schedule, coding and organising activities, resource assignment, baselining, updating and reporting; the essential caution that software computes exactly what it is told and will produce a confident, well-formatted, wrong answer from bad logic; schedule quality checking and the DCMA 14-point assessment as a review framework; exchange formats and interoperability; the reason the hand calculations come first.

Optional Topics

• Earned value management — integrating cost and schedule, CPI and SPI.
• Probabilistic scheduling — PERT, Monte Carlo simulation and schedule risk analysis.
• Linear scheduling and line of balance for highways, high-rise and other repetitive work.
• Lean construction and the Last Planner System — pull planning, percent plan complete, constraint removal.
• 4D BIM — linking the model to the schedule for visual sequencing and clash-in-time detection.
• Critical chain project management and buffer management.
• Preparing and defending a delay claim; forensic scheduling.
• Programme and portfolio scheduling across multiple projects.
• Scheduling for specific sectors — infrastructure, industrial, renovation.

Resources & Tools

• Construction Project Scheduling and Control by Saleh Mubarak — the most widely adopted text for this course, practical, well paced, and strong on both the calculations and the software.
• CPM in Construction Management by James O'Brien and Fredric Plotnick — the comprehensive professional reference, and the standard citation on delay analysis.
• Construction Scheduling: Principles and Practices by Jay Newitt; Project Management for Construction by Chris Hendrickson, which is free online and covers scheduling within a full project management treatment.
• Software, and access matters more than the book:
  • Oracle Primavera P6 — the standard on large, public and infrastructure projects. Expensive commercially; check whether your department provides access or a student licence, since many do.
  • Microsoft Project — dominant on smaller projects; frequently available free to students through institutional Microsoft agreements.
  • Free alternatives worth knowing: ProjectLibre and GanttProject are open source and adequate for learning CPM mechanics; Asta, Deltek Acumen and Smartsheet appear in industry.
  • ⚠ Learn the concepts, not the menus. Employers use different packages and the underlying method is identical; a graduate who understands CPM adapts to a new tool in days.
• Professional organisations and credentials — this field has genuinely useful ones:
  • AACE International — the Planning & Scheduling Professional (PSP) credential, and its Recommended Practices, several of which (notably RP 29R-03 on forensic schedule analysis) are the industry reference on delay analysis.
  • Project Management Institute — the PMI Scheduling Professional (PMI-SP) and the PMP; the PMBOK Guide and the Practice Standard for Scheduling.
  • AGC of America and its Florida chapters; the Construction Management Association of America (CCM credential); the Lean Construction Institute for Last Planner material.
  • The DCMA 14-point schedule assessment — a published, free checklist widely used to evaluate schedule quality, and worth applying to your own coursework schedules.
• Free and practical: Oracle's and Microsoft's own documentation and tutorials; AACE's published recommended practices; the schedule specification sections of real public bid documents, which are online for Florida agencies — reading what FDOT or a school district actually requires of a contractor's schedule is the fastest way to understand professional expectations.

Career Pathways

Scheduling is one of the few construction management skills that is a job title on its own, and it is consistently in demand.

• Construction Managers (SOC 11-9021) — the primary destination; scheduling is a core competence and superintendents and project managers use it daily.
• Project Schedulers / Planners — a distinct and well-paid role on large projects, classified variously under SOC 13-1082 (project management specialists) and 11-9021. Large infrastructure, industrial and institutional projects employ full-time schedulers, and demand consistently exceeds supply because the skill is specific and few graduates have it.
• Project Management Specialists (SOC 13-1082) — across construction and beyond.
• Cost Estimators (SOC 13-1051) — estimating and scheduling are closely coupled, and many practitioners do both.
• Project Controls specialists — the combined cost-and-schedule function, standard on large projects and a well-compensated career track.
• Owner's representatives and construction consultants — reviewing and approving contractor schedules on behalf of an owner.
• Forensic scheduling and claims consulting — analysing delay for litigation or arbitration. Specialised, highly paid, generally entered after field experience, and a real industry in Florida given the volume of construction and of hurricane-related work.
• Public agency project management — FDOT, water management districts, school districts, universities and municipalities all manage large capital programmes and require schedule review capability.
• Scheduling outside construction — the CPM method transfers directly to shipbuilding, aerospace, plant turnarounds, software and event delivery, and Florida's aerospace and defence sector employs planners using the same techniques.

The Florida picture. Sustained population growth drives continuous construction; major infrastructure programmes (FDOT, port and airport expansion, water and utility work) run multi-year schedules with formal requirements; hurricane recovery and resilience work is recurring; and the aerospace and defence sector on the Space Coast and in Orlando uses the same planning methods under different labels.

The concrete advice. Learn Primavera P6 if you can get access — it is the differentiator on large and public projects, it is explicitly named in job postings, and most graduates arrive knowing only Microsoft Project. Then pursue the AACE PSP credential once you have the required experience; it is recognised, it is specific, and it marks a graduate as a scheduler rather than as someone who has used scheduling software. And keep your coursework schedules — a resource-loaded, updated schedule with a variance analysis is a portfolio artefact that an interviewer can ask you about substantively.

Special Information

⚠ The `C` suffix means software time is built in — and that is the point

BCN4720C carries the `C` designation for integrated lecture and laboratory, and UWF's description confirms it: students will be provided hands-on experience with appropriate software. Expect roughly 60 contact hours rather than 45, with scheduled laboratory sessions.

This matters practically for three reasons. Software access is arranged through the course, which for Primavera P6 is a genuine benefit given its commercial cost. The laboratory sessions are where the software is actually learned, and they are difficult to make up. And the schedule you build in the laboratory is normally the term project, so falling behind in the laboratory means falling behind on the largest single assessment.

⚠ Find out which package your section uses before the term and whether you can install it on your own machine — doing the work only in a computer laboratory during scheduled hours is a real constraint on a project of this size.

Prerequisites and position in the curriculum

UWF requires BCN 2251C — construction drawings and graphics. That is the right gate: you cannot sequence work you cannot visualise, and building a realistic schedule requires reading a set of drawings and understanding what has to happen in what order to produce the building on them.

Beyond the stated prerequisite, the course assumes familiarity with construction methods and materials — knowing that the slab must cure, that underground utilities precede the slab, that drywall follows rough-in inspection — and this is the real difficulty for students who have not been on a site. A student without field exposure can compute a forward pass correctly and produce a schedule whose logic is nonsense, and instructors will say so.

BCN4720C is a senior-level construction management course, normally taken after estimating and construction methods, and it pairs with codes and standards, construction contracts, cost control and the capstone. Estimating first is the better order, because durations derive from quantities and crew productivity — the estimate is the schedule's input.

⚠ Do the hand calculations, and expect to be examined on them

Students reasonably ask why they should compute a forward and backward pass by hand when software does it instantly. The answer is specific rather than traditionalist.

Software computes exactly what it is told. Given wrong logic, a hard constraint that overrides the network, or an out-of-sequence update handled with the wrong setting, it produces a confident, professional-looking, wrong schedule. The critical path shifts, the completion date moves, and nothing signals an error. A manager who cannot reproduce the calculation cannot tell that it has happened — and on a real project, someone is making decisions worth millions on that output.

Practically: examinations in this course are typically hand calculations, because that is what can be assessed. Work them until they are automatic. They are not conceptually hard; the errors are bookkeeping errors, and they disappear with practice.

⚠ What separates a good schedule from a plausible one

Students consistently produce schedules that compute correctly and would not survive a professional review. The recurring problems:

• Hard-coded date constraints. Imposing "must start on" dates overrides the network's logic, hides the true critical path and makes the schedule unresponsive to change. Use constraints sparingly and justify each one.
• Open ends. Activities with no predecessor or no successor are not connected to the network and their float is meaningless. Every activity except the start and finish milestones should have both.
• Soft logic presented as hard logic. Sequences based on crew preference rather than physical necessity are where compression opportunities live, and in a dispute, unjustifiable logic is attacked first.
• Excessive lags substituting for missing activities. A thirty-day lag usually conceals work that should be an activity — most often procurement or a cure period.
• Durations invented rather than derived. A duration should trace to quantity, crew and productivity. Round numbers throughout are a signal that none of them do.
• Missing procurement and submittals. Long-lead items — switchgear, chillers, structural steel, elevators — are frequently the actual critical path, and student schedules routinely omit them entirely.
• No weather allowance. In Florida this is not optional; rain days and hurricane season are quantifiable and expected in the schedule.
• Too much or too little detail. A schedule with three thousand activities cannot be updated weekly; one with forty cannot be managed.

⚠ The schedule as a legal document

Worth stating separately because students do not anticipate it and because it explains several of the course's apparent obsessions.

Construction delay disputes are common, and the schedule is the evidence. The baseline establishes what was planned; the updates establish what happened and when; the contemporaneous records establish why. A delay claim is largely a schedule argument, and it is won or lost on documentation created at the time.

Three practical implications. Update discipline matters — updates on the contractually required cycle, reflecting actual progress, are the record; a gap in updates is a gap in the evidence. Notice requirements are strict, and a valid delay claim is most often lost because notice was not given within the contractual period rather than on the merits. And the honesty obligation is professional rather than merely ethical: an update massaged to look acceptable is a false record, and in a dispute it will be compared against daily reports, photographs and inspection records.

Course format and workload

Taught as a lecture with an integrated software laboratory, built around a term project: develop a complete schedule for a real or realistic project — work breakdown, durations, logic, CPM, resource loading, and typically several update cycles with variance analysis.

Expect six to ten hours a week outside class. The calculations are learnable quickly; the project is the workload and it is cumulative — the update cycles depend on a baseline built earlier, so a poor baseline is paid for repeatedly.

Two practical warnings. Build the baseline carefully even though it is early and the deadline seems distant; every subsequent assignment sits on it. And save versions — you will need the original baseline to compare against, and overwriting it is a common and painful error.

Articulation and transfer

BCN4720C carries the same SCNS number across Florida public institutions and SCNS equivalency governs transfer of the credit. As an upper-division course it does not appear in A.A. programmes.

Two notes. Prerequisite chains differ and a transfer student may need the drawings or methods course first. And where the programme is ACCE-accredited, the receiving department checks coverage against its curriculum requirements — keep the syllabus and keep the project schedule file, which demonstrates the competency directly and is also the portfolio piece.

AI Integration

Construction scheduling has used computation since CPM was developed in the 1950s, so automation here is not novel — what is new is the kind.

Where the tools help. Generating a first-draft activity list for a project type, as a checklist to review and correct rather than a schedule to use. Explaining CPM concepts and checking a hand calculation you have already done. Writing software queries, filters and reports, and scripting repetitive schedule maintenance. Drafting narratives — schedule basis documents, monthly update narratives, variance explanations — from your own findings, which is real and tedious work. And summarising long specification sections to extract the schedule requirements, subject to verification.

⚠ Where they fail, and the failures are specific to this domain.

Logic requires knowing how buildings get built. A generated sequence will look plausible and contain errors that anyone who has been on a site would catch — work sequenced before the inspection that must precede it, trades stacked in a space that cannot hold them, a cure period omitted, a long-lead item ignored. Construction logic is physical knowledge, and it is the part of this course that cannot be shortcut.

Durations depend on the specific project. Crew size, site access, weather window, local productivity and the particular contractor all determine how long an activity takes. Generic durations produce a schedule that is defensible nowhere.

The output is confident and unverifiable at a glance. This is the same hazard the course already warns about with scheduling software, in a stronger form: a well-formatted schedule carries an authority its contents may not deserve, and the only defence is a person who can check the logic.

Delay analysis is a contractual and evidentiary exercise. Determining excusability, compensability and concurrency requires the contract, the correspondence, the daily reports and the notice record. It is performed by people who are accountable for the conclusion, and it is tested in arbitration.

What is genuinely changing, and it is substantial. Machine learning on historical project data is being used for duration estimation and schedule risk prediction, and the results are promising where an organisation has enough of its own consistent data. 4D BIM links the model to the schedule and makes sequencing visually checkable. Reality capture — drone photogrammetry and laser scanning — is increasingly used to measure actual progress automatically, which addresses the long-standing unreliability of self-reported percent complete and is arguably the most consequential change in schedule control in decades. Automated schedule quality checking against the DCMA metrics is routine.

And the durable point. These systems improve measurement and detection. They do not decide how to recover a slipping project, negotiate a resequence with a subcontractor who has other jobs, judge whether a delay was excusable, or accept responsibility for a completion date given to an owner. Scheduling is a communication and negotiation discipline wearing a technical costume — the network is the easy part — and that is worth understanding early, because it is what the job actually consists of.

Academic integrity. Read your instructor's policy. The point specific to this course: the hand calculations are examined because they are what proves you can tell when the software is wrong, and the project builds the logic judgement that no tool supplies. A student who generates a schedule has produced a document they cannot defend in the review that follows — which is precisely the position a scheduler is in every month on a real project.