Construction management software features: the counted list from 60 real products
Most lists of construction management software features lead with a Gantt chart, then list everything a vendor's homepage mentions. They are no help for writing requirements, and no help for telling a real system from a convincing demo.
This one is counted. We went through 60 real construction management products across 120 official source pages, and tallied a capability only when a source directly showed it shipping. The counts show which features are load-bearing and which are choices.
They also show something the feature grids never mention. A construction project is shared by businesses that are also competitors — the main contractor, the client, the architect and a dozen trade subcontractors, each with prices the others must not see. Several of the features below are defined as much by who should not see them as by what they do, and each comes with the real version, the decorative one, and a test you can run in a demo.
The core eight, ranked
| Feature | Products (of 60) | Share |
|---|---|---|
| Reports, exports and stakeholder packs | 55 | 92% |
| Tasks, issues and field coordination | 54 | 90% |
| Drawings, markups and revision control | 46 | 77% |
| Procurement and purchase orders | 45 | 75% |
| Mobile and offline jobsite access | 44 | 73% |
| Document repository and version custody | 43 | 72% |
| Budget, job cost, cost codes and variance | 42 | 70% |
| Photos and progress evidence | 41 | 68% |
Integrations with accounting and finance systems also appear in 46 of 60, but they belong on a different list: construction runs on a finance system the project software does not own, and the boundary between them is something to decide up front, not a feature to tick.
1 · Reports, exports and stakeholder packs — 55 of 60
The most evidenced capability in the category.
Decorative version: an export button that produces everything in the table. Real version: an export built from exactly the same view as the screen, so a person gets the same rows in the file that they are allowed to see on the page, and nothing more.
The test: sign in as a subcontractor, look at a list, then export it. Compare the two. If the file contains rows the screen did not show, the export is a second, unguarded copy of the data.
2 · Tasks, issues and field coordination — 54 of 60
Assignments, punch items, RFIs, coordination between trades.
Decorative version: one shared task list for the whole project. Real version: work assigned to companies, where each subcontractor sees their own assignments rather than everyone's.
The test: sign in as one trade and look at the task list. You should see what is assigned to your firm and the shared items you need, not another trade's internal list.
3 · Drawings, markups and revision control — 46 of 60
Decorative version: a folder of uploaded PDFs. Real version: every sheet has a number and a revision, the current revision is unambiguous, and superseded ones are kept and marked.
The test: issue Revision D of a drawing over Revision C. Check which one a trade sees by default, and whether C is clearly marked superseded. A sheet number without a revision is a liability on site.
4 · Procurement and purchase orders — 45 of 60
Decorative version: a list of purchase orders. Real version: purchase orders that carry a vendor and an amount — which makes this the most confidential register on the job — visible to the parties involved and no one else.
The test: as one subcontractor, look for another subcontractor's purchase order. You should not be able to find it, in the list, in search, or in an export.
5 · Mobile and offline jobsite access — 44 of 60
The work happens on a phone in a field.
Decorative version: the desktop screens, shrunk. Real version: the daily log, photos, snags and drawings usable on a phone with poor signal.
The test: open the app on a phone and write a daily log entry with a photo. If the layout spills off the screen, or nothing works without a connection, it will be written up on Friday from memory instead.
6 · Document repository and version custody — 43 of 60
Decorative version: file storage with folders. Real version: custody — knowing which version of a document was current when a decision was made.
The test: pick a change order approved last month and find the specification as it stood on that date. If the system can only show you today's version, it stores files but cannot support a dispute.
7 · Budget, job cost, cost codes and variance — 42 of 60
Decorative version: a budget column and a spent column. Real version: cost codes that connect an estimate to a commitment to an actual cost, so variance is a number you can defend.
The test: open one cost code. You should see what was budgeted, what has been committed in purchase orders and subcontracts, what has actually been spent, and the difference. Variance without the committed figure only tells you about overruns after they have already happened.
8 · Photos and progress evidence — 41 of 60
Decorative version: a photo gallery. Real version: dated photos attached to a record — a daily log, a defect, a location — because that is what settles a dispute months later.
The test: find every photo taken on a specific date on a specific floor. If you have to scroll a gallery, the photos are stored but not evidence.
The features the market under-describes
Just below the core sit the registers that decide whether a shared project is commercially safe. They are documented less often than they matter:
| Feature | Products (of 60) |
|---|---|
| Commitments, subcontracts and purchase contracts | 37 |
| Users, roles, companies and scoped permissions | 36 |
| Change orders, approvals and impact | 34 |
| Daily logs, diaries and site conditions | 32 |
| Master schedule, Gantt and critical path | 31 |
Companies, not just users — 36 of 60. This is the central under-description in the category. In construction, access belongs to firms as well as people, and every other feature here depends on it. A system that treats its most senior role as simply "can see everything" has already got it wrong, because the client, the contractor and each trade need different views of the same job.
Commitments — 37 of 60. The contract sum per trade. It is the register where a visibility mistake does immediate commercial damage, because a rival's price is a negotiating position.
Change orders — 34 of 60. Where the money actually moves. An approval without a named person and a time is not an approval.
Daily logs — 32 of 60. The contemporaneous record. Its value is that it was written that day and cannot be quietly rewritten later.
The schedule — 31 of 60. The image the category is sold on, and documented by only half the market. When it is real, it is a register with genuine float and critical-path flags, not a picture of bars.
What is deliberately not on the list
These are real, but they belong to particular firms rather than to every job:
- Accounting and ERP integration — 46 of 60. Decide the boundary first, so the project system never invents a ledger of its own.
- Project directory — 35 of 60. It spans companies, so it needs the same care as everything else shared across firms.
- Estimating and cost database — 35 of 60. Your unit rates are your cost build-up. Exposing them to a trade partner hands over your negotiating position.
- Specifications and requirement linking — 34 of 60. A submittal that does not point at the section it satisfies cannot be reviewed against anything.
- Portfolio dashboards — 33 of 60. Only useful if every figure opens the records behind it.
- Commissioning, bid levelling and safety incidents — 2 to 3 of 60 each. Rarely documented publicly, and each needs its own rules — safety records carry personal data and a different retention duty from project records.
The requirements list you can hand someone
- Access is defined per company as well as per person. The client, the contractor and each trade see different views of the same job.
- Exports are built from the same view as the screen. A person never gets rows in a file that they cannot see on the page.
- Purchase orders and subcontracts are visible only to the parties involved.
- Every drawing has a sheet number and a revision. The current revision is unambiguous, and superseded revisions are kept and marked.
- Cost codes connect budget, commitments and actual cost, and variance shows all three.
- Change orders move through pending, approved and rejected, with a named approver and a time, and only approved changes reach the contract value.
- Daily logs are dated, attributable and not editable after the day, with photos attached to the log.
- Documents keep their version history, so you can show what was current on any date.
- The daily log, photos and snags work on a phone, including with poor signal.
- Branches chosen in writing: [schedule / estimating / accounting integration / bid levelling / safety / commissioning].
Why AI-built construction systems miss these
Ask a coding agent for construction management software and it will build the Gantt chart and a project dashboard first, because those are the images it has seen. Then a task list and a document folder. All of it will look right, and none of it will know that the people using it work for different companies.
That is the part that separated the builds when four AI models built the same construction specification: keeping each firm's contracts, prices and purchase orders away from the others was the defining test, and the builds differed most exactly there. All four are live, and you can compare them on the construction management demo page.
If your jobs still run on a spreadsheet, construction management in Excel sets one up with commitments and change orders tracked properly, and free construction management software covers where the free plans stop. If the ledger is the harder problem — retentions, subcontractor deductions, payment applications — see construction accounting software.
If you are pointing a coding agent at this, the Construction Management planner is the specification we hand ours: this inventory, access per company, and the cost chain from estimate to commitment to actual.