InsightWorker Logo
  • contact@verticalserve.com

Stale Submission Radar

A daily 6 AM scan that finds submission folders without underwriter activity for 7+ days, emails the team lead a clean list with SharePoint links, and optionally drafts a 'still considering' broker reply for human review.

← All use cases
Insurance — Underwriting Ops
Commercial property, specialty, casualty — any underwriting team with broker-fed SharePoint intake
SharePointschedulingunderwriting opsbroker relationships

The problem

  • Submissions sit in SharePoint with no movement for a week — broker stops checking, relationship cools, the carrier loses optionality on a risk it might still want to write.
  • Underwriting team lead has no single pane showing 'what's stale right now?' — they piece it together from individual underwriter calendars and Slack pings.
  • When stale submissions get rediscovered, the broker reply is hurried and apologetic. A scheduled, low-friction nudge would have saved the relationship.
  • Compliance teams want an audit trail showing every submission was either advanced, declined, or actively followed up — manual processes leave that audit gap.

How InsightWorker handles it

1
Schedule a daily 6 AM scan with cron — '0 6 * * 1-5'. scheduler · cron syntax
2
Walk /Submissions/<LOB>/ folders. For each, check last-modified-date plus the most recent broker email in the folder. sharepoint_list · search_emails
3
Anything >7 days with no recent activity gets queued. Threshold is configurable per LOB in a playbook. agent reasoning · playbooks
4
Compose a list with insured name, broker, days since last activity, TIV (parsed from the SOV), and a deep-link back to the SharePoint folder. create_excel · agent reasoning
5
Email the team lead — HTML body with the table inline, Excel attached for filtering. Subject: 'X stale submissions need attention'. send_email · HTML body
6
Optional second pass: for each stale submission, pull the broker thread and draft a polite 'still considering, here's where we are' reply. Saved as markdown for the underwriter to send manually — never auto-sent. search_emails · email-draft-reply skill
7
Iterate the email format with --dry-run before going live with the team lead distribution. schedule run --dry-run

Sample prompt

"Find all submissions in /Submissions/Property/ with no activity in 7+ days and email the property team lead a daily digest."
Deliverables: stale_submissions.xlsx · daily_digest.html · drafts/broker-reply-<insured>.md (optional)
Prefer the browser?
Run this in InsightStudio — no CLI install for the user.

Authors publish the app once with iw app publish; business users open it in the marketplace and click Run. Your worker box does the execution.

Visit InsightStudio →

Try this use case yourself

Free trial available — CLI, Desktop, VS Code, and the new --worker mode for InsightStudio. See download for details.

Download Free Trial