Construction Project Management Software

Gantt charts built for construction programmes: trade packages, structural milestones, concrete pour sequences, MEP rough-in, finish trades, and commissioning activities -- each with start date, finish date, float, and predecessor/successor dependency links. Critical path calculation identifies which activities, if delayed, extend the project completion date -- the information that tells the project manager where to focus acceleration effort and which float can be consumed without consequence.

Baseline schedule locked at contract award or project start, with every subsequent update measured against the baseline so variance is always visible. Two-week lookahead views for site supervisors and foremen give a short-horizon planning window with the detail that daily work requires, without the noise of a full programme. Milestone tracking with early warning when milestone dates are at risk based on predecessor activity progress. Programme updates driven by daily field progress logs -- when a supervisor marks an activity at 60% complete in the mobile app, the Gantt reflects that immediately, not at the project manager's next weekly update. BIM model integration via Autodesk Forge (now Autodesk Platform Services) API allows 4D scheduling views where programme activities are linked to BIM model elements, so a schedule delay is visible in the model context rather than only as a bar extension on the Gantt. Reference platforms like Procore and Autodesk Construction Cloud offer scheduling in this way; a custom system allows you to define the workflow rules, notification logic, and reporting format that matches how your projects actually run.

Resource planning across your active project portfolio at the trade and crew level. Labour requirements are derived from the programme: each scheduled activity has a resource requirement (trade type, crew size, days on site) that feeds the resource histogram. The histogram shows total resource demand by trade across all active projects by week, set against your available workforce and subcontractor capacity. Conflicts -- two projects both requiring the same formwork crew at peak demand -- are surfaced three to four weeks ahead of when they will become a site delay, not on the Monday morning the crew is supposed to be in two places at once.

Subcontractor labour and direct labour are tracked separately with company name, trade, contract package, mobilisation date, demobilisation date, and peak crew requirements. Subcontractor bid management tracks invited subcontractors for each package, bid submission status, and bid amount. Comparative bid levelling aligns different subcontractor bids for the same scope onto a common comparison format, adjusting for scope inclusions and exclusions, so the lowest bid is not automatically the cheapest once scope gaps are normalised. Material procurement tracking logs purchase orders raised for each trade package against the programme's material delivery requirements, with early warning when a delivery date is at risk of missing the on-site need date. OSHA incident and near-miss reporting is recorded from the field mobile app with the date, location, trade, description, and corrective action, generating the incident log required for compliance reporting and insurance renewal.

RFI (Request for Information) workflow from initiation to close. Each RFI has a subject, trade category, contract reference, and a required response date. The RFI is assigned to the responsible consultant or design team member, who receives a notification and can respond with a written answer, a marked-up drawing, or a reference to a specification clause -- all attached directly to the RFI record. Automatic reminders on overdue responses keep turnaround times within your contract's response window. When the response is received, the contractor can accept it, request clarification, or escalate. Every action on the RFI is timestamped and attributed, creating the audit trail that is the difference between a successful claim and a losing dispute.

Submittal workflow covers shop drawings, product data submissions, and material samples through the review, approval, approval with comments, and rejection/resubmission cycle. Submittals transmitted to the design team with a transmittal record showing what was sent and when. Review status tracked through the full cycle with resubmission rounds numbered and accessible. The current approved submittal version is always clear; superseded versions remain accessible in the record but are visually marked. Distribution lists per RFI and submittal mean the right people are notified without broadcasting to everyone on the project. Closed RFIs and approved submittals are searchable by keyword, trade, drawing reference, and date range -- the reference library that answers "what was the design intent on that detail" at practical completion without someone hunting through email chains.

Drawing register organised by discipline (architectural, structural, MEP, civil, landscape), contract package, and drawing number. Each drawing has a full revision history: issue A, B, C, 1, 2, 3 with issue date, reason for issue, and the transmittal record showing who received that revision. IFC (Industry Foundation Classes) file format support for BIM model coordination -- IFC files uploaded, versioned, and distributed through the same controlled document workflow as 2D drawings, with model viewer integration via Autodesk Forge Viewer (now Autodesk Platform Services) for browser-based 3D model review without requiring desktop software.

New drawing revisions automatically supersede previous issues the moment the new revision is issued. Field workers accessing the drawing register always see only the current revision. Previous revisions are visually marked as superseded and require deliberate navigation to access, preventing accidental use. Outdated drawings already printed on site are addressed by a controlled distribution model: the system does not allow downloading a drawing without logging the download with timestamp and user, creating a record that is verifiable if the wrong revision is ever used.

Transmittal records show exactly who received each revision, on what date, by which distribution method. Document sets managed by discipline and package so structural subcontractors see only the structural drawings relevant to their scope and cannot access the full project documentation. Access controls configurable by company and by individual user. Change order management: variations to the contract scope go through a formal approval workflow before being added to the contract sum. A change order request records the scope change description, cost impact, and programme impact; the architect or client approves, rejects, or requests revision; approved change orders update the contract sum automatically and feed the cost tracker. This is the equivalent of the AIA G702/G703 pay application and change order process in a custom platform context.

Daily site report forms completed by foremen and supervisors from a mobile app with full offline capability -- reports are completed on site and sync to the server when connectivity is restored, so a basement with no signal or a remote rural site without reliable mobile data does not break the reporting workflow. Reports capture: weather conditions with temperature and precipitation (logged automatically from a weather API where connectivity allows, manually where it does not), crew on site by trade and company with headcount, plant and equipment on site, work completed against specific programme activities, and any site instructions received or issues identified.

Photos taken in the mobile app are attached to specific drawing locations, programme activities, or issue records rather than uploaded as an undifferentiated gallery. This means a photo of a crack in a foundation wall is attached to the relevant structural drawing reference and the relevant RFI or issue record -- not in a folder named "week 14 site photos" that takes half an hour to search at claim time. Field time and attendance using geofenced punch-in/punch-out records which operatives were on which site at what time, integrated with payroll data for direct labour. Weather logging from the daily report feeds the programme delay analysis -- if you are claiming an extension of time for weather events, the daily report log is the evidence base.

Reports compiled automatically into weekly progress summaries formatted for client reporting: activities completed this week, activities planned next week, issues outstanding, instructions received, and photos of key progress milestones. The summary is generated from the daily report data rather than written from scratch each Friday, reducing the time a project manager spends on client reporting from an afternoon to a review.

Budget tracking structured around a schedule of values (SOV) that maps the contract sum across work packages, trade packages, and cost codes. The SOV is the basis for progress billing: each payment application (formatted to match AIA G702/G703 for US projects) reports the percentage complete per SOV line item, calculates the amount due for the current period, and accumulates the total billed to date against contract value. The G702/G703 format means your progress billing is in the format your clients' quantity surveyors and bank inspectors expect, without reformatting data from another system.

Committed costs (purchase orders raised but not yet invoiced), actual costs to date (invoices received and approved), and forecast final cost (actual plus committed plus estimate to complete) are visible in real time as each transaction is recorded. Purchase orders raised in the PM system are coded against the SOV line item and cost code at the time they are raised, so the budget picture updates immediately rather than at month-end when someone uploads the accounts payable file. Variation orders go through an approval workflow before being added to the contract value -- scope change descriptions, cost impacts, and programme impacts recorded and approved by the relevant parties before the numbers change. Early warning on cost code overruns shows when actual plus committed costs exceed the budget line, with a configurable threshold alert before the overrun is confirmed. Cost reports by package, trade, and cost code generated on demand without manual spreadsheet assembly -- the financial picture your commercial manager needs to review project performance, available every day rather than produced in a weekly scramble.