Your crew stops drowning in paperwork. Your jobs stop bleeding margin.
Construction companies lose 35% of project margin to admin overhead — not bad crews, but broken systems. RFIs sitting in inboxes for four days. Subcontractor invoices approved without matching lien waivers. Daily reports typed out on a phone at 6pm after a ten-hour site day. Change orders approved verbally and invoiced six weeks late.
At RaftLabs, we build automation software that plugs into how construction companies actually operate. Not generic workflow tools — systems built around your project lifecycle, your subcontractor relationships, your compliance requirements, and your billing cycle. We've solved this class of problem across 100+ projects. We know where the margin leaks.
Automation built for your specific project workflows, not generic templates
Subcontractor payment, lien waiver, and compliance tracking in one system
RFI and submittal workflows that resolve in hours, not weeks
Fixed price agreed before a single line of code is written
RaftLabs builds custom automation software for construction companies -- RFI and submittal tracking, subcontractor payment workflows with lien waiver matching, change order management, mobile daily reporting, and safety compliance documentation. Construction companies lose 35% of project margin to admin overhead, not bad crews. Each system fits your existing project lifecycle, subcontractor relationships, and billing cycle. Most projects ship in 10 to 14 weeks at a fixed price agreed before any code is written.
Trusted by
Construction runs on paper and email. That's why the margin disappears.
Most construction companies manage eight-figure project portfolios on a combination of email threads, shared drives, and spreadsheets. That's not a complaint — it's how the industry grew up. But at a certain scale, the system breaks. RFIs take four days to route when they should take four hours. Subcontractor invoices get approved without the lien waivers in hand. Change orders get missed in the billing cycle because someone forgot to log the verbal approval. The result is margin erosion that looks like project complexity but is actually just broken process.
Capabilities
What we build
RFI and Submittal Tracking
RFIs sitting in email for four days are a schedule risk that compounds -- every day of unanswered clarification is a day the trade crew cannot proceed on the affected scope. We build structured RFI and submittal workflows where the project manager defines the approval chain (architect, structural engineer, MEP engineer, or any combination), sets response deadlines per document category, and receives automatic escalation notifications when a step stalls past its due date. The reviewer receives a direct email notification with the RFI number, question, reference drawings, and a one-click response interface that does not require logging into a separate system -- reducing response friction being the primary reason for delays. Every RFI has a status (open, under review, responded, closed), an owner at each step, a required response date, and a complete audit trail showing who received it, when, and how long they held it before responding. Submittal log integration tracks shop drawings, product data, and samples against the submittal schedule: overdue submittals flagged before they impact procurement lead times. Procore API integration available for companies already using Procore for project management -- RFIs and submittals created in the automation system sync bidirectionally so neither system becomes the authoritative source at the expense of the other.
Subcontractor Payment Automation
Subcontractor payment workflows that require every required document to be present and matched before the approval queue opens -- the invoice cannot advance until the approved work order, the completed field inspection sign-off, and the correctly executed lien waiver are all attached and verified. Lien waiver type tracking enforced per payment cycle: conditional progress lien waiver required before progress payment release, unconditional progress lien waiver required from the prior payment period before the current period's payment can be approved, and conditional final lien waiver before final payment -- the exact sequence that prevents mechanic's lien exposure. Retainage calculations applied automatically from the contract retainage percentage (typically 5-10%), reducing each payment by the correct retainage amount and tracking the cumulative retainage balance per subcontractor across the project. Sub-tier lien waiver management for projects requiring waivers from lower-tier subs and material suppliers: the general can require their subs to upload sub-tier waivers before approving the sub's invoice. Subcontractor self-service portal showing payment status, pending document requirements, and expected payment date without requiring a phone call to your AP team. Dispute documentation captured as a structured record in the workflow -- not in a separate email thread that gets forwarded to the wrong inbox three months later when someone files a claim.
Change Order Management
Verbal change orders are where project profit disappears -- work is completed based on a field conversation, but it is not captured in writing, not priced until the PM has time to write it up, not formally approved by the owner, and not invoiced until someone rediscovers it weeks later. By that point, the owner's recollection of what was agreed and the contractor's recollection have diverged. We build change order workflows that start in the field the moment the instruction is given. The foreman or superintendent submits a potential change order (PCO) from a mobile form: scope description, labour hours estimate, material quantities, and photos of the affected work. The PCO triggers an internal pricing review where unit costs are applied from the project's cost library, overhead and margin are calculated, and the priced change order is submitted to the owner for digital signature. Owner approval or rejection is captured with a timestamp and audit trail. Approved change orders push automatically to the project budget (updating the revised contract value), to the billing schedule (adding a line item to the next application for payment), and to the accounting system -- nothing re-keyed, nothing forgotten. Time-and-materials change orders track actual hours and materials in real time as work progresses, with daily cost summaries sent to the owner to prevent billing disputes at completion.
Daily Reporting and Progress Tracking
Foremen submit daily reports from a mobile form at end of shift -- designed to take under 5 minutes regardless of how the site day went. Captured data: crew count by trade, hours worked per cost code, work completed by activity (tied to the project schedule activities so progress rolls up automatically), equipment on site, materials received with quantities, weather conditions (temperature, precipitation, wind), any delays with cause code (weather, material shortage, subcontractor, design issue), and issues or incidents flagged for the PM. Data flows automatically into the project dashboard: labour hours accumulated against budget per cost code, project completion percentage calculated from schedule activity progress, and earned value metrics (SPI, CPI) updated daily rather than at monthly progress meetings when it is too late to act. Project managers get accurate field data without calling anyone or interpreting handwritten notes. Owner and client progress reports generated automatically from the accumulated daily report data: formatted to your standard report template (or the owner's required format), populated with photos from the daily report submissions, and distributed on a configured schedule (weekly or biweekly) without a PM spending Friday afternoon compiling a report. Change event log compiled from the daily reports showing all recorded delays and issues -- the contemporaneous record that supports change order substantiation when an owner disputes the cause of a time extension.
Safety Compliance Documentation
Safety compliance failures expose you to OSHA citations, project shutdowns, litigation, and insurance premium increases that collectively cost far more than the compliance overhead being avoided. We build safety compliance systems with digital inspection checklists for every required inspection type: daily pre-task toolbox talks with sign-off by each crew member, weekly site safety inspections with mandatory photo attachments for each flagged item, fall protection inspections for scaffolding and leading edge work, and confined space entry permits with atmospheric testing records. Inspection items that are flagged as non-compliant generate a corrective action record with a responsible party assigned, a due date, and a re-inspection requirement -- the non-compliance cannot be closed without the corrective action being completed and documented. Incident reporting: near-miss and incident reports submitted from mobile with witness statements, injury description, root cause selection from a structured taxonomy, and immediate notifications to the site safety manager and project manager. OSHA recordkeeping (300 Log, 300A Summary, 301 Incident Report) generated automatically from incident records. Certification management for workers (OSHA 10/30, First Aid/CPR, fall protection competent person), equipment (crane certifications, rigging equipment inspection records), and subcontractors (insurance certificates with expiration dates) -- automated reminders at 30 and 7 days before expiration, and access restrictions for workers with expired certifications if your safety program requires it. Compliance record export for audits, owner due diligence requests, and litigation discovery in seconds.
Material Procurement and Invoice Reconciliation
Purchase orders triggered automatically when project stage milestones are reached: when framing is approved, the lumber and hardware PO for the next stage issues automatically against the approved budget line -- eliminating the manual step where a superintendent realizes materials haven't been ordered after the crew is standing idle. PO approval routing based on value thresholds: orders under $5,000 approved by the project superintendent, $5,000-$25,000 by the project manager, above $25,000 by the owner or executive -- configurable per contract and automatically enforced. Delivery confirmation captured from the field via mobile form: the foreman records quantities received, notes any shortages or damage, and attaches photos of the delivery paperwork -- creating the receiving record that the three-way match requires. Three-way match view for the AP team: PO (approved order), receiver (field delivery confirmation), and supplier invoice matched against each other automatically. Discrepancies above a configured tolerance (typically 2-5%) flagged for review rather than paid unchecked. Quantity overbilling and duplicate invoice detection: a supplier cannot invoice twice for the same PO line without the discrepancy surfacing in the match. Committed cost tracking: the moment a PO is issued, the committed cost reduces the remaining budget even before the invoice arrives, so budget burn is visible in real time rather than at month-end when it is too late to adjust scope or recover margin.
How much is manual admin costing your business each month?
Most construction companies can't answer that question precisely. We can help you find out — and fix it.
Most of the admin work that project managers hate. RFI and submittal routing — you define the approval chain, the system enforces it and chases respondents automatically. Subcontractor payment processing — invoices matched against work orders and lien waivers before approval queues fire. Change order tracking — verbal approvals captured in a structured flow, priced, approved, and pushed to the billing cycle without manual re-entry. Daily reports — foremen submit from a mobile form at the end of shift, data rolls up into your project dashboard automatically. Safety compliance documentation — inspection checklists, incident reporting, and certification tracking with automated reminders. Material procurement — purchase orders triggered by job stage milestones, tracked against budget, and reconciled on delivery.
Most projects run 10 to 14 weeks from kickoff to live deployment. The first two weeks are discovery — we map your current workflows, identify where the margin is leaking, and agree on what gets built in the first version. Development runs in two-week sprint cycles with working demos at each milestone. You're not waiting 14 weeks to see anything. You're reviewing working software every two weeks and giving feedback that shapes the next sprint. Simpler automation — a single workflow like RFI tracking or subcontractor payment — can ship in 6 to 8 weeks.
Yes. We integrate with the tools construction companies already use: Procore, Autodesk Construction Cloud, Buildertrend, CoConstruct, QuickBooks, Sage, and most ERP systems with an API. The automation layer sits between your existing systems and closes the gaps — it doesn't replace tools your teams already know. If your current stack uses something non-standard, we assess integration feasibility at the scoping call before any commitment is made.
That's the core requirement we design to. Any software that your foremen won't use at the end of a ten-hour site day is worthless, regardless of what it can do in a demo. We build mobile-first interfaces for field teams — simple form submissions, photo uploads, checklist completions. The complexity lives in the back end. Your project managers see a dashboard. Your foremen see a short daily report form. Your AP team sees invoices that are already matched and queued. We run user acceptance testing with your actual team before anything goes live.
Work with us
Tell us what you need. We'll tell you what it would take.
We scope Construction Operations Automation in 30 minutes. You walk away with a clear cost, timeline, and approach. No commitment required.
Scope and cost agreed before work starts. No surprises. No obligation.
Working prototype within 3 weeks of kickoff.
Pay by milestone. You see progress before each invoice.
60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.