An accident is one file, not scattered messages

The field report page opens by scanning the vehicle's code, no account needed, in Arabic, English, Urdu and Hindi. The driver records the accident type and damage level, whether there are injuries, his own details and the other party's — plate, name, phone — and the witness, with guided photos and the captured coordinates, plus the authority's report number once issued. The damage map is interactive: he taps the vehicle's own outline to mark where the damage sits instead of describing it in words.

One question changes the file's path: can the vehicle still be driven? If the answer is no, the system creates — at the moment of registration — an approved movement from the accident scene to the workshop and switches the vehicle's status to maintenance automatically. It does not stand on the road for days waiting for someone to decide where it goes, and it never shows as available in the system while it sits wrecked and immobile.

The file carries the liability percentage assigned to the driver, the insurance company with its policy expiry and the registration's, and the assessed amount against the actual repair cost — so the elements of a claim are complete in one place instead of being chased across email, chats and drawers. Whatever burden is assigned to the driver stays recorded in the file with its percentage, so accountability rests on a documented figure, not on a retelling.

Moving the file to under-repair automatically creates a maintenance record tied to the accident, numbered from its report number — once, never duplicated by later updates — so the repair work and its costs accumulate through the normal maintenance path while staying bound to their origin. Closing the file returns the vehicle to service automatically, and what management reads in the end is a single file: the accident, its parties, its damage, its liability and its cost, from the first photo to the last riyal.