How to pull your Delay Forecast, Progress Overview, and Schedule Status exports directly from Buildots to build your OAC meeting package, instead of manually compiling slides from subcontractor reports.

Building an OAC package usually means pulling subcontractor reports, updating graphs from last month's version, and tracking down which design or owner RFIs are still open and blocking which trades. That process can take a couple of days, and by the time you present, the data is already a week or more old.

There's also a gap between what happened on site and what shows up in the report. Subcontractor updates get filtered through a coordination meeting, which gets filtered through what a foreman remembered to report. If the Owner asks a specific question about a delay, you're often checking before you can answer.

Buildots exports give you current, consistent data you can build the package from directly, including documented evidence for delays that were caused by the owner or design team rather than your trades.

Navigate to Analyze → Delay Forecast to see all at-risk activities.

Use Filters to narrow the list down to the activity you'll cover in the OAC meeting.

If it's easier, scroll the Delay Forecast list directly and locate the activity that way.

Click into the activity to see its Average, Recent, Required, and Planned pace.

Check the pace needed to finish on schedule, and how it compares to current progress.

Click See Trend to view the projected end date based on current pace.

Click Export to generate a PDF you can include in the OAC package.

Optionally, type a short note to include with the export. This is useful for giving the Owner context on the activity.

Click Export again to download the Delay Forecast PDF.

Pivot to Progress Overview, filtered to the activity you just reviewed.

Select on Actual / Planned or Due Dates to get additional insights per location.

Click Export to include this view in the OAC package.

Select the format you need: Excel, Floor Plans PDF, or P6.

Use Delay Forecast to document delays caused by the owner or design team, with a projected schedule impact attached, rather than raising them as a general concern in the meeting. Bringing a specific activity and a specific projected delay turns a conversation that could feel like an accusation into one backed by data.