Construction Project Management in Google Sheets: The Document System That Survived a 14-Month Commercial Build

A practical construction project management system in Google Sheets — track daily logs, RFIs, submittals, change orders, and site photos without paying for software you'll fight with.

Last March, our GC pulled me into the job trailer on our mixed-use build in Raleigh and said, 'The owner's rep just asked for every RFI response and daily log from the last four months. We need it by Friday.' I watched the color drain from our project engineer's face. The RFIs were split between Procore (which the owner was paying for but nobody on our side was updating consistently), a shared Google Drive folder with 400+ unsorted PDFs, and — I'm not making this up — a manila folder in the PE's truck. That Friday cost us two people's entire week.

That's the moment I stopped treating our Google Sheets tracker as a nice-to-have side project and started building it into the actual document backbone of how we run jobs. Not because spreadsheets are glamorous. Because every $150/seat/month construction project management software we'd tried either got half-adopted and abandoned, or required a full-time admin we didn't have. What we needed was something our super, our PE, and our office manager would actually use. Twelve months and three completed projects later, I'm going to walk you through exactly what we built.

Why Most Construction Management Software Gets Abandoned by Month Three

I've used Procore, Buildertrend, CoConstruct, and PlanGrid across different jobs over the past eight years. They're not bad tools. Some of them are genuinely impressive. But here's what I've watched happen on every mid-size commercial crew I've worked with: the PM sets it up, trains people during a slow week, and then the first time a super is running behind on a concrete pour and needs to log something fast, they text a photo to the PM instead. Within six weeks the data in the system is incomplete, and incomplete data is worse than no data because people think they can trust it.

The problem isn't the software. It's the adoption gap. On a $3–8M commercial job, you've got a superintendent who's been in the field for 25 years and types with two thumbs, a project engineer fresh out of a CM program who lives in apps, and an office manager who runs AP/AR in QuickBooks and doesn't want another login. Construction project management software works great when you have a dedicated project controls team. Most of us don't. We need the 80% solution that 100% of the team will actually touch.

That's Google Sheets. Not because it's better than Procore — it's not. Because it's already open on everyone's browser, it doesn't require a login that expires every 30 days, and your office manager already knows how to filter a column.

The Tab Structure That Actually Works on a Live Jobsite

After iterating through three projects, here's the tab structure we settled on. I'm going to explain why each tab exists and what columns matter. The key principle: every tab is a log, not a report. Logs are easy to add rows to. Reports are something you generate FROM the log.

• **Dashboard** — summary tab with COUNTIF/SUMIF formulas pulling from every other tab. Shows open RFIs, pending submittals, week's daily logs, budget burn rate. This is what I open in the Monday morning OAC meeting.
• **Daily Log** — one row per day. Columns: Date, Weather, Crew Count, Subcontractors On-Site, Work Performed, Issues/Delays, Safety Notes, Site Photos (attached). Our super fills in one row at the end of every day. Takes 4 minutes.
• **RFI Log** — one row per RFI. Columns: RFI #, Date Submitted, Subject, Spec Section, Submitted To, Response Date, Status (Open/Pending/Closed), Response PDF (attached).
• **Submittal Log** — same structure. Tracks spec section, sub responsible, date sent, date returned, status, and the actual submittal PDFs.
• **Change Orders** — CO #, Description, Initiated By, Date, Amount, Status (Pending/Approved/Rejected), Signed CO PDF.
• **Budget Tracker** — CSI division breakdown with Original Contract, Approved COs, Revised Budget, Committed Costs, Actual Costs, Variance. Feeds the dashboard.
• **Punch List** — added during closeout. Location, Item, Responsible Sub, Date Identified, Date Completed, Photo Before, Photo After.
• **Contacts** — every sub, supplier, inspector, and owner rep with phone, email, and role. Boring but saves five minutes every time someone asks 'who's the mechanical inspector again?'

The File Problem: Where Every Construction Spreadsheet Falls Apart

