If you have ever been asked to produce a Design Management Plan and wondered what exactly should go into one — or why it is needed in the first place — you are not alone. The DMP is one of the most consistently misunderstood documents in UK construction. It is mentioned in appointments, required by employers and referenced in pre-contract submissions, yet on many projects it is either never produced, produced late or produced as a hollow compliance exercise that nobody reads again after it is submitted.

That is a missed opportunity. A well-written Design Management Plan is one of the most useful documents on a construction project. This article explains what it contains, when it should be produced, who owns it and how it should evolve through the project lifecycle.

What Is a Design Management Plan?

A Design Management Plan is a project-specific document that sets out how the design process will be organised, managed, coordinated and delivered. It defines the structure of the design team, the procedures that govern how the team works, the standards that apply and the tools and platforms that will be used. Think of it as the operating manual for the design process on a particular project.

It is distinct from the Project Execution Plan, which covers the broader project — including construction, procurement and commercial management. The DMP focuses specifically on design. On some projects the two are combined into a single document; on larger or more complex projects they sit separately.

What a Design Management Plan Contains

Project Overview and Design Objectives

The DMP begins by setting the context — a brief description of the project, its key parameters and the design objectives that the plan is intended to support. This section establishes what success looks like for the design process and aligns the team around a common set of outcomes from the outset.

Design Team Structure and Responsibilities

This is one of the most important sections. It sets out who is in the design team, what each party is responsible for and how responsibilities are allocated across the disciplines. It typically includes an organogram showing reporting lines and the key interfaces between consultants, and it cross-references the Design Responsibility Matrix which allocates specific design outputs to specific parties.

On projects where responsibilities are genuinely shared or contested — for example, where a specialist subcontractor is carrying design responsibility for a significant package — this section of the DMP is critical for preventing disputes later.

Design Programme

The DMP includes or references the design programme — the schedule that sets out when each design deliverable is due, the sequence of activities and the key milestones such as planning submission, tender information and construction information release. The programme should be realistic, logic-linked and maintained as a live document throughout the project rather than filed away after the first issue.

Design Procedures and Protocols

This section defines how the design team operates day to day. It covers meeting schedules and formats, how design information is issued and reviewed, the approval process for key decisions, how changes are managed and how the team resolves coordination issues. These procedures should be agreed with the full design team — not written by one party and imposed on the others.

Information Management Approach

The DMP sets out how project information will be managed, naming the Common Data Environment that will be used, defining the naming conventions and folder structure, setting out the document approval workflow and confirming compliance with relevant standards such as ISO 19650. This section should be consistent with the project’s BIM Execution Plan where one exists.

Design Quality Management

This section explains how design quality will be assured throughout the process. It covers the design review schedule, the criteria against which design outputs will be assessed, the process for design verification and the approach to design audits. It should be specific enough to be useful — a generic statement that “quality will be maintained” is not a quality management approach.

Change Management

How scope changes are identified, assessed, approved and recorded is one of the most commercially significant processes on any design project. The DMP should define the change control procedure clearly — who can initiate a change, how it is assessed for programme and cost impact, who has authority to approve it and how it is communicated to the design team and the contractor. A robust change management process defined upfront saves enormous time and money later.

Risk Management

The DMP identifies the key design risks for the project and sets out how they will be managed. This is not a full project risk register — it focuses specifically on design risks: complex interfaces, long-lead specialist design packages, planning uncertainties, novation of consultants, and so on. It should be a live section of the document, reviewed and updated as the project progresses.

When Should a Design Management Plan Be Produced?

The DMP should be produced at the very start of the design process — ideally before the design team is formally appointed, or at the latest within the first few weeks of RIBA Stage 1. The earlier it is produced, the more useful it is. A DMP produced after the design is already underway is largely retrospective and misses the opportunity to establish the procedures and disciplines that prevent problems from arising in the first place.

The document should be issued for comment to the full design team, agreed and then baselined. It is not a static document — it should be reviewed and updated at key project milestones, typically at each RIBA stage gate, to reflect the evolving design team structure, updated programme and any changes to procedures.

Who Owns the Design Management Plan?

Ownership of the DMP typically sits with the Design Manager, who is responsible for producing, maintaining and enforcing it. On projects where the client has appointed a separate Design Manager — such as a Virtual Design Manager from JC Virtual PMs — that role owns the document on behalf of the client. On contractor-led projects, ownership may sit with the contractor’s design manager, with the employer’s team having review and approval rights.

The critical point is that someone must own it. A DMP that is produced collaboratively but owned by nobody will not be maintained, enforced or used.

The Difference Between a Good DMP and a Shelf Document

The test of a Design Management Plan is not whether it exists — it is whether it is used. A good DMP is a live reference document that the design team actually works to. Meeting schedules are followed. Change control procedures are applied. The design programme is updated and reported against. Quality reviews happen on time and to the agreed format.

A shelf document, by contrast, is produced to satisfy a contractual requirement, submitted and then forgotten. It describes procedures that are never implemented, a programme that is never updated and quality standards that are never enforced. The project operates informally, and the DMP becomes an irrelevant document that bears no relationship to how the design is actually being managed.

The difference between the two is almost always the presence or absence of a capable Design Manager who takes ownership of the document and drives compliance with it.

How JC Virtual PMs Can Help

Producing and maintaining a Design Management Plan is a core part of what we do at JC Virtual PMs. We work with clients and design teams from the earliest stages of a project to establish the procedures, structures and disciplines that make the design process run smoothly. Our DMPs are tailored to each project — specific, practical and designed to be used rather than filed.

If your project is about to start and you need a Design Management Plan produced, or if you have an existing project where design management needs to be brought under control, get in touch to discuss how we can help.