Occupants & requesters
Describe the problem, share the location and evidence, then receive updates without chasing individual technicians.
From a leaking pipe to a failed air-conditioning unit, keep every facility issue in one accountable workflow. Capture the location and evidence, notify the right team, track response times and keep a complete record of the resolution.
Based on 200+ reviews on






Trusted By Global Brands Across The World
Bring the initial report, service response and final resolution into one connected facility workflow.
Recognition from software review platforms for value, ease of use, functionality and customer support.







Give occupants, staff and contractors a clear way to report a facility issue. A QR code or request portal opens the reporting workflow; the location, asset, description and supporting photos give your service team the context it needs before the first response. Voice input helps when typing is inconvenient.
Illustrative interface and sample data.
Review incoming incidents in one queue instead of chasing messages across departments. Classify the issue, review its priority and route it to the responsible technician, internal team or service provider. Where approval is required, preserve that decision and the link to the resulting work order.
Illustrative interface and sample data.
Use configured service-level agreements to track first response, follow-up response and resolution. Set targets for the relevant priority, facility, team or contract, then use at-risk alerts and escalation rules to keep delayed cases visible. Each event remains connected to the incident.
Illustrative interface and sample data.
Keep the person who reported the issue informed while the service team works. Technicians record repair notes, checklist results and photos against the linked job. Save the resolution with the incident history so supervisors can review what was done and requesters can see the outcome.
Illustrative interface and sample data.
Review open, in-progress and resolved cases across facilities. Compare response and resolution times, check SLA outcomes and look for repeated issues by asset, location or category. Keep the original report and subsequent actions together so a recurring problem can inform the next maintenance decision.
Illustrative interface and sample data.
Walk through a report, team assignment, response target and documented resolution using your facility workflow.
Use VEDA to help turn spoken or typed descriptions into structured requests, ask about urgent incidents and find relevant maintenance information. AI assistance can also draft a completion summary from the recorded work. Your team reviews the content before it becomes the final record.
Illustrative AI draft. Review before use.
Try a voice request, ask about open cases and review a draft resolution summary in a guided demonstration.
Keep reporting connected to the maintenance work, asset records and evidence needed to resolve the issue.
Give users a defined channel to report issues against a location or asset.
Capture the issue description, photos and context from the field.
Review, classify and route reports to a responsible team.
Track first response, follow-up response and final resolution.
Keep owners informed and surface cases that need attention.
Preserve the connection from the report to the corrective work.
Retain comments, checklist results, photos and closure details.
Review incident outcomes and use VEDA to query connected information.
Connect maintenance information with business systems through available APIs and configured integrations. Confirm the required data flow and connector scope during implementation.
Capture tenant and staff issues with the building, floor and room context.
Report guest-area faults and back-of-house issues to the responsible service team.
Record building utility and equipment issues with location and service history.
Keep classroom, common-area and campus maintenance reports in one workflow.
Describe the problem, share the location and evidence, then receive updates without chasing individual technicians.
Review the queue, confirm ownership and monitor response targets before cases slip through the cracks.
Start with the reported context, record the repair and attach evidence so the next person sees the complete history.
It is the process of recording a facility issue, assigning responsibility, tracking the response and saving the resolution. DreamzCMMS connects the original report, location, asset, updates and linked maintenance history so teams can follow the issue from intake to closure.
An incident records the issue that someone has observed, such as a leak or equipment fault. A work order describes the maintenance task assigned to investigate or fix it. An approved incident can be linked to a work order while preserving the original report and response history.
Yes. QR codes and a dedicated request portal can open the reporting workflow for an asset or facility area. Configured forms capture the description, location, photos and other required details. Mobile, voice and typed input support different reporting situations.
Incidents can be classified by facility, asset, category and priority, reviewed where approval is needed, and routed through configured assignment rules. The responsible technician, internal team or service provider is notified, with the assignment retained in the incident history.
Yes. Configured SLA policies can track first response, next response and resolution against the applicable targets. At-risk warnings and escalation rules notify responsible users when a case approaches or exceeds its service commitment.
The incident and linked work order can retain repair notes, checklist results, photos, attachments and completion details. Together with status updates and communication history, these records help supervisors understand what was done and inform requester updates.
Yes. Teams can review incident status, response and resolution times, SLA compliance, facility performance and recurring issues. Location, category, asset and root-cause context help identify where further maintenance investigation is needed.
VEDA can assist with spoken or typed requests, make connected maintenance information easier to query and support draft summaries of recorded work. Review generated text against the incident details and evidence before saving or sharing it.
No. This page describes a maintenance incident workflow. For immediate danger, follow your facility emergency procedures first; use the incident record for operational follow-up and documentation.
Connect QR and voice reporting, assignment, response tracking, corrective work and resolution evidence in DreamzCMMS.