Assembling A Collaborative Team - Other - Page 47
40
The collaborative issue of the WHAT and
HOW documents
In the following chapters, the tools for determining the WHY, WHO, WHAT,
WHEN and HOW aspects are set out. As noted above, the HOW and WHEN
aspects are the more straightforward documents to produce. These outputs
may need to be updated during Stage 1 as the structure of the team develops
since, in the initial stages, before any contracts are concluded, there are no
major strategic issues to be considered in relation to them.
The WHAT and HOW aspects create one issue in relation to the collaborative
team: if the project team is to be truly collaborative, each party in the team
should agree and be comfortable with the specific aspects of the WHAT and
HOW documents that will impact on their services.
However, to properly obtain fee quotations for these services, the project lead,
with the assistance of the lead designer, will have to prepare initial versions of
these documents. It is therefore essential to ensure that each party is given
adequate opportunity to comment on the suite of documents at tender stage to
allow any refinements to be made. However, it must be remembered that if the
services of one party are adjusted, the relevant services need to be added or
deleted from another party’s Schedule of Services and the Design Responsibility
Matrix incorporating Information Exchanges reconsidered.
Ultimately, the aim is to ensure that the documents for all members of the project
team have been agreed and, more importantly, that they interrelate and dovetail
with each other. It is for this reason that the majority of the tools in Assembling
a Collaborative Project Team are multi-party, ensuring that the risk of gaps or
overlaps in who will do WHAT and HOW is minimised.
Chapter 5 examines the documents that relate directly to the client (WHY), with
Chapters 6 to 9 addressing the WHO, WHAT, WHEN and HOW aspects required
to establish the collaborative team. Chapter 10 considers how these can be used
in conjunction with the range of professional services contracts and operational
or Building Contracts that exists to contractually bind the project team together.
Summary
Assembling a Collaborative Project Team encourages the use of tools that allow
the project team to be assembled incrementally (WHO), defining the specific
obligations of each party and the information that they will deliver at each stage
(WHAT), as well as determining the various Project Programmes (WHEN) and
the protocols and procedures (HOW) that everyone will follow. The completed
documents can be utilised as appendices for inclusion in the relevant contracts
and, more importantly, they become tools that can be used in the day-to-day
running of a project.
www.ribaplanofwork.com
