Vendor incident management: problems documented the moment they occur
When a vendor underperforms, it needs to be documented immediately, not reconstructed from memory three months later. Evalystar logs incidents the moment they happen, tied to the job, the site, and the review that triggered them.
Why vendor problems go undocumented
Facility managers know the situation: something goes wrong, there is a conversation, maybe an email chain. Then the contract comes up for renewal and nobody can find the paper trail.
Problems reconstructed from memory
Something goes wrong. There is a conversation, maybe an email. Three months later when the contract comes up for renewal, nobody can find the paper trail. The incident gets reconstructed from partial memory, or not at all.
Low scores with no follow-through
A reviewer submits a 2-star rating and moves on. No incident is logged. No one follows up with the vendor. The score sits in a report while the underlying problem continues. Documentation only happens when someone remembers to do it.
Problems that never show up in scores
A vendor no-shows. A billing dispute goes unresolved for weeks. A safety issue gets raised in a site visit. None of these appear in evaluation scores; they require a separate record, and without a structured place to put them, they disappear.
From first incident to renewal evidence, every problem on record
Evalystar creates a structured incident record at the moment of the problem, not at the moment it becomes convenient. Every incident logged during a contract term becomes part of the renewal evidence package.
Configure two thresholds per company. When a reviewer submits a rating below the first threshold, Evalystar prompts them to log an incident. Below the second threshold, the incident is created automatically, with no action required. The source evaluation, job, vendor, and site are all pre-populated.
Any team member with the right role can open a job and log an incident directly, useful for problems that do not show up in scores. A vendor no-show, a billing dispute, a safety issue, a conduct complaint. Incidents are not limited to what the evaluation form captures.
Each incident captures a title and description, one or more categories (quality, billing, safety, compliance, communication), a severity level (high, medium, low), and the full context: which vendor, which job, which site, who reported it. Nothing falls through the cracks.
Every incident shows up in the incidents report and in the vendor's performance record. At renewal time, the incident history is an explicit input to the AI renewal feedback, not just the average star rating.