Stop expired vendor insurance from reaching the dispatch queue

A property management vendor COI tracking workflow keeps certificate status connected to dispatch. It collects the certificate, extracts policy and identity fields for review, schedules renewal reminders, pauses unsafe assignments, and records every decision. The automation organizes evidence; an authorized person decides whether the vendor meets the company’s requirements.

That separation matters for operators managing 50 or more units. A PDF in an inbox is not the same as a verified certificate, and a green vendor record is not useful if the dispatcher cannot see it. The workflow belongs between vendor onboarding and the vendor dispatch process, where a stale record can become a real assignment.

Vendor compliance is also a strong first example of how to automate property management. It has a clear trigger, required fields, a review boundary, exception paths, system updates, and measurable outcomes. It should not replace legal or insurance review, and it should never invent approval from an incomplete document.

Why COI tracking breaks at dispatch

Most failures are not caused by a missing spreadsheet. They happen because certificate collection, verification, renewal, and work-order assignment live in separate places.

Accounting may receive a certificate during onboarding. A maintenance coordinator may keep a different vendor list. A regional manager may approve an exception in email. Months later, the dispatcher sees only that the vendor completed three prior jobs and assumes the record is current. The document may have expired, the legal name may not match, or the approved certificate may cover a different entity.

The workflow must make one question easy to answer: what evidence and approval support this vendor’s status for this assignment right now? That requires the same field discipline used in property management CRM workflow automation: structured state, a named owner, timestamps, and visible next actions.

Build one vendor compliance record

Start with a stable vendor identifier, not a file name. Store the vendor’s legal name, any doing-business-as name, contact, tax or internal vendor ID, approved work categories, linked properties, and responsible reviewer. Then attach the certificate as evidence.

Capture certificate fields as structured data:

• issuing agent and certificate source
• named insured and matching vendor entity
• policy types and policy numbers
• effective and expiration dates
• limits or endorsements required by the operator’s policy
• certificate holder information when applicable
• received date, extracted date, reviewer, and review decision
• original document, replacement versions, and decision notes

Field extraction can draft this packet, but it cannot silently approve it. A blurry date, unfamiliar endorsement, legal-name mismatch, or missing page should create a review task. Keep the original document beside the extracted values so the reviewer can compare evidence instead of trusting a summary.

This record should also connect to the vendor’s operational history. A vendor quote collection workflow may identify the preferred contractor, but price and availability do not override an unverified compliance state.

Use explicit states and dispatch rules

Avoid one vague checkbox labeled “insured.” Use states that tell staff what can happen next:

1. Requested: The vendor has been asked for evidence, but no usable certificate is on file.
2. In review: A document arrived and fields were extracted, but an authorized reviewer has not approved it.
3. Verified: The reviewer confirmed the required fields and recorded the approval and expiry date.
4. Expiring: The approved certificate is within the operator’s reminder window.
5. Blocked: Evidence is expired, missing, mismatched, rejected, or superseded without an approved replacement.
6. Exception approved: A named manager authorized a time-limited exception under a documented policy.

Only the operator’s approved states should unlock new assignments. When a coordinator starts maintenance scheduling, the dispatch step should check the vendor ID, work category, property, compliance state, expiry time, and any exception boundary. A certificate verified for one entity or category must not automatically authorize another.

Do not let the rule hide emergencies. If a work order contains defined life-safety or habitability signals, follow the company’s emergency procedure and escalate to an authorized manager. The system may warn that evidence is expired, but it should not improvise a legal or operational decision.

Start reminders before the certificate expires

A single reminder on the expiration date is too late. Create a staged sequence based on the operator’s renewal window, such as 30, 14, and 7 days before expiry. Each message should identify the vendor, certificate, expiration date, accepted submission path, and staff owner.

When a replacement arrives, link it as a new version. Do not overwrite the prior file or change its old approval timestamp. The workflow should compare entity names and dates, open a review task, and leave the current status unchanged until the replacement is verified. This is an evidence-versioning problem, not a document-storage problem.

If the final reminder passes without approved evidence, change the state according to policy and notify the people who control upcoming assignments. The same alert should identify open estimates, scheduled visits, and unresolved work orders that may be affected.

Give humans a focused exception queue

Human review should concentrate on decisions, not inbox searching. Route cases when the named insured does not match the vendor, required fields appear incomplete, dates overlap or contain gaps, the document is unreadable, the vendor disputes a hold, or an urgent repair cannot wait for the normal renewal path.

The reviewer needs the certificate, extracted fields, vendor record, affected work orders, previous decisions, and the exact rule that stopped dispatch. They should be able to approve, reject, request corrected evidence, or grant a time-limited exception if policy allows. Log the reviewer, decision, reason, expiration, and linked assignments.

Permissions matter. The lessons in AI agent permission controls apply here: document parsing does not require unrestricted PMS access, and an automation should not change vendor approval, release payment, or dispatch work beyond its authorized scope.

Write the decision back to the operating record

The vendor record should expose the current state, verified-through date, reviewer, evidence link, and next action. Each affected work order should record the compliance check performed at assignment, its result, and any exception ID. That gives maintenance, accounting, managers, and auditors the same answer without copying sensitive documents into every tool.

Use supported APIs, middleware, tasks, notes, or document links based on the actual platform and permissions. The same writeback discipline used in maintenance intake automation applies: preserve the source, do not claim a status the system cannot verify, and make failed writes visible to staff.

At closeout, retain the assignment-time decision with the work record. A clean work order closeout workflow should show which vendor performed the work, which compliance state was checked, and who approved any exception.

Measure risk prevented and renewal speed

Track the share of active vendors with a currently verified certificate, certificates inside each reminder window, and median time from first reminder to approved replacement. Count dispatches held before an unverified vendor was assigned and exceptions approved, denied, expired, or closed with corrected evidence.

Also audit false blocks and missed holds. If staff repeatedly bypass the workflow because names do not match across systems, fix vendor identity mapping. If a blocked state never reaches the scheduling queue, fix the handoff rather than sending more reminders. Metrics should reveal whether the control changes real assignments.

Roll out with one vendor category

Begin with one property group and one frequently dispatched category, such as plumbing or HVAC. Inventory active vendors, current certificates, required fields, renewal rules, emergency policy, approvers, and every place dispatch can begin. Define states and access permissions before automating reminders.

Run in shadow mode first. Let the workflow extract fields, calculate dates, and flag assignments while staff follow the current process. Compare every proposed hold with reviewer decisions. Then enable reminders, followed by visible warnings, and only then approved non-emergency dispatch holds.

Expand after replacement documents version correctly, exceptions expire automatically, failed writebacks reach an owner, and dispatchers can see the verified state without opening another spreadsheet. If your team still relies on memory to connect certificates with assignments, book a 15-minute workflow audit. EMC2Ops will map the evidence packet, review boundary, reminder timing, dispatch rule, exception queue, and safest system-of-record writeback.