Requirement

Requirement 6.3 Execute the project

To ensure that we implement the project plan of work (PPW) to produce
Objective the identified deliverables to the required standard

Policy or directives
Directive 6 – Do
reference

Pre-requisites An approved PPW.

Guidance – Execute the project

Supporting guidance
Guidance – WIN and DO eform requirements

Table of contents

1. Introduction ........................................................................................................................................... 1
2. Expected results ................................................................................................................................... 1
3. Exceptions and escalations ................................................................................................................ 2
4. Requirements ........................................................................................................................................ 3
6.3.1 Implement the PPW ........................................................................................................................... 3
6.3.2 Develop the information ................................................................................................................... 11
6.3.3 Check the information ...................................................................................................................... 14
6.3.4 Approve the information ................................................................................................................... 15
6.3.5 Share the information ....................................................................................................................... 16
6.3.6 Publish the information .................................................................................................................... 16
6.3.7 Confirm client acceptance................................................................................................................ 17

1. Introduction
Given the diversity of the projects delivered by the Group, we have not detailed how specific types of project
are executed in this process; this information and supporting best practice can be found on relevant practice
sites.
The execute process instead focuses on ensuring that we manage delivery and quality, including co-ordination,
sharing and publishing, of the deliverables.
This is managed through check and approval of deliverables.
Check and approval objectives are to:
• Confirm that the deliverable meets the scope of work in the PPW,
• Confirm the deliverable is technically correct and meets client requirements

2. Expected results
The purpose of the execute process is to ensure that:
• The Project Manager implements the PPW, cascading the necessary information to team leaders
and team members
• All deliverables are checked and approved before sharing (internal) and publishing (external)
• Project records are maintained in accordance with the PPW
• Lessons are learned, recorded and shared (as appropriate) after each major deliverable is published

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 1 of 17
 Requirement

3. Exceptions and escalations

• None

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 2 of 17
 Requirement

4. Requirements
STEP Requirement Supporting guidance/ best
Requirement
activity reference practice
6.3.1 6.3.1 – 1 The Project Manager must execute the project in line with the project plan of work
Implement Role of the (PPW). The Project Manager must brief all team members on the contents of the PPW,
the PPW Project including the project risk assessments (HSSRA, ISRA, PSR, SERA and PABRA).
Manager The project team will deliver the scope of work defined in the contract and identified
in the work break down structure. The PPW should be used by the team as a guide
as to how the commercial success of the project can be achieved through publishing
deliverables that meet client requirements to the agreed schedule.
The Project Manager should liaise with the Client Account Leader throughout the
project to assist in the process of maintaining and improving our relationship with the
client and our right to win further work with them. Through the delivery of the project,
information gathered about prospects for work should be brought to the attention of
the Client Account Leader. Where available, Connect Business CRM should be used
to record touch points with the client organisation as the execute activity progresses.
The Project Manager should liaise with Divisional Practice Managers for the relevant
technical work involved in the scope of work. The objective should be to reapply the
Group’s knowledge to reduce delivery risk and improve project efficiency. Where
appropriate on complex projects, support may also be sought from members of the
Excellence community such as, Technical Excellence Leaders, Sector Leaders or
Knowledge and Innovation Managers.
The role of the Project Manager throughout Execute, in addition to any role they have
in developing information, is to plan ahead and seek to ensure that with the support
of the Project Principal, Account Leader and Resource Manager for the project that
delivery is successful. Within this, the Project Manager should liaise with divisional
support services colleagues to facilitate billing the client promptly, correct commercial
implementation of the contract and compliance with the Group’s requirements. Project
controls resource allocated to, or embedded in, the project may undertake a number
of these activities.
All regions except NASA: The Project Manager must ensure that climate risk
mitigation actions identified in the SERA should be implemented.

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 3 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.1 – 2 The Project Manager shall review the due diligence carried out on the sub
Outside consultancy. The appointment of the sub consultant may only proceed when all
services supporting information required has been provided by the sub consultant and
mobilisation confirmed as being appropriate
The Project Manager is to confirm in risk treatment plans in the project risk
assessments are included in the sub consultant relationship when applicable.
6.3.1 – 3 The Project Manager must prepare the Group standard sub consultancy agreement. Guidance: Standard sub-consultancy
Sub This must define the scope of services, which must include the following where agreement
consultancy relevant:
agreements • Project title and project number (including any sub-project references)
• Key Group personnel and organisation chart
• Brief description of the project
• Description of the work to be undertaken
• Background data and criteria, including codes standards and statutory
requirements
• Reference documentation
• Requirements for checking, approval, review, audit and documentation
formatting
• Inspection requirements and acceptance criteria
• Calibration requirements for inspection, measuring, test and survey equipment
• Programme and key dates
• Health, safety and security requirements e.g. risk assessments or method Hazard information sheet: HIS 52 –
statements, relevant training etc – see hazard information sheet HIS 52 Working with third parties
• Sustainability, environmental and carbon requirements, with reference to the
Group environmental policy
• Information security and confidentiality requirements, with reference to the
Group information security policy
• The principles of the General Data Protection Regulation (UK) shall be adopted
by the sub-consultant or its equivalent in the project’s territory.

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 4 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
• Requirements to comply with our policies on respecting people, diversity,
equality and inclusion, avoiding modern slavery or human trafficking, providing
effective safeguarding for people at risk and giving the staff the right to speak
up if the need arises.
• Ethical requirements, with reference to the Group ethics policy
• Reporting requirements to monitor progress
• Payment schedule and invoice procedure
The sub consultancy agreement shall also comply with territory specific legislation and
regulation.
Where the work to be executed is in the context of a regulated industry the sub
consultancy agreement will document relevant requirements.
6.3.1 - 4 Sub consultancy agreements must be approved by the Project Principal. Two
Approval of sub unsigned copies must be sent to the subconsultant and both returned signed to the
consultancy Group to confirm acceptance by the subconsultant. Both must then be signed on
agreements behalf of the Group and one returned to the subconsultant.

