The tour
Rashid runs three buildings he does not own: a 384-bed labour camp in Al Quoz, a labour village in Jebel Ali and a compound of partitioned staff villas in Dubai Investments Park. He pays three landlords and bills forty-odd companies. Follow one month of that, step by step, and by the end you will have used most of this product.
The landlord
Holds the building. Takes one head lease payment, usually as twelve post-dated cheques, and wants to know whether each one has cleared.
The corporate client
Signs for a headcount — twenty beds, forty beds — and rotates staff through them without the agreement changing. Billing follows the contract.
The occupant
Sleeps in one bed, carries four documents with four expiry dates, and is not the person being invoiced. Compliance follows him.
The camp boss
Runs the site: jobs, cleans, the gate, the stores. Holds zero permissions matching invoice, payment, cheque, deposit, expense, head-lease cost or rate.
Step 01 of 8 · Monday
The landlord wants AED 115,000 a month for Al Quoz Camp 1 — 384 beds, six blocks, AED 1,380,000 a year, twelve post-dated cheques. That number tells Rashid nothing about whether the building is worth taking, because he is not going to let the building. He is going to let 384 things inside it: most of them to two contractors on committed lines at a negotiated rate, and the rest one bed at a time to individuals at a higher one.
So the cost is one figure on one agreement and the revenue is dozens of figures on a dozen agreements against the same physical asset. The difference between them — the spread — is the only number that decides the question, and no system that models a lease as landlord-to-tenant can produce it, because it has nowhere to put the second side.
Underneath the head lease sits everything else it costs to hold the building before anybody sleeps in it: security, cleaning, the mess subsidy, unrecharged utilities. In the demonstration below, Al Quoz breaks even at about 55% occupancy measured against the lease alone, and about 70% once those costs are in. The second figure is the one an operator loses sleep over, and a break-even computed against the rent alone flatters the business.
Drag the occupancy slider down until the gold bar shrinks to the break-even line and crosses it. Then switch buildings — the villa compound and the labour village have completely different shapes.
Al Quoz Industrial 3, DubaiLabour accommodation · 6 blocks
Head lease AED 115,000Security, cleaning, mess and unrecharged utilities AED 34,000
AED 41,272 a month of spread at 86% occupancy. Break-even is 70.1%.
| Line | Held | Committed | Rate | Per month |
|---|---|---|---|---|
| Al Nakheel Contracting | 160 | 160 | AED 540 | AED 86,400 |
| Emirates Facilities Co | 96 | 96 | AED 564 | AED 54,144 |
| Individual residents | 74 | 128 available | AED 672 | AED 49,728 |
Two corporate lines hold 256 of the 384 beds. The rest is sold one bed at a time, at a higher rate and with a month’s notice.
A corporate line is a pooled quantity, not a list of beds: the contract says “160 beds” and allocation decides which ones, later. When occupancy falls below the commitment the line is short — the marked figures above — and that is a conversation with the client, not a billing change.
And what it does not do
Step 02 of 8 · Monday afternoon
A camp is not a list of beds. It is blocks, then floors, then units; inside a unit, rooms; inside a room, partitions; inside a partition, beds. Rashid describes that shape once — the blocks, the floors, the units on each floor, each unit a dormitory room split into partitions of three — and watches the count update as he types, until the preview reads four hundred and eighty spaces. One press writes the blocks, floors, units, rooms, partitions and beds in a single transaction. Nothing half-built is possible.
Every level of that tree is a thing somebody could let, and that is exactly the problem. The same cubic metre appears four times over, and it cannot be sold four times. So the interesting question is not how the tree is drawn but who refuses it — and the answer is PostgreSQL, not a check the application might forget.
What comes out is the tree below — a slice of that camp, small enough to read at a glance and deep enough to reach all three levels. Press “Let this room” on a room with one occupied bed inside it and the attempt is rejected, with the offending bed named. Press it on the clean room in Block B and it succeeds on the first press. The refusal is walked from the real ancestor and descendant chains, so every space in the tree answers correctly — including the ones nobody thought to script.
Expand the tree, select Room A01 and press the let button. Then try Block A from two levels up, and Room B01, which is clean.
HINTRoom A01 is selected. Press “Let this room”, and watch it be refused.
None of that is screen logic. It is three lines of schema, and they hold whether the request arrives from this page, the API or a script somebody ran at midnight.
The eight statuses a space moves through — 29 legal moves between them, and the screen only ever offers the ones the server will accept
And what it does not do
Step 03 of 8 · Tuesday
ASGC want twenty beds from January, for twelve months, at AED 750 a bed. They do not care which twenty, and Rashid needs to keep the freedom to move people between rooms without opening the agreement. So the contract line says a quantity and a scope — “20 beds in Camp A” — not bed numbers.
This is the thing generic property software gets wrong in the same way every time. It models a lease as pointing at a unit, so the only way to express twenty beds is twenty leases, and then moving one man one metre becomes a contract amendment. Here the beds are chosen later, one arrival at a time, by an allocation — a time-bounded join between the agreement and the person.
Two things the instrument will not let you do. Place the twenty-first man: the line says twenty, and the way past it is a variation — a priced, approved change — not a quiet insert. And place anybody in the nine beds a rival contractor holds from March to June: they are empty tonight, and still refused, because the constraint is over the period rather than over the instant.
Fill the line to twenty and then try the twenty-first. Try one of the amber beds. Then move a man from one bed to another and watch the contract card refuse to move.
ASGC Group · SUB-2026-0117
That figure is the same at nought beds allocated and at twenty. A pooled line is billed on its quantity, so the invoice never waits for the site office to decide who sleeps where.
20 still to place. Click a mint bed.
Camp A · blocks A and B · 48 beds
Point at any bed. Click a mint one to place a man against the line.
GET /contract-lines/CL-1042/allocations → 0 rowsTwelve contract states — each move costing its own permission, so the person who negotiates the deal is not the person who signs it off
And what it does not do
Step 04 of 8 · Over the fortnight
Twenty men arrive over two weeks. Each is placed on a specific bed against the pooled line, and each move-in completes only when all five items are true: keys issued, induction done, bedding issued, ID verified, meter reading taken. Anything outstanding is named in the refusal. Completing the checklist is what makes the allocation active and the bed occupied — not somebody changing a status.
An unanswered “keys issued” is a man in a room he cannot lock. An unanswered “ID verified” is an undocumented occupant in the camp on the morning of an inspection.
And then the part that runs for the next year without Rashid touching it. Each man carries a passport, a residence visa, an Emirates ID and a labour card, each with its own date. The expiry is not an event on the day it happens; it is the bottom rung of a ladder that started sixty days earlier — and the bottom rung is not a message. It is a refusal at the gatehouse.
Drag the scrubber from one end to the other and watch Ashraf’s residence visa walk every rung and end in a refused pass. Click a different document to make it the ladder’s subject — the passport behaves differently, deliberately.
Today1 Sep 2026
A renewal notice goes out and the document acquires a date. Nothing else changes: the man works, the bed bills, the file is simply no longer quiet.
A task is raised and the document joins the renewals board. It stops being a date in a folder and becomes somebody’s job, with a name against it.
Escalation. The supervisor is named in the daily digest until the document is replaced or the occupant is stood down. Silence is no longer an option anyone has.
Not a message. The gate pass is refused, the allocation cannot be renewed and no exit permit will print. The ladder ends at a locked turnstile, which is the only rung anybody ever remembers.
Anika Fernandes
Housekeeping supervisor · Meraas Facilities
Jebel Ali Staff Village · C04-1 · AED 1,150/mo
Rajesh Kumar
Electrician · Gulf Steel Contracting
Al Quoz Camp 1 · A03-2 · AED 750/mo
Bilal Haque
Driver · Emirates Logistics
Al Quoz Camp 1 · B01-4 · AED 900/mo
Mohammed Ashraf
Steel fixer · Gulf Steel Contracting
Al Quoz Camp 1 · A02-3 · AED 750/mo
Four beds, AED 3,550 a month, contracted to three employers. Not one of those invoices pauses because a document did — the bed is still let, the head lease is still owed, and the only thing that stopped is the man. Which is why the ladder starts ninety days out and not on the morning it matters.
More than 60 days
Valid. Nothing fires, nothing is owed, and the cell on the compliance matrix is green.
60 down to 30
Expiring. The occupant and their employer contact are told, once. A renewal that pushes the date back does not re-fire it on the way out.
30 down to zero
Critical. A task is raised for the HR coordinator at 30 days; the property manager hears about it at 7.
Past zero
Expired. The person is marked not compliant, and a gate pass is written REFUSED with the document named on it.
And what it does not do
Step 05 of 8 · The 1st
ASGC’s twenty beds at AED 750 — except the men arrived on the 14th of a thirty-one-day March. They owe eighteen of thirty-one days, and the invoice line has to say so on its face, because every disputed invoice in this business is a part month. The line prints the days and the dates next to the amount, so the argument ends at the invoice instead of in a meeting.
Everything on the document is a whole number of fils. A damaged window recovered from three men is split so the three parts add back to exactly what went in, odd fils handed out largest-remainder — not three equal shares with a fils nobody can explain. Tax is resolved line by line against the date of supply, from a rulebook that is editable rows in your own database rather than code, and each line stores the sentence explaining which rule chose that rate.
Then press Issue. The document freezes — not the screen, the database. From that moment the amounts, the customer, the number and the dates cannot be changed by anybody, including us, and a correction is a credit note with a reason code against a cap that two clerks racing each other cannot jointly exceed.
Step through it, or let it play. Stop on the proration and check the arithmetic against a calculator — every figure on the panel is computed, none is typed. Then issue it and try to edit it.
Step 1 of 8. An empty draft. Running total AED 0.00.
Tax invoice
INV-2026-1043
Gulf Falcon Contracting LLC
1–31 March 2026 · AED
| Description | Basis | Amount |
|---|---|---|
| No lines yet. Press Next. | ||
Seven invoice states — and five aging buckets an unpaid one falls through
A year of rent here does not arrive as twelve payments. It arrives once, on the day the contract is signed, as twelve pieces of paper dated a month apart — and from that moment Rashid is a custodian of physical instruments as much as a landlord. A payment schedule cannot bounce, cannot be postponed by approval, and is never in a drawer in Al Quoz. So a cheque here is its own record with its own lifecycle, its own calendar and its own custody report.
Run the clock forward. July’s cheque goes to the bank and comes back unpaid in August. A bounce is not a status change: the risk band steps down and never improves from a bounce, a bounce-fee invoice raises and issues itself, a collection case opens with a number, and the payment the cheque had already produced reverses so its invoices go back to unpaid — one transaction, and the reason you pick decides which of them happen. Pick “technical” — your own wrong date, a missing endorsement — and no fee is charged, because charging a client for your clerical mistake is how a small error becomes a lost client.
Drive the clock month by month. Stop on the bounce and watch four things land together. Then look at the custody count — which cheques the system believes you are physically holding, and where.
C-2026-0184 · Gulf Contracting LLC
Al Quoz Camp 1 · 240 of 384 beds · 01 Jan – 31 Dec 2026 · AED 2,160,000 for the year, handed over as twelve cheques on the day of signing.
Day one — 28 Dec 2025 12 in the safe, 0 at the bank, 0 cleared.
12 instruments issued against this contract, 12 accounted for, counted as at 28 Dec 2025. A returned cheque is still a piece of paper in a drawer — it is worth nothing and it is still yours to hold, which is why it is counted and not deleted. A schedule of due dates cannot answer this question at all.
Against these sit four outbound cheques to the landlord — AED 1,440,000 for the whole property, all 384 beds, written the same week. This one contract of 240 beds covers every dirham of it and AED 720,000 besides. That is the two-sided lease: one asset, two chequebooks, and a spread rather than a rent roll.
Eleven cheque states, from received to recovered — only the legal next moves are ever offered
And what it does not do
Step 06 of 8 · Wednesday, 06:12
The air conditioning stops in C-204. The job does not arrive by phone: a resident points a phone at the sticker on the door and the fault is raised already attached to the right bed, in the right unit, in the right property, with no sign-in. That is one of seven ways a job can start — the portal, a staff member, a call logged at the desk, the QR code, a failed inspection, a planned-maintenance schedule, an incident follow-up. A work order attached to nothing is refused outright.
It is triaged by 06:41 and assigned by 07:02, and then it stops: the compressor capacitor is on order from Jebel Ali and takes 29 hours to arrive. Both of the job’s clocks stop while it is awaiting parts, and pausing needs a written reason. That single subtraction is the difference between a maintenance team that looks like it failed and one that did not — and if the clock kept running, the lesson every technician would learn is to never record a hold.
As the product counts it — 5 h against a 24 h fix target
Met, with 19 hours in hand
If the clock never paused — 34 h, because the compressor took 29 h to arrive
Breached by 10 hours — the same job, the same technician
Both clocks stop while a job is on hold or awaiting parts, and pausing one requires a written reason. A supplier who takes a day and a half is not your maintenance team failing — and if the clock kept running, the lesson every technician would learn is to never record a hold, which loses you the one signal saying where the delays actually are.
It cannot be closed on the word “fixed”. Marking it done requires a written description of what was actually done and the labour hours; a P1 or P2 also needs at least one photograph before and one after; and if the technician needed access to an occupied room, somebody signs that the room was left in order. Every missing item is listed at once, because a technician told one problem at a time on a phone in a corridor gives up and finds a way round the check.
Verification is then a separate step with its own permission, and it is refused if the verifier is the person the job was assigned to — refused by the database as well as the application, so it survives anybody rewriting the code.
And in the same week a man leaves. His bed goes into notice period before it is empty, so it appears in “coming available” while somebody still sleeps in it. When the move-out completes, the bed goes to turnover and the clean is raised in the same transaction — and passing that clean is the only thing in the product that returns a bed to available.
Completing the move-out needs all five, and names whichever is outstanding
Then the clean, which has six items of its own. Pass every one and the bed moves from turnover back to available and the status change is recorded. Fail one and the bed is clean and still not lettable — a room whose light does not work is not a room you can sell. Nothing else in the product returns a bed from turnover, which is the point: a bed somebody left with no clean behind it would otherwise be permanently unlettable, in a business whose central number is how many beds are lettable.
Ten states a work order moves through
And what it does not do
Step 07 of 8 · Any morning
The man who runs Al Quoz needs everything about the site: the job list, the asset register, the room handover sheet, the repair history, who is inside the fence this minute, whose papers lapse this month. He needs none of the money. More than that, he must not have it — what Rashid pays that landlord is the one number that would let a competitor outbid him for the building.
A screen can hide a field. It cannot un-send one. Anything that reaches the browser is in the network tab, in any log, and in anything holding that login — so the figures a role must not see never leave the server at all. The site dashboard goes further and never asks for them: nothing in it queries an invoice, a payment, a rate or a cost, so there is no money field in the response for anything to leak.
Where a figure is withheld it is withheld, not deleted. The tile keeps its label, its unit and its definition and names the permission that would open it, because an empty cell reads as “there is no revenue” rather than “you may not read this”. This project shipped that mistake once.
Pick a tile, then step through the seven roles and watch that one figure open and close. It is not a hierarchy — look for the three places it refuses to be one.
Everything in the organisation, including billing and the danger zone.
OwnerThe owner sees the whole board. Nothing here is withheld from them — which is the only reason the other six views are worth looking at.
Pick any figure to see the permission key that governs it, and which of the seven roles hold it.
Withheld, not deleted — the tile keeps its label, its unit and its definition, so nobody mistakes you may not read this for this is empty. And the redaction happens before the JSON is written, not in the markup: a screen can hide a field, it cannot un-send one.
And what it does not do
Step 08 of 8 · Friday
What did the month actually do? Forty-six named reports over twenty-nine published data views, thirty-three KPIs each carrying the sentence that defines it, and five dashboards written for five different jobs — because a camp supervisor and a finance controller do not want the same screen with different rows hidden.
A report Rashid’s camp boss is not allowed to run is not on his list. Not greyed out — omitted. A greyed row named “Head-lease obligations” tells a supervisor that head-lease cost exists and roughly what it is called, and the list of questions a company asks is itself information.
Withdraw financial visibility on the wall below and watch it go dark — including three reports that are not in the Financial group, because the gate is on the number rather than on the tab. Then switch to a site supervisor and press the same switch: nothing happens at all, because that role never held a money permission to withdraw. That last fact is computed from the real role bundles, not asserted.
Type “gate pass”, or “mess”, or “cheque” into the search. Switch the role. Then withdraw financial visibility and count what disappears.
46 reports in the catalogue — 46 available to a Property Manager.
Full operational and commercial control within scope. Every report declares one permission, and that declaration is the gate — there is no /reports/rent-roll endpoint to go round.
Blank, never zero
A property with no beds has no occupancy rate; a month with no invoices has no collection rate. Those come back empty rather than as 0% — a zero sorts worst in a league table and drags the estate average down, so a camp still in fit-out would make the whole portfolio look like it was failing.
Last night stays last night
Every night the system records that day’s KPIs, for the estate and for each property. Sparklines are drawn from those recordings rather than recomputed — so the March figure you gave your board does not silently change in June when somebody corrects an allocation.
Targets that know which way is good
A target can be set on any KPI, for the estate or one property, standing or for a single month. At or above is green, within 10% amber, below red — and it inverts automatically where lower is better, because a rising arrears ratio is not an improvement and nobody should have to invert it in their head at 7am.
And what it does not do
The end of the month
The tour skipped the parts that do not fit a single narrative: the CRM funnel before the contract, the resident and corporate and landlord portals, housekeeping rotas and the stores, the notification catalogue, the automation rules, and the platform side — packages, quotas and the console that runs them. Those are all in the catalogue.