Build a supplier evidence folder that stays useful across customer requests

A useful supplier evidence folder has a memory. It should show which record supports which customer answer, where that answer stops being valid, and who needs to review it when the record changes. Saving another copy under a customer’s name makes retrieval easier today but can leave several conflicting versions tomorrow.

This guide is for suppliers maintaining evidence across successive customer requests. The worked case is entirely fictional. Its purpose is to build a small reusable catalogue and a customer-release history, so that a correction can be followed through to the answers that actually used it.

Give each evidence item a stable identity

The US Geological Survey’s metadata guidance explains why context is needed to interpret and reuse data, and recommends keeping data and its descriptive record together. That scientific-data principle informs this voluntary business exercise; USGS requirements do not become supplier reporting obligations.

Use an evidence ID that stays with an item through its revisions. Keep a separate version for each approved revision. An ID such as EN-N-26 identifies the North site’s electricity schedule for April 2025 to March 2026; v1 and v2 identify different versions of that schedule. Neither the ID nor a folder named “approved” establishes that every customer can receive it.

For each item, maintain a short catalogue entry:

• Identity and scope: evidence ID, description, legal entity, included sites, period and unit where relevant.

• Source and version: controlled file location, precise source references, version, preparation date and the person responsible for resolving questions.

• Use limits: what the record can support, known exclusions, review status and any trigger for another check.

• Sharing route: the responsible approver, restrictions and the approved recipient or use. Leave unresolved permission visibly unresolved.

A small spreadsheet can hold this catalogue while the actual files remain in the organisation’s approved storage. The index should point to the controlled item. Customer folders can contain a release copy or an approved reference, but should not become competing master records.

Separate reusable evidence from customer answers

In the fictional supplier, two items are available. Policy P-01 v3 covers the North and South sites and is approved for the specified customer sharing. Electricity schedule EN-N-26 v1 covers only North, for April 2025 to March 2026, and states 84,600 kWh. It has a retained trail to the relevant monthly records. South’s schedule is still being prepared.

Three customers ask different questions. The supplier records each decision before issuing a response:

• Customer A, release A-04: asks for North’s electricity use in the stated financial year. The approved answer uses EN-N-26 v1 and names its site, period and unit. The release record identifies the exact shared version and authorised recipient.

• Customer B, release B-02: asks for the current environmental policy covering both sites. The approved attachment is P-01 v3. No electricity schedule is needed for that question.

• Customer C, request C-07: asks for the combined electricity use of North and South for the same year. EN-N-26 can support the North component, but no combined answer is issued while South’s records remain unresolved.

The same evidence may be useful in several requests without making the answers interchangeable. Customer C has asked a wider question than A. B has asked a different kind of question. The catalogue stores the evidence; the release history stores the meaning, permission and exact version of each customer answer.

Follow one correction through the customer history

The supplier discovers that one 700 kWh entry was counted twice in EN-N-26 v1. After checking the affected schedule and its source trail, the owner approves v2 at 84,600 − 700 = 83,900 kWh. The illustration assumes this is the only correction; it does not establish a method for estimating missing consumption.

Keep v1 as superseded history and record why v2 replaced it. Search the release history for EN-N-26 v1, rather than sending every customer the entire folder again. The resulting review has three different outcomes:

• A-04 is affected. Its recorded answer used v1. The authorised owner follows Customer A’s correction process, retains the original submission and records the corrected answer, approval and dispatch evidence. An internal revision alone does not prove that the customer received a correction.

• B-02 is unaffected by this correction. Its only evidence reference is P-01 v3. Record that conclusion so a later reviewer can see why no revised policy attachment was needed.

• C-07 stays pending. Update its proposed North component to v2, but keep the missing South component open. A corrected North total still does not answer a two-site question.

The arithmetic is small; the dependency check is the useful work. It identifies one issued answer requiring review, one issued answer outside the correction’s scope and one unissued answer that remains incomplete. These are case outcomes, not a measured reduction in work or a supplier performance score.

Original fictional dependency example. EN-N-26 v2 replaces v1 after a 700 kWh duplicate is removed. Trace each customer answer to its evidence version; retain prior releases and the authorised correction record.

Make the next request a deliberate reuse decision

Before reusing an item, compare the new request with the catalogue entry. Check the entity and site, period, measure, version and permitted use. A North-site annual total cannot answer a calendar-year or product-level question simply because the number is already approved. Record a new answer when the question changes, even if some supporting evidence stays the same.

Keep four items together in each release record: the customer’s question and clarification, the answer actually submitted, the evidence IDs with exact versions, and the approval and sharing record. Store material qualifications with the answer, so a short portal field does not become the only surviving account of what was agreed.

Assign a folder owner and practical review triggers, such as a source correction, a new reporting period, a site change or a revised customer purpose. Apply the organisation’s retention rules rather than deleting superseded evidence merely to tidy the folder. Test that an authorised colleague can find one released answer and trace its evidence without asking the original preparer.

For one questionnaire’s response decisions, use the supplier questionnaire guide. When sharing is restricted, use the confidential evidence guide to resolve the permitted route. The reusable folder’s job is to preserve those decisions and keep later changes connected to them.

Source checked 14 October 2026. Credit: U.S. Geological Survey. The supplier, evidence IDs, quantities and customer releases are original fictional teaching material. This workflow does not authenticate documents, grant sharing permission or provide independent assurance.