Reconcile the Duck Creek underwriting exception queue daily
Every morning, WebRun opens Duck Creek, checks the underwriting exception queue for every policy stuck waiting on review, logs each one in Google Sheets with its exception reason and days in queue, and posts a summary to Notion sorted oldest first so underwriters clear the queue in the order it actually matters.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I keep the Duck Creek underwriting exception queue visible and prioritized?
WebRun checks Duck Creek every morning for every policy stuck in the underwriting exception queue, logs each one in Google Sheets with its exception reason and days waiting, and posts a summary to Notion sorted with the oldest policy first. That keeps the exception queue visible and prioritized instead of growing quietly in the background.
- The oldest exceptions surface first instead of getting buried
- Every exception is logged with its reason for pattern tracking
- Cleared policies drop out of the summary without manual cleanup
Built for underwriters · insurance operations teams · policy administration staff · insurance IT teams
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.duckcreek.comin a real browser with your saved login - no setup, no API keys. -
1
Duck Creek Technologies - check policies stuck in the exception queue
duckcreek.com
WebRun opens Duck Creek Technologies to check policies stuck in the exception queue. - Open Duck Creek policy administration and check the underwriting exception queue
- Capture the policy number, exception reason, and days in queue for each
- Note any exception newly added since the last run
Done when Every policy in the exception queue is captured with its reason and age.
-
2
Google Sheets - log every exception with its reason
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log every exception with its reason. - Log each exception with its policy number, reason, and days in queue
- Update the record once a policy clears the exception queue
- Keep a running count of exceptions by reason
Done when Every open exception is logged with its current status.
-
3
Notion - post the exception summary
notion.so How to Automate Notion
WebRun opens Notion to post the exception summary. - Post the exception summary sorted with the oldest policy first
- Group the count of exceptions by reason
- Link to the full log in Google Sheets
Done when The underwriting team has today's exception summary in Notion.
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 clear the exception or approve the policy for me?
No. WebRun only reads the exception queue in Duck Creek and reports it. Reviewing and clearing an exception stays a decision your underwriters make.
What counts as an exception?
Any policy Duck Creek itself has already flagged into the underwriting exception queue, whatever the specific reason. The daily summary just makes that queue visible and prioritized.
What happens once a policy clears the queue?
It reads the live exception queue each morning, so a policy that clears review drops out of the log and summary automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.