SubmittalLink

Three months into a commercial build. Work is moving. Crew is on site. Subs are billing. Then the owner asks: "How much of the project is actually complete, and what have we paid for so far?" If you're scrambling to pull that together from a handful of spreadsheets and invoices, you have a billing problem waiting to happen. This is where the Schedule of Values comes in. Most people treat it as a payment formality. Something you hand over before the first pay app and forget about. That's the wrong way to think about it. A well-built SOV is one of the most useful financial tools you have on any project. It tells you what each piece of work is worth, tracks progress at every payment period, and gives you early warning on cost overruns before they spiral. Here's what a bad SOV looks like in practice: A line item is 90% billed but only 60% complete in the field. That gap is a real problem. And without a solid SOV, you won't see it until the end of the job when your options are limited. A few things that kill your Schedule of Values: → Building it after the project starts instead of during pre-construction → Not updating it when scope changes and change orders come in → Keeping it too vague to actually verify progress → Treating it as a billing document instead of a management tool → Forgetting to account for stored materials (legitimate cash flow left on the table) And here's a connection most people miss: Your SOV is only as accurate as your document control. A delayed submittal holds up steel fabrication. An unanswered RFI stops rough-in work. The line items in your SOV sit still. Billing stalls. Cash flow takes a hit. The document side of your project directly affects the financial side. When submittals move fast and RFIs get answered before they stall work, your SOV keeps advancing. And payments keep coming in. That's the problem SubmittalLink was built to solve. Clean submittal and RFI tracking so the document side of your project stops dragging on the financial side. No per-user fees. No enterprise complexity. Just organized document control that keeps work and billing moving together. #construction #submittallink #generalcontractor #subcontractor #submittalsoftware #rfisoftware

You first hired two people. Now you've got six. Four projects running at once. Revenue hit $3M and you're pushing toward $5M. You've outgrown sticky notes and gut feel. So you Google "construction project management software." First result: Procore. Looks impressive. You try to find pricing. No pricing listed. Just a "Contact Sales" button. You get on a demo. The number they land on? Easily five figures per year. You're doing $3M in revenue. That's a serious chunk of it just for software. This is the small contractor software trap. Most platforms are built for enterprise. Priced for enterprise. And require enterprise-level effort to set up. Meanwhile you just need to: → Track submittals without things falling through the cracks → Know where each project stands without calling everyone → Find the right document in under a minute → Stop losing decisions that were made over text The honest answer? You probably don't need all-in-one software yet. A focused tool for submittals and RFIs. A simple Gantt for scheduling. QuickBooks for job costing. Google Drive for files. Total cost: a fraction of what enterprise platforms charge, for tools your team will actually use. vs. paying thousands per month for a platform where you use 20% of the features. And here's what nobody tells you about enterprise software: Your team won't use it. It's too complex. Too many steps. Field crews don't want to spend an hour learning a system. They want something that works in five minutes. That's why so many small contractors buy comprehensive software, struggle with adoption, and end up back on spreadsheets within six months. If you are ready for dedicated software, here's the actual framework: Identify your biggest pain point (just one) → Calculate what it's actually costing you → Find the simplest tool that solves that specific problem → Pilot it on one project before rolling it out everywhere →Start small. Solve one thing well. Expand from there. At SubmittalLink, we focus on submittals, RFIs, and document control. Not scheduling. Not accounting. Not safety modules you'll never touch. Just the stuff that bogs down small teams the most, starting at $150/month with unlimited users. Sometimes simple is exactly what you need. #construction #submittallink #generalcontractor #subcontractor #submittalsoftware #rfisoftware