Here's the thing nobody tells you when they say 'just use Google Sheets for project management': spreadsheets don't natively handle files. And construction runs on files. Every RFI has a response letter. Every submittal has a PDF package. Every daily log should have site photos. Every change order has a signed document. Without those attachments living IN the row — not in some parallel folder structure you have to cross-reference — your tracker is a fancy index that still requires you to go digging.

This is the problem that almost killed our system on the first project. We tried hyperlinking to Google Drive files. Within a month we had broken links, files that had been moved, and a Drive folder with 600 items in the root because nobody followed the folder structure. Our PE was spending an hour a day just filing documents into the right subfolder.

FileFox is what closed that gap for us. It lets you drag a file — a PDF, a photo, whatever — directly into a cell in Google Sheets. The file lives right there in the row, attached to that specific RFI or daily log entry. When the owner's rep asks for RFI #47's response, I don't search Drive. I open the RFI tab, go to row 47, and the PDF is sitting in the cell. That's the moment our sheet went from 'nice reference document' to 'actual project document control system.'

I know that sounds like a sales pitch, but I'm telling you — the file attachment piece is the difference between a spreadsheet your team uses and a spreadsheet your team abandons. If you don't use FileFox, you need SOME solution for this. Hyperlinks to a rigorously maintained Drive folder can work, but you need a team that will actually maintain it. We didn't have that team.

Project Management in the Construction Industry Doesn't Need to Be Complicated — It Needs to Be Consistent

The single biggest lesson from running this system across three projects: the tool doesn't matter as much as the habit. We have a daily standup at 6:45 AM on site. At the end of it, I remind the super: 'Log's open, drop your photos in before you leave today.' That's it. No training session, no workflow diagram, no onboarding document. One sentence, every day.

For the PE, the habit is different: every incoming RFI response gets logged within 24 hours. Not next week, not when things slow down. The rule is simple — if it's not in the sheet, it didn't happen. When the architect claims they never responded to RFI #23 and you can pull up the row with the PDF, the timestamp, and the spec section in 10 seconds, that's not just organization. That's CYA that protects your contract.

Here are the specific habits that keep our system alive:

• Daily log entry by 4 PM every working day. Non-negotiable.
• RFI/submittal log updated within 24 hours of any status change.
• Change orders logged the day they're issued — even before approval. Status column tracks where it stands.
• Budget tab reconciled weekly against QuickBooks committed costs. Our office manager owns this one.
• Punch list starts the day the first inspector walks through, not at substantial completion.

Formulas That Do the Thinking For You

You don't need to be a spreadsheet wizard. But a few formulas on the Dashboard tab turn your logs into actual intelligence. Here's what we run:

**Open RFI count** — tells you at a glance how many responses you're still waiting on:

**Average RFI response time** — this number matters in OAC meetings when the architect is dragging. It's hard to argue with data:

(Where column F is Response Date and column C is Date Submitted. Adjust to match your layout.)

**Budget variance by CSI division** — simple but critical. In the Budget tab, the Variance column is just:

(Revised Budget minus Actual Costs. Conditional formatting turns this red when it goes negative. When Division 07 — Thermal & Moisture Protection — goes red on a roofing-heavy job, you know it immediately instead of finding out at the monthly draw.)

**Days since last daily log** — a gentle accountability check sitting right on the dashboard:

If this number is greater than 1, someone missed a log. It's a small thing, but it keeps the habit alive.

Scaling This Across Multiple Jobs

When we had one job, this was a single spreadsheet. Now we're running three concurrent projects, and the structure is: one master spreadsheet per job, identical tab structure, plus one 'Portfolio Dashboard' spreadsheet that uses IMPORTRANGE to pull summary data from all active jobs. The Portfolio Dashboard shows me, across all projects: total open RFIs, budget health per job, and which daily logs are current.

The IMPORTRANGE setup looks like this for pulling open RFI counts from a specific job:

It takes about 20 minutes to set up a new job from our template. Copy the master sheet, update the project info on the Dashboard tab, share it with the job's team, and you're running. No onboarding call with a software company. No waiting for licenses. No 'we're still getting the account set up.' You're tracking on day one.

