Riyadh: queue design for Olaya, Hittin, Al Nakheel, Al Malqa
Start with a location code for Riyadh, then append building and unit references. Keep separate queue groups when Olaya, Hittin, Al Nakheel, Al Malqa are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Riyadh code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Riyadh groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Olaya, Hittin, Al Nakheel, Al Malqa appear in one shared portfolio report.
Jeddah: queue design for Al Rawdah, Al Hamra, Al Zahra, Al Salamah
Start with a location code for Jeddah, then append building and unit references. Keep separate queue groups when Al Rawdah, Al Hamra, Al Zahra, Al Salamah are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Jeddah code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Jeddah groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Al Rawdah, Al Hamra, Al Zahra, Al Salamah appear in one shared portfolio report.
Eastern Province: queue design for Al Khobar, Dammam, Dhahran, Jubail
Start with a location code for Eastern Province, then append building and unit references. Keep separate queue groups when Al Khobar, Dammam, Dhahran, Jubail are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Eastern Province code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Eastern Province groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Al Khobar, Dammam, Dhahran, Jubail appear in one shared portfolio report.
Makkah portfolio: queue design for Al Aziziyah, Al Awali, Al Naseem, central business areas
Start with a location code for Makkah portfolio, then append building and unit references. Keep separate queue groups when Al Aziziyah, Al Awali, Al Naseem, central business areas are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Makkah portfolio code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Makkah portfolio groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Al Aziziyah, Al Awali, Al Naseem, central business areas appear in one shared portfolio report.
Madinah portfolio: queue design for Qurban, Al Aridh, Al Iskan, King Fahd district
Start with a location code for Madinah portfolio, then append building and unit references. Keep separate queue groups when Qurban, Al Aridh, Al Iskan, King Fahd district are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Madinah portfolio code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Madinah portfolio groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Qurban, Al Aridh, Al Iskan, King Fahd district appear in one shared portfolio report.
Northern cities: queue design for Tabuk, Hail, Sakaka, Arar
Start with a location code for Northern cities, then append building and unit references. Keep separate queue groups when Tabuk, Hail, Sakaka, Arar are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Northern cities code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Northern cities groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Tabuk, Hail, Sakaka, Arar appear in one shared portfolio report.
Southern cities: queue design for Abha, Khamis Mushait, Jazan, Najran
Start with a location code for Southern cities, then append building and unit references. Keep separate queue groups when Abha, Khamis Mushait, Jazan, Najran are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Southern cities code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Southern cities groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Abha, Khamis Mushait, Jazan, Najran appear in one shared portfolio report.
Commercial portfolio: queue design for Riyadh offices, Jeddah shops, Dammam warehouses, Jubail staff housing
Start with a location code for Commercial portfolio, then append building and unit references. Keep separate queue groups when Riyadh offices, Jeddah shops, Dammam warehouses, Jubail staff housing are handled by different colleagues or accounts. Within each group, sort by property code and due date. This gives the reviewer a predictable sequence and keeps a multi-building run from becoming one unstructured list.
For recurring SAR cheques, preview the first and final dates for every tenancy, compare the instalment count with the source schedule, and show the series total on the internal cover sheet. After printing, filter history by the Commercial portfolio code and compare the number of passed rows with the physical count. If a set is transferred to another office, record the receiving team and handover time in the non-cheque register.
A useful weekly view for Commercial portfolio groups the next due items by account and property. The team can then identify missing series, replacement records, or items whose status was never updated. Searchable codes are especially valuable where names repeat across buildings or where Riyadh offices, Jeddah shops, Dammam warehouses, Jubail staff housing appear in one shared portfolio report.
