In a railway project, the design is often done by a team of experts from several companies. Each company has its own guidelines, systems and quality assurance practices. In the project, these must be aligned so that everyone shares the same understanding of how the work is progressing, who is responsible for what, and when a plan is ready for handover.

The project's shared plans and guidelines lay the foundation for this. In day-to-day work, however, more precise answers are needed: who is responsible for the internal review of a plan, how the solutions of the different technical disciplines are coordinated, who makes the corrections, and how is it ensured that they have been made? These matters should also stay clear when work passes from one company or expert to another.

In a project with several parties, this matters most when shared milestones are tracked. Besides the agreed date, you need to know when the material was submitted for internal or external review, whether it met the review-readiness criteria for that stage, when feedback was given and how the corrections have progressed. If a milestone is not met as planned, this information shows at which stage the delay arose and how it affects the work of the other parties. It also makes it possible to assess, on the basis of shared, documented information, how well responsibilities and agreed procedures have been followed.

The aim is for quality assurance to form a coherent whole within everyday design work. National and EU regulation, the applicable standards, and the client's technical, safety and information management requirements must show in how the work is done and in how compliance with the requirements is demonstrated.

At the same time, a second, longer-term question needs an answer: how can what was learned in the project also be put to use in the next projects?

Find what matters for your role

A shared way of working shows up differently in design management, in day-to-day work and in the client's design steering. You can read the whole article or use the table to go straight to the part that interests you.

Your roleYour question is probablyRead first
Project manager/
lead designer
What is the overall status of the design and which decisions are still open?
Have the plans been coordinated?
How are the project's shared requirements applied, and who settles unclear interpretations?
Project and company practices must be aligned
Service provider's railway design managementWhich of the project's agreements are project-specific, and which are worth adopting as the company's permanent practice?
Are skills and resources sufficient when the work is shared among several service providers?
Project and service provider practices must be aligned
Responsible designer
What information do I need to confirm that a design package is ready for handover when the work is done in several companies?
Everyone must be able to find the information that matters for their own work, then Seven questions from requirement to handover, especially point 6
Information model or quality coordinatorHow can the shared way of working be implemented in the existing systems so that the necessary information can be found without duplicate recording and tracking?Five questions for assessing your own way of working
Designer or internal reviewerWhen is a plan ready for internal review or for handover?
How are review findings handled, and how is it ensured that corrections are made?
Seven questions from requirement to handover
Client's design steeringWhich requirements and procedures does the client define, and what do the service providers doing the design agree among themselves?
How is handover readiness demonstrated to the client?
Project and company practices must be aligned, then Self-delivery brings together the information on handover readiness
Management of the client's design divisionWhich ways of working are agreed project by project, and which belong to the shared practices of the technical discipline?
How can the project's lessons also be used in future projects?
The project's lessons must also carry over to the next projects

Shared ways of working must be agreed early enough

Itärata (the Eastern Rail Link) is a current example of a stage in which shared ways of working are being built. In September 2026, Itärata Oy said it was defining the scope and schedule of the general plan and the shared ways of working together with its design partners. Already in a procurement announcement published in March, the goals of the development phase also included preparing an operations and quality plan.

The design is carried out by Itäradan tekijät, a service provider consortium formed by Sitowise and Ramboll, and by Timantti, a service provider consortium formed by Sweco and Finnmap Infra.

The development phase is a natural time to also agree on how the shared principles are put into practice in individual design tasks, reviews and handovers. When responsibilities and procedures are gone through at the start of the work, they can be used to steer the design throughout the project.

Itärata's public descriptions set out the goals of the development phase. They do not allow an assessment of the project's detailed quality assurance practices. Here, Itärata serves as an example of when a shared way of working is defined.

Project and service provider practices must be aligned

In a project involving several organisations, the way of working is defined at different levels. The client sets the requirements and approves the project's shared procedures. The service provider consortium, or another design organisation of the project, agrees on cooperation between the service providers and on coordinating the plans. Each service provider is responsible for its own quality assurance, competence and the organisation of its work.

Together, these practices must form a whole that the designer and the internal and external reviewers can follow in their own work.

For example, a service provider's internal review may be well defined. The project must still agree on how its results are passed on to another service provider, to the external reviewer or to the client. It must likewise be agreed who decides when a correction in one technical discipline affects the plan of another.

The service providers' working practices are a good starting point. Joint agreement is needed especially at the points where responsibility, information or a plan passes from one party to another.

Seven questions from requirement to handover

Nexpert's framework looks at the way of working through seven questions. It is a framework for supporting practical work, applied in line with the project's own requirements and agreed procedures.

  1. What is the requirement based on?
    The designer must know which guideline, requirement or project decision the work follows. The version to be used and any project-specific clarifications must also be clear.
  2. Who is responsible for each stage of the work?
    The tasks of the plan's author, the internal reviewer and the responsible designer must be agreed. It must also be known who settles an unclear interpretation, handles a deviation and decides whether the work proceeds. The responsibilities for any external review, and how it links to the other stages, are agreed separately.
  3. What material is used and where is the work done?
    Everyone who needs them must know where the source data, plans and models are and whether they are up to date. Cooperation requires that the parties know which material is in use at any given time.
  4. What is checked before the work is passed on?
    The content of the designer's own check and of the internal review, and the division of work between them, must be defined. It is also agreed how the reviews are documented and where the next party can see what has already been reviewed.
  5. How are findings handled and corrections verified?
    A finding needs a responsible person, an agreed way of handling it and information on how it was resolved. After a correction, it must also be possible to show that the correction has been reviewed and the finding can be marked as closed.
  6. On what conditions is a plan ready for handover?
    The readiness criteria are agreed in advance. The material handed over must carry information on its version, the reviews carried out and any open issues and how they are being handled. The delivery and receipt of the material are also documented in the agreed way.
  7. How does experience change the way we work?
    Recurring findings must also be looked at from the point of view of the way of working. Is a guideline unclear, is something missing from the checklist, or does the division of work or the onboarding need to change?

