Vendor incident management: problems documented the moment they occur
Evalystar documents a vendor failure at the moment it happens, rather than reconstructing it from memory months later. Each incident is logged against the specific job, site, and evaluation that triggered it, with a timestamp, notes, and photo evidence. Facility and operations teams use that record in escalations, chargeback disputes, and renewal reviews, where an undocumented complaint carries no weight.
Jobs 1284
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.
Common questions
What counts as an incident?
Any vendor failure worth a record: a missed service window, a job done badly enough to need redoing, a safety or compliance lapse, or damage caused during the work. It is logged against the specific job, the site, and the evaluation that triggered it.
Why log an incident if the evaluation already has a low score?
A low score is a data point; an incident is a documented event with a timestamp, notes, and photo evidence attached. The first shows a trend. The second is what you produce when a vendor disputes a chargeback or an auditor asks what happened.
Can incidents be linked to a contract renewal?
Yes. Incidents sit on the same vendor record as the scores and the contract documents, so the incident history is already assembled when the renewal review comes up.
Who logs an incident?
Usually whoever saw it, which in practice is on-site staff or a site manager rather than the person who owns the contract. Evalystar can also raise one from the evaluation itself: you set two rating thresholds per company, and a score below the first prompts the reviewer to log an incident, while a score below the second creates one automatically with the source evaluation, job, vendor, and site pre-populated. The rating is always submitted by a person; only the incident record can be automatic.
Configure your incident thresholds and start building the accountability record today
Start free. No credit card required. Set your evaluation thresholds, add your vendors, and let Evalystar document problems the moment they happen.
- A real person reads every message
- Demo requests get a tailored walkthrough
- Or skip the call: the Free plan needs no card