6.3.1 - 5 Before mobilising the sub consultant, the Project Manager must confirm that the
Mobilising sub relevant agreements are in place and must have all necessary approvals and
consultants signatures.

6.3.1 - 6 Health The Project Manager must:

and safety • Complete any outstanding actions identified in the project safety review (PSR)
management
• Implement the control measures identified in the health, safety and security risk
assessment (HSSRA) and inform the project team members of any client
and/or contractor-specific requirements
• Ensure that all staff visiting site have read and understood the HSSRA and
read and acknowledged/ signed the declaration (HSSRD) to confirm this
• Ensure that, where the Group is undertaking a statutory health and safety role,
the project team members responsible are competent and have adequate
resources

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 5 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.1 - 7 For work involving design, the project manager must ensure that: Form: MMF110 Designers' hazard
Work involving • Designers are familiar with, and apply, the principles of ‘safe by design’. This elimination and management record
design shall be achieved by viewing the mandatory online training programmes for (Word)
safe by design and attending the country-specific duties of the designer training
course MMF110 Designers’ hazard
• Design decisions are recorded on the relevant version of form MMF 110 - elimination and management record
Designer hazard elimination and management record and that any justifications (Excel)
for action taken or not taken are included
• Designers follow any specific legislation applicable to design in the country of
operation and/or the country in which their design will be constructed (if
different)
6.3.1 - 8 The Project Manager should ensure that all information is developed under the
NASA and guidance of the registered engineer who is to be responsible for the final deliverables.
other regions All final engineering documents are to bear the Engineer’s name, signature, date, and
with seal by a fully licenced and state registered professional Engineer.
professional
engineer
status
6.3.1 - 9 For UK, EIRE and South Africa specific requirements, see requirements for design Requirement: ERQ13 Requirements
For UK, EIRE for design
and South
Africa specific
requirements
see
requirements
for design
6.3.1 - 10 The Project Principal shall propose the Engineer for the work and seek approval for Requirement: Requirements - DO -
Site supervision the appointment from their Unit General Manager. Plant the project
and contract The Engineer must ensure that the construction supervision plan is implemented. Requirement: ERQ15.3 Appointment
management of Engineer for the works

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 6 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.1 – 11 The Engineer is responsible for implementing the health, safety and security
Engineer requirements, including:
responsibilities • Fire and emergency arrangements
• Displaying statutory notices
• Testing of electrical appliances and equipment
• Training and competence
• Office conditions including display screen equipment
• First-aid arrangements
6.3.1 – 12 Where the contractor provides these arrangements, the Engineer must satisfy Form: MMF114 Site safety review
Engineer themselves that they are in place and record them in the site safety review Form 114.
responsibilities
– site safety
review
6.3.1 – 13 On projects where Mott MacDonald are the Engineer, the Project Manager and project Link: UN Sustainability Development
Sustainability team members must eliminate, or at least minimise and mitigate, any adverse Goals
and environmental impacts when developing the scope of work.
environmental The Project Manager should work with the client to realise sustainability opportunities Information: Signposts to
management and optimise compliance with the UN Sustainability Development Goals. sustainability
They must co-operate with, and seek advice from, the Project Sustainability Co-
ordinator (PSC) as necessary.
6.3.1 – 14 The engineer should ensure that all environmental incidents, near misses and positive Mandatory reporting: Major
Notification of interventions are reported using the Environmental Incident Portal on ServiceNow incidents and emergencies standing
environmental instructions
accidents and
incidents Link: Environmental incident portal

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 7 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.1 – 15 Where projects require procurement on behalf of the client, the Project Principal must
Clients approve the procurement strategy statement and the production and issue of the
procurement prequalification questionnaires, tender, specifications and contract documents as
strategy appropriate.
The Project Principal shall ask those involved in the procurement process to review
whether they have a conflict of interest if they are to be involved. Within this,
colleagues are to review any shareholding they may have in the companies (and
parent companies) on the prospective tender lists are to declare holdings to both the Form: MMF052 Procurement strategy
Project Principal and client prior to tender documents being issued. All possible statement
conflicts of interest are to be disclosed and discussed with the client as soon as they
are identified.
They must confirm the procurement process in procurement strategy statement form
MMF 052, which must identify the type and number of contracts and be approved by
the client.
Record copies of documents issued, plus any supporting documentation, must be filed
in the project filing system. Superseded copies must be stamped but do not have to
be archived, unless this is a project requirement.
6.3.1 - 16 Where the Group is responsible for auditing other organisations, the Project Manager Requirements: Manage the
Auditing third must agree the date and time of the audit with the organisation being audited. operation (1.4.4.6 Implement audit
parties The purpose and standards against which the audit is to be undertaken are to be and review requirements)
shared with the organisation.
The lead auditor must contact the auditee to confirm the date of the audit, duration
and required resource.
The findings of the audit are to be agreed with the organisation in the close out
meeting.
The audit report is to be published in accordance with the contract within one week of
the audit.
6.3.1 - 17 The audit must be conducted in accordance with ISO 19011 - Guidelines for auditing Form: MMF037 Corrective action
Auditing third management systems. The audit report must record the result of the audit, including request
parties - observations, nonconformities and corrective action requests (or similar), along with
standard follow-up actions

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 8 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.1 - 18 The Project Manager must review and approve all incoming information for use on the
Management of project, which must be recorded either on the documents and/ or in the incoming
incoming information register.
information Where incoming information is in digital format the relevant Practice Leader should be
consulted to confirm that the approach to checking the information is adequate.
6.3.1 - 19 The minimum information management requirements for incoming information are to
Management of ensure:
incoming • We record what was received from whom and when, including:
information – o Date stamping incoming hardcopy documents Form: MMF017 Incoming drawing
information
management o Recording all incoming documents (reports, drawings, calculations and document register
information presentations etc) using MMF017 – Incoming information register, or a
requirements system which records the same information
o Saving all incoming information in the document management system
• We identify how we are going to track required actions and their completion
• We consider the suitability of received material before its inclusion within the
Group’s work.
• We recognise who owns the intellectual property and copy wright of the
information and whether we have a right or licence to build on this.
• We recognise any confidentiality obligations associated with the information
and how these are going to be complied with
• We assess whether the information contains personal information and how it
shall be protected whilst being held by the Group or any sub-consultants
involved in the project
6.3.1 - 20 Any sensitive incoming information must be forwarded to the Divisional Manager for
Management of review and further action, if required.
sensitive
incoming
information

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 9 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.1 - 21 The minimum information management requirements for outgoing information are that
Management of information is:
outgoing • Prepared in the format described in special commitments (disclaimers),
information including company details in an email signature or similar
• Given a reference which comprises the initials of the Project
Principal/writer/project number
• Signed by a member of staff authorised to sign correspondence, as identified in
the project plan of work
• Placed in the relevant location of the document management system
• Sent and distributed internally, as specified in the project plan of work
6.3.1 - 22 Information that affects the scope of work, programme, fees or may have a commercial Form: MMF010 Record of telephone
Management of impact on the project shall be recorded and retained with the project information. or online conversation
information – The Group’s senior representative at a meeting shall confirm before it starts whether Form: MMF011 Record of meeting
meetings and a full minute of the meeting is required or whether only the actions arising will be Guidance: Templafy – Record of
telephone recorded, they will also confirm who is to make the record. meeting
discussions The Project Manager or senior Group representative at project meetings must arrange
for notes to be taken during the meeting and recorded using the project OneNote
notebook or the MMF011 Record of meeting.
Telephone conversations and internal discussions resulting in an exchange of key
project information must be recorded using the project OneNote notebook, the
MMF010 Record of telephone or online conversation or the MMF011 Record of
meeting, unless confirmed by an email or letter.
Where minutes and/ or records of conversations/ discussions are to be circulated to
external parties, they should be recorded using a Templafy Word document.
Minutes and records of conversations/ discussions must be completed as soon as
possible after the meeting or discussion, saved to the project file and promptly
distributed to attendees and others as required.
If action is required in advance of receipt of formal minutes, the meeting record must
be saved to the relevant project folder and a link circulated as required.
The Project Manager must ensure the minutes from any previous meetings are
agreed and the status of actions recorded.

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 10 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
The Project Manager must review formal minutes from externally hosted meetings
and, in event of a disagreement, must either raise the issue at the next meeting or
write to the originator of the minutes.
6.3.2 6.3.2 - 1 The Project Manager must brief the project team on:
Develop the Project • The control of incoming and outgoing information
information Manager • How and where project information is to be stored (e.g. document management
responsibilities system)
• The format to be used for reports, calculations and drawings
• Revision control
• Record of meetings
• Check and approval requirements for all deliverables generated during the
project prior to sharing and/or publishing the information.
• No deliverables can be shared or published without check and approval to
confirm suitability for the intended purpose (this activity may be also known as
verify/verification in some standards)
6.3.2 - 2 Project team members must:
Project team • The resources committed to the project understand the relevant aspects of the
member scope of work plan and the quality plan as it applies to the information they are
responsibilities to develop
• Where the developed information is to be shared with others, the requirements
related to the interface will be considered at the outset of developing the
information
• Read and understand the technology plan
• Apply all the requirements for information management
• Report any problems with software to the divisional program representative,
who must record the details in the approved software list
• Produce deliverables which are complete and correct
• Self-check each deliverable before sending to the checker

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 11 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
• Provide the checker and approver with enough notice of when check and
approval will be required
• Implement any changes identified by the checker before issue
• Retain all check copies
6.3.2 – 3 Reports must be drafted using a report template from Templafy. The first issue must
Preparation of be ‘A’, unless specified in the project plan of work.
reports The report will be stored in accordance with the project’s information management
plan throughout its development.
The document must include:
• A unique document reference on all pages, comprising the project number/
Requirements: ERQ15 Special
report number/ revision letter
commitments
• The company name, address and appropriate Group disclaimer, as specified in
requirements ERQ15 Special commitments
• A list of contents, including all attachments
6.3.2 - 4 Drawings must be drafted using the Group’s standard frame and title block, in Manual: CAD Manual
Preparation of accordance with the Group CAD manual, unless specified in the project plan of work.
drawings The report will be stored in accordance with the project’s information management
plan throughout its development.
The drawing must include:
• A unique drawing number, comprising project number/unique number/revision
letter
• The appropriate Group disclaimer

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 12 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.2 - 5 Calculations must be prepared using a standard calculation sheet, MMF021, unless Form: MMF021 Calculation sheet
Preparation of specified in the project plan of work. For each set of calculations, we must state:
calculations • The specific purpose of each set or subset of calculations
• Assumptions
• Parameters and formulae
• Output
• Applicable codes and standards
• Software used
• That they have been checked and approved
o The checker must not be the same as the originator
Calculations must be prepared, not only to satisfy the designer of the suitability of the
design, but also as a permanent record of the design decisions and criteria used
leading to the design output.
6.3.2 - 6 The content and structure of calculations must be enough to allow a technically
Preparation of qualified person to follow the process for checking, review and future reference.
calculations - This must include calculations in BIM models, specialist transport assignment and
content and forecasting models, etc.
structure
6.3.2 - 7 Appropriate software protocols must be established that satisfy the project’s or client’s
Preparation of needs for storage of data files during their production and subsequent archival.
calculations – ProjectWise or the SharePoint project site (or an appropriate document management
software system as specified in the project plan of work) must be used.
protocols
6.3.2 - 8 The features and status of every set of calculations must be recorded using MMF019 Form: MMF019 Calculation cover
Preparation of Calculation cover sheet. All calculations must be recorded using MMF018 Calculation sheet
calculations – index. Form: MMF018 Calculation index
cover sheets

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 13 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.2 - 9 Calculations produced using simple spreadsheets must be saved to the relevant
Saving project calculation folder.
calculations Calculations produced using specialist applications, including software or
spreadsheets with links to other spreadsheets or external data, must be saved to the
document management system.
6.3.2 – 10 During the development of project information, the Project Principal must consider the eForm: E2905 Project review or
Need for need for a technical review. Connect Business eForm
technical If a review is required, the Project Principal must nominate and brief a project reviewer, Form: MMF036 Project review (excel)
reviews identifying any project-specific requirements and any additional questions (based on
MMF036 Project review – detailed
MMF036 Project review questionnaire) and recording the result on the Project review
questions (word)
eForm.
Form: MMF037 Corrective action
The reviewer must be a subject matter expert in the technical area(s) under review.
request
6.3.3 Check 6.3.3 -1 The Project Manager is responsible for planning and implementation of check and
the Check approval activities in line with the strategy and approach developed in the project plan
information responsibilities of work.
The Project Manager is responsible for:
• Ensuring that selected checkers have both the appropriate technical
competence and delivery experience to be able to assess the accuracy of the
information presented for checking.
• Where multiple competences are required, the Project Manager shall select
additional checkers.
• Ensuring the originator and checker are different people unless the information
is developed as part of an expert witness statement.
• Identification of any inter-disciplinary check and approval requirements
• Applying any additional practice specific requirements for check and approval
• Identification and implementation of project digital workflows for check and
approval (for example SharePoint or ProjectWise)
The checker is responsible for studying every part of the deliverable and confirming
that the detail is correct, or not. If not, feedback will be provided to the originator for
correction. The check should be completed with supporting input data.

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 14 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.3 – 2 The checker must record the scope and date of check and provide a record of Form: MMF154 Comment and
Check – record checking via a check copy, Word tracked changes document or similar. resolution record
requirements • If satisfactory, the originator and checker must sign under their names on the
issue and revision record sheet on the document for issue
• The approver will assess the document and records for checking and, if
satisfied, must sign the report as approved
• Scan the original with OCR-enabled scanner or appropriate software and save
a record copy in the relevant project folder
6.3.3 – 3 The Project Manager must confirm that input data has been checked and that output Form: MMF019 Calculation cover
Check – checking has been carried out appropriately, by approving the MMF019 Calculations sheet
calculations cover sheet.

