Chase change orders waiting on client sign-off
Every morning, WebRun opens Buildertrend, finds change orders still pending client approval, notes which are past their approve-by date, drafts a polite follow-up email to each homeowner, and posts your team a ranked chase list of unsigned work in Slack.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I follow up on Buildertrend change orders awaiting client approval?
WebRun chases the change orders your homeowners have not signed yet. Every morning it opens Buildertrend, finds change orders still pending client approval, drafts a polite follow-up email for each customer, and posts your team a chase list in Slack, so approved scope gets billed and no extra work stays unsigned.
- Approved scope gets billed instead of quietly slipping by unsigned
- Every pending change order followed up the morning it goes overdue
- Signed change orders fall off the chase list automatically from live Buildertrend status
Built for residential builders · home remodelers · general contractors · construction project managers
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
buildertrend.comin a real browser with your saved login - no setup, no API keys. -
1
Buildertrend - find change orders awaiting approval
WebRun opens Buildertrend to find change orders awaiting approval. - Open Buildertrend and filter change orders to those released but still pending client approval
- Capture the job, client, amount, and the approve-by date for each
- Note which are already past their approve-by date and skip any reminded today
Done when Every change order awaiting client sign-off is listed with its amount and approve-by date.
-
2
Gmail - draft a homeowner follow-up
WebRun opens Gmail to draft a homeowner follow-up. - Draft a polite, on-brand follow-up to each homeowner with the change order summary and amount
- Point them to the approve or decline buttons in their Buildertrend client portal
- Leave every email as a draft for you to review. Never send to a client on its own
Done when A follow-up email is drafted and waiting for your review for each pending change order.
-
3
Slack - post the chase list
WebRun opens Slack to post the chase list. - Post a ranked chase list to your project channel
- Put the oldest and largest unsigned change orders first, with the job and amount
- Flag any already past their approve-by date so they get a call, not just an email
Done when Your team has today's ranked list of change orders still waiting on sign-off.
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 email my clients without me?
No. WebRun drafts each homeowner follow-up and leaves it unsent in Gmail for you to review. Nothing reaches a client until you read it and hit send, so every approval nudge stays your call.
How does it know a change order is still unsigned?
It reads the live approval status in Buildertrend each morning, listing only change orders that are released but still pending. Anything a client has already approved or declined is skipped automatically.
What about a change order that gets approved overnight?
It re-reads live Buildertrend status every run, so a change order signed since yesterday drops off the chase list and no stale reminder goes out for work that is already approved.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.