The GoCONSTRUCT modules

The floor every edition stands on. Access is controlled per project and per branch; every field change is recorded with who changed it, when and from what; documents attach to projects, tasks, requisitions, purchase orders, work orders and RA bills rather than living in someone's email.

The back office is usable on a tablet or phone, which is what a site engineer actually has. Sites, contacts and leads can be seen on a map. Backup, monitoring, patching and disaster recovery run under the Go Live managed service.

A tender master with sequence, dates, department and job type, published to a public contractor portal. Pre-bid enquiries and a structured questionnaire are captured against it, and an amendment can be issued with controlled revision and re-notification.

Bidders price line by line against material, labour and overhead schedules. Every bid is then compared against your internal estimation workbook with a configurable ranking template, and moves through Draft → Submitted → Under Review → Won / Lost / Cancelled.

Budget independently at any level of the tree. Task, material and labour libraries feed both the estimate and the site requisition, so what was priced and what is bought are the same catalogue.

Group-wise cost variance and category budget consumption show where the job is drifting while there is still time to do something about it. A configurable stage workflow — Draft → Approve → Amend & Draft → Foreclosed — is reused across projects, purchase orders and work orders, and QA procedures and payment-schedule templates attach to it.

Planned and actual start and finish per task, with completion percentage, rendered hierarchically so a director sees the portfolio and a planner sees the task — in the same view.

A requisition raised against a project, sub-project, WBS or task converts into RFQs and purchase orders, with balance quantity tracked so it is always clear what is still open.

Quotations are compared side by side across six vendors with per-vendor tax particulars and approve or cancel per vendor. Material rate masters and price-trend analysis let a buyer challenge an incoming quotation with history rather than instinct.

Vendor advances recover automatically against later bills, debit notes net against payment, and consumption is booked against project and task — issued versus consumed versus balance. Short supply and unbilled GRN are reports, not a spreadsheet someone maintains.

A labour or works requisition is compared across six contractors with full tax detail each, against a historical rate trend by trade. The winning quotation becomes a work order with its own payment schedule and commencement date.

Completion certificates record quantity, percentage, date and site remarks. RA bills carry the basic amount, taxes, the previous certificate carried forward and the balance — retention held and tracked to a formal release document, advance recovered on a schedule, debit and credit notes netted against the bill.

Work ordered but not yet certified is a live view, not a monthly reconciliation.

Core accounting is configured for construction during implementation: the analytic structure follows the project hierarchy, so revenue, cost and margin per project and sub-project fall out of ordinary posting rather than a month-end exercise.

On top of that: assets, budgets, a financial reports suite, lock dates, recurring payments, cash-flow statements, journal restriction by user and controlled document sequences.

Invoices are built, signed and submitted to the Egyptian Tax Authority from inside the system, with the submission status and the authority's response kept against the invoice.

Post-dated cheques are tracked to maturity, cleared or bounced, on both the receivable and payable side — the way Egyptian construction actually settles. Instalment schedules attach to payment terms, and a credit limit per customer warns on the due amount and can block further exposure.

Run Cairo and Alexandria as separate books and still see the group. Transactions are segregated by branch; reporting consolidates.

Employee master, contract types and site assignment are configured during implementation. Payroll runs on localisable salary rules, structures and payslips.

Timesheets capture against project, sub-project and task, and site attendance feeds labour cost back to the job — so the labour line in the cost report is a record, not an estimate.

A snag raised at handover is a ticket with an owner, an age and a resolution — not an item on a punch list nobody owns.

This is the interface, and it is available today. A connector to a specific third-party system is a separate piece of work — see the Integrations page, which states plainly which connectors exist and which are on the roadmap.