Construction software
What types of construction software are available for construction companies?
The estimator works with quantities and prices. The planner considers teams and dependencies. On site, the site manager wants to know which agreement applies. They work on the same project but do not use the same information. That is why construction software comprises different types of applications that can complement each other.
By: Floris Meulensteen
Direct answer
Eight useful construction software categories are estimating, planning, ERP, job sheets and service, quality records, BIM, residential property files and document management. This is a practical classification by work process, rather than a formal standard. One package can support several categories. Project communication runs through all these processes: Woub can complement them by keeping conversations, agreements and follow-up actions within the project. The right combination depends on your work, existing setup and collaboration with other parties. Enquiry platforms, formal process communication, site records and HR may also need their own place.
What are the eight core categories of construction software?
The eight categories mainly differ in what they record or process. A budget item is different from an approved drawing, a recorded working hour or an agreement discussed. Decide which system is the primary reference for each information item.
Category | What does it focus on? | Specific question from the work |
|---|---|---|
Estimating | Quantities, unit costs and cost estimates | Which labour and materials are budgeted for this change? |
Planning | Sequence, capacity and dependencies | Which crew can start, and which work needs finishing first? |
ERP | Business administration and project costs | Has the order been processed, and what does it mean for project costs? |
Job sheets and service | Completed work, hours and materials | What has the installer carried out on this job? |
Quality records | Checkpoints, deviations and records | Which inspection has been carried out, and which point remains open? |
BIM | Construction models and linked information | How does this element connect to the work of other disciplines? |
Property handover files | Property-specific choices, documents and processes | Which option is confirmed for this plot number? |
Document management, DMS/CDE | Documents and controlled information exchange | Which revision is approved, and to whom has it been issued? |
To DMS means document management system. A CDE, or Common Data Environment, is a shared environment where project information is managed and shared under agreed processes. Those functions may come together on a construction project. That does not automatically give every shared folder the same management and approval process.
Two overviews with different purposes
Alongside the landscape, use the Bouwend Nederland construction software overview. It helps you find suppliers and applications. Bouwend Nederland expressly gives no judgment on quality or suitability through it. This Woub explanation then helps distinguish which work process you want to support and which information remains the primary reference.
The eight categories are a starting point. They do not cover every digital need of a construction company. A cloud workspace, payroll administration or formal message flow is different from an extra construction project app, for example. See the relevant additions below and check current product information with the supplier.
How was this overview researched?
Product information checked on 22 October 2026. For this article, the supplied Woub software landscape and the Bouwend Nederland overview were compared. The corresponding official product pages or guides were consulted for the substantive tool examples. Links appear with the relevant tools. For Bouwportaal, the product description in the Exact App Store was used.
The comparison follows five questions: which tool is meant, which work process does it support, which information remains the primary reference there, which coordination can Woub complement, and when is that addition unnecessary? Product functions come from the sources cited. The work situations and selection questions are editorial examples, rather than results of a comparative practical test. Nor has every product in both overviews been tested individually or verified for current accuracy. The selection is not a ranking, quality mark or complete market list.
Not every name in the industry guide could be sufficiently confirmed as current. BouwVision, Infrabox, DigitaalBouwdossier and Wecap XE have therefore not been developed into current product recommendations. That is not a judgment that these products no longer exist.
Read the software landscape across project stages
Caption: Supplied Woub software landscape for main contractors in new-build construction, civil engineering and infrastructure works, and non-residential construction. The text version below describes the original image; the subsequent tool comparison uses checked product information.
The supplied Woub software landscape shows the connections: enquiries and tenders, estimating and design, project preparation, site work, handover and aftercare. A market or tender platform helps with enquiries, for example; that is a different step from calculating a cost estimate. ERP, documents and model information may support several stages. Conversations and tasks between those involved run across them.
The image is a discussion aid for main contractors in new-build construction, civil engineering and infrastructure works, and non-residential construction. It is not a complete, current product comparison or compulsory software package for every business. Names and functions may change. Some products shown support several processes; a logo's position does not prove a specific function or integration with Woub.
Text version of the supplied software landscape
The project stages along the bottom of the image are enquiries and tenders, estimating and design, project preparation, site work, handover, evaluation and aftercare. The top rows show tasks and project communication spanning those stages: from preparation checklists and meeting actions to aftercare and evaluation. The names below reproduce the image, rather than an updated feature list.
Row in the image | Names and resources shown |
|---|---|
Task management | Woub, Microsoft To Do, Excel, Outlook, notes and OneNote |
Project communication | Woub, Microsoft Teams, email, WhatsApp, calling and Slack |
Marketplace | 12Build |
Estimating | IBIS, Relatics, wpCalc and 2Jours |
Planning | KYP Project, MS Project, Exact Online Bouw, Powerproject and Robaws |
Quality control / Wkb | ED Controls, Dalux, Snagstream, STA Software, Fieldwire, KIK, GO2sure, ECI HomeDNA, WTT and MoreApp |
ERP | Exact Online Bouw, AFAS, Robaws, Bouwinfosys, Bouwmakers, 4PS, Bouwsoft, ECI Admincom, Microsoft Dynamics 365 and Centric |
DMS | Dalux, Autodesk BIM 360, Procore, Trimble Connect, Prostream, Bricsys, SharePoint, Autodesk Build, Aconex and DigiOffice |
Property handover file | Volgjewoning, Ziggu, HOOMCTRL, Pylon, ECI HomeDNA, LUXS and Bryder |
BIM | Dalux, Autodesk BIM 360, Relatics, Construsoft, BIMlink, Bricsys, Solibri, ECI, Autodesk Navisworks and Revit |
Some names appear in several rows. Do not treat the placement as product advice: listing Relatics under ‘Estimating’, for example, does not prove a budgeting function. Older product names and supplier logos also make the image less precise than a current product description. Use the text version to understand the image and the source links below to assess a specific application.
Which tools specialise in estimating, scheduling and ERP?
Estimating substantiates costs before and during a job. Scheduling organises when work can happen and with which capacity. ERP processes administrative and financial business operations. These three processes connect, but answer different questions.
Estimating: calculate the effect of a change
Ibis Calculeren voor Bouw describes entering quantities and assigning prices to materials, labour and other cost items. For extra wall finishing, the construction estimator might investigate how much surface area is added and which resources it needs.
The calculated amount is not yet proof that the client has approved the change. Supporting information, the decision and processing need to align in your approach. Woub can help keep conversations and follow-up actions around that decision within the project; it does not calculate the budget in place of estimating software.
Scheduling: assess the implications for other work
A diary date tells you when someone is expected. Specialist scheduling can also calculate dependencies and implications. The official Powerproject help on rescheduling describes critical path calculations, float, and start and finish dates, for example.
Whether your existing scheduling supports this depends on the package and setup. Discuss a delay with the parties involved first, confirm assumptions, and have the planner process the implications in the primary programme. A task in Woub does not automatically move an activity in Powerproject.
Estimating and scheduling tools through the same five questions
The examples below describe possible handovers. They assume neither a missing supplier function nor an existing Woub integration.
Tool and official source | Work process | What remains the primary reference there? | When can Woub complement it? | When is extra communication through Woub unnecessary? |
|---|---|---|---|---|
Construction estimating | Quantities, prices and cost estimate | A client requests extra wall finishing; the conversation and action to have it costed remain within the project | If the request, clarification and follow-up already fit well within the existing approach | |
Project scheduling and rescheduling | Activities, dependencies and calculated dates | The site manager and subcontractor discuss a delay before the planner processes the implications | For calculating or changing the programme itself; Powerproject remains necessary for that | |
Cost estimates and forecasts | The calculated cost breakdown | A project manager has missing assumptions investigated and keeps that follow-up agreement within the project | If it is purely a calculation and all required input is available | |
RAW specifications, estimating and administration | The specification and configured calculation or administration | Those involved coordinate which deviation needs investigating; the authorised employee processes the outcome | For formal or administrative processing already following the prescribed route | |
Assessing lifecycle costs | Assumptions and results of the options calculation | A choice needs explanation from design, site teams and management; follow-up actions are recorded | For the lifecycle cost comparison itself, or if coordination is already well organised |
ERP: align administration
An ERP system can combine project administration, purchasing, invoicing and other processes. Exact voor Bouw shows that scheduling and mobile functions may also sit within a broad construction package. The boundaries between categories therefore differ from those between suppliers.
For changed work, the project manager may organise the agreement while the authorised employee handles the order or financial processing in ERP. For an integration, look precisely at which data is transferred. Creating a project from ERP does not prove automatic processing of every subsequent site agreement.
Which additional estimating and ERP solutions are relevant?
Alongside the examples above, solutions exist for other business types and estimating questions. Look beyond whether a product is listed as a ‘complete package’ to which processes the supplier actually supports.
Tool and official source | Work process | What remains the primary reference there? | When can Woub complement it? | When is extra communication through Woub unnecessary? |
|---|---|---|---|---|
Construction ERP, including administration and scheduling | The configured project administration, orders and financial processing | A change is agreed by phone; the person responsible gets the action to process the confirmed implications in Exact | If that coordination and follow-up already work well with the parties involved in your Exact approach | |
Integrated construction processes and portals | The configured processes for new-build construction, refurbishment or job sheet work, for example | A project conversation involves several roles that first need to agree one site arrangement | If the modules and portals used already organise those conversations and follow-up actions sufficiently | |
Construction ERP, estimating, project monitoring and service | The cost estimate and configured project and service administration | Project management and site teams clarify an agreement before administrative processing | If the necessary communication and actions already reach the right people in your Kraan setup | |
Construction and infrastructure processes, including scheduling and records | The configured business processes and site records | A deviation requires discussion of site work and follow-up before the person responsible processes it | If the existing Metacom approach already fully supports that coordination and is used | |
Modular ERP for construction and development | The configured project and financial administration | A verbal decision needs coordination with site teams and project management | If the agreement and follow-up are already recorded in your existing setup without information loss | |
Projects and assets, possibly combined with production | The configured project, production and management processes | A non-standard site question needs a short discussion between the disciplines involved | If existing processes already connect participants, information and actions well | |
ERP for building services contractors | The configured business and service processes | An unusual situation on site needs coordination before processing in the business process | If the existing Acto approach already covers the relevant coordination and follow-up |
These are functional examples, rather than a ranking or proven recommendations for your business. Acto targets its ERP at building services contractors with 50 or more employees. That supplier-specific target threshold is not a general threshold for ERP. A small contractor with complicated projects may have different needs from a large service company handling many short jobs.
Which software supports site work, Wkb, BIM and files?
During site work, the status and meaning of information are particularly important. Has something merely been discussed, carried out, checked or formally approved? That distinction determines which application and responsible person you need.
Job sheets record completed work
A job sheet can record hours, materials and work carried out. The official Robaws explanation of Wappy describes how employees record hours and materials and how these go into a job sheet in Robaws. Available capabilities depend on the licence and setup. The app also supports tasks and chat on a job sheet; communication is therefore not exclusively a function of separate chat software.
Investigate what is still missing alongside this. A conversation between project manager, supplier and subcontractor before work serves a different purpose from recording completed work. If that coordination already fits well in the job sheet approach, you do not need to organise it again elsewhere.
Quality records organise inspections and deviations
Quality software supports the agreed records. The Dalux documentation describes inspection and test plans by discipline, with records before, during and after the work. This helps distinguish which element has been checked and which information is still needed.
Using software is different from meeting every requirement of the Wet kwaliteitsborging voor het bouwen. Where the quality assurance system applies, risk assessment, the assurance plan and the Dutch building quality assurer have their own roles. The Informatiepunt Leefomgeving describes that role. Align the required records with the project and responsible specialist; ticking off a general task does not replace that assessment.
BIM concerns construction information, rather than just a 3D image
With BIM, parties work with digital models and their associated information. Using that data requires agreements on what is supplied and how. The BIM basis ILS from digiGO provides an application guideline for structured, unambiguous exchange.
A question about a clash or missing specification may need discussion, but the model and current information agreements remain the primary reference for model coordination. A separate chat description is not a changed model version.
A property handover file organises information by property
Property handover file software can organise buyers' choices, documents and communication around a plot number. HomeDNA Kopersbegeleiding describes how buyers submit choices and documents remain available by property, for example. Such an application may itself offer communication and action follow-up.
Assess which additional site conversations fall outside that process. Do not create a second list with different buyers' choices in another system. Nor does the commercial label ‘property handover file’ automatically mean every required handover or statutory file is fully configured.
Document management controls the agreed document flow
Drawings and documents may need more than file sharing. Examples include approval, version management, access permissions and records of what was issued to whom. Autodesk describes such functions in the current Forma Data Management documentation, including document control, reviews and transmittals with an audit trail.
In daily coordination, refer to the current source rather than circulating a different copy each time. Woub can then support the conversation about a drawing while the DMS or CDE continues managing the agreed document status.
Which tools broaden site work and collaboration?
Site work involves more working methods than one general project file. The examples below clarify needs that might otherwise be too easily grouped under the same ‘project software’ label.
Tool and official source | Work process | What remains the primary reference there? | When can Woub complement it? | When is extra communication through Woub unnecessary? |
|---|---|---|---|---|
Job sheets, hours and materials | The job sheet and associated records | A conversation about work still to be carried out falls outside the job sheet approach used | If Wappy's own chat and tasks already reach the people involved and support follow-up well | |
Inspection and test plans | The checkpoints, records and deviations | Those involved discuss cause, access or the sequence of remedial work around an item | For an extra copy of the same inspection or action already managed well in Dalux | |
Buyers' choices and property-specific information | The confirmed choice and documents for the plot number | A confirmed choice needs additional coordination with the parties carrying out the work | If the relevant communication and actions already work well within the buyer support process used | |
Management and exchange of project documents | The approved revision and review and issue trail | The site team discusses a question about a drawing and refers to the current source | For parallel version control or a second approval route alongside the existing document process | |
Field service scheduling and work records | The scheduled job and recorded work | Planner, client and site manager need to discuss an unexpected situation | If the existing job process already organises that coordination and follow-up well | |
Scheduling and job sheet process | The job sheet and configured processing | A site manager needs an explanation before work can continue | If that question and action are already handled well within the job sheet approach used | |
Refurbishment by property | The configured survey, site work and settlement | A deviation affects several parties and needs discussion outside the process used | If its own communication capabilities already cover the parties involved and actions | |
Inspection and handover | Items on drawings, images, assignments and reporting | The team discusses cause, access or the sequence of remedial work around an inspection item | If it concerns the same item and action already followed up well in DiviD | |
Safety and quality processes | The configured records and follow-up workflow | A missing inspection needs an explanation or agreement between those involved | If the existing workflow already organises the information question and person responsible well | |
Task-led project work | Planning board, project templates and forms | Relevant project conversations remain outside the approach actually used | If the planning board and its own collaboration already organise the necessary coordination and actions | |
Collaboration around maintenance | Information and results between housing association and maintenance parties | Daily coordination is missing outside the configured collaboration | If that collaboration already covers the relevant conversations and actions well | |
GIS and project processes | The map and configured processes for issues and stakeholders, for example | An issue needs a short discussion; outcomes are processed through the agreed route | For a second issue register or an extra conversation already covered by the approach used | |
Document and information management | The agreed project information and collaboration within the platform | Site teams need brief coordination around that information | If the platform and working agreements used already organise that discussion and follow-up actions | |
Client portal, surveys and handovers | The configured client information, options and surveys | Internal or external coordination is missing alongside the portal processes used | If the existing functions already cover the relevant information exchange and follow-up |
The last two columns describe editorial assessments, rather than demonstrated product shortcomings or existing Woub integrations. Many of these applications support tasks, communication or collaboration themselves. Adding Woub only has value if it organises the relevant conversations and follow-up better. Sharing the same message in two places is not an improvement.
Why are formal communication and site images separate needs?
Formal process communication: VISI from Bakker&Spees uses process frameworks, for example for issuing instructions and project processing. If a project prescribes such a route, it remains necessary. A phone conversation or Woub task does not replace required formal processing. Woub can support preparatory coordination: which explanation is missing, who investigates something, and when can the person responsible take the formal step?
Site capture: OpenSpace describes 360° images linked to a floor plan. This helps review conditions on site. A recorded condition is not yet an agreement on the solution. Discuss a deviation with the right party and record who picks up follow-up. Use the original images in the application configured for that purpose.
Which supporting systems fall outside the eight categories?
A construction company also needs systems to run the organisation itself. SD Worx focuses on HR and payroll for construction, for example. That differs from recording hours on a job sheet: payroll and personnel matters have their own process and data requirements.
To LOSNING graphical cloud workspace is different again. It enables work with graphics or 3D applications, for example, from a managed workspace environment. The workspace is not the same as the modelling program running on it. Assess such facilities with the person responsible for IT.
Additional systems through the same five questions
Tool and official source | Work process | What remains the primary reference there? | When can Woub complement it? | When is extra communication through Woub unnecessary? |
|---|---|---|---|---|
Formal process communication | The prescribed message flow and formal processing | The team first investigates missing information before an authorised employee takes the formal step | If that preparatory coordination already works well; the formal step always follows the required route | |
Site capture with 360° images | The images and their relationship to the floor plan | A visible deviation needs an agreement on investigation or follow-up | If it only concerns looking back, or the follow-up agreement is already well organised | |
HR and payroll for construction | The personnel and payroll process | A separate project agreement remains open; HR and payroll data do not belong in a project chat by default | For payroll processing or personnel administration itself | |
Graphical cloud workspace | The managed working environment; the construction application used retains its own function | Colleagues coordinate on the project while working with their specialist applications | For providing or managing the graphical workspace itself |
Quotation requests and tenders also belong to their own step before site work. The landscape shows a market/quotation platform for this. Do not confuse finding and inviting quotations from a construction partner with estimating, confirming an instruction or holding the later conversation about site work.
When is Woub complementary rather than a replacement?
Woub is complementary when the right software already exists, but relevant conversations and follow-up actions do not sufficiently reach the project and people involved. It does not replace ERP, BIM, estimating, DMS or specialist scheduling. The addition needs to be justified by work currently coordinated through separate phone calls, WhatsApp and email.
For supported conversations through Woub, Wouby AI can provide the transcript and summary and automatically record recognised commitments as tasks. For a recorded site meeting, the output supports reviewing decisions and actions. A person responsible continues to assess what was actually agreed and what needs processing in the other system.
How does the combination change with business size?
Headcount is practical context, rather than a fixed product threshold. Project complexity, type of work and client requirements also determine what is needed. The situations below are examples for organising a trial.
With 1–10 employees: can someone take over from the owner? Suppose the owner discusses a changed delivery while a colleague carries out the work. The agreement and follow-up action need to be retrievable; the order stays in the system used for that purpose. Test whether the colleague can find and follow up the confirmed delivery arrangement without calling the owner again. If an existing module already handles that well, a second communication channel adds little. Eight categories do not mean eight subscriptions. Even a small business may need specialist scheduling or BIM.
With 10–100 employees: does one change reach everyone responsible? A project manager agrees a different sequence of work with a subcontractor. The site manager needs to know the agreement, the construction project coordinator assesses materials, and the planner processes the implications in the primary programme. Test with someone covering for a colleague whether everyone involved finds the same confirmed agreement and knows who handles each next step. Also look at which information subcontractors need. Access to a project conversation is a different need from access to the whole business administration. If this handover already works well, avoid a parallel action list.
With 100+ employees: does the handover remain manageable between teams? Take a project handed over to another team and a subcontractor who is leaving. Have process owners and IT test whether the successor finds current agreements, who is responsible for further processing and how access for departing participants is ended. Check the actual permissions, export and integration capabilities with the relevant suppliers. These are selection questions, rather than a promise that Woub or an Enterprise licence automatically covers them. An extra application only helps if it solves a demonstrable communication problem and fits within management arrangements.
One agreement can produce different types of information
Take an illustrative change of door type in a residential development. The buyer's choice or design requirement is confirmed in the agreed place. The construction estimator calculates the difference, the project manager organises the decision on site work, the planner assesses the sequence, and administration processes the confirmed implications. The site manager receives the current work instruction. Model or document changes follow the agreed route; a required inspection is recorded in the quality process.
Woub can connect conversations and actions between these steps. Agree which WhatsApp project group or separate task list stops for that purpose so that you do not open an extra parallel channel. If you wish, start without an integration. Only investigate automation once the data flow and person responsible are clear.
Want to decide which category fits your bottleneck? Use the construction software selection guide. Is the problem specifically daily conversations and follow-up? Try free for 14 days and test the approach with one project. View the pricing and conditions beforehand. Start small. Experience the calm. Only then expand.
Frequently asked questions
Do I need a separate software package for all eight categories?
No. One package can support several processes. First identify which features you actually use and which problem remains unsolved. The eight categories help distinguish activities; they are not a compulsory list of subscriptions.
Are BIM and document management the same?
No. BIM focuses on building models and their associated information and agreements. Document management focuses on documents and their management and issue process. One platform can support both. Agree which information source and status take priority for each activity.
Can quality software replace the Dutch building quality assurer?
No. A record-keeping application can support inspections and compiling project records. Where quality assurance applies, the assessment, assurance plan and quality assurer's role remain separate elements. Align the setup with the project concerned.
Does a small construction company need fewer types of software?
Not automatically. Simple administration matters greatly in a small company, but project complexity and client requirements can make specialist features necessary. Look at the work and handovers; staff numbers are not a fixed product threshold.
What is the difference between a comprehensive package and specialist construction software?
A comprehensive package combines several business processes, such as administration, project monitoring and planning. Specialist software goes deeper into a particular type of work, such as RAW estimating, model coordination or inspections. Both can work together. Assess the actual setup and handover; a broad feature list does not prove that every process is properly organised.
Is Bouwend Nederland's overview a ranking of the best software?
No. Bouwend Nederland says its overview helps with searching and does not judge quality or suitability for your business. Use it for initial research, then check the current features and fit with your own work process.
Does Woub replace formal project communication through VISI?
No. If the project prescribes a formal route, it remains in force. Woub can additionally support daily conversations and follow-up actions. Agree who formally processes a discussed outcome through the required route.
This site is protected by reCAPTCHA. Google’s Privacy Policy and Terms of Service apply.
