Supplier Issue Statement

Supplier issues reported through email or informal conversations give procurement and vendor management teams an inconsistent record of what went wrong, when it occurred, when it was discovered, how severe it is, and what resolution is being sought. Actions already taken to address the issue are not documented alongside the original report. Supporting evidence arrives as email attachments that need to be matched to the issue record manually. Without a structured, centralized intake process, managing supplier disputes and escalations consistently and maintaining an auditable record of each case requires more effort than it should.

The Supplier Issue Statement template for SharePoint, built with Infowise Ultimate Forms, provides a structured issue report form that captures the supplier's details, the issue category and severity, a detailed description, the date the issue occurred and the date it was discovered, prior actions already taken, supporting document uploads, the desired resolution, additional comments, and the reporting person's contact details. Every report is stored as a complete, auditable record in SharePoint.

How it works

Supplier details

The form captures the supplier name, contact person's name, contact email, and contact phone number. Capturing supplier contact details in structured columns within the issue record ensures the procurement team has everything needed to follow up with the correct person at the supplier without searching through correspondence or a separate vendor directory.

Issue category, severity, and description

A structured issue category column categorizes the report from the point of submission, enabling the procurement team to filter and group issues by type without reviewing every free-text entry. An issue severity column captures the assessed impact level. A detailed description column gives the reporter the space to document the issue comprehensively, providing the team with a written account that is consistent and actionable rather than a summary recalled from an informal conversation.

Issue and discovery timeline

The form captures both the date the issue occurred and the date it was discovered. Capturing both dates as separate structured columns is important for any situation where the gap between occurrence and discovery is itself relevant — for quality, compliance, or contractual purposes. The timeline creates a clear, documented chronology within the issue record from the moment of reporting.

Prior actions and supporting documentation

A prior actions column documents any steps already taken to address the issue before the formal statement was submitted, giving the reviewing team a clear view of what has already been attempted and what still requires action. A supporting documents upload column allows the reporter to attach photos, invoices, correspondence, or other evidence directly to the issue record, ensuring the full evidence base is stored alongside the formal statement.

Desired resolution and reporter details

A required desired resolution column captures what outcome the reporting party is seeking from the supplier, providing a clear basis for the procurement team to formulate and communicate the organization's position. An additional comments column captures anything not covered by the structured columns. The reporting person's name, email address, and optionally phone number are captured in a dedicated contact section, ensuring the procurement team has a clearly identified internal contact for follow-up.

What you get

• A structured supplier issue statement capturing supplier name, contact person, email, and phone number
• Issue category, severity, and detailed description for consistent, categorizable issue documentation
• Date of occurrence and date of discovery providing a complete issue timeline
• Prior actions taken and supporting document upload for a complete evidence record
• Desired resolution column establishing a documented basis for supplier engagement
• Reporter name, email, and phone number for internal follow-up contact
• Every report stored as a complete, auditable record in a standard SharePoint list
• Free for all Ultimate Forms customers, installed automatically with a single click

Built on standard SharePoint lists

The Supplier Issue Statement system is built entirely on standard SharePoint lists. There is no external data storage and no custom interface. All issue records stay inside your SharePoint environment, governed by your existing permissions and data policies. The system can be extended or adapted at any time in the browser by the administrator who manages the site.