What This System Won't Do (And When You Actually Need Software)

I want to be honest about the limits, because pretending a spreadsheet replaces everything is how you end up with a different kind of mess. Here's where Google Sheets falls short for construction project management:

• **Scheduling**: Don't try to build a CPM schedule in Sheets. Use Microsoft Project, Primavera P6, or even a simple Gantt tool. Sheets can track milestones and deadlines, but critical path logic doesn't belong here.
• **BIM coordination**: Obviously not a spreadsheet problem.
• **Multi-party collaboration with external subs**: If you need 15 subcontractors logging into the same system, you probably do need Procore or similar. Our system works because it's our internal team (3-5 people) using it, with subs submitting docs to us via email that we log.
• **Document version control**: Sheets tracks THAT a document was submitted, but it doesn't track version history of the document itself. For specs and drawings, you still need a plan room or Bluebeam-type workflow.
• **Large-scale enterprise projects**: If you're running a $50M+ job with a full project controls department, you need enterprise software. This system is for the $1M-$15M range where you're wearing three hats and don't have dedicated admin staff.

For everything else — document tracking, daily logs, RFI management, budget monitoring, punch lists, and the general 'where the hell is that file' problem — Sheets handles it. The total cost of our system is $0 for Google Sheets and a FileFox subscription for the file attachments. Compared to the $3,600/year per seat we were paying for construction management software that was half-empty, I'll take it.

Start With the Daily Log. Seriously, Just That.

If you've read this far and you're thinking 'that's a lot of tabs,' here's my advice: don't build all of it on day one. Start with the Daily Log tab. Just that one tab. Get your super logging every day for two weeks. Once that habit is locked in, add the RFI Log. Then the submittal log. Then the budget tracker. Layer it on as the habits form.

The worst thing you can do is build a beautiful 8-tab system, show it to your team on a Monday, and have nobody use it by Wednesday. Construction is a habits business. Build the habit first, then build the system around it. The daily log is where the habit starts — it's the easiest entry, the most frequent touchpoint, and the one that pays for itself the first time a dispute comes up about what happened on site three months ago.

Open a sheet. Make eight columns. Start logging tomorrow morning. Everything else can wait.

Frequently Asked Questions

What is the best construction project management software for small contractors?

For small contractors (under $15M/year in revenue), Google Sheets with a solid template and file attachment add-on like FileFox handles 80% of what you need — daily logs, RFI tracking, budget monitoring, and document management. If you need scheduling, add a lightweight Gantt tool. Full platforms like Procore and Buildertrend are powerful but often get abandoned on small teams because nobody has time to maintain them.

How do I track RFIs and submittals in Google Sheets?

Create a dedicated tab for each with columns for: sequential number, date submitted, subject, spec section, responsible party, response date, status (Open/Pending/Closed), and an attachment column for the response PDF. Use data validation dropdowns for the Status column and conditional formatting to highlight open items in red. A COUNTIF formula on a dashboard tab gives you the total open count at a glance.

Can Google Sheets replace Procore for construction project management?

Not entirely. Procore excels at multi-party collaboration, drawing management, and workflow automation that Sheets can't match. But for teams of 3-5 where adoption is the real problem, Google Sheets with file attachments covers daily logs, RFI tracking, budget monitoring, submittals, and punch lists effectively. Many small-to-mid GCs use Sheets as their primary tracker and only add Procore when project size or owner requirements demand it.

How do I attach site photos and documents to a Google Sheets construction log?

Natively, Google Sheets doesn't support file attachments in cells. You can hyperlink to files in Google Drive, but links break when files get moved. A tool like FileFox lets you drag and drop files — photos, PDFs, signed contracts — directly into cells so they stay attached to the correct row. This is critical for construction logs where every entry should have associated documentation.

What should a construction daily log include?

At minimum: date, weather conditions, crew count (your forces and subs on-site), subcontractors present, description of work performed, issues or delays, safety observations, and site photos. Keep it to 8 columns or fewer — the simpler the format, the more likely your superintendent will actually fill it out every day. Consistency matters more than detail.