حلول
Event readiness · Kingdom of Saudi Arabia

Proof that the venue was ready.

HULUL is one record for getting an event ready to open, shared by the Event Owner who must be satisfied it is safe, the Event Manager who delivers it, the Event Inspector who checks it, and the Operators who fix what is found.

  • Made by ASK LLC
  • Data stored in Saudi Arabia
  • Arabic and English
  • Invitation only
Example
Critical #K7qa Open

Exposed cable at the stage entrance

Electrical · Main stage, Zone A · Raised from the checklist

Responsibility of
Stage services operator
Logged
21 Sep, 18:40
Deadline
21 Sep, 22:40

3 photographs, taken with the app’s camera on the spot, time and place stamped

Looking at HULUL for your events?

Tell us who you are — Event Owner, Event Manager, Event Inspector or Operator — and we will walk you through it on an event like yours, in Arabic or English.

Ask for a walkthrough

Invited to HULUL?

Open the link in your invitation email once, then sign in with the Google or Microsoft account it was sent to. Your phone signs in the same way. Help with signing in.

Sign in
Today

Four versions of the truth.

A season opens, a stadium fills, a festival ground takes in thousands in one night. None of it happens until someone signs one sentence: “This venue is safe to open.” Today that signature rests on records scattered across four places.

  • Photographs in a WhatsApp group.
  • Checklists on paper, in a car.
  • Findings in a spreadsheet emailed on Tuesday.
  • Sign-offs in four organisations’ inboxes.

When something is missed, nobody can prove when it was found, who was told, or whether it was ever fixed.

Four organisations, one record

Who does what.

Every organisation on an event works in the same record, and sees exactly what its role allows — nothing more.

  • Event Owner

    Must be satisfied the event is safe.

    A government authority or a season organiser. Sees every event’s readiness, the reports and every escalation, and approves — or refuses — the venue.

    Gets: a decision it can stand behind, on the record.

  • Event Manager

    Delivers the event.

    Appoints the Operators, submits the readiness documents and answers for every log raised on its venue. It is the first to hear when a deadline is missed.

    Gets: one list of what is still open, and by when.

  • Event Inspector

    Checks the documents and walks the venue.

    The inspection company. Sets up the event year, the required documents, the checklists and the roadmap; reviews what comes in, inspects on the phone and recommends whether to open.

    Gets: inspections it can defend — who, what, when, standing where, with the photograph.

  • Operator

    Fixes what is found.

    Vendors, exhibitors and service operators. Each spot’s phone signs in from the code on the spot’s sign, sees the logs raised against it and photographs the fix.

    Gets: a clear list and a clock, not a phone call.

The platform

One record, from the first plan to the last photograph.

Six things happen before the gates open. HULUL keeps every one of them — with a time, a name and, where it matters, a photograph.

Before the gates open

  1. Plan every event on one roadmap.

    A roadmap plan — kick-off, meetings, documents to send, inspections, reports to release — is built once and rolled onto every event. Each step gets a real date, and shows late the moment it is.

    • Projects group the events of an event year; sub-events carry their own steps
    • One board shows every event’s position on every step
    • Meetings start from templates, invite roles, and record who came
    Roadmap · Event Year 2026Today 21 Sep
    Event Kick-off Documents Inspection Opening
    Winter Garden Done Done Today 24 Sep
    Night Market Done 2 days late 26 Sep 28 Sep
    Lakeside Stage Done Done Done Tonight
    Example event year. The names are invented.
  2. Readiness documents, scored — not just stored.

    The venue management plan, or the full set of safety, emergency, traffic, crowd and security plans, is sent to each event under one deadline. Each comes back filled in on the platform or uploaded, is reviewed line by line, and is accepted or sent back with a reason.

    • Standard templates ship with the platform, in Arabic and English
    • Completion, quality and a readiness score come from the review, not a feeling
    • The event page shows which mandatory Operators are still missing
    Readiness documents · Winter GardenDue 22 Sep
    • Zone safety management planAccepted
    • Emergency response planAssembly points not markedSent back
    • Traffic and transport planIn review
    • Crowd management planAccepted
    • Security management planAwaiting upload

