Every client asks the same question in a different phrasing: where does my project actually stand? Most contractors answer with a monthly report, a phone call, or a WhatsApp photo with no context attached. Between updates, the client fills the gap with their own assumptions about delay or a hidden problem — because an absence of information is almost always read in the worst direction. A client portal replaces all of that with one link that shows what is true right now, without asking the client to hold an account or remember a password for a project they open twice a month.
Key takeaways
- The link itself is the credential — no account, no password, no sign-in step.
- The client sees progress, milestones, budget by category, variations, open RFIs and recent photos — whichever of these actually has data yet.
- The data is a snapshot as of the last update, not a live feed — and the page says so.
- A brand-new project with no budget entered yet does not render a broken page; every section shows or stays hidden on its own.
- Internal detail — unit prices, supplier identities, your team's internal discussion — stays internal unless deliberately rolled into what is shared.
Why the monthly report quietly erodes trust
The problem is not that the monthly report lies. The problem is that it is structurally late: assembled from data that is a week or two old by the time it is sent, landing in the client's inbox among dozens of other messages. Between one report and the next, the client calls, or shows up at the site unannounced, or sends one message with three question marks. Not because they are anxious without cause — because the gap between what they know and what is actually happening widens with every day that passes without an update.
- A hand-assembled report costs the project engineer real time every month — time that never appears on an invoice.
- A WhatsApp photo with no date and no caption gets opened once and forgotten, and never becomes a record anyone can return to.
- A phone call carries an impression, not a number — the client remembers the tone more than the detail.
- Any question raised between two reports requires rebuilding the answer from scratch instead of pulling it from one place.
The real cost is not the preparation time alone. It is that a client who feels like the last to know starts treating every subsequent delay as something that was hidden from them first — even when it was not.
What the client actually sees
The client portal is a single, read-only page built from the same sections your team already uses internally — not a stripped-down summary rewritten for the client, but a direct reflection of what is recorded on the project.
| Section | What it shows |
|---|---|
| Progress and dates | Overall percent complete, start date, and expected completion date |
| Milestones | Total milestones, how many are achieved, and how many are overdue |
| Budget | Budget against actual spend, broken down by category: labour, materials, equipment, subcontractors, overhead, other |
| Variations | Approved change orders, with their cost and schedule impact, and the date signed |
| Open RFIs | A list of requests for information that have not yet closed |
| Site photos | The most recently uploaded photos from the site |
Notice what is deliberately absent from this table: no unit-price breakdown inside any line, no supplier name behind a cost figure, no view into your team's internal discussion on an RFI — only its status. The portal shows the outcome that matters to the client, not the mechanics behind it.
No login is not a gap — it's the point
A project owner who opens a progress link once every two weeks will not remember a password they created two months ago. Every additional account is friction: a verification email, a password, maybe two-factor authentication, then a "forgot password" flow on the third visit. The client portal skips all of it with a different design: the link itself is the credential.
The project team generates a link
One link tied to the project, with no setup required from the client.
The link is shared directly
By email or message — the same way any other link gets shared.
The client opens it on any device
No app to install, no sign-in step, on a phone or a laptop.
They see the project as it stands right now
Current as of the last time data was entered on the project.
Day one of a project isn't an empty portal
A project that was just created, with no budget lines entered and no photos uploaded, should not hand the client a page that looks broken. Every section on the portal is independent of the others: it renders if its data exists, and stays quietly absent if it does not yet — instead of showing an empty table or an error message that confuses someone with no technical background.
- The progress-and-dates section is the only one required to render at all — every other section is optional depending on what exists yet.
- A project with no budget entered yet shows progress and milestones only, rather than an empty budget block that raises a question it does not need to.
- The first photo uploaded from the site makes the photo section appear on its own — nothing to switch on manually.
- An expired or revoked link shows a clear message asking the client to contact the contractor, not a generic, confusing error.
This matters more than it sounds like in the first two weeks of any project — exactly the window where a new client wants to see that things are moving, not a blank screen that makes them second-guess their choice of contractor.
What the client doesn't see
The most common reservation a contractor raises on hearing about a client portal is always the same one: will my client see my margin? Short answer: no, not unless you deliberately put it there.
- The budget renders by category (labour, materials, equipment, subcontractors…), not line by line with unit price and quantity.
- The supplier or subcontractor name behind any line never appears on the portal.
- Your team's internal discussion on an RFI stays internal — the client sees only its final state: open or answered.
- The portal is entirely read-only — no comment, no edit from the client side. Any question still goes through your usual channel with them.
If a client needs more than a view — an actual seat on the team — that is a different arrangement: the "Client (view only)" role inside muqawil's permission system gives them a real account instead of a portal link, but it stays without access to financial detail too, by the same design.
How this works in muqawil
The client portal in muqawil is one link per project, with no account and no password, showing progress, milestones, budget by category, approved variations, open RFIs and recent photos — every section rendering or staying hidden based on what actually exists. The page is bilingual and works on any phone that can open a link, and it always carries the date of the last update so the client knows they are looking at a snapshot, not a live feed.
- One link per project, generated and shared with no setup required on the client side.
- Independent sections that adapt to what the project actually has.
- Financial figures render by category only — no internal pricing detail.
- Full Arabic and English interface, works from a phone with no app to install.
Frequently asked questions
Does the client need to create an account to open the portal?
No. The link itself is the credential — the client opens it on any device with no sign-in step and no password.
What happens if the link reaches someone it was not meant for?
Since the link is the credential, treat it the way you would a password. If you suspect it reached the wrong person, reissue a fresh link for the project. The page is deliberately excluded from indexing and caching, but that is an added safeguard, not a substitute for treating it as sensitive.
Is the data on the portal live?
No — it is a snapshot as of the last update to the project, and the page states that plainly in its footer. That is far more current than a monthly report, but it is not a real-time feed.
Our project is brand new with no budget entered yet — will the portal look empty or broken?
No. Every section is independent and renders only if its data exists. A new project shows progress and milestones, and the rest of the sections appear as data is entered.
Can the client comment or request a change from inside the portal?
No, the portal is entirely read-only. Any question or note still goes through your usual channel with the client, not through the portal itself.
Will the client see our margin or our supplier pricing?
No. The budget renders by broad category (labour, materials, equipment…) rather than line by line with unit price, and supplier or subcontractor names never appear behind a figure.
Send a link, not a PDF
Generate a portal link for one of your projects in muqawil, and try opening it from your phone exactly the way your client would.