I was scouring the internet (as I do) for interesting articles on what 'not to do' in Microsoft Project. that same day, I then spent several hours reviewing a program from a sub-contractor which had several links between summary activities.

Here's an interesting article to explain why it shouldn't happen!

So, thou shalt not use summary logic in Microsoft Project because:

  1. It is lazy planning
  2. The logic becomes difficult to follow
  3. The summary logic can artificially extend the plan
  4. The detail underneath the summary drives the summary process at the parent level (ie, dates, duration, float/slack)
  5. more importantly, it can lead to 'bench time' and a reduction in planned resource optimisaion

Other recent articles

Full blog index
December 01, 2021
December 01, 2021

Find out how GBA Projects can help your project perform.

Contact us.


  • 01-santos-logo.jpg
  • 02-bhp-logo-new.jpg
  • 03-hansen-logo.jpg
  • 04-sydney-water.jpg
  • 05-beach-energy.jpg
  • 05-kbr-logo.jpg
  • 06-aurecon-logo.jpg
  • 08-riot-tinto-logo.jpg
  • 09-sa-govt-logo.jpg
  • 10-spotless-logo.jpg
  • 11-built-environs-logo.jpg
  • 12-dyno-logo.jpg
  • 13-sa-power-logo.jpg
  • 14-incitec-logo.jpg
  • 15-electranet-logo.jpg