The venue becomes data
A venue is drawn on the map — its real boundary, its zones, and every stand and stall placed inside them. The risk categories that apply are named, and only an inspector qualified in a category can be assigned to it.
HULUL is one platform for the whole of event readiness. Plan the venue. Inspect it. Log what is wrong. Prove it was fixed — before the gates open. Every action, by every party, on one record.
A season opens. A stadium fills. A festival ground takes in eighty thousand people in a single night. None of it happens until someone puts their name to one sentence: “This venue is safe to open.” Today, that signature rests on paperwork nobody can see.
When something is missed, nobody can prove when it was found, or whether it was ever fixed.
Everything that has to be true before the gates open, and the evidence that it was.
A venue is drawn on the map — its real boundary, its zones, and every stand and stall placed inside them. The risk categories that apply are named, and only an inspector qualified in a category can be assigned to it.
Projects group the events, every event carries its sub-events, and the Event Owner sets the roadmap each one follows: kick-off, document deadlines, the opening inspection, opening night.
Risk assessments, sign-offs and certifications are uploaded against a required list, then reviewed, accepted or sent back with a reason. The mandatory operators must all be appointed.
On a phone, standing in front of the thing being inspected. Each item is complied, not complied or not applicable, and a failure cannot be recorded without a photograph taken on the spot.
A failure becomes a risk log: its category, its severity, where exactly it was found, and the operator it was raised against. The clock starts the moment it is raised.
Open risks by severity, category and who owes the fix. A photographic timeline of the whole event. An audit log nobody can edit: who raised each risk, who resolved it, who closed it, and exactly when.
The operator it was raised against opens the log, does the work and photographs the fix. An inspector reviews it. Approved, and it closes. Rejected, and it reopens — with the clock still running.
A critical risk might have two hours; a low one, a week. Nobody has to chase it, and nobody can quietly let it lapse.
The company that delivers the event and answers for the venue hears first.
Then the people above them, with the log, its photographs and the time it has been open.
Then the authority that must be satisfied the event is safe.
A government authority, for example. Sets the event year, the roadmap and the standard every event is held to.
Appoints the operators, submits the readiness paperwork, and is first to hear when a risk is running late.
Reviews documents, walks the venue with checklists, raises risk logs and reviews the fixes.
Vendors, exhibitors and service operators each answer for the logs raised against them, from their own phones.
Inspectors and operators work from the HULUL app: today’s checklists and logs, the live venue map, the camera. A photograph is taken by the camera on the spot and stamped with where and when — never picked from a gallery. What is recorded offline is sent when the signal returns.
Every screen runs in both, on the web and on the phone, right to left where it should.
Every organisation can name things the way it already speaks, and every role sees only what it should.
Platform data is stored in Saudi Arabia. Maps are served from HULUL’s own servers, so nobody else learns where an inspector is standing.
The same pattern runs anywhere inspections have to be controlled, evidenced and closed out, and holds every contractor to one standard.