Two processes that only look similar
A UAE visa application and a global visa application (say, a Schengen or a US visa) share the word "visa" and not much else procedurally — different document requirements, different processing timelines, different status stages, and often a completely different submission channel. Forcing both through one generic "visa" form means one of them is always working around fields that don't apply.
Where a one-size-fits-all form breaks down
Free-text notes fields end up doing the work that structured fields should — which makes reporting on processing times, rejection reasons, or document completeness across applications almost impossible, because the data was never structured in the first place.
Purpose-built workflows for each type
The fix is separate, purpose-built application types for UAE and global visas, each with the fields and status pipeline that actually match how that specific process moves — so the data captured is usable for reporting, not just for record-keeping.
How Muhasib structures this
Muhasib treats UAE visas and global visas as distinct, dedicated booking types with their own relevant fields and status pipeline, rather than stretching one generic form to cover both.