Automatic re-evaluation

When monitoring spots that a competitor shipped something — a new entry in their release notes, changelog or blog — Vector can re-check that competitor against your features on its own, and update the comparison without waiting for you.

​

Keep the comparison current automatically

Open Monitoring and go to the Settings tab. Two switches control this, and both are on by default:

• Auto-update side-by-side comparison when monitoring detects a change — re-evaluates the competitor as if you’d clicked Evaluate vs comparison in their dossier.
• Create a new dossier revision after auto-update — saves each automatic re-evaluation as a new version in the competitor’s dossier, marked as automatic.

Automatic re-evaluation runs only while both are on. The first switch can’t be turned on while the second is off, and turning the second off stops re-evaluation too — monitoring then just logs the change and notifies your Inbox. The settings apply to the whole workspace, not to individual competitors.

​

Decide whether it’s worth the cost

Each automatic re-evaluation is a paid AI run on your AI key, on top of the ones you start yourself. Keep it on if you want the comparison always current. Turn it off if you’d rather decide when evaluations run — then re-evaluate a competitor from their dossier when you choose.

​

What starts a re-evaluation

Only a change in a source that says something about features:

• release notes
• changelog
• blog
• resources of the Other kind

Changes to pricing, help and docs pages, the feedback portal, social media, reviews or job postings never start one, whatever your settings; they’re logged and notified as usual. A change held for review because Vector isn’t confident in it doesn’t start one either, until you confirm it. See Finding confidence and feedback. To avoid repeat runs, a competitor is re-evaluated automatically at most once every 24 hours, and never twice at the same time.

​

See what a re-evaluation changed

When a re-evaluation finishes, you get an Inbox notification saying it ran after a change on that source, and listing which feature statuses changed, from what to what. Its link opens the source page. The new version in the dossier is marked as automatic, so you can tell it apart from one you ran yourself. If nothing changed, no new version is created — the check log records that the competitor was re-evaluated with no changes, so the dossier’s history isn’t padded with duplicates.

​

Find out why a re-evaluation didn’t run

Every automatic re-evaluation — including the ones skipped — is recorded in the Check log, with the reason: If a re-evaluation fails, the failure is recorded the same way, and monitoring carries on as normal.

​

Where to go next