Hi Stephen
Rafael has summed up the case very precisely - pitch yourtext to your audience.
If you are a contractor trying to bamboozle an employer by an overwhelming volume of data and technical gobble de gook then employ a delay analyst who charges by the volume of printed words.
Then you will receive archived texts and paragraphs copy - pasted from earlier submissions for similar cases - some of which may be relevant but do not need to be re-stated ad infinitum.
When a client asks me to review such a submission I can usually state a reasoned case for rejection in 2 or 3 pages - in one case 3 paragraphs.
If I am presenting a reasoned narrative to a tribunal who may not be technically qualified I assume they know nothing about the subject - a sort of Jack and Jill approach to claims - or Cat in the Hat for our US cousins.
They will not know - for instance - that the pre formed legs of an off shore drilling rig is called a "Jacket" - neither did I until I asked what? during an arbitration breifing last week.
In complex cases use animations - powerpoint is good to show what was planned v what happened - if the money is there use 3d cad.
In every case tell the story in a single "book" per event - stating:
Cause: What happened?
Effect: What was the result!
Compare: How the effect compares with the As Bult data.
Then what: How did the Contractor deal with the problem?
In every case I embed snapshots of the programme stages or specific text extracts at each stage so the reader does not have to go scrabbling through multi appendicies to find the reference.
The skill of a delay analysts does not include the narrative phase - that follows instinctively - what is important is the ability to cut to the essence of the problem and focus on the real cause of the delay.
This only comes from a thourough analysis of the data and a knowledge of the construction process - plus talking to the charge hands if they are still there.
Best regards
Mike Testro