Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Gate Meetings and Project Status Reports

5 replies [Last post]
PM Hut
User offline. Last seen 14 years 39 weeks ago. Offline
Joined: 30 Jan 2008
Posts: 35
Groups: None
Hi all,

I have recently published an excellent (and long) article on gate meetings, the article is quite comprehensive and can definitely act as a reference.

The article first defines Gate Meetings (what they are, why and when they need to be held, who should attend), it then explains the list of things that usually get done during a Gate Meeting. The article then explains how you should run the Gate Meeting, how decisions are made, and who are the decision makers. Again, this article is an excellent reference on the subject. Your comments on the article are always welcome.

I also published another article about the project status report, the article defines the components of project status as well as the key data to be included. The article is fairly comprehensive and a template (project status report) can be easily drawn based on this article.

Thanks and Enjoy!

Replies

PM Hut
User offline. Last seen 14 years 39 weeks ago. Offline
Joined: 30 Jan 2008
Posts: 35
Groups: None
Thank You each & every one for your reply!

Samer your reply is a nice addition to the article. Would you be interested in posting this information as a comment on the Project Status Report article? This will certainly be very helpful to fellow Project Managers.

Carmen I can see a short article on the Gate Meetings specific to your industry. Would you care to write one (I will definitely publish it if you do)? In case you decide on doing so, then please contact me (through the Contact Us form on PM Hut) and we’ll take it from there.

Now I have chosen a very popular and light article on PM Hut for your reading pleasure: Do You Speak Project.
Carmen Arape
User offline. Last seen 7 years 2 days ago. Offline
Joined: 26 Jun 2004
Posts: 292
PM Hut

Reading your article "Conducting Successful gate meetings" , gave me the opportunity to carefully review the various Gate meetings that we execute in house.

Being involved in Oil&Gas, Chemicals projects the Gate meetings have a different purpose, importance and time execution.

The most important gate meetings are executed at early project stage. The two main aims are: to ensure the quality (technical) of END deliverables and to identify/mitigate risks.

Early project stages for us are: conceptual and feed or basic engineering. During these phases we identify the key deliverables and perform the meetings in order to identify End quality problems, which usually have to be repaired with a lot of effort in the next phase.

During these phases the gate meeting attendees are external quality reviewers to the project. Some key project team members are invited, but the review will be lead by Company expert reviewers (normally senior specialist).

The most important gate meeting is the one executed at the end of the project phase which is opening the door for the bulk execution.

Cheers,




Anoon Iimos
User offline. Last seen 2 years 31 weeks ago. Offline
Joined: 22 Sep 2006
Posts: 1422
For Project Status Report(s), I supposed the number one rule to follow is to tell the truth (facts), supported by mathematically calculated figures.
Samer Zawaydeh
User offline. Last seen 5 years 24 weeks ago. Offline
Joined: 3 Aug 2008
Posts: 1664
Dear Sir/ Madam (PM Hut),

Thank you for your article about the Project Status report. It is directed toward creating a brief summary of the project. This is what the Executive Summary in the Monthly report should contain.

Please allow me to add, that if the Planner is trying to create a Monthly Status report, then it should be more comprehensive.

These segments are a must in each Monthly status report:

Scope:
I. Engineering (Material and Shop Drawings)
II. Procurement
III. Construction
IV. Commissioning and Testing

Cost:
I. Invoicing
II. Extra Work
III. Variations

Time:
I. Approved schedule with Critical Path
II. Actual progress with updated Critical Path
III. Delays and reasons for delays

The status report should address each issue above in addition to list all the following:

1. Minutes of Meeting
2. The following logs:
a. Correspondence sent and received
b. Non Conformance Recrods Issued
c. Material submittals status Log
d. Shop Drawings status Log
e. Procurement Log
f. Invoicing, insurance and guaranttees Summary
g. Request for Information
h. Confirmation of Verbal Instructions
i. Daily reports
3. Manpower summary
4. Outstanding Issue and Recommendations

Thank you again for your excellent article.

Samer
Arnold Puy
User offline. Last seen 9 years 28 weeks ago. Offline
Joined: 25 Apr 2007
Posts: 1147
Hello PM Hut,

Your Articles are very useful and interesting to all Planners. I will try to give a copy to my Project Manager and let him read about it.

Thank you & More Power..


Arnold