Choosing construction software deliberately
Construction software can prepare specifications, organize bids and track cost states. An executing contractor nevertheless needs different workflows from a design office or client. Start with the work that should improve.
Define project roles and scope
State whether you design and manage projects, execute construction work or monitor projects as a client. Issuing a tender differs from calculating your own bid, recording work and billing it. A shared project name does not make those tasks interchangeable.
Describe typical projects, concurrent projects and planned users. Include people who only check, approve or record information on site.
| Use | Important workflow |
|---|---|
| Design and construction management | Tendering, award and cost states |
| Executing contractor | Calculation, work reports and billing |
| Client | Checks, approvals and traceable reports |
Check specifications and exchange
Digital use of NPK specifications requires distinguishing the suitable application from the data-use licence. Required chapters and updates should appear in the quotation. This does not establish a general duty to use that catalogue for every project.
Actual format, version and exchanged content matter. CRBX and its rules differ from a PDF. A SIA 451 label alone does not describe all technical functions. Test receiving, editing and returning a suitable example.
Keep cost states traceable
Estimates, budgets, awarded contracts, variations, checked invoices and payments are different states. Software should distinguish them clearly and report against the agreed cost structure.
Check reasons, approvals and change history. A dashboard does not replace reviewing a contractor invoice or deciding whether additional work is justified.
Connect site work and approvals
Reports, dates, open issues and defects need responsible people and current project versions. Check which tasks work on mobile devices and without a reliable connection. A mobile view does not automatically provide offline editing.
Define who enters, corrects and approves records. Outside participants may need limited access. Test synchronization and corrections as well as initial entry.
Define interfaces and migration
Accounting, documents, time records and design models may come from different sources. For each connection, clarify direction, transferred content and error responsibility. An attached PDF is not a structured accounting entry.
Separate active projects from completed archives when switching. Agree a pilot transfer and preserve the existing records until values, attachments and assignments have been checked.
Compare like-for-like costs
Use the same assumptions for users, modules and project scope. Data licences, mobile access, interfaces and approval functions may cost separately. Prices from a few packages do not constitute a Swiss average.
Separate setup, migration and training from ongoing use and support. Clarify upgrades, extra users and complete export costs.
| Cost component | Include in comparison |
|---|---|
| Software access | Users, modules and mobile use |
| Data and exchange | Catalogue licences, versions and interfaces |
| Implementation | Setup, pilot migration and training |
| Operation | Support, updates, archive access and export |
Prepare the enquiry and implementation
State your role, projects, users, modules, known systems and office or site use. One short brief can explain project scale, languages, exchange partners and transfer needs. Confidential bids, invoices and credentials are unnecessary.
Start with a limited example from project opening to final reporting. Test exchange, variation, approval and invoice review against agreed tasks before extending to more projects and people.
Frequently asked questions
Is construction software the same as CAD?
CAD produces drawings or models. Construction software can manage administration, costs and site information; their connection needs separate checking.
Does every project need NPK?
It depends on the agreed specification and exchange process. Digital use of the relevant catalogue data has its own licence and application requirements.
Is a SIA 451 label enough?
No. Clarify supported formats, versions and content, then test exchange in both directions.
Does a cost report automatically show the final price?
Not necessarily. Estimates, contracts, variations, invoices and payments have different meanings and should be distinguishable.
Does mobile use always work offline?
No. Check specific offline functions, later synchronization and conflicting edits.
What belongs in an initial enquiry?
Role, projects, users, modules and known systems support an initial assessment without confidential construction or financial records.
