The page includes a structured form for logging work, system, customer, or operational incidents from the start.
Issue type -> report detail -> submit
INCIDENT REPORT
Use Incident Report to submit work, system, operational, customer, or other issues that need management review, evidence, status tracking, and follow-up action.
Users submit the facts, attach supporting evidence, and track the report while authorized reviewers manage status and next steps.
Use this section to understand the incident-report features available on the page before opening a record.
The page includes a structured form for logging work, system, customer, or operational incidents from the start.
Issue type -> report detail -> submitUsers can record category, business unit, department, owner, date, priority, and descriptive context inside the report.
Category -> priority -> incident contextImages, videos, files, and other supporting proof can be attached to help reviewers understand the reported issue.
Upload file -> attach proof -> reviewer contextThe tracker view helps users find a ticket and review its submitted state, progress, and overall lifecycle.
Ticket list -> current status -> progress viewAuthorized reviewers can add remarks, update review status, and manage the next action directly from the incident record.
Remarks -> review action -> follow-upThe incident workflow collects the issue context, evidence, review state, and report history in one place.
Report work, performance, system, operational, customer, or other issues for management review.
Capture business unit, department, issue owner, category, title, description, date, priority, and order number where relevant.
Upload files, images, or videos, take a photo, or choose evidence from gallery and files before submitting.
This is the normal sequence from starting a report to sending it for review.
Start from the sidebar, page link, or dashboard shortcut.
Click Submit Incident Report or Start Incident Report to open the guided form.
Select Incident Report and proceed to the report information fields.
Choose business unit, department, issue target, category, location, and people involved.
Add title, description, date and time, severity, order number, and supporting evidence.
Check required details, then submit the completed incident report.
Each stage keeps the report structured so reviewers can understand what happened and what needs action.
Start the report and confirm the incident type for workplace issues requiring review or action.
Enter business context, issue category, title, description, date, priority, and related order number.
Upload supporting evidence if available. Attachments are optional but help management review the incident clearly.
Submit the completed report after all required fields are filled.
Complete the business, people, timing, impact, and evidence fields as accurately as possible.
Select the business unit connected to the incident.
Select the department after choosing a business unit.
Choose whether the issue involves an individual staff member, team, department, or manager.
Select Work and Performance Issue, System Issue, Operational Issue, Customer Issue, or Others.
Confirm the report type before continuing through the workplace issue flow.
Enter a concise title, up to 160 characters, such as customer complaint escalation or equipment damage.
Add where the incident happened when location helps reviewers understand the context.
Describe the report clearly. The form supports detailed descriptions up to 10,000 characters.
Record the staff, team, manager, department, or affected people connected to the report.
Add an order number when the incident is related to a customer order or transaction.
Select when the incident happened so it can be reviewed against the correct timeline.
Choose High, Normal, or Low based on urgency, impact, and follow-up priority.
Choose the closest category so the incident reaches the right review context.
Forgotten customer follow-up, incorrect data entry, not following SOP, arriving late, absent without notice, unprofessional communication, or not responding on WhatsApp.
AppSheet not updating, calendar not synced, incorrect information, data mismatch, system lag, error, or access problems.
Job or service delay, scheduling clash, poor coordination between teams, unclear task assignment, or incomplete handover.
Slow service complaints, wrong or incomplete items, customer dissatisfaction, or customer miscommunication.
Use this for isolated cases that do not fit the main categories.
Attachments are optional, but clear evidence helps reviewers understand the incident faster.
Drag files into the attachment area or use Select Files to upload evidence.
Take a photo directly when evidence needs to be captured immediately.
Choose existing images, videos, or documents from gallery and files.
Add supporting files, images, or videos when they help explain the report.
Submitted reports can be searched, opened, reviewed, and updated by users with the right permissions.
IncidentReportDetails.tsx shows the incident context, attachments, and current status.
DetailsAuthorized users and admins can open the management page to retrieve and review submitted reports.
ReviewFilter by status, severity, category, date, company, department, or search text.
FilterThe tracker helps users find their own submitted reports and open the full incident details.
The tracker shows the user's submitted incident report history in one place.
Search by ticket ID to quickly find a submitted incident report.
Click View to open the full incident report details page.
Shows the report type so users can distinguish incident reports from other feedback records.
Displays the selected category, such as Work and Performance Issue, System Issue, Operational Issue, Customer Issue, or Others.
If no incident reports have been submitted yet, the tracker shows an empty message instead of a report list.
Use a clear title, describe what happened, include who was affected, select the closest category, set a realistic severity, and attach evidence when it helps explain the issue.