Several horizontal contractors on a Belgian site: identify who coordinates safety execution

A client can appoint several contractors directly for the same site. Those businesses may work beside each other without one being the other's subcontractor. If the planning tool invents a vertical chain, instructions, incidents and safety actions can be escalated to the wrong party. The coordination model must reflect the contracts.

Start with the current source and the right identity

The Federal Public Service Employment's temporary or mobile construction-site guidance distinguishes the usual vertical cascade from a horizontal situation where the client chooses several contractors without a project supervisor for execution. In that case, the guidance says the client takes that execution-supervisor role.

Turn the source into one bounded decision

List every contract, the client, designers, execution supervisor, safety coordinator and contractor. Mark whether each relationship is direct, vertical or horizontal. Confirm who organises coordination for simultaneous and successive work before assigning shared-site actions or approval responsibilities.

Keep evidence without hiding the next step

Connect meeting decisions, hazards, phases and owners to the relationship map. A schedule dependency does not create legal authority. Revisit the map when a new contractor joins or the client delegates a role, and have the competent safety professional validate uncertainty.

Test exceptions before making the workflow routine

Test at least a missing company number, an ambiguous party, a duplicate and a temporarily unavailable source. The workflow should stop with a focused question and name an owner. Keep the source, review date, input, outcome and confirmation without copying more personal data than needed. Escalate tax, legal, labour or safety uncertainty to the competent person.

Repeat the check when the amount, party, invoice action, site, schedule or official instruction changes. An earlier result is useful context, not automatic permission. Define who corrects an error, who informs affected people and when the exception is genuinely closed.

Make the status readable to a colleague who did not prepare the file. They should see what was checked, what remains uncertain and which next action is allowed or blocked. Use stable fields for identity, date, source and decision; a free-text note can explain the evidence but should not be the only evidence.

Connect the record to controlled execution

Enfin can connect the customer, supplier, quote, project, task, document and invoice in one record. Alfie can prepare information and propose an action within available permissions; an authorised user confirms consequential actions. Explore Enfin, compare pricing or discuss your workflow.