Projects and hours without retyping Custom apps for project administration Figures per project in your dashboard

Custom BouwWorks integration development

Appfront builds integrations with BouwWorks, the business software from BouwInfosys for construction firms. BouwWorks has integrations with payroll software among others, and exchanges messages according to the Ketenstandaard. Where that falls short, we build the integration: hours from your own app or time recording into the projects, projects and work orders to the site, data from subcontractors and suppliers, and project figures into your own dashboard.

What is a BouwWorks integration?

BouwWorks is the business software from BouwInfosys for construction firms, covering project administration, costing, purchasing and hours, among other things. BouwWorks has integrations with various other packages and exchanges messages according to the Ketenstandaard, for example with suppliers. Systems and processes outside that scope need a custom integration.

Without an integration, site managers and tradespeople record their hours in a separate app, and someone in the office retypes them into BouwWorks. A project is created in BouwWorks, and again in the planning. Subcontractors send their data by email. And management wants to see per project what has been budgeted and what has already been spent, which someone pulls from an export every month.

We build custom software because the integration has to fit how you work: which apps and planning tools you use, which system is the source for projects and employees, how hours and materials are approved, and which figures you want to see. Which integration options BouwWorks offers for your version, we will examine in the first step, together with you and, where necessary, with BouwInfosys.

Hours from the site

Hours and materials from your own app into the right projects and work orders in BouwWorks, after approval.

Projects outward

Projects, work orders and staff from BouwWorks into your planning and apps, without creating them twice.

Figures per project

Budgeted, spent and remaining per project into your own dashboard.

How we build your BouwWorks integration

We start with your systems: which ones you use alongside BouwWorks, how projects, hours and purchasing flow, and where retyping happens now.

1
Mapping systems and data flows

Your apps, planning, portals and dashboard, and which data should move in which direction.

2
Build integration

BouwWorks connected to your systems, for projects, work orders, hours and materials.

3
Testing and monitoring

Testing with real projects and hours, error monitoring, and a log per message.

4
Go-live and management

Phased go-live, and maintenance when BouwWorks or your systems change.

What a BouwWorks integration does in practice

The components below come up in almost every BouwWorks integration. Which ones you need depends on your systems.

Projects

Projects and work orders kept in line between BouwWorks and your planning.

Hours

Hours from the site transferred to the right projects, once approved.

Materials

Materials used per project fed back into the administration.

Subcontractors

Subcontractor details and hours linked to the project.

Procurement

Purchasing and messages with suppliers aligned with the Ketenstandaard.

Dashboard

Budgeted and spent per project in your own dashboard.

Who we build BouwWorks integrations for

The integration is intended for construction firms that use BouwWorks alongside their own systems.

Contractors

Many projects at once. Hours and figures per project are the core.

Finishing contractors

Short projects with many tradespeople. Site hours matter most.

Installers

Projects and service work mixed together. Work orders sent to the app are what's needed.

Companies with their own app

An app for the site. The integration with projects is the core.

Technology and integrations

This page is about integrations with BouwWorks. For another construction package, see our page on a Bouw7 integration; for budgets, our page on works budgeting software for construction; and for subcontractors, our page on an app for subcontractor contracts. You can read about how we work under getting software built.

For construction firms using Bouwportaal alongside their own app or planning tool, see our page on a Bouwportaal integration.

For companies without DICO in their own system, see our page on a DICO integration.

BouwWorks Projects and work orders Hours Materials Subcontractors Ketenstandaard Planning Custom apps Dashboard Log per message

Why choose Appfront for your BouwWorks integration?

Hours that get retyped arrive late and sometimes wrongly in the final costing. We build around that: hours that flow through automatically, projects created just once, and figures without exporting.

No duplicate entry

Projects and employees are created just once.

Hours on time

Site hours appear in the administration the same week.

Project at a glance

Budgeted and spent per project without exporting.

Security and privacy in a BouwWorks integration

The integration processes data on employees, subcontractors and projects, including hours. Access credentials are stored encrypted and used only by the integration, with only the rights it needs.

The integration runs in a European data centre, with encrypted storage, daily back-ups and a log of every message.

Frequently asked questions about a BouwWorks integration

Questions construction firms ask before starting with this.

BouwWorks is business software from BouwInfosys for construction firms, including project administration, estimating, purchasing and hours. It belongs to BouwInfosys's Works range, with variants for other sectors. Construction companies use it to track projects from estimating through to final costing, with purchasing, hours and materials per project.

Yes, with salary software among others, and messages via the Ketenstandaard with suppliers. Often that's enough. A custom integration is needed for your own apps, your own planning, or a dashboard the standard setup doesn't cover.

Through the integration options of BouwWorks and the interfaces of your other systems. We'll work out which route suits your version in the first step. For each data flow, we define which system is the source and how often data is synchronised.

Yes. Hours and materials from your app go to the right project and work order in BouwWorks once approved. Hours not yet approved stay put until they've been reviewed.

Yes, via a portal or app. Hours and data from subcontractors feed into the project, so they count towards administration and post-calculation. Anything a subcontractor submits is checked before it reaches BouwWorks.

The integration reports the problem and records what went wrong. The message is retried or set aside for review. An overview shows which messages have been processed, which are waiting and which need attention.

For construction companies with their own apps, their own planning, or a dashboard alongside BouwWorks, where data is currently re-keyed by hand. If standard packages are enough, the standard integration is often sufficient. We usually start with the flow that costs the most re-keying, often hours, and expand from there.

BouwWorks and the site, with the same data?

Tell us which systems you use alongside BouwWorks, how hours and projects flow, and where data is currently re-keyed. We'll show you what the integration would look like.

Edit content