On the ground

  1. Inspect it standing in front of it.

    On the phone, item by item: ticked, crossed or N/A. A crossed item cannot be saved without a photograph taken there and then — and it becomes a risk log by itself, with its risk level, its Operator and its clock.

    • Every visit gets a score; N/A is left out of it
    • Your own checklist catalogue, imported, for opening and operational inspections
    • Visits are scheduled to qualified inspectors, and gaps show who still needs one
    Checklist · Food court, Zone BItem 7 of 12

    Hand-wash sink connected, with hot waterFood & Beverage › Hygiene · risk level High

    TickedCrossedN/A
    21 SEP 17:02 · IN VENUE ±6 m

    No photograph without locationThe camera will not take evidence with GPS or Wi-Fi off, or outside the venue.

    Crossed → log #Qm2x raised, 24 hours to fix

  2. Fixed is not a claim. It is evidence, reviewed.

    The Operator opens the log, does the work and photographs the fix. The Event Inspector reviews it: accepted, and it closes; sent back, and it reopens — with the clock still running.

    The life of a log#Qm2x
    1. OpenRaised on the phone
    2. ViewedThe Operator opened it
    3. SubmittedThe fix, photographed
    4. ReviewedThe inspector checked it
    5. ResolvedClosed, on the record

    Sent back? It reopens, and the clock keeps running.

  3. Nothing quietly expires.

    Every log has a time to fix, set by its risk level — by default four hours for Critical, a day for High, a week for Low. Miss it and the log climbs, by itself, to people who can act.

    • Whoever it reaches cannot carry on in the platform until they press Noted
    • High-risk logs are announced again as their time runs down
    • Who each step reaches, and how long it waits, are your administrator’s settings
    Escalation · log #K7qaCritical
    1. Deadline passesThe Event Manager’s teamon the event
    2. One day laterThe Event Manager’s directorswith the log and its age
    3. Two days after thatThe Event Ownerwith the log, its photographs and its age
    NotedA risk log needs your attention. Read it, then press Noted to carry on.
    Default timings. Every one of them is a setting.

The proof

  1. Decide on the record, and prove it later.

    The Event Inspector records its evaluation and recommendation; the Event Owner approves the venue or refuses it, on the platform. Behind the decision sit the reports, and every run of them is kept.

    • Cut-off reports 48, 24 and 2 hours before opening: what is still open, by risk level and by Operator
    • Checklist, log and document review reports, released by the role responsible
    • Pick any moment — 20:00 on opening night — and read the whole platform as it stood then, with nothing changeable
    • An audit log of every action that nobody can edit
    Opening approval · Winter Garden
    • Event Inspector · recommendation

      Ready to open. Two Medium logs remain, both with fixes submitted.

      21 Sep 19:10
    • Event Owner · decision

      Approved to open.

      21 Sep 19:45
    • Cut-off report · 48 hours19 Sep 20:00
    • Cut-off report · 24 hours20 Sep 20:00
    • Cut-off report · 2 hours21 Sep 18:00
    • Document review report21 Sep 12:30
    As of 21 Sep, 20:00Read-only: the platform as it stood then.
The phone app

Built for the venue floor, not the office.

Inspectors and Operators work from the HULUL app: today’s checklists and logs, the live venue map, and the camera.

Evidence you can trust

The camera opens only inside the app, never the gallery. No photograph without GPS and Wi-Fi on, and no log raised from outside the venue — how far is your setting.

Works without signal

Checklists, logs, photographs and fixes are recorded offline and sent when signal returns. Home shows what is waiting and when it last synced.

A spot’s phone, in one scan

Each spot gets a sign with a code. The spot’s phone scans it and works as that spot — no account, no email, no administrator.

The live map

Zones and spots coloured by what is open, fixed or clear; tap one to raise a log or review a fix. On the phone the map comes from HULUL’s own servers.

Android: in testing with invited organisations — your organisation gets you set up. iPhone: in preparation. Store links will appear here once the listings are public.

Live mapWinter Garden
Zone A Zone B Zone C Main stage
OpenFixedClearNo logs
2 items waiting to sendLast synced 21:14Sync now
Built for the Kingdom

Your record stays in Saudi Arabia.

What a security review asks first, answered plainly.

  • Stored in Saudi Arabia

    Records, photographs and locations are stored on Google Cloud in Dammam. Inspectors’ live positions never leave the platform.

  • Invitation only

    Nobody signs up. Your organisation invites its people; they sign in with Google or Microsoft, or with a passkey.

  • Permissions you control

    Every permission is a tick in a grid your own administrator sets. Every action is in an audit log nobody can edit.

  • Arabic and English, all the way

    Every screen, email and report in both — including people’s names, job titles and event names.

  • Help built in

    A guided tour of every page and a guide for every task, inside the platform, in both languages.

Security and data

Getting started

From first email to first inspection.

HULUL is set up for each organisation, not bought off a shelf.

  1. Write to us

    Tell us who you are and the events you work on. We reply in Arabic or English.

  2. We set up your organisation

    Your organisation and its first administrator, with a walkthrough on a sample event.

  3. You invite your people

    Your administrator invites Event Managers, Inspectors and Operators, and sets what each role may do.

See it on an event like yours.

We will walk you through HULUL on an event shaped like yours: the roadmap, the documents, the inspection, the logs and the opening decision.

Or write to support@hulul.co

Running inspections outside events — construction, utilities, infrastructure? The same record works there. Ask us.