Track every document through recording without lifting a finger
Every morning, WebRun opens ResWare, checks the recording status of documents submitted to the county for all recently closed orders, updates a Google Sheets recording tracker, and posts a Slack digest flagging any documents that are delayed, rejected, or past the expected recording window.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically track post-closing document recording status?
WebRun checks ResWare every morning for post-closing documents that have not yet been confirmed as recorded, updates a Google Sheets tracking log, and posts a Slack digest flagging any document past its expected county recording window or rejected. Your post-closing team always knows exactly where each deed and mortgage stands.
- Delayed and rejected recordings are caught before they become title defects
- The team shares one live recording tracker updated every morning
- Confirmed recordings are marked automatically with no manual log updates
Built for title companies · post-closing teams · escrow officers · real estate attorneys
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
www.resware.comin a real browser with your saved login - no setup, no API keys. -
1
ResWare - check recording status for all post-closing documents
resware.com
WebRun opens ResWare to check recording status for all post-closing documents. - Open ResWare and pull all orders closed within the last 30 days where recording is not yet confirmed
- For each document, record the order number, document type, county, date submitted, expected recording window, and current status
- Flag any document that is past the expected recording window or marked with an exception
Done when Every unrecorded post-closing document is listed with its current status and any delay flag.
-
2
Google Sheets - update the recording tracker with current status
google.com How to Automate Google Sheets
WebRun opens Google Sheets to update the recording tracker with current status. - Open the post-closing recording tracker sheet
- Upsert each document row with today's status, recording book and page where available, and any rejection notes
- Mark documents confirmed as recorded since the last run
Done when The recording tracker sheet is current with confirmed recordings marked and delays identified.
-
3
Slack - post a digest of delayed or at-risk recordings
slack.com How to Automate Slack
WebRun opens Slack to post a digest of delayed or at-risk recordings. - Post a digest to the post-closing Slack channel listing documents past their expected recording window or with a county rejection
- Include the order number, document type, county, and days overdue for each flagged item
Done when The team has a list of delayed or rejected recordings in Slack with enough detail to follow up with the county.
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
How does it know when a document has actually been recorded?
It reads the recording status and any book and page information logged in ResWare. When your team updates ResWare with confirmed recording details, the tracker reflects that on the next run.
What does it do when a county rejects a document?
Rejections logged in ResWare are flagged in the Slack digest and in the Google Sheet with the rejection reason, so your post-closing team can prepare and resubmit the corrected document.
How far back does it look for unrecorded documents?
By default it checks orders closed within the last 30 days with recording not yet confirmed. This window can be adjusted to match your typical county recording turnaround time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.