The answers may sit in several systems. What matters is that they can be found and are linked to the right design material. It pays to make use of the existing systems and the links between them so that the same information does not have to be maintained in several places.

Everyone must be able to find the information that matters for their own work

A shared way of working serves different roles in slightly different ways.

The project manager and the lead designer need an overall picture of the progress of the design, the coordination of the plans, open decisions and the issues affecting handover. Design management must also be able to assess whether resources and competence are sufficient.

The responsible designer of a technical discipline needs information on the applicable requirements, the reviews carried out and unresolved technical questions. The designer, in turn, must be clear about what is expected and when the work is ready for the next stage.

The internal reviewer must know which version is being reviewed, what the review covers and how findings are handled. The reviewer must have access to the source data needed for the review and to information on decisions that affect the design solutions.

Information model and quality coordinators support the whole according to their own tasks. Their work requires clear links between models, documents and review records.

Job titles and the division of responsibilities vary from project to project. That is why the roles must be gone through with the project's own organisation. Naming a responsible person does not yet tell what they are responsible for or what information they need to carry out that responsibility.

Self-delivery brings together the information on handover readiness

In design self-delivery, the service provider verifies the quality and handover readiness of its own work before delivering the material to the client. It brings together the information showing that the agreed reviews have been carried out, the findings handled and the material meets the handover conditions.

Nexpert has taken part in developing the shared minimum requirement for self-delivery in the Finnish Transport Infrastructure Agency's (Väylävirasto) design projects. The work has included workshops, comment rounds, preparing Excel templates and supporting the roll-out.

Self-delivery builds on the quality assurance done during the design, such as the designer's own check and the internal review. When reviews and corrections are documented as the work proceeds, handover readiness can be followed well before the handover date. This also reduces the need to work out afterwards what has been reviewed and what is still open.

The procedure to apply is always determined by the project's requirements and contracts. It cannot be assumed without a separate check that the model developed for the Finnish Transport Infrastructure Agency suits, for example, the Itärata project.

The project's lessons must also carry over to the next projects

Projects constantly produce knowledge about what works and what should be improved. Too often this knowledge stays in the project documents or with the people who were involved. The next project team then has to solve the same questions all over again.

A learning organisation needs an agreed way of processing experiences and turning them into shared practices. Who collects the findings? With whom is their significance assessed? Who makes sure that a necessary change is taken into the guideline, the checklist or the onboarding?

Not every project-specific solution needs to be carried over as such to the next project. Instead, you need to identify which lesson can be used more widely and in which situations it works. It also pays to keep the reasons for the solution, so that the next user understands why the way of working was changed.

In a project with several design companies, it must also be agreed how jointly identified development needs are handled in the participating companies. Updating the project's shared guideline does not yet ensure that the lessons reach the service providers' own practices and future assignments.

It is worth setting aside time for processing lessons already during the project. Experiences are then fresh, and the ongoing work can also benefit from the improvements.

Onboarding shows in practice how well the knowledge has been captured. A new expert should be able to find out which requirements to follow, what their responsibility is, how the work is reviewed and whom to ask for help in an unclear situation. Finding these answers should not require going through old meeting minutes or knowing the right person.

Five questions for assessing your own way of working

You can look at your own project's situation with the following questions:

  1. Does every designer know when their work is ready for internal review and when for handover?
  2. Is it clear who is responsible for the internal review, any external review, corrections and confirming handover readiness?
  3. Can the right material version, review results, records of how corrections were handled and the dates of the different stages be found in one place or through clear links?
  4. Can the necessary information be produced and found in the existing systems without unnecessary duplicate recording?
  5. Do the project's lessons carry over into shared guidelines and onboarding so that the next project team can use them too?

An unclear answer helps you see what to specify next in the way of working. It may be a single responsibility, the flow of information between companies, or an agreed practice that has not yet made its way into onboarding.

A shared way of working serves its purpose when it helps experts do their work, demonstrate its quality and make use of what has been learned before. The competence built in the project then also carries over to the next projects.

Sources

Author

Tanja Karonen, Nexpert. Nexpert acted as the responsible service provider when the Finnish Transport Infrastructure Agency (Väylävirasto) developed and introduced a shared self-delivery operating model for general, road and railway design in 2024–2026. Read what the work involved →

Filed under

Tanja Karonen is an entrepreneur and digital transformation expert whose expertise includes process development, project management, quality assurance, and leveraging artificial intelligence in business development. Through Nexpert, she helps organizations develop their processes, manage data, and adopt new technologies in a practical and human-centered way. Her background also includes public administration development projects, Lean thinking, and digital business.

About Nexpert