Projects & multi-site control on Smart Construction
Most contractors in Pakistan do not lose control of a project on day one. They lose it in month four, when a second and third site start competing for the same store, the same crew, the same cash, and the same three people in head office who know what is really happening. Each site keeps its own file. Each project manager keeps their own progress number. By the time the numbers meet in a monthly meeting, nobody can say which version is true.
Multi-site control is the discipline of making every project report the same way, at the same cadence, into the same system. Smart Construction gives every job a workspace that holds its milestones, budget, bills, purchase orders, labour, site diary, drawings, and documents. Because the workspace is the same shape on every project, a portfolio view stops being a monthly reconstruction exercise and becomes something leadership can open on any weekday morning.
That structure is what makes escalation possible. When a milestone slips, the slip is attached to a project, an owner, and a date, not to a message in a group chat. When cost runs ahead of progress, the variance is visible while there is still time to act on it. The value of a project control system is not the dashboard; it is the number of weeks earlier you find out.
Operational value
Portfolio-level dashboards for schedule, spend, and site status
Standard project governance with role-based accountability
Clear escalation path for at-risk milestones and blockers
One reporting language across every site, client, and package
Core capabilities
Project workspaces with project progress tracking
Milestone planning, status updates, and delivery checks
Client records linked to their projects
Cross-project leadership reports for management reviews
Permissions scoped per company, per project, and per module
Document, drawing, and agreement filing against the right job
How it works
What you get, feature by feature
Every capability below is included on Starter, Growth, and Enterprise. Plans differ only on active project and user limits.
Project workspaces that hold the whole job
Every project gets one workspace: scope, client, contract value, milestones, budget, and the full commercial and site record attached to it. Nothing about a job lives in a personal folder, so handover between project managers costs a conversation instead of a month.
Contract value, start date, and target completion held on the project record
Bills, purchase orders, expenses, and labour all coded to the project
Drawings, agreements, and approval documents filed in the same place
Milestones with owners and escalation
Plan delivery checkpoints, assign an owner, and record progress against them. A milestone that is behind is visible as behind, with the reason recorded, so a review meeting starts from the exception list rather than from a status recital.
Planned against actual completion on every checkpoint
Reason coding so repeat causes of delay become visible over time
Escalation to PMO and leadership without a separate report
Portfolio dashboards for leadership
One screen across every active project: progress, committed cost, billed value, collections, and open risks. Leadership stops asking for a status pack and starts asking about the two projects that need a decision.
Cross-project comparison on schedule and spend
Cash exposure per project and across the portfolio
Drill-down from the portfolio number to the source record
Permissions that match your org chart
Access is scoped by company, project, and module. A site engineer sees their own job. A commercial manager sees every bill. An owner sees everything. Nobody has to be given the whole system to do a narrow task.
Role templates for site, commercial, finance, HR, and leadership
Project-level access so subcontracted teams see only their scope
Audit trail on approvals and sensitive record changes
Client records tied to delivery
Each client record links to their projects, their bills, their payment history, and their variations. When a client calls about a certificate, the answer is one click away rather than an afternoon of searching email.
Client contacts, projects, and outstanding balance in one view
Branded project update PDFs for owner and consultant reporting
Shareable client update links for progress transparency
Standardised governance across sites
The same approval chain, the same coding, and the same document conventions apply on every job. Standardisation is what lets you add a fourth or fifth project without adding a fourth or fifth way of working.
Consistent cost codes and package structure across the portfolio
Approval limits configured once and applied everywhere
New projects opened from a known starting configuration
Before and after
What changes on day one
The same job, run the way most contractors run it today and the way it runs on the platform.
Spreadsheets and WhatsApp threadsOn Smart Construction
Spreadsheets and WhatsApp threads: Each project manager keeps progress in their own spreadsheet format
On Smart Construction: Every project reports the same milestone structure into one portfolio view
Spreadsheets and WhatsApp threads: Portfolio status is rebuilt manually before every management meeting
On Smart Construction: Leadership opens a live dashboard on any day of the month
Spreadsheets and WhatsApp threads: A delay is discovered when the client raises it
On Smart Construction: An at-risk milestone escalates to PMO as soon as the date moves
Spreadsheets and WhatsApp threads: Committed cost is known only after invoices arrive
On Smart Construction: Purchase orders commit cost against the project the moment they are released
Spreadsheets and WhatsApp threads: Access is all or nothing, so junior staff either see everything or nothing
On Smart Construction: Permissions scoped by company, project, and module
Spreadsheets and WhatsApp threads: A departing project manager takes the project history with them
On Smart Construction: The full record stays in the project workspace
Use cases
Situations this is built for
Recognisable scenarios from construction businesses operating in Pakistan.
01
A contractor going from one site to four
The situation
A Lahore contractor wins three new jobs in a single quarter. The systems that worked for one site, a shared drive and a WhatsApp group per project, stop working the moment the same storekeeper is supplying two sites.
How Smart Construction handles it
Each job opens as a project workspace with its own milestones, budget, and store. Purchase orders, labour attendance, and bills are coded to the project at the point of entry, not reconciled afterwards.
What changes
Head office sees committed cost per project the same week it is committed, and the monthly review moves from rebuilding numbers to deciding what to do about them.
02
A developer with phased handover
The situation
A housing developer hands over in blocks. Each block has its own completion date, its own snag list, and its own set of buyers waiting on possession.
How Smart Construction handles it
Blocks are tracked as milestones inside the project, each with an owner and a planned date. Progress photos and site diary entries attach to the milestone they evidence.
What changes
Sales and delivery work from one date per block, and slippage is flagged to leadership weeks before it becomes a customer commitment problem.
03
A group running two companies from one office
The situation
A construction group operates a contracting company and a development company. Staff overlap, stores overlap, and consolidated reporting is a manual quarterly exercise.
How Smart Construction handles it
Each company is a separate entity in the platform with its own projects and ledgers, while leadership permissions span both for consolidated reporting.
What changes
Statutory separation is preserved and group leadership still gets one portfolio view, without maintaining a shadow spreadsheet to join them.
04
A PMO standardising a mixed portfolio
The situation
A contractor runs road work, a commercial fit-out, and two residential jobs. Every project manager reports progress in a different format, so nothing can be compared.
How Smart Construction handles it
One milestone structure, one set of cost codes, and one weekly update cadence applied across all four jobs from the same templates.
What changes
Projects become comparable. The PMO can say which job is genuinely at risk instead of which project manager writes the most alarming update.
Benefits
What improves, and why it matters
Find slippage weeks earlier
Milestone status is updated continuously rather than assembled monthly, so an at-risk date surfaces while there is still float to recover it.
One number per project
Progress, committed cost, billed value, and collections all read from the same records, ending the standing argument about whose figure is correct.
Add sites without adding overhead
Because governance is configured once and inherited, growth costs you a project setup rather than another head-office coordinator.
Handover stops being risky
When a project manager leaves, the project record stays. Institutional knowledge lives in the workspace, not in one person’s laptop.
Client conversations get shorter
Progress, certificates, and payment status are retrievable in seconds, which changes the tone of every client and consultant call.
Leadership time goes to decisions
Review meetings start from the exception list. The reporting effort that used to fill the first hour is already done.
Who uses it
Built around the roles that do the work
Owners and directors
See the whole portfolio without asking anyone to prepare anything, and drill into the two projects that actually need a decision this week.
Portfolio dashboard
Cash exposure
Exception review
PMO and project controls
Enforce one milestone structure and one reporting cadence across every job so projects can be compared rather than described.
Milestone planning
Progress tracking
Risk escalation
Project and site managers
Run a job from one workspace instead of a folder, a chat thread, and three spreadsheets, with everything the office asks for already recorded.
Daily updates
Package status
Document filing
Client-facing and commercial leads
Answer progress and certification questions immediately, with branded updates that go out without a design step.
Client updates
Certification status
Variation history
Implementation
How rollout runs, step by step
A sequenced path with named owners on both sides, not an open-ended project.
01
Map your portfolio and access model
We list your active projects, the companies they sit under, and who needs to see what. Roles are drafted before any data is loaded so access is right from the first login.
02
Open project workspaces
Each live job is created with its client, contract value, dates, and package structure. Opening balances and committed costs are brought in so the workspace reflects reality on day one.
03
Set milestones and owners
Delivery checkpoints are planned per project with named owners and target dates, giving the portfolio view something to measure against immediately.
04
Move the daily cadence into the system
Site diary, progress updates, purchase orders, and bills start flowing through the platform. This is the step that turns the dashboard from a picture into a live position.
05
Run the first portfolio review
Leadership runs a review entirely from system reports. Anything the report cannot answer becomes a configuration change before the next cycle.
06
Scale to new projects from the template
Each new job opens from the configuration you have already proven, so the fifth project takes hours to set up rather than weeks.
Timelines depend on how much historical data you want to carry across. Most contractors run their first full portfolio review within the first month.
Modules
Key modules included
Projects
Portfolio workspaces with live progress and ownership per site.
Milestones
Plan, track, and escalate delivery checkpoints across projects.
Clients
Client records linked to their projects and bills.
Reports
Cross-project leadership reports for schedule, spend, and site risk.
Included
Everything in this solution area
One subscription. Nothing on this list is a paid add-on.
Unlimited project workspaces within your plan limits
Milestone planning with owners, dates, and status
Portfolio dashboards across every active project
Committed, billed, and collected value per project
Client records linked to projects, bills, and variations
Role-based permissions by company, project, and module
Document and drawing management filed per project
Agreements and approval documents with branded output
Progress photo logs tied to packages and milestones
Audit trail on approvals and sensitive changes
Cross-project management report exports
Shareable client project update links
Terminology
The vocabulary on this page, explained
Plain definitions of the terms Pakistani contractors and consultants use day to day.
Project workspace
The single record that holds one job: its client, contract value, milestones, budget, commercial documents, site records, and team. Every other module codes back to it.
Milestone
A dated delivery checkpoint with an owner, such as structure complete, block handover, or utility connection. Milestones are what a portfolio view measures schedule health against.
Committed cost
Money a project is already obligated to spend through released purchase orders and subcontracts, even where no invoice has arrived. Tracking it is the difference between knowing your position and knowing your bank balance.
Portfolio view
A single screen comparing every active project on the same measures, rather than a folder of individually formatted project reports.
Role-based access
Permissions granted by job function and project rather than by seniority, so people see the records their work requires and nothing else.
PMO
The project management office: the function that sets delivery standards, monitors progress across jobs, and escalates risk to leadership.
Questions
Frequently asked questions
Does Smart Construction support multiple construction sites in Pakistan?
Yes. Manage portfolios with milestones, dashboards, and role-based access across every active project from one subscription. Each job gets its own workspace holding its budget, commercial records, site records, and team, and leadership sees all of them in one portfolio view.
Can I keep client records linked to their projects?
Yes. Maintain client records with contact details and see each client’s projects, bills, payment history, and variations in one place, so a query about a certificate is answered in seconds rather than from email.
How does the platform handle a group with more than one company?
Each company is a separate entity with its own projects, ledgers, and document branding, so statutory reporting stays clean. Leadership permissions can span entities for consolidated portfolio reporting without maintaining a joining spreadsheet.
Can site engineers update progress without seeing commercial data?
Yes. Permissions are scoped by company, project, and module. A site engineer can update progress and the daily diary on their own project without any visibility of billing, payroll, or vendor balances.
What happens to a project record when a project manager leaves?
The record stays with the project. Milestones, documents, drawings, site history, and commercial activity all live in the project workspace rather than in an individual’s files, so handover is a conversation instead of an archaeology exercise.
How quickly can we add a new project once we are live?
New projects open from the configuration you have already proven, including cost codes, approval limits, and document branding. Setting up an additional site is typically a matter of hours, not another rollout.
Does it track committed cost or only invoices?
Committed cost is captured when a purchase order is released, not when the invoice arrives. That is what lets you catch over-commitment at approval time, while it is still a decision rather than a fact.
Keep reading
Related pages worth reading
Where this solution area connects to the rest of the platform.