Project Controls International

FPSO and Topsides

West African Costs

Basis of Estimate

(white papers)


         Project Knowledge = Success


Que$tor Estimates

(white papers)    |   contact:   |   check me out at




- Construction Unit Costs

- FPSO and Topside Costs

- Offshore Fabrication Costs

- Welding Consumables


B.Dev./ Contracts

- Contracts: Quantum Meruit

- Guide to Business Acquisition

- Proposal Development

- Relationship Building

- Video: LATTE (Starbucks)

Mind Maps

- Estimating

- Planning

- Schedule Development

- Schedule Maintenance

- Risk Management



- Constructability

- Document Management

- Estimating Process

- Project Claims and COs

- Project Controls

- Project Execution Plan

- Project Execution Strategy

- Contract Synopsis


- Basis of Schedule

- Number of Schedule Activities

- MS Project vs. Primavera P6

- Planning and Scheduling

- Schedule Extension of  Time

- Typical Primavera P6 Settings

- Updating a P6 Schedule

- Video: Liquidated Damages

- Why Your Project will be Late



- Construction Estimating

- Estimating Course

- Planning and Scheduling

White Papers

- Basis of Estimate

- Communicating Effectively

- Construction Escalation

- Earned Value Management

- Estimating Productivity

- Evaluating Change Orders

- International Multipliers

- Nigerian Content Development

- Project Execution Plan

- Project Risk Contingency

- Project Variables

- Que$tor Estimates

- Risk Analysis Spreadsheet

- Risk Breakdown Structure

- Risk Management

- Spreadsheets vs Databases

- Starting the Project

- Why Project Controls

- Work Breakdown Structure

Interesting Stuff

- Programmable Robot

- Pipe Dimensions and Weights

- Concurrent Database

- LibreOffice Base vs. MS Access

- SharePoint Database

- SAP vs Oracle ERP

- Free Unit Converter

- Motivational Food for Thought

- Passionate about Meetings?

- Video: Project Controls



Contact Us

- Bio

- PMC Consultancy

What Makes for a Good Project Execution Plan?


The project execution plan (PEP) is an important document that describes what the project is and outlines the plan on how it is to be successfully achieved.

A typical project execution plan layout would be as follows:

-          Introduction

-          Project Description

-          Proposed Construction Methodology

-          Resource Plan

-          Risk Management Assessment

-          Alternates (if applicable)

-          Technical or Other Considerations (if applicable)

-          Appendices


While preparing the project execution plan the focus should be on a simple, cohesive, well thought out “story telling”. It is very well to narrate the sequence of activities necessary to complete the project, but by itself it does in no way demonstrate to the reader that these activities are achievable in terms of cost, schedule and quality as narrated. This is where the all important “How”, “When”, “Where” and Whys” comes into play: e.g. How is the activity going to be performed and with what resources? When and will this clash with other resource requirements elsewhere? Why in this manner and not in a different way? etc. The intent of “story telling” is to clearly and simply communicate to the reader, weather a Client or the assigned Project Manager, with no necessary prior background or knowledge to the project how the project is planned to be executed as well as clearly explaining that it can be achieved as outlined.


Below listing includes common complaints by proposal evaluators:


-          Lots of "What" but not much “How” - where's the beef?

-          Customer name not mentioned early on in the proposal.

-          Proposal was written by committee - the story doesn’t hang together.

-          Be very, very careful with boilerplate - too many errors in which prior proposal usage was not changed to the current proposal.

-          Lack of discrimination among all other submittals - provide a way for customer to see that your solution is different and better than the standard solution.


Additionally while it should have to go without saying, it is often the case that proposals are very poorly put together and presented, with errors (including spelling) throughout the document. Even if the actual content of the PEP is carefully thought out and well written, a poor presentation will discredit much of this work.


Conclusion: The Project Execution Plan is an important document of use to various parties, whether they be the Client’s proposal evaluator, Estimator, Planner or the Project Manager. Typically PEPs will cover with sufficient detail what activities need to be performed to execute the project, but will often leave the reader’s essential question of “how” unanswered due to a lack of informative “story telling”.

Project Execution Plan


The importance of good communication. Or telepathy as the alternate!

An “armchair scheduler” or frontline messenger?

Why Project Controls

Selected Articles

A necessary document to support and explain the cost estimate: How did you arrive at that number?

Basis of Estimate

Love them or hate them. How to conduct successful productive meetings.

Funny, but true. Video on the functions of Project Controls.


Settings do matter: pick the wrong settings and your schedule’s output will be meaningless.

What the text books didn’t tell you
Primavera P6 Settings
Video - Project Controls

Selected Articles

Tips on Scheduling

50% Science, 50% Art, 100% Communication

Why Project Controls?

Email: Friend/colleague?subject=Interesting link - Project Execution Plan&body=Interesting link from Project Controls International: