.svg)
.svg)
best risk management software for construction
See the why behind the when
With Schedule Impact Requests (SIR), you get a clear record of every schedule change, what happened, when, why, and who approved it. This brings more control, fewer surprises, and stronger accountability across the team. No more chasing down updates or piecing together emails. It all runs behind the scenes without slowing anyone down.
Spot schedule impacts instantly
If a lookahead task drifts beyond its parent schedule activity, Outbuild flags it automatically. A simple icon alerts the superintendent to review the change and submit a Schedule Impact Request right from the iPad.
Get a personalized demo
Streamline approvals and communication
Each SIR includes key details like responsible parties and whether the task is on the critical path. Once submitted, reviewers receive email and in-app alerts, can preview the schedule impact, and approve or reject with a single click, keeping communication fast and transparent.
Get a personalized demoMaintain a complete record of schedule changes
Every approved or rejected SIR is logged automatically, creating a clear audit trail of when and why the schedule evolved. This change history helps teams explain decisions, resolve disputes, and build accountability across the project.
Get a personalized demo
What our customers are saying.
From billion-dollar companies to smaller family-owned businesses. They all believe that construction deserves a better scheduling and planning tool.
.webp)
.webp)
Frequently Asked Questions
What is a Schedule Impact Request (SIR) in Outbuild?
A Schedule Impact Request is Outbuild’s workflow for documenting schedule impacts in a single system. It captures what changed, which activity is affected, who submitted it, who reviewed it, and whether it was approved or rejected.
When does Outbuild create a Schedule Impact Request?
When the field team updates a Lookahead task and that change pushes past the Master Schedule guardrails, Outbuild flags a potential schedule impact and prompts the superintendent to submit a request.
What does the field team do when a task slips?
The superintendent opens the alert, adds the reason, selects a reviewer from a permission-based list, and sends the request. After submission, the superintendent gets notified when the request is approved or rejected.
What does the office team see when reviewing a SIR?
The reviewer gets notified, opens the request, and sees the key context quickly, including the affected activity, whether it is on the critical path, what task triggered the request, and how the activity end date shifts. The reviewer previews the impact to the Master Schedule and approves or rejects it. If approved, the schedule updates to reflect the field change.
Where do teams track all schedule impacts?
In the Schedule Impact Request module, a single table shows every request, whether open, approved, or rejected. The table supports filtering, grouping, and column customization. Teams can save private views and export to Excel to share with stakeholders.
What information does the SIR table show at a glance?
You can see who submitted, the affected activity, critical path status, assigned reviewer, what triggered the request, how the end date changes, and how long the request has been open. For pending requests, teams can also update key fields such as compensable and excusable directly in the table.
Ready to see Outbuild?
Join hundreds of contractors from 10+ countries that are saving money by scheduling better
We’ll be in touch soon!