6.3.3 – 4 The project document management system check, and approval workflow must be
Use of used to record the checking and approval process.
document The signatures of the originator, checker and approver are not required if the check
management and approval workflow is used. If these are required, then a scanned issue and
system – check revision record sheet will need to be included
requirements
6.3.4 6.3.4 - 1 Information must be approved in line with the approach defined in the project plan of
Approve the Approver work
information responsibilities The approver is responsible for confirming that the originator and checker had the
appropriate competence to develop and check the information.
The approver must ensure that check and approval process has been completed in
line with the defined requirements.
The Project Manager shall ensure that all required project documentation has the
appropriate approvals throughout the lifetime of the project.
Internal project documents also require approval. In this instance the Project Principal
completes both check and approve.

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 15 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.5 Share 6.3.5 – 1 The Project Manager is responsible for ensuring that information is presented in the
the Project correct format and is suitable to enable coordination checks between the various
information Manager disciplines to be carried out.
responsibilities - The Project Manager must ensure that the information is complete, checked and
share approved before sharing and publication in line with PPW requirements.
6.3.5 – 2 The Project Principal must consider the need for a technical review before sharing the eForm: E2905 Project review
Project Principal information. or Connect Business eForm
responsibilities- If a review is required, the Project Principal must nominate and brief a project reviewer, Form: MMF036 Project review (excel)
need for identifying any project-specific requirements and any additional questions (based on
MMF036 Project review – detailed
technical review MMF036 Project review) and recording the result on the project review eForm.
questions (word)
The reviewer must be a subject matter expert in the technical area(s) under review.
Form: MMF037 Corrective action
request
6.3.6 6.3.6 – 1 Before publishing information, the Project Principal must be satisfied that:
Publish the Publish • All originator(s) and checker(s) were competent and understood and carried
information responsibilities out their duties diligently
• All information has been prepared and checked (and is in the correct format) as
specified in the project plan of work
• National and international codes and standards, plus regulatory requirements
have been met
• Environmental issues have been addressed adequately
• Client requirements have been met
6.3.6 – 2 The project must retain a record of all information published, providing details of whom Form: MMF016 Drawing/ document
Records of it has been sent to, what the information is, its status and version reference and a register and transmittal (word)
published record copy. All outgoing drawings, other than those issued through the Group’s MMF016e Drawing document register
information common data environment, must be issued with a transmittal sheet, irrespective of and transmittal (excel)
whether a letter is issued.
Verified record copies of all documents, drawings and deliverables must be retained
as described in the PPW.
All information must be published using MMF016 Drawing/ document register and
transmittal, or on a system that records the same information.

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 16 of 17
 Requirement

STEP Requirement Supporting guidance/ best

Requirement
activity reference practice
6.3.6 – 3 Incomplete information (for example drawings produced during design and
Incomplete development) must be marked as such, e.g. preliminary or for information only.
information
6.3.6 – 4 Emails must include the address and contact details of sender’s office and must
Outgoing include the following information (in the signature):
information This message is from Mott MacDonald Limited, registered in England number
1243967. Registered office: 8-10 Sydenham Road, Croydon, CR0 2EE, United
Kingdom.
6.3.7 6.3.7 – 1 The Project Manager must obtain a client acceptance statement for the published
Confirm Client information. The nature of the statement must reflect the complexity of the project and
client acceptance information, so for a simple project, this may just be an email confirming acceptance
acceptance statement
6.3.7 – 2 The Project Manager must record the acceptance statement and allocate any follow-
Recording client on actions resulting from the published information.
acceptance

Requirement – DO – Execute the project

Document number 2939 [Version 13]
Version date 23/02/2022 Page 17 of 17