Construction Project Activities: Work Breakdown, Network Scheduling, and Activity-Based Costing

The word activity shows up in two very different conversations on a construction site. In one, it describes marketing buzz, a tool brand releasing its first new product in years, posting on social media, and suddenly generating activity again. In the other, it is a technical term at the heart of project management. For schedulers, an activity is a defined unit of work with a start, a finish, a duration, and resource requirements, and the way you define, sequence, and cost these activities determines whether a project finishes on time and on budget. Even routine upkeep, like keeping a top handle jigsaw sharp and ready, is an activity that deserves a slot in the plan. This article covers work breakdown structures, network scheduling, dummy activities, and activity-based costing, the tools that turn a pile of tasks into a manageable schedule.

Experienced superintendents break every project into activities almost instinctively, but writing the breakdown down is what makes it useful. A schedule is only as reliable as the activities that feed it, and a costing system is only as accurate as the activities it tracks.

Defining Activities and Building a Work Breakdown Structure

A work breakdown structure, or WBS, organizes a project into progressively smaller pieces: project, phases, work packages, and finally activities. The WBS is deliverable-oriented, meaning each level describes a result rather than a process. Foundation work, for example, breaks into excavation, formwork, rebar placement, and concrete placement, each an activity with its own crew, duration, and cost code.

Activity characteristics

• Measurable: you can tell when it is done.
• Bounded: it has a clear start and finish.
• Resource-defined: it consumes labor, equipment, or material.
• Independent: its status can be tracked without confusing it with other work.
• Duration-estimable: you can assign a realistic time to complete it.

The 8/80 rule in practice

Most schedulers aim for activities between 8 and 80 working hours. Shorter activities create overhead from excessive tracking; longer ones hide progress problems. A three-week concrete pour sequence breaks into daily or two-day pours, each an activity, so delays surface immediately rather than at the end of the month.

Equipment constraints belong in the breakdown. Crews running modern cordless tools powered by lithium-ion battery technology must schedule charging time and spare batteries as part of the activity plan, and crews running compressed air must account for compressor placement. Any resource that can bottleneck work deserves its own line in the plan.

1. Start with the project scope and the final deliverable.
2. Decompose into phases such as site work, structure, enclosure, and finishes.
3. Break each phase into work packages owned by a trade or crew.
4. Split work packages into activities of 8 to 80 hours.
5. Assign each activity an identifier, a description, and a responsible party.
6. Review the breakdown with the field team before locking the schedule.

Sequencing Activities and Estimating Durations

Once activities are defined, they must be ordered. Sequencing records which activities must finish before others start, which can overlap, and which are independent. The four classic dependency types are finish-to-start, start-to-start, finish-to-finish, and start-to-finish. Finish-to-start dominates construction: excavation precedes footings, and footings precede walls.

Four dependency types

• Finish-to-start: B cannot start until A finishes. Example: rebar before concrete.
• Start-to-start: B cannot start until A starts. Example: formwork and rebar placement overlapping on a long wall.
• Finish-to-finish: B cannot finish until A finishes. Example: painting and trim inspection.
• Start-to-finish: rare, but used where B must not finish until A starts.

Duration estimates come from productivity rates, crew size, and conditions. Published rates provide a starting point: a four-person framing crew erects roughly 1,000 to 1,500 square feet of wall per day, a concrete crew places 30 to 40 cubic yards per day with a pump, and a drywall crew hangs about 1,200 square feet per day. Equipment changes the math too, so a framing crew with a capable circular saw and sharp blades cuts faster than one fighting dull steel.

Adjusting for reality

Apply factors for weather, site access, crew experience, and inspection delays. A 20 percent weather factor is common in scheduling software, and rework typically consumes 5 to 10 percent of direct labor hours. The goal is a duration you can defend, not an optimistic number that looks good in a bid.

Dummy Activities in Network Analysis

Network diagrams, also called arrow diagrams or activity-on-arrow networks, represent activities as arrows between events, drawn as numbered circles. The rules of the diagram create a problem: two activities cannot share the same start and finish events, and every arrow must represent real work with a real duration. When the logic demands connections that do not correspond to actual work, schedulers insert a dummy activity.

