Skip to main content

Catch drawing vs spec conflicts before you price

Find where the drawings and specs disagree, then turn the conflicts into pre-bid RFIs.

👥 Who it’s for: Estimators, Chief Estimators, Precon Managers

🗓 When to use it: Week 1 of the bid

When the drawings say one thing and the specs say another, you usually have to price the more stringent one. Catch it before you price and it becomes an RFI. Miss it and it comes out of your margin.

At a glance

📁 Add these files

Full drawing set · Specifications (project manual) · Recommended: addenda, equipment/door/finish schedules, bid instructions (Division 00), previous RFI logs

🔌 Connect (optional)

Your project management tool (e.g., Procore, Autodesk) to log the RFIs

🤖 Start with

Agents › Drawings vs Specs Conflict Agent

📄 You get

A conflict register ranked by cost impact, and a pre-bid RFI log ready to send

⏱ Takes about

5–15 minutes for the agent, a few minutes for the RFIs

Example output (illustrative data)

What to ask

1. Find the conflicts. Start the Drawings vs Specs Conflict Agent from Agents and add your drawings and specs. (See How agents work.)

2. Turn them into RFIs:

Draft the pre-bid RFIs for these conflicts.

3. Send them to your tool:

Log these RFIs in Procore.

Go further:

Which of these conflicts has the biggest cost impact? Explain why.

Group the RFIs by trade so I can send them to the right designer.

Remove any RFI already answered in Addendum 2.

Tips & best practices

  • ✅ Check the top findings. Open 2–3 and click the source link to see the exact sheet or spec section. See How Muro cites its sources.

  • 💡 Add the full set, not single sheets. More coverage means better findings.

  • 💡 Add your old RFI logs and Division 00. Muro skips questions that were already answered and merges duplicates.

  • 🔒 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

  • With only drawings or only specs, Muro runs partial checks and tells you what it skipped.

  • It compares drawings against specs. It doesn't review the contract. For spec-to-spec and discipline issues, use Project Risk Review, but not on the same set at the same time.

  • Muro finds the question; the architect answers it.

  • Don't see your tool in Apps? Contact our team.

Did this answer your question?