The next project starts with the right local knowledge, not a blank folder

The next construction project should not begin with a blank folder when the company has already solved a similar problem.

A bridge contract and a housing development can share a contractor and still require different local requirements, permits, decisions and evidence. The knowledge from the earlier job is valuable, but only when the next team can find the relevant part and see where it came from.

We built a project knowledge structure that lets a new team start from prior work while keeping the municipality, project type, contract, date and source visible. The outcome is a better starting point for the next project, not a copied checklist that someone assumes is still current.

Client background

Our client is a large construction company delivering public bridge contracts, housing developments and other multi-site projects. Its teams work with a national baseline of building rules and a local layer of plans, requirements, permits and authority decisions.

The company already possessed much of the necessary expertise. The challenge was to make that expertise reusable when the person, project folder or inbox that held it was not immediately known.

Business challenge

Local requirements change the practical shape of a project. The relevant municipality may have its own plans and processing requirements. A public contract has its own obligations. The site condition, development type and work package introduce further context.

When a new team cannot find the earlier decision, it repeats the work. A compliance officer may be asked to reconstruct a previous submission. A project manager may ask a colleague for the same explanation. A delivery team may discover a local requirement late, after the programme and budget have already been built around a different assumption.

The cost is not only duplicated research. It is slower mobilisation, inconsistent handoff and a higher chance that useful experience stays with the person who happened to be involved last time.

The company needed a way to search by the context that actually matters: municipality, project type, contract, work package, requirement, decision and source.

Implementation

We structured project knowledge around the records that give it meaning. Requirements, policies, permits, decisions and supporting documents are connected to their source project, municipality, contract, work package and date.

The system uses retrieval-augmented generation, or RAG, to find relevant source documents before answering a question. In plain English, it searches the approved project material first, then gives the team an answer with the earlier source still visible.

That lets City A, Project Y use the relevant knowledge from City A, Project X as a starting point. The new team can see what the earlier project did, which document supported it and who was responsible. The old work is useful because its context remains attached, not because it is automatically copied into the new project's compliance position.

The same structure connects people and work packages. A team can find the person who worked on the earlier development or bridge package and transfer the reasoning, rather than only forwarding a document without its context.

Why it was difficult

Knowledge reuse becomes risky when similarity is mistaken for equivalence. Two projects in the same municipality may still have different site conditions, contracts or approvals. A national rule may provide a baseline while a local plan changes what is relevant on a specific site.

The system therefore had to make reuse easy and verification unavoidable. It surfaces the right starting material, but a responsible project or compliance professional still checks the current requirement before the company acts on it.

Value delivered

• New project teams can find relevant prior requirements, decisions and evidence.
• City A, Project X can provide a source-backed starting point for City A, Project Y.
• The municipality, project type, contract, date and source remain visible with the retrieved material.
• RAG helps the team search approved project documents before receiving an answer.
• People and work packages can be connected to the knowledge they helped create.
• The next project can reuse experience without treating an earlier approval as automatically current.

The value is a faster, safer start. The company does not have to choose between repeating the work from scratch and copying a previous checklist without checking it.

What this means for your business

If each new engagement begins by asking who remembers the last similar one, the organisation has knowledge but not knowledge transfer. Make the source, context, owner and date part of the record, then let the next team retrieve the relevant starting point.

The pattern applies to property, insurance, lending, accountancy and legal work. Prior cases become useful when the next team can find what is relevant and understand what still needs to be verified.

Related: Knowledge systems · Systems integration · Property management