A dummy activity is a dashed arrow with zero duration and zero resource consumption. It exists purely to preserve correct logic in the network. The classic case involves four activities: A and B both start at event 1, C depends on both A and B, and D depends only on B. Drawing C as dependent on both A and B is easy, but expressing that D depends only on B, while keeping A and B from sharing identical start and finish events, requires a dummy. Our primer on dummy activity in network analysis works through this example in detail.

Two cases that require a dummy

• Identity case: two or more activities share the same start and finish events, so the diagram cannot tell them apart. A dummy separates them so each keeps a unique identity.
• Logic case: one activity depends on a subset of the predecessors of another. A dummy carries the partial dependency without inventing false work.

What a dummy is not

A dummy is not a lag time, not a weather delay, and not a milestone. It adds zero days to the critical path. Its only job is to keep the network mathematically correct so that forward and backward pass calculations, float values, and the critical path stay valid.

Drawing Network Diagrams Without Errors

Building a correct network takes a disciplined sequence, and the common errors are easy to list. Worked examples in network analysis show where beginners go wrong.

1. List all activities with their immediate predecessors.
2. Draw an event node for the start and one for the finish.
3. Add arrows for activities that have no predecessors.
4. Add each remaining activity once its predecessors are in place.
5. Insert dummy arrows wherever two activities would share identical start and finish events.
6. Add durations to each real activity arrow.
7. Run the forward pass to compute early start and early finish times.
8. Run the backward pass to compute late times, float, and the critical path.

Common errors and how to spot them

• Loops: arrows that circle back and create an impossible cycle. The network must flow forward only.
• Dangling activities: an activity with no successor other than the project finish, which breaks float calculations.
• Redundant dummies: extra dashed arrows that add nothing and confuse the diagram.
• False dependencies: a dummy that forces a constraint that does not really exist, lengthening the schedule artificially.

Checking your work

Count the events and arrows before calculating. For a valid arrow diagram, the number of arrows equals the number of activities plus the number of dummies. If it does not, some dependency is missing or duplicated.

Activity-Based Costing for Construction Firms

Activity thinking extends beyond scheduling into cost control. Traditional job costing spreads indirect costs, such as supervision, equipment mobilization, and office overhead, across projects as a percentage of direct labor. That approach distorts reality because not every project consumes the same share of support activities. Activity-based costing, ABC for short, assigns costs to the activities that drive them, then charges each project for the activities it actually uses.

Consider a firm with $200,000 of annual indirect costs. Traditional costing might spread that evenly as 12 percent of labor across all projects. ABC instead identifies cost pools: equipment moves at $150 per move, material receiving at $2 per order line, supervision at $45 per hour of field support, and rework at actual cost. A small renovation that triggers ten equipment moves and twenty material orders gets charged accordingly, while a large new build with two moves and bulk deliveries pays far less per dollar of labor.

Common cost drivers in construction

• Equipment mobilization: number of moves and distance.
• Material handling: number of deliveries and order lines.
• Supervision: field hours logged per project.
• Quality control: inspections and rework events.
• Safety management: toolbox talks and audits.

Getting started with ABC

Start small. Pick the five indirect costs that vary most between your project types, define a driver for each, and track drivers for one quarter. Compare the ABC result with your traditional allocation and look for projects that were subsidizing others. A printable summary of understanding activity-based costing is useful for walking the field team through the change.

Putting Activity Thinking to Work

The payoff comes when scheduling and costing use the same activity definitions. A WBS built with measurable activities feeds directly into the network diagram, the network gives durations and float, and ABC assigns cost to the same activities. That alignment turns the schedule into a cost model and the cost model into a schedule.

Start with the basics. If your team has never used these tools, review what activity-based costing is before building the cost pools, and practice network logic on a small project before applying it to a critical one.

• Decompose the first two weeks of work into activities of 8 to 80 hours.
• Draw the network by hand before opening scheduling software.
• Add dummies only where logic demands them, and label them clearly.
• Track two indirect cost drivers for one quarter and compare with your old allocation.
• Review the schedule with the field crew before locking it.

Defining activities precisely, sequencing them honestly, and costing them accurately is the difference between a project that is managed and one that merely happens. A tool brand that returns to the market after years of silence proves that activity, in the marketing sense, can restart quickly. On a jobsite, activity in the scheduling sense is slower to build but far more valuable once it is in place.