On this page
An incident and a lawsuit can create different work
The selected Insurance Services Office (ISO) CG 00 01 04 13 base form calls for practicable notice of potentially claim-producing events and claims, and immediate recording/forwarding of specified claim and legal papers. Actual amendments and applicable law must be checked.
The owner’s weekend availability should not decide the route
Fictional example: on Friday, a U.S. customer emails a service supervisor that a repaired pump leaked and damaged nearby stock. The supervisor files the email as a warranty complaint. The overseas owner sees the monthly report three weeks later.
The business has combined two workflows: assessing the pump remedy and communicating a potential liability incident. Set up a route that reaches the authorised policy handler without waiting for the owner’s monthly review. Continue any necessary safety and damage-protection response through qualified people; reporting is not an instruction to defer it.
| Record | Decision to resolve |
|---|---|
| Initial report | Preserve original words, sender, receipt date/time and affected customer/site. |
| Known facts | Equipment/work identity, alleged damage, incident timing and current uncertainty. |
| Notice route | Actual policy contact/channel; responsible sender and backup. |
| Receipt and follow-up | Confirmation, reference and requests for further information. |
| Later papers | Send demands or legal papers through the required route immediately on receipt. |
Rehearse an escalation without a real incident
Use invented customer details to test who opens an urgent message, finds the current policy contact and records delivery. Check coverage of holidays, staff absence and a supervisor leaving the business. Keep the real evidence in approved systems with access controlled.
Insurance notification, customer reporting, product-safety assessment and government injury reporting can have different triggers and deadlines. This page supplies no universal number of days and makes no finding about fault or cover. Use Launch dependencies to assign the notice process; a task marked complete does not prove a future report was delivered.
Scope
- Selected historical base-form condition; actual endorsements, legally effective notice, deadlines and any consequences of delay require policy/jurisdiction review.
Next step
Use Launch dependencies to assign the incident-notice process and rehearsal. Keep reports, papers, policy communications and any sensitive records outside the tool.
Sources & review notes
Insurance Services Office; insurer policy packet published by BMP Management
Passage, dates and research notes
primary · Base form printed pages1–2,10–15; packet declarations/form schedule and modifying endorsements CG 24 26 and BP 04 48 inspected; no whole-policy coverage decision
Selected actual body read. Source identifies a limited framework or named form; no actual business policy, insurer approval or coverage outcome established.
Detailed rule records (1)
The selected ISO base-form condition requires event/claim notice and forwarding/recording of specified papers; actual wording and law govern.
Published 2023 Sage Springs policy packet — selected ISO CG 00 01 04 13 base-form clausesBookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.