Automated Autodesk Build Submittal Tracking
Every morning, WebRun opens Autodesk Build, reviews the submittal log, captures each item's status, ball-in-court, and due date, flags the ones overdue or pending review, and posts your team a Slack list of submittals to push today.
How do I track overdue construction submittals automatically?
Every morning, WebRun reviews your Autodesk Build submittal log, capturing each item's spec section, status, ball-in-court, and due date. It flags submittals that are overdue or pending a reviewer, logs them to a Google Sheet, and posts your team a ranked Slack list, so stalled submittals get pushed before they delay procurement.
- Overdue submittals surface every morning, not at the deadline
- Each stalled item names who it is waiting on
- The submittal log stays current without manual status chasing
Built for general contractors · project engineers · construction project managers · subcontractors
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
acc.autodesk.comin a real browser with your saved login - no setup, no API keys. -
1
Autodesk Build - review the submittal log
WebRun opens Autodesk Build to review the submittal log. - Open Autodesk Build and go to the Submittals log
- Capture each item: spec section, status, ball-in-court, and due date
- Flag items overdue or pending action from a reviewer
Done when Every open submittal has been captured with its status and ball-in-court.
-
2
Google Sheets - log status and due dates
WebRun mirrors the submittal log into a ranked sheet. - Log each submittal with its due date, status, and who it is waiting on
- Sort so overdue and soon-due items sit at the top
- Keep a running view of the log's health
Done when The submittal log is mirrored and ranked in the sheet.
-
3
Slack - post what is stalled
WebRun posts the submittal push list to Slack. - Post a short list of overdue and soon-due submittals
- Name the ball-in-court party for each so the right person acts
- Leave it for the team to action. Never approve or reject a submittal automatically
Done when Your team has today's submittal push list in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it approve or reject submittals?
No. WebRun only reads the submittal log and reports status. Approving, rejecting, or responding to a submittal stays with your team inside Autodesk Build.
How does it know what is overdue?
It reads each submittal's due date and current ball-in-court in Autodesk Build, then flags anything past due or pending a reviewer's action and ranks it by urgency.
Can it tell me who is holding things up?
Yes. Each flagged submittal names the ball-in-court party, so it is clear whether the delay sits with a reviewer, the architect, or the submitter.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.