HR can place the right construction experience where the next project needs it

The person who solved the last construction problem should not be the only place the company stores the answer.

When a new bridge, housing or public works project starts, HR and delivery leaders need to know who has relevant experience. They may need someone who worked on a similar municipality, contract, compliance question or work package. If that knowledge lives only in a person's memory or private contact list, the company cannot transfer it reliably.

We connected people, roles, projects, work packages, decisions and source documents in one company structure. HR and delivery teams can find relevant experience and move it to the next project. The result is structure-led governance: people remain responsible for judgement, but the organisation no longer depends on personal memory to know where its experience is.

Client background

Our client is a large construction company delivering public bridge contracts, housing developments and other multi-site projects. Different jobs need different combinations of local knowledge, technical experience, compliance understanding and commercial awareness.

The company had capable people across the operation. Its challenge was making experience visible and transferable without exposing sensitive personnel information or turning every project into a loose company-wide folder.

Business challenge

Resource planning is often treated as a list of names and job titles. That is not enough when the relevant experience is specific to a project context.

The useful questions are more precise:

• Who has worked on a similar bridge or housing development?
• Who understands the requirements of this municipality?
• Who handled the relevant work package last time?
• Which compliance officer made the earlier decision?
• What evidence and project outcome should the next person review?

Without a shared structure, the answer depends on who is asked. A manager may know the person, but HR may not. A project lead may remember the work package, but the decision history remains in an old folder. The company then loses time finding the right experience or assigns a new team without the knowledge that would make its start safer.

Implementation

We modelled people and experience in relation to the work that created it. A person can be connected to a project, site, municipality, contract, work package, role, date, decision and source document. That gives HR and delivery teams a way to search for relevant experience using the context of the new project.

The knowledge system uses retrieval-augmented generation, or RAG, to retrieve relevant documents before answering questions. A project lead can find the evidence from a prior job and the people connected to it. The answer is not based on a person's title alone. It is grounded in the project work and source material associated with that experience.

This is how City A, Project X can help City A, Project Y. The new team can retrieve the earlier requirements and decisions, identify the people who worked on them and ask those people for context. The organisation transfers knowledge while keeping the current project responsible for verifying what still applies.

Permissions remain part of the design. HR and project information must be findable by the people who need it without becoming unrestricted personal data. The structure supports useful discovery while keeping access governed.

Why it was difficult

Experience is not a static attribute. A person may have worked on a project but not on the relevant work package. A prior decision may be useful but no longer current. A local requirement may differ on the next site.

The system therefore had to connect people to evidence and context, not turn a project history into an automatic staffing or compliance decision. Structure supports the human decision. It does not replace it.

Value delivered

• HR and delivery teams can find people connected to relevant project experience.
• Work packages, decisions, documents and dates give experience useful context.
• City A, Project X can help the next team prepare for City A, Project Y.
• RAG makes supporting project evidence easier to retrieve.
• Knowledge transfer reaches across HR, compliance and delivery instead of staying in a silo.
• Permissions keep sensitive personnel and project information governed.
• Company governance becomes structure-led rather than dependent on who happens to remember the answer.

The value is organisational reach. A person's experience can inform more than the project where it was first created, while the responsible people still make the judgement about the current job.

What this means for your business

If resource planning begins with “who do we know that has done this before?”, make the experience searchable through the work that created it. Connect people to projects, cases, decisions and evidence, then let the next team use that context responsibly.

The same pattern applies to professional services, accountancy, insurance, legal work and property. The organisation becomes less dependent on private memory and better able to move expertise where it creates value next.

Related: Knowledge systems · Platform engineering · Construction companies