Declaration of Works for concrete suppliers: record the branch without falsifying the subcontractor chain

Belgium's Declaration of Works process recognises a practical problem in ready-mixed concrete deliveries: the exact delivery subcontractor may not be known when the project is declared. The official FAQ allows the declaring contractor to select known, potential or all subcontractors associated with the relevant concrete plant branch when exact data is unavailable. That provisional approach must still lead to a record that reflects who actually attended the site.

Resolve the correct branch

Record the concrete plant, branch postcode, order reference, delivery window and project. Similar company names or a national supplier account are not enough to identify the branch used for the official list. Preserve the supplier confirmation and the version of the list consulted so the declaration decision can be reconstructed.

Use provisional options honestly

When the exact carrier is unknown, select the known or potential subcontractors made available for that branch in accordance with the official workflow. Do not invent a single carrier to make the declaration look precise. Mark the internal status as provisional and assign an owner to compare it with dispatch and site-presence evidence after delivery.

Reconcile with attendance

The social-security FAQ explains that the declared chain can be cross-checked with Checkinatwork to determine the subcontractor and workers who performed the activity. Connect delivery tickets, gate records and presence registrations to the same project and date. A mismatch should create a review task, not silently overwrite the earlier declaration.

Preserve the real chain

Record which company contracted the delivery, which branch dispatched it and which subcontractor or driver attended. These roles are not interchangeable. If another subcontractor is engaged later, add it through the official Declaration of Works process. The project record should show both the provisional basis and the later verified reality.

Test operational exceptions

Use a late carrier change, two branches with the same supplier name, a missing delivery ticket and a person absent from Checkinatwork. The workflow should surface each exception before payment or close-out. For uncertainty about the declaration, contact the NSSO rather than using the software record as legal interpretation.

Finally, make the workflow reviewable in daily operations. Assign an owner, record the official source and product version checked, and define when the decision must be reviewed again. A software flag is not legal advice, and an AI proposal is not approval. The authorised person must be able to see the customer, project, amounts, permissions and exceptions before confirming. Measure not only time saved but also ambiguous cases stopped safely. Update the instruction when regulation, contract terms, channels or product capabilities change. That discipline keeps the record useful to the site team, office, accountant and a later reviewer instead of turning today's configuration into an undocumented permanent rule.

Use the official Declaration of Works FAQ and Checkinatwork guidance. Explore Enfin, pricing, or discuss the workflow.