👥 Who it’s for: Estimators, Precon Managers, Project Managers
🗓 When to use it: Week 1–2 of the bid
Some problems aren't conflicts. The design just can't be built the way it's drawn, the site doesn't match the design, or work is implied that no trade will pick up. Find them before bid day and they become RFIs or line items. Find them in the field and they become change orders you can't recover.
At a glance
📁 Add these files | Full drawing set · Specifications (project manual) · For the site review: geotechnical report and boring logs, survey, hazmat/environmental reports, utility records · Recommended: addenda |
🔌 Connect (optional) | Your project management tool (e.g., Procore, Autodesk) to log the RFIs |
📄 You get | A site risk list, a constructability and implied-scope register with sources, and a pre-bid RFI log |
⏱ Takes about | A few minutes per step |
Example output (illustrative data)
What to ask
1. Check the site against the design:
Review the site and existing conditions against the design. Flag anything in the geotech, survey, hazmat or utility records that the drawings don't account for.
2. Find what can't be built and who owns it:
Review the drawings and specs for constructability. Flag details that are hard to build, implied scope, work no trade owns, and scope that two trades would carry.
3. Turn the findings into RFIs:
Draft pre-bid RFIs for the top findings and log them in Procore.
Go further:
Which of these findings should I carry as a cost in my number instead of an RFI?
Group the implied scope by trade so I can add it to the bid packages.
List the coordination clashes between structural and MEP, with sheet numbers.
Tips & best practices
✅ Check the top findings. Click the source link to see the exact sheet, spec section or boring log. See How Muro cites its sources.
💡 Add the site reports. Without the geotech, survey or hazmat reports, Muro can only review what's on the drawings. Example: the boring logs show groundwater at 6 feet, the drawings show a basement with no dewatering.
💡 Run the site review first. Site findings often explain why a detail is hard to build.
🔒 You stay in control. Muro shows a preview and waits for your approval before creating anything in your tools. See Your data, security & approvals.
Good to know
If a site report is missing, Muro tells you which checks it skipped.
Muro flags the risk and points to the source. Your team and the design team decide how to handle it.
For drawing vs spec conflicts, use the Drawings vs Specs Conflict Agent instead.
Don't see your tool in Apps? Contact our team.