Thursday morning. Two crews show up to the same floor at the same time. Electrical. Drywall. Eight workers. Nobody can move. Your schedule says electrical was Wednesday. Your super moved them to Thursday. The drywall foreman got an email two weeks ago that said Thursday. Before everything changed. Nobody lied. Nobody was careless. Everyone just had different information. That's $2,000 in wasted labor before lunch. This is the real collaboration problem in construction. It's not that people don't want to communicate. It's that information lives in 10 different places, email, texts, phone calls, random conversations and changes never reach everyone who needs them. And it gets harder when you consider: → 30+ companies on one project, all with their own systems → Teams spread across job sites, offices, and time zones → Drawings that change weekly → Decisions that need to happen by tomorrow morning or the pour gets delayed Traditional methods (meetings, calls, walking over to someone's desk) don't cut it anymore. What actually fixes it? One place where everyone sees the same information. ✅ Current drawings. Not the version someone printed 3 weeks ago ✅ RFI responses visible to everyone affected, not just the person who asked ✅ Change notifications that go out automatically when something shifts ✅ Issues logged, assigned, and tracked until they're actually resolved The software doesn't make people want to collaborate. It removes the friction that gets in the way when they're already trying. A few things to keep in mind if you're shopping for tools: If it takes 7 steps to log an issue, nobody will use it. If the mobile experience is bad, field teams go back to texting. If subs won't adopt it, you're back to square one. Start simple. One project. Core features only. Then expand. At SubmittalLink, we keep it focused. Document management, RFI tracking, and submittals, all in one place, built for teams that don't have time for enterprise complexity. Because the goal isn't to have the most powerful software. It's for everyone to show up knowing what's actually happening. #construction #submittallink #generalcontractor #subcontractor #submittalsoftware #rfisoftware

Who's responsible for making sure we can find documents six months from now? The answer is usually nobody. So the plumbing submittal ends up in Sara's inbox. The shop drawings are on the shared drive, maybe. The RFI log exists in three different versions. The as-builts are in the super's truck. Then closeout hits. And suddenly you're paying two project engineers full-time just to dig through emails and chase down subs who left the project months ago. That's not an organization problem. That's a money problem. Here's the math: Assume your PM earns $130K/year (about $62.50/hr). 30 minutes a day hunting for documents = $112.50 wasted. Every single day. Over a 6-month project? That's $13,500 from one person alone. Add your project engineer. Add your super. Add your admin. It adds up fast. And that's before you factor in: → Change order disputes you can't prove → Inspections delayed by missing approvals → Rework from outdated drawings → Warranty claims with no product data → Closeout holdbacks Bad document management isn't just annoying. It's expensive. We've seen teams try the "perfect folder structure" approach. Week 1: everyone follows it. Looks great. Week 4: someone saves to the wrong folder. Week 8: three people have "reorganized" it. Week 20: total chaos. The problem isn't the system. It's that it requires perfect discipline from everyone, forever. That's not realistic on a busy project. What actually works? ✅ One source of truth. Not email + shared drive + random binders ✅ Automation that organizes documents as they come in ✅ Version control that happens without anyone thinking about it ✅ Context. So you can see how that RFI connects to the drawing and the submittal At SubmittalLink, we built exactly that. ✅ Submittals, RFIs, and drawings: automatically organized, version controlled, and searchable in seconds. ✅ No enterprise complexity. No month-long implementation. Just documents that are actually findable. ✅ If your team is still spending 30 minutes hunting for files, that's the problem worth solving first. #construction #submittallink #generalcontractor #subcontractor #submittalsoftware #rfisoftware

How often are you satisfied with the��first RFI response? Most of the time it goes like this: - you ask the question - you get a partial answer - you follow up for clarification - someone references a detail that isn’t attached - a week later, nobody remembers what actually got agreed to RFIs are rarely one-and-done. They’re a conversation and the risk is when that conversation gets scattered across email threads and PDFs. That’s why we built SubmittalLink’s RFI workflow around back-and-forth: ✅ every response is tracked in order ✅ clarifications don’t get lost ✅ attachments stay with the thread ✅ the final answer is clear (and easy to find later) It’s meant to feel intuitive. More like dropping comments on this post but with the structure you need on a project. Because the goal isn’t to send an RFI. It’s to close the loop and preserve the decision. #construction #generalcontractor #RFI #constructionmanagement #submittallink

Using ChatGPT to create a submittal log is a great start. It’s fast. It’s better than a blank spreadsheet. And it can absolutely help you get momentum. But on real projects, it’s often not enough. Because the log isn’t just a list. It has to be defensible: - tied to the exact spec sections - separated by scope and packages - consistent numbering - aligned with the latest drawings - complete (including implied submittals buried in Part 2/3) If the AI misses one item or mixes two similar ones, you don’t notice until procurement or install. That’s when it gets expensive. That’s why we built SubmittalLink differently. Instead of asking you to manually build the log, SubmittalLink can: ✅ read your specs and drawings ✅ generate a structured submittal list ✅ show it to you for review first ✅ then create the actual submittal records after you approve So you get the speed of AI… without trusting a raw draft as the contract record. #construction #generalcontractor #submittals #constructiontech #chatgpt #submittallink

��The submittal log Excel file has a version conflict.” That sentence should scare every GC. Because it usually means: - two people updated the log at the same time - the “latest” file isn’t actually the latest - revisions and attachments are now out of sync - nobody trusts the status report And the worst part? You don’t find out until you’re under pressure. Install is coming, lead times are burning, and someone asks for a clean record. This isn’t a discipline problem. It’s what happens when contractual tracking lives in a spreadsheet. Submittals and RFIs need a system that enforces structure by default: ✅ one source of truth ✅ revision history tied to the package ✅ clear ownership and status ✅ exportable log when you need to prove it That’s why we built SubmittalLink: submittal + RFI tracking for builders and small GCs without the overhead. #construction #generalcontractor #submittals #RFI #constructionmanagement #submittallink

If you’re searching for submittal tracking software or RFI tracking software, here’s what you actually need (especially as a local builder). Excel just lists submittals. It doesn't prevent the mess that causes rework and disputes. A solid system should enforce structure by default: ✅ Unique numbering per spec section (no duplicates, no ambiguity) ✅ Automatic revision tracking (Rev 2 vs Rev 3 is never “maybe”) ✅ Clean package separation (scope stays attached to the right record) ✅ Attachments + history preserved (email threads don’t count as records) ✅ Simple reporting (status, lead times, open items, without spreadsheets) Submittals and RFIs aren’t “admin.” If the record is sloppy, your risk is real. That’s the wedge we built SubmittalLink around: submittal + RFI tracking for builders and small GCs without the overhead. If you’re still doing this manually, you’re not behind. You’re just one revision away from chaos. #construction #generalcontractor #submittals #RFI #constructionmanagement #submittallink

Submittal numbering sounds boring...until it breaks your project. A real example: 32 00 00-1 Rev 2 32 00 00-1 Rev 3 Same number. Different material. Different scope. Now imagine filtering, reporting, or defending that in a claim. The fix isn’t “better discipline.” It’s systems that enforce structure by default: ✅ Unique numbering per spec section ✅ Automatic revision tracking ✅ Clear package separation This is one of those problems you only understand if you’ve lived through it. If you’re still managing this manually, you’re one mistake away from chaos. #construction #generalcontractor #submittallink

Construction still runs on email. But submittals shouldn’t. Every week I see teams: ➡️ Forwarding emails to themselves ➡️ Copy-pasting specs into logs ➡️ Losing attachments The biggest time drain isn’t reviewing submittals. It’s creating and tracking them. We designed SubmittalLink so teams can go from: Email → structured submittal → tracked record No spreadsheets. No re-entry. No guessing. If your PMs are doing admin work, your process is broken, not your people. #construction #generalcontractor #submittallink