FACILITIESThe maintenance request
Supervisor on leave
×NO OWNERWent to a supervisor who was on leave.
Dashboard module 06 — Ticketing
Every request has an ownerand a resolution.
Requests arrive tagged, located and evidenced. Reply, forward, close. The record outlives the conversation.
01Evidence attached02Owner assigned03History retained
Ticketing / Live workspaceLIVE
Evidence attachedOwner assignedIndividual messages never become organizational knowledge.
01
Requests die inside individuals
02
Repeated faults look like separate incidents
03
After an incident, nobody can prove whether it was raised
04
The reports you most need never arrive when a name is required
Evidence first. History intact.
CONTROL 01 · 3 attachments
The evidence, not a description
Photos, video and GPS attached at submission.
IMGLeak entrance.jpgPhoto · 2.4 MBVIDSite walkthroughVideo · 00:18GPSWarehouse 3Location verified
CONTROL 02 · Category + GPS
Category and location in the header
Understand the issue without three follow-up questions.
Water leak beside loading entrance
Priority HighSubmitted 09:42
CONTROL 03 · 1,284 requests
A searchable inbox
Find a person, subject or active thread.
#2048Water leak · Warehouse 3OPEN#1982Loading entrance · Warehouse 3CLOSED
CONTROL 04 · Thread intact
Replies carry their evidence
PDFs and images stay with the answer.
NA
Nour AdelThe leak is beside the loading entrance.
FMFacilitiesTeam dispatched. ETA 20 minutes.
CONTROL 05 · History travels
A forward keeps the history
The full thread moves to the responsible team.
FACILITIES→SITE OPERATIONS
CONTROL 06 · Record retained
A close keeps the record
Workspace clean, history searchable.
✓Request closed#2048 · Resolution retained
See the operational patterns currently hidden from you.
Anonymous submission is one checkbox. The subject and evidence still route normally, and every request remains logged.
WHAT THE ORGANIZATION RECEIVES
NANour AdelReporter identityNAMED
1Evidence retained2Owner assigned3Action recorded
The route and record stay operational even when the person’s identity does not.
✓Safety violations surfaced while still hazards01✓Harassment visible before it becomes a legal matter02✓Procedural shortcuts corrected earlier03✓A record that someone raised it — and that you acted04
From report to retained resolution.
Tawasol / TicketingLIVE WORKSPACE
Submit anonymously if needed
Open the reporting form from the app, anonymously when needed.
Anonymous
Attach photos, video and location
Add photos, video and a verified GPS location.
Categorize by subject
Use the subject to send the request to the responsible team.
Facilities→Warehouse 3→Site maintenance
Respond or forward
Reply in thread or forward it with the full history intact.
The maintenance team has arrived. Is the request still open?
Yes. Reply here when the repair is complete.
Close and retain
Resolve the issue while keeping the evidence and conversation searchable.
✓Ticket #2048Resolved and retainedClosed by Facilities · 15:42
Conversation8 messagesEvidence3 filesResolution time2h 14m
Four functions that cannot afford a lost request.
Safety-critical operations
The issue reaches a named owner while it is still a hazard.
Hazard report→+Photo + GPS→✓Safety team
Regulated sectors
Submission, reply, evidence and closure remain in one trail.
Compliance concern→+Complete thread→✓Audit record
Facility and property management
Repeated faults across buildings become visible as one operational pattern.
Site fault→+Location pattern→✓Facilities
Large HR functions
Employees get a protected route without making the report less actionable.
Sensitive concern→+Anonymous option→✓HR case owner
The questions worth asking
We have a helpdesk already.
For IT, probably. This covers HR, facilities, safety and operations from the app employees already have.
Anonymous reporting will be abused.
Volume is low and value is high. Subject and evidence make unfounded reports as visible as founded ones.
How do we respond anonymously?
Act on the content; the reporter sees the thread while the record shows what you did.
Practical answers.
A checkbox at submission; it still routes by subject.
Photos, video and GPS location.
Closed, retained and searchable.
Forward the thread; history travels with it.
Every request is logged with subject and location.
Live, not slides
Raise a ticket from the room.
We will submit one from a phone with a photo and location, then show how it arrives and closes.