When more than one person from a supplier communicates, buyers can lose track of who has authority and what was approved. The working method below keeps names, roles, statements, and approvals connected so you can move to the next sourcing decision with a visible record. Apply these steps to calls, emails, chat messages, and factory visits.

Build a contact map and authority matrix first

Start by listing every person you interact with for a supplier and assign a role label you and your team will use consistently. Use simple role categories such as sales, account manager, technical, production, quality, and finance. Add columns for preferred channel, language, working hours, and whether they can give commercial commitments, technical approvals, or only provide information.

Convert that list into an authority matrix that states who can approve price, lead time, tooling changes, spec deviations, samples, and invoices. The matrix does not need legal force but gives your team a shared expectation. If a person claims authority outside the matrix, record the claim in your log and ask for written confirmation from the person who appears to hold higher authority.

• Fields to capture in the contact map: full name, role, email, phone, chat ID, language, time zone, decision rights
• Authority categories: commercial approval, technical approval, sample sign-off, release to production, billing and payment

Create a single-source contact log and naming convention

Use one primary repository for every supplier contact entry. This can be a shared spreadsheet, a CRM record, or a simple document management folder with a controlled filename pattern. The key is that your team always adds new interactions to the same place so history is continuous and searchable.

Adopt a concise naming convention for entries that includes date, supplier short name, contact initials, and topic. For example, 2026-08-01_SUPPLIERX_LW_sample-feedback. Consistent names make it faster to find the original message, and they help when you need to link a log entry to a purchase order, specification version, or inspection report.

• Minimum log fields: date and time, contact name, role, channel, short summary, evidence link, decision tag
• Optional fields: meeting attendees, language, translator used, risk level, follow-up deadline

Record conversations as actionable, source-linked entries

Every time a supplier explains a constraint, commits to a change, or gives a timeline, enter an actionable summary into the log. Write a one-sentence summary of the statement, then add an action item and owner for your team. Attach the original source: forward the email, paste the chat snippet, or upload the meeting minutes and timestamp the excerpt.

When someone makes a commitment, capture who is committing and the exact words or numbers used. If the commitment is verbal, follow up immediately with an email that restates the commitment and asks the supplier to confirm in writing. Add both the verbal summary and the supplier reply to the same log entry so the progression from claim to confirmation is visible.

• When documenting a statement include: exact phrasing or numbers, context, whether it was a question or a commitment, and next steps
• For meetings, add a short attendance list and list decisions made with assigned owners

Capture approvals and designate acceptable evidence

Decide what counts as an approval for different categories. For price and payment terms, an emailed and signed price confirmation can be acceptable. For technical changes, require a revised specification document or a sample sign-off. Record the format (email, signed PDF, electronic signature, confirmed chat) and which incident types require stronger evidence.

When you accept an approval, enter the approving person, their role and authority from your matrix, the evidence file, and the approval scope. If the approver lacks clear authority, note that the approval is pending higher-level confirmation and send a request for formal sign-off. This reduces future disputes about who said yes.

• Common evidence types: stamped PDF, email from named approver, recorded meeting minutes, photo of physically signed document
• Flag approvals that require escalation and set a reminder to verify before production release

Link records to documents, versions, and purchase steps

Keep every contact log entry linked to the document versions it affects: specifications, CAD files, sample photos, quotes, POs, and inspection reports. Note the exact version number or timestamp so you can show which specification was in force when a decision was made. This prevents mismatches between what a supplier believed they were approving and what you intended.

Use a version control field in your log. When a supplier proposes a change, create a change request entry and assign it a change ID. Track its lifecycle from proposal to trial sample to approved revision or rejection. This creates a clear audit trail that ties people, statements, and document versions to the final sourcing decision.

Use the record to make the next sourcing decision and review regularly

When it is time to make a sourcing decision, review the contact log filtered by decision tags: price, capacity, quality approval, or lead time. Confirm that the required approvals are present and that approvers matched the authority matrix. If any approvals are missing or come from unauthorized persons, use the log to craft a single follow-up request so you do not create additional contradictory entries.

Schedule brief weekly or milestone-based reviews of the log with your procurement and product teams. These reviews can identify recurring gaps, ambiguous authority claims, or communication silos. Use the findings to update the contact map, tighten evidence requirements, or adjust who on your team must receive confirmations before a purchase order is released.

Create a contact-map sheet for one supplier and add entries for the last three interactions now.