Website Error Report

Website errors reported through email or informal channels give development and QA teams an inconsistent record of what went wrong, where, and under what conditions. The URL where the error occurred is not always included. The browser and device type are described informally or omitted entirely. Steps to reproduce the error are rarely documented at the point of reporting, meaning the development team must attempt to replicate the issue without a reliable starting point. Without a centralized, structured error reporting process, diagnosing and prioritizing website issues efficiently requires more back-and-forth than it should.

The Website Error Report template for SharePoint, built with Infowise Ultimate Forms, provides an error report form that captures the reporter's name, email address, and user role, the date and time the error occurred, the URL where it was encountered, the device type and browser used, a brief description of the error, the steps to reproduce it, the error severity, supporting screenshot or file uploads, additional comments, and an accuracy declaration. Every report is stored as a complete, actionable record in SharePoint.

How it works

Reporter identity and role

The form captures the reporter's full name, email address, and user role. Capturing the user role alongside the reporter's contact details gives the development team important context for assessing the error — an issue encountered by an administrator may indicate a different root cause than the same symptom experienced by a standard user, and the role determines which code paths and permissions were active at the time.

Error location and timestamp

The form captures the date and time the error occurred and the exact URL where it was encountered. Capturing both in structured columns at the point of reporting gives the development team the specific location and timing context needed to correlate the report with server logs, deployment records, or other recent changes, without asking the reporter to attempt to recall this information after the fact.

Device type and browser

Structured columns capture the type of device and the browser the reporter was using. Capturing the environment in which the error occurred is a prerequisite for reproducing it — many website errors are browser-specific, device-specific, or dependent on a particular combination of the two. Having this information documented at the point of report submission enables the development team to set up the correct test environment immediately.

Error description and reproduction steps

A required brief description column captures what the error was and how it manifested. A steps to reproduce column gives the reporter the space to document the sequence of actions that led to the error. Capturing reproduction steps in a structured column at the point of reporting is the single most valuable input the development team can receive — it transforms an abstract description of a problem into an actionable starting point for investigation.

Severity, screenshots, and accuracy declaration

An error severity column captures the impact level the reporter assigns to the issue, providing the development team with a triage signal. A file upload column allows screenshots or other supporting files to be attached directly to the report record. An accuracy declaration confirms the information provided is correct and complete.

What you get

• A website error report capturing reporter name, email, and user role
• Error date and time and the exact URL where the error was encountered
• Device type and browser for environment-specific reproduction and diagnosis
• Error description and steps to reproduce for actionable development triage
• Error severity, screenshot upload, and accuracy declaration
• Every report stored as a complete, actionable record in a standard SharePoint list
• Filterable by severity, browser, device type, or URL for efficient issue prioritization and tracking
• Free for all Ultimate Forms customers, installed automatically with a single click

Built on standard SharePoint lists

The Website Error Report system is built entirely on standard SharePoint lists. There is no external data storage and no custom interface. All error report 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.