Anvil SystemsSearch project information
Ask questions across drawings, specs, emails, RFIs, submittals, schedules, field notes, and project folders. Get answers with source references.
Connect
If your current tools work, we connect to them.
Built for construction teams with scattered project information
Custom project information systems for construction teams.
Anvil builds private systems that organize drawings, specs, emails, RFIs, submittals, approvals, schedules, photos, field notes, and trackers so your team can search project information, track open items, route work, and generate updates from one place.
project-information-system.map
Scattered evidence becomes a usable job record
Scattered across
Questions that stall work
- Which version is current?
- Who owns the next response?
- Is this extra work or base scope?
- What is overdue this week?
Anvil system
Project job record
Source linked evidenceOwner next person + due dateStatus open, blocked, approvedOutput queue, log, report, packet
Team can use
- Answers with source links
- Live open-item list
- Review and approval queues
- Change backup packet
- Weekly owner update draft
The point is not another platform. It is a project system that keeps evidence, ownership, status, and output tied together.
The problem
The information is there. It is just scattered everywhere.
Construction teams already have the information they need to run projects better. It is buried across emails, drawings, specs, RFIs, submittals, shop drawings, change requests, schedules, meeting notes, photos, spreadsheets, trackers, and disconnected tools.
That makes simple questions hard to answer.
- Who needs to review this?
- What changed since the last version?
- Which submittals are overdue?
- Where is the latest drawing?
- Was this in the original scope?
- Can we prove this is extra work?
- What is holding up the schedule?
- Which contractor owes us a response?
- What needs to be in this week's update?
- What needs to happen next?
What the system does
One custom system for search, tracking, routing, and updates.
Anvil builds a private project information system around the way your team actually works. It can connect to existing tools, clean up messy trackers, or replace manual workarounds when they are slowing the team down.
Track open items
Turn scattered emails, notes, documents, and decisions into live trackers for RFIs, approvals, change requests, schedule blockers, punch items, and owner decisions.
Route work to the right person
Send shop drawings, submittals, punch items, field issues, approvals, and overdue items to the right reviewer, PM, contractor, owner, or trade lead.
Generate updates
Create weekly reports, open-item summaries, overdue lists, change logs, meeting notes, owner updates, contractor follow-ups, dashboards, and closeout reports.
See it live
A working system on a real public project.
We built a sample project information system on the public Sanibel Fire Station No. 171 bid package — real drawings, specs, and addenda you can search, plus guided flows that route reviews, track open items, and generate updates. Ask it a question and it answers with source references.
- Search drawings, specs, and addenda with citations
- Six guided flows across all three team types
- Live review queues, change packets, and weekly updates
- Simulated actions — nothing public is ever changed
Custom, not one-size-fits-all
Built around your project, your team, and your process.
Anvil is not a fixed construction platform every company has to use the same way. Some teams need a better way to search project documents. Some need review routing and approval tracking. Some need a field issue app for contractors. Some need their current trackers cleaned up.
Clean Up
If your current tools are messy, we clean up the workflow around them.
Replace
If your current tools are holding the process back, we build something better.
We start with your project information and build the system around the workflows that matter most.
Example Systems
Different teams. Same information problem. Custom systems for each.
The core problem is the same: project information is scattered and hard to act on. The system we build depends on who is using it and what workflow matters first.
Route shop drawings to the right reviewer.
Problem: Shop drawing emails arrive in a shared inbox and someone manually guesses the project, reviewer, and due date.
System: Email intake that extracts details, links attachments, suggests the reviewer, and creates a tracked review item.
Outputs: Review queue, owner, due date, source email, attachment links, status, and overdue summary.
Give every reviewer a clean queue.
Problem: Engineers are asked to review drawings, substitutions, clarifications, and equipment options without one clean list.
System: Role-based review queues by engineer, project, discipline, due date, and status.
Outputs: Engineer task lists, overdue reviews, manager summary, and weekly workload view.
Know which subs owe you what.
Problem: PMs and supers chase subs through texts, emails, calls, and meetings with no single source of follow-up.
System: Subcontractor follow-up workflow with tasks, source message, owner, due date, project area, and status.
Outputs: Sub-specific task lists, overdue follow-ups, weekly sub summary, and escalation queue.
Document changes before they become disputes.
Problem: Change evidence lives in meeting notes, emails, texts, photos, and field notes when it is time to price or dispute.
System: Change intake workflow that captures source evidence, location, scope impact, cost impact, schedule impact, and status.
Outputs: Change log, evidence packet, pricing status, approval status, and source trail.
Find the trade-specific details faster.
Problem: Estimators dig through specs, drawings, addenda, and schedules to find what matters for their trade.
System: Bid package workflow that makes documents searchable and summarizes relevant requirements, sheets, spec sections, and alternates.
Outputs: Scope summary, spec references, sheet references, bid checklist, and RFI questions.
Capture change evidence from the field.
Problem: Crews perform extra work or hit field conditions without enough backup to support the change order.
System: Field change app that captures photos, location, description, source request, labor/material impact, and authorization.
Outputs: Change evidence log, daily backup, cost impact notes, and change order packet.
These are not separate products. They are examples of modules inside a custom project information system — see them running in the live demo →
Who We Help
Different teams get different project systems.
Engineering / MEP Teams
Shop drawing reviews, equipment approvals, submittals, RFIs, project emails, engineer signoffs, and review queues.
See Engineering Systems →Builders, GCs & Developers
Schedules, subs, change orders, RFIs, punch lists, field issues, owner updates, closeout, and reporting.
See Builder Systems →Specialty Trades
Bid packages, specs, takeoffs, material approvals, submittals, field changes, change documentation, and contractor follow-ups.
See Trade Systems →How It Works
Start with the workflow causing the most pain.
Audit one project or process
We look at one real project or painful process and map where information is scattered or handled manually.
Identify the first workflow
We find the workflow to build into the project system first: search, tracking, routing, reporting, or follow-up.
Build the pilot system
We build the first working version around real project information, existing tools, and the users who need it.
Expand after it works
Once the first workflow is working, the system can expand into more projects, teams, and workflows.
Modern Automation
Powered by automation and AI where it actually helps.
We use AI where it creates practical leverage: reading project emails, summarizing documents, searching drawings and specs, extracting key details, drafting reports, and identifying follow-ups.
But the goal is not to add AI for the sake of it. The goal is a project system your team actually uses.
Next Step
Start with one project system audit.
We will map the information, identify the bottleneck, and design the first system to search, track, route, and update the work your team is handling manually.