All solutions

Insurance

The 2nd payment on the same claim

One action worth checking.

Your agent settles routine claims. A licensed adjuster holds the rest.

A payout or policy change can commit the business before the right reviewer sees it.

HELD AT THE GATE

Second payment on the same claim — Hold for adjuster [Team+]
Routine claims settle themselves. Runledge catches the ones that shouldn't.

A limit for the consequential change.

ActionGateDecision / record
01

Estimate under $2,500

Allowed

Allow

routine claims should settle at machine speed; that's the efficiency the agent was bought for.

02

Estimate or settlement above the authority limit

Held

Hold for licensed adjuster

above the settlement-authority limit, the decision belongs to a licensed adjuster, not the agent.

03

Policy reinstatement

Held

Hold for adjuster

reinstating the wrong policy resurrects coverage that was deliberately ended.

04

Second payment on the same claim

Held

Hold for adjuster [Team+]

duplicate payments slip out precisely because the claim already looks handled.

05

Instructions hidden in an uploaded estimate or document

Held

Hold for adjuster (detection)

a contractor's PDF should not be able to tell your agent to approve it.

06

One agent's settlements pass the daily spend cap

Held

Hold, spend cap [Team+]

the rule checks recorded spend and the proposed settlement; strict ceilings need serialized writes because parallel checks do not reserve spend.

07

Second or upward-revised estimate on the same claim

Held

Hold [Team+]

a repeat or upward revision changes the claim decision; a human checks what changed before it proceeds.

08

Settlement to a contractor or payee not on the approved list

Held

Hold

a claim reference does not approve its recipient; a human checks the contractor or payee before settlement.

09

Estimate sent to a repair shop carries the policyholder ID

Adjusted

Adjust: mask the policyholder ID to its last 4

the rule masks the policyholder ID in the returned estimate; your integration must use that version after the re-check.

10

New claim created from a first notice of loss

Held

Hold for adjuster assignment

the claim doesn't exist until the agent creates it — the first write is the moment to check it, before it lands on the wrong queue or under the wrong coverage.

11

Policy document drafted by the agent for issue

Held

Hold for review before issue

the agent drafts the document; it is not issued until a human validates the draft — the approval is what turns the draft into the issued document.

12

Claim assigned by an agent

Held

Hold for 1 reviewer

assignment decides who owns the claim and what gets looked at first; a misrouted claim sits invisible until the claimant complains.

13

Document filed to a claim

Held

Hold for 1 reviewer

once a document is in the claim file, every later decision trusts it; the wrong document in the file quietly poisons estimates, reviews and settlement.

Review requirements for this workflow

Held for review — owner email approval on Pro; Slack and Teams review on Team. Team supports up to 2 reviewers in one stage; Growth adds a second approval stage with up to 5 reviewers per stage. Named finance leads, adjusters and supervisors must be eligible workspace reviewers; Runledge does not verify professional licences.

Rolling-count and spend-cap Holds, and entity-counting Holds, require Team or above. Start free to test policies in Shadow; the review workflows shown require the applicable paid plan. Shadow is delayed, aggregate and report-only, with a free 14-day shadow pilot per workspace; afterward Shadow Held, Blocked and Adjusted outcomes count toward the allowance.

One billable action is one recorded Held, Blocked, or Adjusted outcome; Allowed actions are free. Your integration must honor the decision and execute only the permitted version. Account, payee and destination checks use the fields and approved lists you supply, not independent bank or claims verification. Adjusted examples mask or drop fields before re-checking every rule; they do not guarantee safe downstream handling. Approval records are evidence of review, not a certification or an audit guarantee.

Security and data handling →

What's your scariest agent action?
Test it in shadow mode first.

Start free with the Developer plan — 10,000 actions every month. Start in shadow mode, then block actions when you trust the rules (or hold for review on Pro and above). Shadow is free during the 14-day shadow pilot for each workspace. After the 14-day shadow pilot, shadow Held, Blocked, or Adjusted outcomes count toward your plan like enforcing mode does.

Start free

Where this goes: the same rules and signed records, between companies.

Need a security review, in-VPC deployment or a custom contract? Leave your work email and we will reply within one business day.