👥 Who it’s for: Project Managers, Project Executives, Superintendents
🗓 When to use it: As soon as you find a site condition or field issue that may change cost or schedule
Notice deadlines are easy to miss when the field is busy. Muro reads the condition you found against your contract, drafts an editable notice to the owner, and lists what you still need before you send it.
At a glance
📁 Add these files | The specs, including Division 01 and the general conditions · your field report or notes on the condition · Optional: photos, drawings, survey or existing-condition reports, related RFIs and correspondence |
🔌 Connect (optional) | Your project management tool (e.g., Procore) |
📄 You get | An editable Word notice to the owner, plus an internal review: the contract requirements that apply, the notice deadline, supporting evidence, cost and schedule status, and missing documents |
⏱ Takes about | A few minutes |
What to ask
1. Draft the notice:
Draft an owner change notice for the rock we hit at grid C-4. Use today's field report and photos.
2. Check the notice requirements:
What does the contract require for notice of a differing site condition, and how many days do we have?
3. Get it ready to send:
List what's still missing before we send this notice to the owner.
Go further:
Draft an RFI to the architect about the condition at grid C-4.
Add this condition to the open items for this week's OAC meeting.
Tips & best practices
✅ Add Division 01 and the general conditions. That's where the notice rules and deadlines are.
💡 Document the condition well. A dated field report and photos make the notice stronger.
💡 Start right away. Run it the same day you find the condition, so you don't miss the notice window.
✅ Review before you send. The notice is a draft for your team to check and edit.
Good to know
Muro doesn't send or issue the notice. Your team reviews it and sends it.
Muro doesn't estimate the cost or the delay, and it isn't legal advice. It marks cost and schedule impact as still to be confirmed.