A target operating model for construction
Tie every certificate to installed quantity and an accountable decision.
Bring contract baseline, BOQ, change, site request, procurement, installed quantity, client and subcontractor certification, and cash impact into one project story.
This is a design map, not a claim of a ready construction product. BOQ, site, subcontractor, and progress functions require an accepted blueprint and tests.
Project cycle
From contract commitment to close
- 1Contract & baseline
- 2Supply & site
- 3Quantity & approval
- 4Certificate & cost
Illustrative target model; not a public release or customer-project view.
Project gaps
Cost moves every day while its management picture arrives late.
What was contracted separates from what was requested, supplied, installed, approved, and billed—so risk appears after it becomes commitment.
- 01
Baseline changes without a trace
BOQ versions, variations, and budgets do not always show what is current and what changed.
- 02
Site and procurement run on different clocks
Need precedes request, or supply arrives without a precise link to item, quantity, and purpose.
- 03
Technical progress is detached from commercial progress
Installed, measured, approved, and certified quantities use different definitions.
- 04
Cash commitment lacks context
Buying, subcontract, retention, and collection are not read beside expected cost to complete.
Target workflow
From contract baseline to cost and collection close.
We test the project using one real item because measurement, approval, and responsibility differ by company and contract.
- 01
Contract and baseline
Scope, items, quantities, rates, budget, and approval responsibilities.
Handoff owner
Contracts & project management
- 02
Delivery plan
Work packages, timing, resource need, and each package’s BOQ relationship.
Handoff owner
Planning & project
- 03
Site request and supply
Need with reason, item, quantity, approval, purchase, and expected date.
Handoff owner
Site & procurement
- 04
Receipt and issue
What arrived, where it was used, and what differed from request or specification.
Handoff owner
Stores & site
- 05
Measurement and progress
Installed quantity, review, supporting evidence, and approval or rejection.
Handoff owner
Site & technical office
- 06
Party certification
Client or subcontractor statement under agreed deduction and retention rules.
Handoff owner
Commercial & finance
- 07
Cost and close
Commitment, actual, estimate to complete, collection, and settlement through closure.
Handoff owner
Cost control & finance
The integrated story
The BOQ item is the thread between contract, site, and money.
When request, receipt, measurement, certificate, and cost share an agreed reference, management can explain variance before it disappears into the project total.
- Contract & BOQ
- Plan & budget
- Supply & site
- Measure & certify
- Cost & cash
Approved baseline
Every change has a version, reason, authority, and time and cost effect.
Item and package reference
Request, issue, and execution retain the purpose that created them.
Installed is not approved
Technical progress does not become a financial right without review.
Requirements grouped by outcome
What construction scope must resolve before delivery.
These requirements are assessed in the blueprint. They are not presented as a ready module or field-app promise before design and acceptance are proven.
Evaluated and established in blueprint
Protect the baseline
Make contract, change, and budget traceable.
- Project structure, BOQ, and units
- Budget and responsibility allocation
- Variation impact and approval
- Commitment tied to item and package
Evaluated and established in blueprint
Control site and supply
Connect need through receipt and use.
- Site request and approval
- Purchase, timing, and delivery
- Receipt and issue tied to purpose
- Quantity or specification exception ownership
Evaluated and established in blueprint
Progress, commercial, and cost
Explain installed, approved, and billed differences.
- Progress measurement and evidence
- Client and subcontractor certification requirements
- Contract-defined retention and deduction
- Commitment, actual, and estimate to complete
Value by role
Every role reads the project from the same baseline.
Visibility and approval boundaries follow company and contract structure.
Project manager
Where is execution departing from baseline, and why?
Progress, need, and change tied to item and package.
Site engineer and technical office
What was installed, and which evidence supports it?
Measurement, review, and approval separated with a clear effect.
Procurement and stores
Which item created this material need, and where was it used?
A thread from site request through receipt and issue.
Commercial and finance
What is committed, due, and expected to complete?
Commercial and cash context beside cost.
The measurement story
Measures that explain variance instead of decorating it.
Definitions begin with contract, unit, and approval point. No number is shown before a real project baseline exists.
Conceptual measurement model—no values or outcome guarantees.
- 1
Operating definition
Committed versus approved cost
Open purchase and subcontract commitment against the current item budget.
Decision supported
Stop commitment, approve change, or reallocate.
- 2
Operating definition
Site-request fulfilment time
Valid request to accepted receipt, with waiting reasons separated.
Decision supported
Address approval, supplier, or needs planning.
- 3
Operating definition
Measurement-to-certificate lag
Time between installed quantity and approved billable quantity.
Decision supported
Remove missing evidence, review, or contract dispute.
- 4
Operating definition
Variation exposure
Defined time, cost, and revenue effect of unresolved changes.
Decision supported
Prioritise negotiation or stop unprotected work.
Discovery scenarios
Test the model on an item with real movement.
Choose a scenario spanning site, supply, and commercial control—not a feature list.
- 01
Quantity-changing item
Trace who requested the change and how it affected budget, supply, and certification.
- 02
Critical-path material
Connect site request, approval, buying, and receipt to delay impact.
- 03
Disputed certificate
Separate installed, measured, approved, and rejected quantity with reasons.
Egypt project context
The local contract is the rule source—not a generic template.
Contract types, measurement units, retention, tax treatment, and evidence vary by project and must be reviewed with accountable specialists.
- Certification, retention, and deduction rules derive from the approved contract.
- Tax or regulatory treatment needs entity- and project-specific review and an accountable source.
- Project-specific Arabic outputs can be delivered within scope.
- A mobile or offline site need does not imply a public app; it is tested as a separate requirement.
Why GizaLink
Because a project needs a shared decision model before more reports.
We connect contract, site, procurement, stock, and finance in one blueprint while clearly separating proposed design from evidenced capabilities.
Discovery around one real item
Definition, document, and owner differences surface early.
Core connection where scope proves it
Purchase, stock, sales, and invoicing can connect; construction functions need their own acceptance.
Governed change and acceptance
Each stage has an owner, test scenario, and transition evidence.
Complete the decision picture
Construction operating-system questions
Clear boundaries before the project map becomes a commitment.
Does GizaLink offer a ready construction product?
This page makes no such claim. It presents an operating blueprint whose BOQ, site, subcontractor, and progress functions require defined scope and acceptance tests.
Can BOQ connect to procurement and cost?
That relationship is assessed through item, unit, revision, and the reference carried by requests, commitments, and movements.
How are variations handled?
We establish request source, approval authority, current version, time and financial effect, then define where commitment is prevented or allowed.
Does scope automatically include a site app?
No. Site experience, connectivity, device, privacy, and offline operation are separate requirements with their own design and acceptance.
Where should discovery begin?
Choose one item that passed through site request, purchase, execution, measurement, and certification. It exposes the complete thread.
Begin with one item
Turn a real project—from contract to certificate—into an acceptable blueprint.
Bring a contract, BOQ, and one item that moved on site. We map accountability, evidence, and cost and identify what must be proven.