How complete are supplier contacts before an assistant uses them?

Question and scope

This review asks how complete a supplier contact record is before an assistant uses it to act. The unit is one supplier contact used for a routine or urgent request. The scope covers suppliers that support client work, payments, deliveries, or software. The review does not estimate a universal completeness rate, because the supplier mix and the risk level vary.

The question matters because an incomplete contact record can cause a delayed delivery, a missed payment, or a fraudulent change. The assistant may have a name but not a role, a channel, or a limit. The record looks usable until the moment it is tested. A short verification before use is cheaper than a correction after the fact.

The review separates a missing field from an unverified field. A record may have a phone number that was never checked, or a role that was copied from an old email. The field exists, but it may not be current. Completeness includes verification, not only presence.

The review also asks whether the assistant knows the limit of the contact. A record may name a person but not say whether that person can approve a payment change or only a delivery date. The limit is part of completeness because it tells the assistant when to pause. An unclear limit turns a routine request into a guessing game.

Build the sample

Take the suppliers the assistant contacted in the past month. Include routine orders, invoice questions, delivery changes, and urgent issues. Add the suppliers that appear in the client contract even if they were not contacted. The sample should cover the relationships that matter, not every company in the directory.

For each supplier, record the contact name, role, company, channel, hours, backup, and the last verification date. Add the account reference and the risk level. If a field is missing, record it as missing rather than leaving it blank. The blank may hide a gap that the team has learned to work around.

Compare the record with the source that created it. The source may be a contract, a supplier email, or a client introduction. If the record cannot be traced to a source, mark it as unverified. A name without a source is a guess that may have been repeated for years.

Record the last time the contact was used and whether the request succeeded. A contact that has not been used in a year is more likely to be stale. A contact that failed recently is a priority for repair. The usage history helps rank the findings.

Define complete

A complete contact has a named person, a role, a verified channel, and a reason to contact them. It also has a backup and an escalation path for urgent work. The record should show the last verification date and the source. Without those, the team cannot tell whether the contact is current.

The required fields should match the risk. A low-risk stationery supplier may need only a general support line, while a payment processor needs a named account manager and a verified escalation path. Do not apply the same template to every supplier. The risk level should decide the depth.

A complete record also states what the assistant may do without approval. A delivery reschedule may be within scope, while a bank detail change is not. The limit belongs beside the contact. The assistant should know when to pause and ask the account owner.

Measure completeness

Report the share of contacts with every required field and the share missing at least one. Add the share with no verification date and the share with a channel that was never tested. The four numbers show whether the record is present, current, and usable. Read them together rather than reducing the result to a single score.

Group the results by supplier risk and by client. A high-risk supplier with a missing escalation path is a bigger finding than a low-risk supplier with no backup. A client with many unverified contacts may need a different onboarding step. The grouping helps prioritize the repair.

Compare the record with the outcome of the last request. A contact that worked may still be incomplete for an urgent case. A contact that failed may be complete on paper but wrong in practice. The comparison shows whether the fields predict a usable path.

Why records decay

A supplier record decays when a person changes role and no one updates the sheet. The old name may still receive email for a while, which hides the change. The next urgent request reaches the wrong person. The fix is a verification step at each supplier contact, not only a yearly review.

A record also decays when the channel changes. A supplier may move from phone to a portal, or from a personal email to a support queue. The old channel may still appear to work for routine messages. The urgent case reveals that no one is monitoring it. Test the channel before relying on it.

A third cause is a record created from an invoice or a marketing message. Those sources may contain a sales contact rather than the account manager. The record looks complete but points to the wrong role. The fix is to verify against the contract or the client introduction.

A fourth cause is a supplier that changes its own support model. A named account manager may be replaced by a shared queue or a portal. The old record may still work for a while, which hides the change. Ask the supplier to confirm the current path at each contract review.

Controls that help

Require a source and a verification date for each contact. Make the source a link or a document reference, not a name alone. Review the unverified contacts first and either confirm or remove them. A short verified list is more useful than a long unverified one.

Test the channel before an urgent request. Send a routine message and confirm a reply, or call the number on the contract. Record the result. A channel that has not been tested is a hope, not a path. The test is especially important for payment and delivery contacts.

Review the sheet when a supplier or client changes. Add the review to the quarterly client check-in and the supplier onboarding. Record the change and the person who verified it. The sheet should describe the current relationship, not the one from last year.

Keep a short risk tier beside each supplier. The tier decides how often the contact is verified and how much detail is required. A payment supplier may need a quarterly check, while a stationery supplier may need a yearly one. The tier keeps the review proportional to the risk.

Method and limitations

This review describes a local completeness check rather than a study of supplier records across providers. The sample depends on the contacts the team uses and the records available. Some suppliers may be reached through a client contact who is not in the sheet. The result is a floor rather than a full census.

The review may also change behavior. The team may verify contacts more carefully because the sample is being checked. That effect is useful, but it makes the first period a weak baseline. Use a later period and note when the review began.

The sample should also include a supplier that was never contacted. A record can look complete because no one has tested it. Including an unused supplier shows whether the sheet is maintained for the whole relationship or only for the busy accounts. The comparison is useful even when the sample is small.

Decision checklist

List the suppliers used in the past month and the fields needed for each risk level. Add the source, verification date, backup, and assistant limit. Mark missing and unverified fields separately. Use the same fields for every supplier at the same risk level.

Report the complete, incomplete, unverified, and untested shares. Group by supplier risk and client. Require a source for new contacts. Test the channel and review the sheet after every change.