Heavy civil project management

Why spreadsheets fail heavy civil projects

Spreadsheets can store an RFI number. They cannot show you where that RFI sits on a two-mile corridor, which crew it affects, or what other open items are at the same station. That gap is where heavy civil projects break down.

Six reasons heavy civil teams outgrow Excel

• Rows have no geography — Cell B47 does not tell you whether this RFI affects the crew at Station 42 or Station 78. The field crew has to read every row and mentally map it themselves.
• RFIs belong to a location, not a cell — An RFI at a specific culvert crossing needs to be visible to anyone who approaches that crossing. A spreadsheet row is invisible until someone filters for it and reads it.
• Lane closures are geometry, not numbers — A daily lane closure on a two-mile roadway project has a start station, an end station, and a direction. A spreadsheet cannot render that as a polyline over a satellite map.
• Version control chaos on multi-crew projects — Three foremen, one PM, and two subs all editing the same workbook produces stale filters, conflicting edits, and a log that nobody fully trusts.
• Field crews will not use it on a phone — A 40-column RFI log formatted for a desktop monitor is unusable on a phone screen in direct sunlight. Field adoption collapses and the log stops getting updated.
• No connection between related items — The RFI that triggered the directive that created the change order lives in three separate rows across two tabs. The connection between them exists only in someone's memory.

What works instead

Map-based project tracking pins every item to the GPS location where it occurred. The field crew at any station opens the map and sees what is open right where they are standing. The PM sees density of open items across the whole corridor at a glance. The connection between related items is visible because they share a location.