Keep supplier documents current without chasing everyone

For each required document, keep a record of who needs to provide it and what it must cover. This makes it easier to spot a missing document or one that belongs to another site.

Record the supplier and facility, required document type, relevant scope, expiry or review date, owner and acceptance decision. Use the document’s stated expiry when it has one. If it has none, follow your program’s review policy rather than inventing an expiry.

Requirements may differ by product, customer and supplier relationship. Before chasing a replacement, confirm that the requirement still applies. Otherwise, teams can spend time collecting records they no longer need.

Work backwards from when acceptable evidence is needed. Allow time for the supplier to obtain the replacement, your team to review it and a correction if it is incomplete.

For example, if replacement usually takes 20 working days and review takes 10, starting a week before expiry is unlikely to leave enough room. Those are planning assumptions, not a standard renewal timetable. Use your actual supplier lead times and business calendar.

Put the first request and next review date in the record. A reminder should say what is needed, which facility it must cover and where to send it. Avoid asking a supplier to resend every document just because one is due.

Check the replacement against the requirement: correct entity and site, appropriate scope, usable dates and any verification your program requires. Keep the earlier version and the reason for accepting or rejecting the new one.

In the example above, the new certificate belongs to another facility. Closing the task would hide the remaining gap. Return a specific question so the supplier knows what to correct.

If acceptable evidence will not arrive in time, route the decision to the person responsible for the program or order. Do not let an automated reminder system silently approve an exception or block all supplier activity.

AI can extract names, dates and scope from documents that arrive in different layouts. It can then propose a match to the requirement record. A reviewer still needs to check that the document meets the requirement and complete any authenticity checks your program calls for.

Keep the original visible and flag uncertain matches for review. A date-based reminder can use ordinary rules once the date is checked; it does not need AI. Test with wrong-site documents, unclear scans and records with no expiry before expanding the workflow.

Start with one document family. Measure reviewer time, repeat requests and renewals accepted before they are needed. Count avoided order holds only when you can connect the earlier renewal to an actual decision.