One project. One record. Everyone works from the same truth.
Owners, contractors, and consultants work in one place. The agreement, the work, the inspections, and the money all live on the same record, so there is nothing to argue about later.
Document control & approvals for GCC construction
Owners, contractors, and consultants work in one place. The agreement, the work, the inspections, and the money all live on the same record, so there's nothing to argue about later.
The priced line is the spine.
Most tools keep your documents in one place and your money in another. Hallal puts them together. Your Bill of Quantities sits at the center, and every document does something to a line: a shop drawing clears it to build, an inspection turns it into earned value. Paper and money become one trail.
An approval isn't a stamp. It's a transaction.
Four systems, one priced spine.
Every document type: RFIs, submittals, NCRs, transmittals, method statements, all structured and on one audit trail.
The spine. Rates split three ways, value earned in stages and proven by inspection. Cost-coded, never guessed.
Certify on site and the value earns itself. The payment certificate builds itself, ZATCA-correct.
Cross-party approvals, working-day deadlines, and a tamper-proof record ready for any claim.
One system. Three parties. Each one sees what matters to them.
Before any money goes out, you see what's been built, inspected, and approved, line by line, priced. Retention and advance are handled for you.
A time-stamped history, ready the day a claim lands
See where every submission sits, whose desk it's on, and how long it's been there. The moment work is inspected and signed off, you can bill it.
Interim certificate builds itself, ZATCA-correct
Retention, VAT, advance recovery, done in seconds
Everything to review is in one place, with a clock on it. No email digging, no "which version was this?" Give a coded verdict, comment where it matters, send a rejection back to the right step.
It has read every line. It never signs one.
Hallal AI works from the same priced spine as everyone else, so every answer, draft, and flag comes from the live record, not a guess. Ask it anything about the project in plain language. It replies with the lines, documents, and dates behind the number.
"How much of the façade is certified, and what's blocking the rest?" is answered from live data, every figure traceable to its source.
RFIs, method statements, rejection reasons, certificate narratives, pre-filled from context, yours to edit and send.
A claim above certified quantity, a variation that double-counts, a review past its clock, surfaced before it costs anyone.
Grounded, cited, and never the decider. It surfaces and drafts; a named human always signs.
Follow one BOQ line, "supply & install 200 façade panels," from empty to paid.
Value, retention, advance, VAT, the review clock, lump-sum vs remeasurable. All captured once, signed off through the same flow. Every number downstream now has a source of truth.
The QS splits the rate three ways: material, manpower, machinery. Then it picks how it earns in stages: 60% on supply, 40% on install. "Percent done" becomes a fact you can bank.
Contractor submits; consultant and owner approve. The BOQ becomes the live baseline. Need to change pricing before money moves? Propose a revision. The last approved version wins.
The façade shop drawing is uploaded and linked. The consultant approves. The line flips from defined to live, cleared to build. No live line, no claim. Ever.
Panels land on site. A material inspection is verified. 60% of the line's value, the supply stage, earns automatically. The owner sees it; the contractor can bill it.
80 of 200 panels installed. The consultant certifies on site, maybe 80, maybe 75. Certified quantity × rate × stage weight earns instantly. Fail, and nothing earns. It's logged honestly.
Contract → variations → revised → earned → certified → retention held → advance recovered → net payable, right now. One number. No versions.
A variation order is approved and applied as new lines, original IDs untouched, so earned history stays intact. An omission can't remove more than what's left unclaimed.
Retention drops 10%→5%, effective next month. A forward-dated amendment. Past certificates untouched; the next uses the new rate. Nobody re-litigates the past.
Month end: the interim certificate sweeps every newly-certified item, deducts retention, adds 15% VAT, recovers the advance, ZATCA-correct, in a click. The invoice was never typed. It was earned.
10 STEPS · 3 COMPANIES · 1 LINE · 0 ARGUMENTS
Under the hood: in plain terms.
Retention, advance, VAT, terms, captured once, applied everywhere, resolvable at any date so amendments never corrupt the past.
The 3M split and stage recipes turn percent-complete into a defensible, earnable fact.
Real quantities, real guardrails. Certify against them and value earns itself.
Contract → variations → revised → earned → certified → retention → advance → net. Computed from signed reality.
The interim certificate is the invoice, assembled, tax-correct, in a click.
Variations amend the right lines; amendments change terms going forward. Two clean registers.
Working-day SLAs that turn amber then red before a delay costs anyone.
Earned value flows out by cost code to your ERP. The money story doesn't stop at the platform edge.
The document types are a language. Hallal already speaks it.
To an outsider they're just acronyms. On site, each one is a promise about what happens next: who can raise it, how it's numbered, who approves it, and what it does to the line and the money. Pick the type. The rules take care of the rest.
Approvals that move between companies.
Most tools route approvals inside one company. Hallal routes them between companies that don't share a system, on one shared, tamper-proof record where each party sees their part.
Between companies: contractor submits, consultant reviews with a coded verdict, owner signs.
Inside each company: experts weigh in together, before the company answers with one voice.
A rejection routes back to the exact step that needs fixing. Every round stays on the record.
If it's tangled across inboxes, chat threads, and three companies' spreadsheets, that's exactly where Hallal starts.
The answer, before the question is asked.
The flood of daily events, turned into the few views each party actually needs. The register exports to a spreadsheet exactly as you see it, so the report you read is the report your board gets.
Every document, its reply code, who reviewed it, days taken, lines touched.
How much is truly earned, sliced the way finance thinks. Feeds the ERP.
Approval rates, days-to-review, and the reviews blowing past the clock.
Every open document, the party it is sitting with, and the days it has been there.
Who's uploading, reviewing, commenting. Accountability without a witch-hunt.
It interrupts you only when a human is needed, and tells you what to do.
Most systems send so many notifications that people mute them, and miss the one that mattered. Hallal does the opposite, on purpose.
A working-day clock on every review; amber, then red
One notification center, not five: one click to the thing that needs you
This work is being claimed but hasn't passed inspection. Don't pay it yet.
This line's been rejected three times for the same reason. Someone needs to make a call.
Four inspections are due this week and the consultant who signs them is on leave.
You've been asked to approve this. Here's the one line that changed since last round.
The quiet assistant · never decides for you · judgment, not noise
One focused platform. Not six stitched-together tools.
One tool for documents, another for the field, a third for drawings, and an inbox for everything else. Most projects run on five or six systems that do not talk to each other, and still argue about what is true.
The priced document record, and nothing else. No modules to configure, no seats to justify, no features you will never open.
One inbox, one BOQ, one audit trail. What matters to your role is what you see, not a settings menu.
All three parties included from day one. No enterprise sales call, no surprise tier six months in.
Most tools digitize one piece and leave you to connect the rest. Hallal connects it for you.
Documents in one system, money in another, reality in a third
One priced spine where documents, approvals, and money are the same record
Each company keeps its own files → three versions of the truth
Cross-party by design: one shared, tamper-evident record
Earned value is a fact: verified by inspection, priced, cost-coded
The payment certificate is a monthly spreadsheet ordeal
The certificate builds itself: retention, VAT, advance, tax-correct, in a click
Approvals rot in inboxes; disputes surface at handover
A clock on every decision, and a history that ends most disputes early
Your data is trapped; "integration" means a support ticket
Open API, clean exports, no lock-in. Your data travels on your terms.
Built for one country's paperwork, bolted onto others
Local from the start: Arabic, ZATCA-correct tax, the region's contract reality
Bring it in fast. Take it out anytime. No lock-in.
Drop it in. Sections, quantities, rates, cost codes, and the 3M split all come across in one guided step, with per-row checks that show exactly which lines to fix first. No re-typing thousands of rows.
Every register exports to the formats your stakeholders expect: submissions, earned value, cost-by-trade, project health, the certificates themselves. Print-ready when someone still wants paper. Your history is always yours to pull out.
An API your team will actually enjoy.
Not a locked door with a keyhole. A clean, documented REST API your engineers can build on, without filing a support ticket.
GET /v1/projects/:id/earned-value?by=cost_code
One priced spine. One shared truth. One platform.
Simple enough for the site, trusted enough for the boardroom, so the record is actually complete when you need it.
Related