Germany

BZL Kommunikation und Projektsteuerung

Independent steering, controlling and communication management for building and infrastructure projects.

  • Independent of the contractor
  • Developers and public clients
  • Schedule and cost oversight

What an independent steering mandate actually is

A construction or infrastructure project rarely fails on one decision. It drifts: a design change that nobody priced, a trade that starts two weeks late, an authority comment that sat unanswered in somebody's inbox, a report that says the project is on schedule because nobody checked the baseline it was measured against.

Project steering is the client-side function that catches that drift. We act for the client — the developer, the public authority, the owner — and only for the client. We do not design, we do not build, and we hold no contract with the executing firms, which is precisely what allows us to assess their schedules, their claims and their progress reports on your behalf.

In practice that means three things running in parallel: controlling, so that deadlines, costs and quantities are measured against an agreed baseline rather than against optimism; communication management, so that everyone involved receives the same information at the same time and decisions are documented when they are taken; and stakeholder coordination, so that planners, authorities, operators, neighbours and committees are brought in at the point where their input still changes something and not after.

What we take off the client's desk

Schedule oversight with a real baseline

We review the contractor's programme, fix a baseline the client has actually approved, and track milestones and critical path against it. Delays are reported when they appear, with the cause named and the recovery options set out.

Cost and quantity controlling

Budget lines, commitments, invoices and forecast to completion in one running picture. Change orders are assessed for merit and priced before they are signed, not explained after they are paid.

Communication management

One information channel, one minute of record, one version of the drawing set in circulation. Decisions get an owner, a date and a place where they can be found again two years later.

Stakeholder coordination

Planners, specialist engineers, authorities, operators, committees and neighbours each need something different and at a different moment. We sequence those inputs so approvals arrive before they block the programme.

Claim and deviation assessment

Supplementary claims, disruption notices and defect notifications are examined against the contract and the as-built record, so the client enters negotiations with a documented position rather than an impression.

Reporting the client can forward

A regular status report written for the people who decide — board, committee, authority — with status, deviation, risk and the decisions required before the next period.

Mandates we are engaged for

Each is scoped to the project phase. Most clients combine two of them.

Most requested

Project steering

Client-side management of the whole project, from preparation through to handover.

  • Organisation, information and documentation rules
  • Programme, cost and quality oversight
  • Decision templates for the client body
  • Contractor and planner performance review

Project controlling

The measuring function alone, where steering already sits with an internal team.

  • Baseline schedule and budget structure
  • Deviation analysis per reporting period
  • Forecast to completion
  • Risk register maintained with the client

Communication management

The information architecture of a project with many parties and long duration.

  • Single document and plan circulation route
  • Meeting structure, minutes and action tracking
  • Escalation path for unresolved items
  • Reporting formats for client and committees

Stakeholder coordination

For projects where approvals, operators or the public are on the critical path.

  • Stakeholder map and input sequence
  • Authority correspondence managed in one place
  • Preparation for committee and public sessions
  • Record of commitments made to third parties

Second opinion review

A bounded review of a running project where the reported status is no longer trusted.

  • Audit of schedule and cost reporting
  • Interviews with the project parties
  • Written findings with prioritised measures
  • Handover briefing to the client team

Scope, duration and fee are agreed per project after the initial review. No standard package is quoted in advance.

How an engagement runs

  1. Initial conversation

    You describe the project, its phase and what is currently going wrong or what you want kept from going wrong. We say plainly whether a steering mandate is the right instrument.

  2. Review of the existing position

    We read the contracts, the current programme, the cost status and the last reports, and walk the site if there is one. The output is a short written picture of where the project actually stands.

  3. Mandate and scope

    Scope, reporting rhythm, decision thresholds and the client's own responsibilities are fixed in writing before we start, so nobody is unclear about who decides what.

  4. Steering in operation

    Regular site and coordination rounds, controlling against the baseline, documented decisions and a status report per period with the items that need a client decision marked as such.

  5. Handover and closure

    Defect tracking to completion, final cost reconciliation and a closed documentation set passed to whoever will operate the asset.

What you are left holding at the end

A steering mandate is worth what it leaves behind. When we step out of a project, the client holds a complete and ordered record of it — not a shared drive that three firms each organised differently.

That record is also the reason clients engage an independent party in the first place. Where a dispute arises, the position is already documented; where it does not, the operator inherits a building or an asset whose history is legible. Both outcomes are products of how the project was run, not of what was written down at the end of it.