It is seven in the morning on a site in the New Administrative Capital. The site engineer sends a voice note to the WhatsApp group asking for rebar before tomorrow's slab pour. The foreman writes the day's labourers in a school notebook. The plastering subcontractor is on the phone to head office, asking for the third time when his progress claim will be paid. Meanwhile a second site on the North Coast is waiting for concrete trucks, a rented loader stands idle at a third site in New Cairo because nobody renewed the hire, and the technical office in Nasr City is pulling quantity take-offs from scattered Excel files to make this month's claim. This scene is illustrative, but anyone who owns a contracting company in Egypt will recognise every detail of it.
The owner can see columns rising and cheques going out, yet cannot answer simple questions with confidence. Is this project making money as of today? How much have we spent on the concrete item against what we priced in the bill of quantities? How much do clients owe us in unpaid claims and unreleased retention? And what do we owe subcontractors and suppliers next month? That is usually the moment someone starts looking for construction management software in Egypt.
This guide is for contracting company owners, project managers and technical office heads, not programmers. It covers the warning signs, the modules a company running several sites needs, ready-made versus custom, cost factors, and the first 30, 60 and 90 days. At Jad Digital we have been building custom business systems since 2019, and we will tell you plainly when a ready-made product is the smarter choice.
If you build in the Saudi market, the tax and contract picture is different, and we cover it in our guide to a construction ERP in Saudi Arabia.
The short answer
Construction management software in Egypt is a system that ties the bill of quantities to the site and the accounts in one record: items and rates, client and subcontractor progress claims, material requests, equipment, daily labour, retention, cash flow and cost per project.
- The bill of quantities (BOQ) is the foundation of construction management software: every item, with its quantity, rate and price analysis, becomes a budget line that actual site spending is measured against for the life of the project.
- Subcontractor progress claims in construction management software are built from quantities measured and approved on site against contract rates; the system then deducts advance recovery, retention and issued materials to show the exact net amount due.
- A site material request in construction management software starts on the engineer's phone, is checked automatically against the quantity remaining in the BOQ before approval, and becomes a purchase order or a transfer from another site's store.
- Cost per project in construction management software is built from materials, daily labour, equipment, subcontractors and petty cash, all coded to BOQ items, so the owner sees a project's profit during execution rather than after handover.
- Retention and cash flow in construction management software show what clients owe you in claims, retention and guarantees, and what you owe subcontractors and suppliers, so you can plan liquidity across all sites before a crisis arrives.
- The cost of construction management software depends on the number of sites and users, the depth of the claims cycle, the site app, integrations with accounting and e-invoicing, data readiness, and the choice between ready-made and custom.
Signs that Excel and WhatsApp can no longer run your sites
You know you have outgrown them when the following signs appear together, not when a competitor buys a new system:
- Project profit is only known after handover. The numbers are assembled from site notebooks and bank statements at the end, and you learn too late that an item you priced confidently was losing money from the first pour.
- The monthly claim takes weeks. The technical office collects quantities from several files, the consultant sends comments back, the approved version gets lost in the messages, and collection slips along with everybody's payments.
- Subcontractors claim more than they built. There is no single record of what was previously approved, so the same quantity appears in two claims, or someone is paid beyond their contract quantity without anybody noticing.
- Material requests arrive as voice notes. An engineer asks for rebar on WhatsApp, nobody compares the request with the quantity remaining in the BOQ, and purchases creep above budget with no explanation.
- Daily labour sheets cannot be audited. Names are handwritten, the money leaves in cash, and you cannot tell whether those people were on site at all.
- Letters of guarantee catch you by surprise. You remember one when the bank calls, and old retention sits with clients unclaimed because nobody tracks the dates.
What makes contracting different from a generic ERP
The difference is that the unit of work in contracting is the project and the BOQ item, not the invoice or the stock item. A generic system assumes a company that buys and sells from a fixed location. A contractor sells first, at a price fixed during the tender, and then discovers the true cost over a year or more at a temporary location far from the office.
Any construction software has to understand a few more things:
We explain the general logic of comparing software in ready-made accounting software versus a custom system. Even sectors with a similar cost-per-order idea, such as a garment factory management system, work from a fixed place with known lines, while your site starts as empty land and disappears after handover.
- Revenue follows approved quantities. You do not earn money because you delivered a product. You earn it because a consultant approved a measured quantity in a claim.
- Each project is a small company. It has its own budget, store, labour, subcontractors and manager. A profitable project can sit beside a losing one, and the combined figure hides both.
- The subcontractor layer. Much of the work is done through subcontractors with their own agreements, rates, claims and retention, which makes you a contractor and an employer at the same moment.
- The most important user is not in the office. The engineer, the foreman and the storekeeper stand on a dusty site with a phone. If the system does not suit them, they go back to paper.
Message us on WhatsApp or book a free consultation — we answer plainly, with no obligation.
The modules a contractor running several sites actually needs
A contractor needs about a dozen connected modules, running from the BOQ to site reporting, though they should never all be built at once.
BOQ and price analysis: from the technical office to the budget
The bill of quantities is where any serious construction software begins. The system stores each item with its number, description, unit, contract quantity and rate, and keeps a version for every revision, so you know which BOQ was in force when a given claim was issued. It must import the BOQ from Excel as it arrives from the client or the consultant, because nobody is going to retype hundreds of items by hand.
Behind every rate sits a price analysis: how much cement, sand, gravel, labour, equipment and subcontract work goes into a cubic metre of concrete. Once the system holds those analyses, the BOQ turns automatically into a budget per resource.
Cost per project and per item: planned versus actual
Cost is the number you buy the system for. Every movement in the company, whether a cement issue note, a daily labour sheet, a subcontractor claim, a loader hour or a diesel receipt, has to carry a project code and an item code. The system can then show three figures side by side for each item: planned in the budget, actually spent to date, and the forecast remaining until completion.
Comparing what was spent with what was claimed is not enough. A good system also counts commitments, meaning open purchase orders and unexecuted subcontract work, so the picture lands closer to reality. How revenue and cost are treated in the books is your accountant's decision, and the system applies it consistently.
Client progress claims: take-off, approval, interim and final
The interim claim is your collection cycle, and every day it slips is a day you finance the project out of your own pocket. The site engineer measures executed quantities against BOQ items and attaches measurements, drawings and photos. The technical office reviews the take-off, and the system produces the claim in cumulative form: previously paid, executed this period, total to date, then the agreed deductions.
The claim then goes to the consultant or the supervising body and usually comes back with adjusted quantities. The system should record the submitted and the approved quantity for each item with the reason for any gap, and track the claim's status: submitted, under review, approved, invoiced, collected.
Variations and change orders
The most dangerous leak in contracting is work done on a verbal instruction whose price was never agreed. The system needs a variation register: who asked, when, which items are affected, the quantity, the proposed rate, the approval status and the supporting document. The engineer can open a request with a photo from the phone before starting, so your entitlement is not lost months later when everybody disagrees about what was said.
Subcontract agreements and subcontractor claims
A subcontractor is your client in reverse: you are the one who approves, deducts and pays. Each subcontractor, whether for plastering, electrical work, plumbing, formwork, steel fixing or painting, has an agreement in the system with its items, quantities and rates, linked to the client's BOQ items. The system can then compare what you pay with what you claim for the same item, and it reveals any item you have given away for more than you collect.
A subcontractor claim follows the same path: a take-off signed by the site engineer, then deduction of the advance instalment, retention, materials you issued from your store, equipment, and the cost of fixing defective work, leaving the net amount due. The system blocks quantities beyond the agreement unless someone approves them, prevents the same quantity being claimed twice, and keeps a full history for any dispute.
Site material requests and purchasing
The right cycle starts with a request from the site and ends with a signed goods receipt. The engineer opens the request on the phone: item, quantity, BOQ line and the date it is needed before the pour. The system immediately shows what was planned for that line and what has been issued, and anything beyond the remaining quantity goes to the project manager for special approval. The purchasing officer sees requests grouped from all sites, checks whether another site has a surplus, or collects quotations and issues a purchase order with the supplier, price and delivery date.
On site, the storekeeper records the actual quantity received with a photo of the delivery ticket, especially for ready-mix concrete, sand and gravel, where disputes over truckloads are routine.
Site stores, custody and transfers between projects
Every site is a temporary warehouse, and its biggest losses are invisible. The system needs a balance per site, issue notes linking every outgoing item to a BOQ line and a subcontractor, inter-site transfers confirmed by the receiving side, periodic counts by phone, and custody records for tools such as formwork, vibrators and scaffolding under named people. The principles of balances and counts are close to what we describe in our guide to a warehouse management system in Egypt, except that this warehouse moves with the project.
Owned and hired equipment
Equipment is a cost that runs by the hour whether it produces or not. The system records every machine, owned or hired, from loaders, excavators and cranes to mixers, concrete pumps and generators, with its operator and current location. The site supervisor logs running hours, idle hours with the reason, and diesel each day, so each item carries its true share.
For hired equipment the system holds the hourly or daily rate and the hire period, and it matches the owner's invoice against logged hours before payment. For owned equipment it tracks maintenance by running hours and calculates operating cost.
Daily labour and labour contractors
Daily labour is the hardest item to control because it is cash and it changes every day. The alternative to the notebook is a digital sheet the foreman completes on the phone: name, trade, BOQ item, hours and overtime, approved by the engineer the same day. From it the system calculates wages due, advances and payments, and charges the cost to the item.
Where a labour contractor supplies workers at a daily rate, the attendance sheet becomes the basis of his claim. Rules on social insurance, tax and worker contracts change, so confirm them with your accountant and the official authorities.
Retention, letters of guarantee and advance payments
This is the module for money in limbo, and a whole project's profit can disappear here without anybody noticing. Retention runs in two directions: what the client holds from you, and what you hold from subcontractors. The system records it in every claim according to the contract rate, tracks the balance per project and the release date tied to provisional or final handover, and reminds you before it is time to claim.
The same goes for letters of guarantee, whether bid, performance or advance payment guarantees, each with its number, bank, value and expiry, an alert before expiry at a lead time you choose. The advance payment is recovered gradually from each claim according to the contract, and the system shows what remains. Tax deductions from claims and VAT treatment vary with the contract and the client, so confirm them with your accountant and on the official portal, and the system will apply what you decide.
Cash flow across all projects
Many contractors make a profit on paper and still struggle at the bank, because one late claim from a big client can stop a pour on another site. The system combines expected inflows from submitted and approved claims and retention falling due, adjusted for each client's payment habits, with expected outflows from subcontractor claims, supplier cheques, hire charges, daily wages and payroll.
The result is a weekly schedule for the company and for each project. You see weeks ahead where the squeeze will come and can decide accordingly: which payment to defer, which claim to chase, and whether to bid on that new tender at all. The system also has to manage post-dated cheques, issued and received, by their due dates, because they are the working language of Egyptian contracting.
Site reporting from a phone
The site app is what turns the system from an office program into a picture of what is really happening. The goal is a daily report in minutes: work done, labour and equipment on site, materials received, dated photos, and problems such as late drawings or waiting for materials.
It has to work offline on new sites and sync when the signal returns, with simple Arabic screens and large buttons that suit a dusty hand. We build this kind of field tool through our mobile app development for businesses service.
Hardware and integrations: what you actually need
You need simple hardware and a few integrations, and the integrations matter more than the devices.
E-invoicing. A registered contractor issues invoices for its claims, and in many cases those invoices fall within the Egyptian Tax Authority's e-invoicing system. In practice, the invoice generated from an approved claim is submitted to the platform with the client's tax details and the required coding, instead of being retyped into the portal. We walk through the mechanism in our guide to connecting your system to Egypt's ETA e-invoicing. Because obligations depend on how your company is registered and on the type of contract, confirm your position on the official portal and with your accountant.
Accounting. Either accounting lives inside the system, or the system connects to the package your accountant already uses, so entries for claims, purchases and retention flow automatically instead of being typed twice.
- Android phones for engineers, foremen and storekeepers, with rugged cases, a battery that lasts the working day and a decent camera.
- A backup mobile data line per site, while making sure the app still works with no network.
Ready-made construction software or a custom system?
Both answers are right for different companies, and the honest test is the number of sites and how specific your financial cycle is.
When ready-made is enough
A small company running one or two projects at a time, with simple BOQs, few subcontractors and one accountant following everything, is usually well served by ready-made construction software on a subscription. You get a tested claims cycle and updates you do not have to manage, and you can start within weeks. We will not tell you otherwise: building a custom system for a company that size is usually not economical.
The trade-off is that you adapt your work to the tool, fees grow with users.
When custom pays off
Custom starts to make sense with several simultaneous sites across governorates, claims cycles that differ between government bodies and developers, many subcontractors and labour contractors, a site app shaped around how your engineers really work, owned equipment that needs true costing, or a link to an accounting package you do not want to replace. You own the code and the database and pay no per-user fees. The trade-off is a longer build and the need for a real partner after launch. The general version of this decision is in custom ERP versus off-the-shelf.
The middle path
Many companies keep their current accounting package and build a custom layer on top for what makes contracting different: the site app, material requests, claims and the owner's dashboard. That phased path is how we build custom construction management software: the biggest problem first, with each phase working on a real site before the next begins.
What determines the cost of construction management software?
The cost is set by the scope of what you will really manage, not by the project's title, which is why no single figure fits every company. The main factors:
Start from a real running project rather than a wish list: book a free consultation to scope your construction system, and we will work out with you which modules deserve to come first and which can wait.
- The number of modules you start with, and whether they include tendering and pricing or execution only.
- The number of sites and users, with their roles and permissions.
- The depth of the claims cycle: approval stages, formats that differ between clients, and the link between subcontractor and client claims.
- Integrations: accounting, e-invoicing, the programme of works and attendance devices.
- Data readiness: the BOQs, open balances and previous claims that must be migrated for running projects.
- The commercial model: a subscription to a ready product, or ownership of a custom system built in phases, along with support after launch.
The first 30, 60 and 90 days
In this period you typically move from understanding to one pilot site and then to several. This is an approximate sequence for a mid-sized custom project, and the real schedule is set after visiting your sites.
The first 30 days: understanding and foundations
A site visit and working sessions with the technical office, purchasing and accounts, followed by a map of the real cycle from material request to paid claim. Then come unified codes for items, materials, subcontractors and equipment, the choice of one running project as the pilot, and loading its BOQ and subcontract agreements.
From 30 to 60 days: one site on the ground
Material requests, the site store, the daily labour sheet and the daily report go live on the pilot site, with a careful opening stock count and training for engineers and foremen where they work. The first subcontractor claim runs through the system, side by side with the old method so you can compare the two.
From 60 to 90 days: claims and expansion
The client claim is issued from the system, retention and letters of guarantee are added, and accounting and e-invoicing are connected. A second site follows, then the others gradually, and the owner's dashboard starts feeding a weekly meeting on real numbers.
A checklist to bring to your first meeting with any software company
A first meeting is far more useful if you bring these, with any company and not only with us:
To turn these materials into a structured document, read our guide on how to write a software project brief.
- A real BOQ from a running project, in the form it reached you from the client or consultant.
- An actual client claim and subcontractor claim, including deductions and retention.
- A typical subcontract agreement, and an example of a variation or additional work order.
- The Excel files your technical office, purchasing and accounts work from.
- Paper forms from site: material request, delivery ticket, daily labour sheet and daily report.
- A list of current sites, their locations and size, and next year's plan.
- The software you want to keep, such as your accounting package, and how you currently handle e-invoicing.
- The three problems you most want solved first, in order of priority.
How Jad Digital builds construction management software
We build in phases starting from a real site, not from a list of features. The work begins with a workshop at your office and a site visit where possible, walking with your technical office, purchasing and accounts through the path of an item from BOQ to collection, and mapping where information and money get lost. We then define the first phase that solves the biggest problem.
After that we deliver in short phases you can see and try: Arabic and English interfaces, a site app that works offline, role-based training at the place of work, and support that continues after launch. You own the code and the database at handover. And if we believe a ready-made product will serve your company better at this stage, we will say so in the first meeting.
Choosing who builds your system follows the rules for choosing any technology partner, which our guide to choosing the best software company in Egypt covers in detail. Book a free consultation with our ERP solutions team for contractors, bring the checklist above, and we will leave the meeting with a specific next step.
Frequently Asked Questions
What is the best construction management software in Egypt?
+
No single program is best for every company. The right one matches your number of sites, your claims cycle and the way your engineers work. Ask any vendor to run a complete claim in front of you using real data from your own project.
What is the difference between construction software and normal accounting software?
+
Accounting software records invoices and journal entries after they happen. Construction software starts from the BOQ and the site: items and quantities, progress claims, subcontractors, material requests, retention, and cost per project and item. It then passes the final entries to accounting.
How does a system help prepare progress claims?
+
The site engineer records measured quantities against BOQ items, the technical office reviews them, and the system produces the claim in cumulative form showing previous, current, total and deductions.
How can I know the profit of each construction project during execution?
+
Every transaction must carry a project code and an item code: materials, daily wages, equipment, subcontractor claims and petty cash. The system then compares planned with actual and adds open commitments and the remaining cost to complete, giving you a forecast profit that updates as work progresses instead of a number at the end.
Does a small contracting company need a management system?
+
It needs an organised record more than it needs a big system. With one or two projects, simple ready-made software with a claims cycle and cost per project may be enough. The need for something custom begins when sites multiply and the owner can no longer follow everything personally.
Can construction software connect to e-invoicing in Egypt?
+
Yes. An invoice can be generated from the approved claim and submitted to the platform directly or through an intermediary, with the client's tax details and the required coding. Because obligations depend on your registration and the type of contract, confirm the current requirements on the official portal and with your accountant.
How long does it take to implement a contracting company system?
+
Simple ready-made software can be running in weeks, while a custom system is usually delivered in phases over several months depending on modules, sites and integrations.
