👥 Who it’s for: Project Managers, Project Engineers
🗓 When to use it: As soon as a sub sends a submittal, before it goes to the architect
Checking shop drawings and product data line by line takes hours. Muro reviews the submittal against the specs and drawings, flags every deviation with its source, and recommends whether to forward it or send it back.
At a glance
📁 Add these files | The submittal package · the specs · the drawings · Optional: your submittal register, addenda, the approved material list, earlier review comments |
📄 You get | An Excel review with each item, the spec requirement, what was submitted, a status (Compliant, Non-compliant, Partially compliant or Cannot verify), the action needed and the spec and drawing references |
⏱ Takes about | A few minutes |
What to ask
1. Review the submittal:
Review submittal SUB 08-003 against spec 08 71 00 and the door schedule. Flag every deviation.
2. Find what's missing:
What can't be verified from this submittal? List what the sub still needs to send.
3. Write the comments:
Write the review comments to return this submittal to the sub for revision.
Go further:
Which submittals are still open, and who has the ball?
Build the submittal register from the specs.
Tips & best practices
✅ Add the right spec section. Muro reviews against the documents you give it. The spec section and the related drawings matter most.
💡 Include the addenda. If a requirement changed in an addendum, Muro checks against the latest version.
💡 Look at "Cannot verify" first. These are the items where the submittal doesn't show enough to decide.
✅ Use it before the architect does. Catch the deviations yourself and save a review cycle.
Good to know
Muro doesn't approve submittals or replace the architect's review. Your team decides whether to forward or return it.
Muro doesn't send or upload the submittal anywhere. It gives you the review to act on.