One trusted renewal follow-up per Company

Task automation starts only after monitoring has been activated. A new task requires:

• The canonical RenewalResolution is task-eligible.
• The Company is eligible for tasking.
• The resulting Renewal Risk is actionable under the production rules.
• The existing Sighub task lifecycle and account controls allow creation.

Renewal Risk severity answers “how urgent is this account?” Timing confidence answers “how trustworthy is the renewal date?” A Company can be High or Critical risk while its timing is still too uncertain to automate.

This is why a Low-confidence estimate can remain visible in monitoring but cannot become a HubSpot task trigger.

Renewal Radar tasks use a Sighub: subject, are associated with the Company, and include concise renewal evidence and the recommended next step. Assignment follows the configured routing: Company owner or one selected HubSpot user.

Sighub maintains at most one owned renewal follow-up per Company. A change in winning source, source record, or policy version does not by itself create a second logical task.

• If the same actionable canonical renewal risk remains, the existing open task stays.
• If complete authoritative evidence shows the risk cleared, Renewal Radar can complete the task.
• If required timing or signal data is temporarily incomplete or unavailable, Renewal Radar does not treat that as proof that the risk disappeared.
• Per-account controls such as Renewed, Lost, snooze, healthy overrides, or exclusion continue to affect task lifecycle as documented in Risk controls.