Starting Your Project Right: The Key Design Documents You Can’t Ignore

Scenarios like this don’t just happen on poorly run projects. They happen all the time, and the root cause is nearly always the same: the basics of design information were never set out properly at the start.

And here’s the first truth: no two projects are the same. The contract type, how much design sits with the client or the contractor, even which consultants are in play — all of it changes job to job.

So let’s be clear up front: this isn’t a comprehensive checklist of every document you’ll ever need. Projects come with health & safety plans, statutory approvals, endless contract clauses, and enough paperwork to fill a skip. What we’re talking about here is one slice of the picture: design information.

Because if you don’t get the design information right from the start, even the best contract won’t save you.

We’ve seen it too many times. The wrong drawing gets issued, the right drawing arrives late, or a client decision never comes at all. The result? Delays, disputes, extra costs. And those costs don’t usually fall on the consultants producing the drawings — they fall on the builder or the client.

When information isn’t managed, site life becomes a guessing game. Which drawing is right? Which version rules? It’s chaos, and chaos costs money.

Before we even talk about specific documents, there are a few basics that should be nailed down on every job:

• Clarity of design ownership. If a contractor is responsible for part of the design, it shouldn’t just be listed as a vague heading. It needs a full description, the outputs required, and a clear process for how that information will be approved.
• Agreement on approvals. Whether set out in the contract or agreed informally, everyone should know how contractor design portions will be checked, approved, and signed off. Don’t assume “competence” will cover it. It rarely does.
• Basics of document control. Revision control, issue procedures, consultant responsibilities. Even a short, simple statement covering these points can prevent months of pain later.

This is the map of who does what. It should clearly list out which party is responsible for which design element — client, consultant, or contractor. It should flag statutory items like Building Regulations, CDM, and planning consents. And it should leave no doubt about who the principal designer is, who the lead consultant is, and who’s responsible for coordinating packages.

It’s amazing how many projects skip this, and equally amazing how much confusion it prevents when it’s done properly.

If there’s one document that makes or breaks a project, this is it.

The Design Information Release Schedule (IRS) sets out:

• What information is required.
• When it’s required.
• Who is responsible for producing it.
• In what format it should be issued.
• Where coordination with other packages is critical.

And it’s not just about drawings. Client decisions should also be listed — phased so the client knows exactly when a decision is needed, and crucially, why.

The best IRS documents account for the different stages information is needed:

1. For procurement (placing orders).
2. For coordination (checking clashes and interfaces).
3. For construction (building from the final design).

That means factoring in lead times for design, approval, fabrication, and delivery. It’s a thinking document. One that forces the whole team to plan ahead — instead of stumbling from one “urgent” drawing issue to the next.

We’ve already tackled document control. The next step we’re building is a smarter way to manage design information release and responsibility in one live tool. It isn’t available yet, but if you’d like to be part of the beta, get in touch.

Skip these basics, and the outcome is predictable. Endless email chains. Duplicate drawings in circulation. Late client decisions. Poor coordination. Disputes that end up costing real money.

If you don’t plan the information, you’ll end up planning the excuses. Get the basics in place.

Put these documents in place, and the benefits show up quickly:

• Clear responsibilities, less finger-pointing.
• Right information at the right time, smoother workflow.
• Clients make decisions in context, not under pressure.
• Less wasted time, less wasted money.
• More trust across the team.

And if you’re using Capsa, these documents don’t get buried in folders or lost in inboxes. They sit alongside your project information, live and shared, always showing the latest version. The basics stay visible — and the whole team stays aligned.

Too often, consultants avoid this conversation. Sometimes it’s down to misunderstanding. Sometimes it’s complacency. And sometimes it’s just the assumption that “we’ve got this covered.” But a competent consultant won’t be afraid to set responsibilities and information flow out clearly.

Clients and builders shouldn’t be afraid to demand it. If your team can’t provide these basics, that’s a red flag. The best consultants will welcome the conversation, not avoid it.

Because whether you’re a client, a builder, or a consultant, the principle is the same: start your project with the right design documents in place. They’re not complicated, but they are essential.

Small effort now, big savings later.