What you decide before you start
Two things are yours to decide.
- The threshold. From your filing. It is one number in one expression.
- Scope — which policy types are included. Each needs its own copy of the configuration. Remember any type closed to new business that still renews.
Everything else already has an answer.
Days of notice is not set by this feature. It is the Renewal Invoice offset on each billing schedule — a number of days before the policy term expires. The renewal commits on that date and the notice carries it. Changing it moves renewal invoicing for your whole book, so it should not be adjusted to satisfy a notice requirement. The check is a single comparison: read the offset off your billing schedules and see whether your filing demands more. If it does, the issue is renewal timing rather than the notice.
Renewal timing needs nothing done. The notice and the declaration both carry the commit date, so they join the same print run automatically. They only separate if a renewal is committed far ahead of its term.
No agent or agency copy is created. The notice is generated once per recipient your site already sends declarations to, which in the ordinary case is the named insured alone. If you want an agency copy, that comes from your existing declaration-copy settings and is a separate change.
Renewals committed before you go live get nothing. The rule fires when a renewal is committed; one already committed never fires it again. There is no configuration that changes this — if the gap matters, raise it with BriteCore as a separate piece of work.
You will need Administrator access to Lines configuration, and a UAT site to test on.
