Answer Structure

Most requirements are for reports, briefing notes or letters/emails. Sometimes there is a requirement for slides.

For the first three, it would be normal to have heading like To/from/date/subject and to start with a very brief introduction and to end with a conclusion/recommendation – depending on the requirements. Slides are simpler: direct to the point and usually expanded in notes.

There are no simple guides for ‘numbers of lines per mark’. Some people write 20 lines of rubbish; others two lines full of insight. Better to calculate how much time you have for each part of the requirements (many people suggest something like 0.5 – 1 hour for reading, thinking and planning and 3.5 – 3 hours in which to write your answers). When you start writing fill the time available, but then leave the question. It is better to have, for example, four points fully explained than 10 bullet points which say little. Think that you are having to explain your points to a relatively unskilled person as that will help you reach the level of detail needed.

You should try to avoid explaining models/frameworks/theories: instead use them to advance your answer towards a reasonable conclusion

It it certainly important to try to identify and detail fully with the most important issues. Peripheral matters can be dealt with more quickly. Don’t feel you have to deal equally with every part if a model. Eg if using PESTEL probably only 2 or 3 matters will be of key importance and there might be nothing to say about the others.

Focus on the question data not the models.