Vellum & Razor Blades

20/05/2026

How does every deliverable handoff land clean?

By starting with clarity.

Every project is a chain of handoffs.

The surveyor's real world site confirmation becomes the design team's starting point. The architectural design models become the MEPF backgrounds. The specification becomes the contractor's instruction and the shop drawings become what they build.

Each handoff carries one person's progress and sets up the next person's work.

When the start clearly defines every handoff and the deliverable expectations we land on firmer ground downstream. Coordination is more reliable and the build reflects more closely to the intent. The project leads walk into meetings with fewer surprises and better answers.

A clean project is not about luck or hope. It is a series of defined handoffs that landed where they should because they were choreographed effectively.

Follow for more like this.

20/05/2026

19/05/2026

How does it feel to work on projects? There's a slight shift that changes the experience completely.

Most teams think about their deliverables as outputs. The drawings they produce, the model they hand over or the schedule they publish.

But every deliverable a project produces also becomes someone else's input. What the surveyor confirms becomes the design team's starting point. What the design team models becomes the cost consultant's basis for pricing and the fabricator's background for shop drawing coordination. The coordination in the specs and shop drawings is what the contractor builds from.

Once you see deliverables in this way, the project stops looking like a list of tasks and starts looking like a choreography of collaborations. Each handoff carries someone's progress and kickstarts another series of guided steps.

This is what scripting a project means, it's not setting a series of tasks, it's the choreography of who carries what to whom, by when and at what level of quality.

Teams that script their work well make the rest of the work easier for everyone downstream. They tend not to produce so much work that needs unwinding later because the connections are visible and coordinated.

The layers of a project run deep and they live in each of those handoffs. They are far easier to script before anyone opens a model than to try to repair after the fact.

The free Delivery Control Scorecard helps you see where your next project is starting in control and any areas that may be prone to causing friction.

Link in bio.

18/05/2026

Most projects do not run out of time at the end. They miss the clarity at the start that would have prevented much of the reactive firefighting we see across the industry.

The kickoff meeting is treated as the beginning, but the real work should have happened well before anyone sits at that table.

Site surveys, building surveys, as-builts, true north, geodetic elevation, geotechnical, utilities, zoning, and other existing elements introduce the guardrails the design must respect. They are not background documents. They are critical to starting the project with clarity.

When iterative design processes start without them, assumptions get made, embedded in the design, and often not uncovered until late in design or in construction, when correcting issues is at its most costly in complexity and effort.

This is where owners need to be aware of what their design teams will need to start in a clean and composed manner. The most useful thing an owner can do is not push for design to begin with haste. It is making sure the existing conditions of the site or asset are verified, packaged, and ready when the team is expected to start real design coordination.

The future of this is clear: owners handing across a coordinated, three-dimensional record of their assets at the start of every project, instead of one being rebuilt from scratch. This is the world of digital twins providing the starting point. We are not there yet across the industry, but the direction is set.

When existing conditions arrive late, assumptions get embedded into drawings, cost plans, and procurement decisions. They often stay hidden until construction, when the team pays by losing evenings and weekends to unwind them.

Preparation of your projects cannot start too early.

Take the Delivery Control Scorecard through Link in my bio or the first comment to see whether your next project is starting in control or hoping for control.

Follow for more on defining your path before the journey begins.

15/05/2026

Most teams treat templates as admin, but that is the wrong frame entirely.

Too many projects start as if nothing was learned from the one before.

The last project finishes, and lessons that were noticed are forgotten, or maybe they were discussed but went no further. They may sit in someone’s head or get buried in a folder nobody opens again.

Then the next project begins, and the team starts rebuilding from scratch, usually in a rush to get started. This is a systems problem.

Templates should be seen as the place where lessons go to survive.

When the things a team learned on the last project return to the template strategy, the next project starts from a more refined position with less friction at the start, fewer decisions made under pressure, and less time spent rebuilding what already existed.

That is the difference between a team that prepares and a team that simply begins.

Start With Clarity is not just a phrase. It depends on the setup being strong enough to carry the lessons forward.

Take the free Delivery Control Scorecard via the Visit My Website button. It will show where your delivery setup is strong and where the gaps may exist.

Name one thing your team had to rebuild from scratch on the last project that should have been carried forward from the one before?

11/05/2026

Most projects are not given the start they deserve.

Preparation is rushed and key data is delivered in fragments or not at all.

Scope starts unclear and remains unclear, maybe without recognition where it matters.

Where could your project starts be improved? Let us know in the comments.

Follow for more on defining your path before the journey begins.

06/05/2026

Most project templates get treated as admin which is the wrong frame entirely.

I have spent over thirty years watching delivery teams start projects the same way. The kickoff is busy, the timeline gets issued loosely, and the production team begins. And through all of it, nobody has clearly defined the destination or the key steps along the road to get there.

Templates are not there to create more work. They exist so that when a team arrives at the first decision point, they are not inventing the answer under pressure. The scaffolding is already there and ready to build on.

Its not theory and its not BIM standards. Its practical systems that hold under real deadline pressure.

Take the free Delivery Control Scorecard via the link in my bio. Let me know in the comments whether it was useful.

06/05/2026

Most project templates get treated as admin which is the wrong frame entirely.

I have spent over thirty years watching delivery teams start projects the same way. The kickoff is busy, the timeline gets issued loosely, and the production team begins. And through all of it, nobody has clearly defined the destination or the key steps along the road to get there.

Templates are not there to create more work. They exist so that when a team arrives at the first decision point, they are not inventing the answer under pressure. The scaffolding is already there and ready to build on.

The firms that deliver predictably do not work harder than the ones that don't. They start cleaner. They have pre-defined the decisions that would otherwise get made in a rush, by the wrong person, at the wrong moment.

That is what this series is about. Its not theory and its not BIM standards, a series of documents sitting on a server that nobody reads. Its practical systems that hold under real deadline pressure.

Take the free Delivery Control Scorecard via the Visit My Website button. It will show you where your delivery setup is strong and where the gaps are. Let me know in the comments whether it was useful.

What is the one thing your team always has to figure out mid-project that should have been locked on day one?