<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Project Perspectives &#187; Writing it up</title>
	<atom:link href="http://projectperspectives.co.uk/category/writing-it-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://projectperspectives.co.uk</link>
	<description></description>
	<lastBuildDate>Mon, 23 Apr 2012 17:40:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Six ways to ease report writing</title>
		<link>http://projectperspectives.co.uk/2008/11/six-ways-to-ease-report-writing/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=six-ways-to-ease-report-writing</link>
		<comments>http://projectperspectives.co.uk/2008/11/six-ways-to-ease-report-writing/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 17:23:41 +0000</pubDate>
		<dc:creator>May Johnstone</dc:creator>
				<category><![CDATA[Writing it up]]></category>

		<guid isPermaLink="false">http://mayjohnstone.co.uk/?p=120</guid>
		<description><![CDATA[It&#8217;s so easy to put off the task of writing up that report! Tempting to divert to an easier job, find something that&#8217;s more urgent, or a myriad of other excuses. Here are six tried and tested tips to make report writing more approachable. They will help you get started quickly. 1.    Decide on your <a href='http://projectperspectives.co.uk/2008/11/six-ways-to-ease-report-writing/' class='excerpt-more'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p><strong><a href="http://www.projectperspectives.co.uk/wp-content/uploads/2012/03/women-using-computer-150x150.jpg"><img class="alignleft size-full wp-image-534" title="women-using-computer-150x150" src="http://www.projectperspectives.co.uk/wp-content/uploads/2012/03/women-using-computer-150x150.jpg" alt="" width="150" height="150" /></a>It&#8217;s so easy to put off the task of writing up that report!</strong></p>
<p>Tempting to divert to an easier job, find something that&#8217;s more urgent, or a myriad of other excuses.</p>
<p>Here are six tried and tested tips to make report writing more approachable.</p>
<p>They will help you get started quickly.<span id="more-120"></span></p>
<h4>1.    Decide on your structure</h4>
<p>Sorting out the structure first means you’ll know where everything has to go. It’s rather like planning your journey in advance, so you don’t end up taking detours or ending up in dead ends. Here’s my suggestion for a structure, which you can modify to suit:</p>
<ol>
<li>Title page</li>
<li>Contents</li>
<li>Introduction</li>
<li>Executive summary</li>
<li>Methods</li>
<li>Results</li>
<li>Conclusions &amp; recommendations</li>
<li>Appendices</li>
</ol>
<h4>2.    But don’t write in that order!</h4>
<p>It would be difficult and daunting to write a report from beginning to end. I suggest you set up the headings for the different sections of your report, and then get started on a section which feels easy to you.</p>
<ul>
<li><strong>You might start with:</strong></li>
</ul>
<p style="padding-left: 30px;">The Title page and Contents page.<br />
Introduction, Methods, and any Appendices relating to the Introduction or Method</p>
<ul>
<li><strong>Then move on to:</strong></li>
</ul>
<p style="padding-left: 30px;">Results, any Appendices for Results.</p>
<p style="padding-left: 30px;">If you have a lot of detailed results, which warrant an Appendix, you’ll probably need to write up the Appendix first, so you can summarise it into your Results section.</p>
<ul>
<li><strong>And write these parts last:</strong></li>
</ul>
<p style="padding-left: 30px;">Conclusions and recommendations, Executive Summary</p>
<h4>3.    Structure each section before you start</h4>
<p>Just as you have structured the whole report, it will help you to write the main headings within each section. For example a Results section might include:</p>
<ul>
<li>Trends from desk research</li>
<li>Employers’ views</li>
<li>Trainees’ views</li>
<li>Stakeholder views’</li>
<li>Summary of results</li>
</ul>
<h4>4.     Ask for help</h4>
<p>If you find it difficult to structure your report, ask a colleague to help. You don’t necessarily need someone familiar with your project – explaining things from scratch will give you insight into a reader’s perspective.</p>
<h4>5.    Start writing anywhere within a secton</h4>
<p>It can be hard to write the first paragraph of a section, partly because it’s an overview of a section which you haven’t written yet! Word processing makes it easy to start anywhere. I usually start with a part I can write easily. Then I add bits in, moving them around as necessary.</p>
<h4>6.    Use technology</h4>
<p>Computer software offers many ways to make writing easier. Here are my favourites:</p>
<ul>
<li>Keep a backup of your report</li>
<li>When you have added substantially to your draft, save your report as another version, so you end up with versions 1.1, 1.2, 1.3 etc. This means you can easily go back to earlier drafts if necessary.</li>
<li>Use styles for different levels headings, so they are consistent.</li>
<li>Use Word’s facility to automatically generate, and update, your Contents page (Insert/Reference/Index and Tables).</li>
<li>Use Word’s facility for Footnotes, to add short pieces of information which interrupts the flow of the text, at the bottom of the page (Insert / reference / Footnote)</li>
<li>Use Word’s ‘Track changes’ facility if you want to circulate your draft and be able to see each other&#8217;s changes (Tools / Track  Changes)</li>
<li>Use Word’s Help menu to learn to use any of the above features.</li>
</ul>
<p><strong>The bottom line: </strong>Report writing doesn’t need to be daunting. Once you have a structure, the trick is to start with a part of the report which feels easy to you, and build out from there. A range of software tools will help you.</p>
<address>© May Johnstone, 2009, <a href="http://www.projectperspectives.co.uk/">Project Perspectives.co.uk</a>. Please feel free to circulate this article provided it is used in its entirety, including this acknowledgement.</address>
]]></content:encoded>
			<wfw:commentRss>http://projectperspectives.co.uk/2008/11/six-ways-to-ease-report-writing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A foolproof structure for your research report</title>
		<link>http://projectperspectives.co.uk/2008/10/a-foolproof-structure-for-your-research-report/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=a-foolproof-structure-for-your-research-report</link>
		<comments>http://projectperspectives.co.uk/2008/10/a-foolproof-structure-for-your-research-report/#comments</comments>
		<pubDate>Wed, 29 Oct 2008 17:02:15 +0000</pubDate>
		<dc:creator>May Johnstone</dc:creator>
				<category><![CDATA[Writing it up]]></category>

		<guid isPermaLink="false">http://mayjohnstone.co.uk/?p=115</guid>
		<description><![CDATA[You’ve collected and analysed the research information your project needs, now the prospect of writing it up feels a bit daunting. The good news is there’s no need to reinvent the wheel; there are plenty of good reports to draw ideas from. To save your time and energy, here’s a tried and tested template that <a href='http://projectperspectives.co.uk/2008/10/a-foolproof-structure-for-your-research-report/' class='excerpt-more'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p><strong><a href="http://www.projectperspectives.co.uk/wp-content/uploads/2012/03/blank-report-150x150.jpg"><img class="alignleft size-full wp-image-509" title="blank-report-150x150" src="http://www.projectperspectives.co.uk/wp-content/uploads/2012/03/blank-report-150x150.jpg" alt="" width="150" height="150" /></a>You’ve collected and analysed the research information your project needs, now the prospect of writing it up feels a bit daunting.</strong></p>
<p class="MsoNormal">The good news is there’s no need to reinvent the wheel; there are plenty of good reports to draw ideas from.</p>
<p class="MsoNormal">To save your time and energy, here’s a tried and tested template that works!<span id="more-115"></span></p>
<h3 class="MsoNormal"><strong>Contents for a project research report</strong></h3>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>1.</span></strong><!--[endif]--><strong>Title page</strong></h4>
<p class="MsoNormal">This should include:</p>
<ul>
<li><!--[if !supportLists]--><!--[endif]-->title of the research</li>
<li><!--[if !supportLists]--><!--[endif]-->date</li>
<li><!--[if !supportLists]-->who commissioned the research</li>
<li><!--[if !supportLists]-->author(s)</li>
</ul>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>2.</span></strong><!--[endif]--><strong>Contents</strong></h4>
<p class="MsoNormal">This is a list of all the sections of your report. You may wish to include sub-sections for a long report.</p>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>3.</span></strong><!--[endif]--><strong>Introduction</strong></h4>
<p class="MsoNormal">The aim of your Introduction is to introduce your project, and the research, to someone who knows nothing about your project. It is likely to include:</p>
<ul>
<li><!--[if !supportLists]-->background to your project: its aims, partners, activities to date etc</li>
<li><!--[if !supportLists]-->broad reason(s) for the research</li>
<li><!--[if !supportLists]-->the research brief</li>
</ul>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>4.</span></strong><!--[endif]--><strong>Executive Summary</strong></h4>
<p class="MsoNormal">The Executive Summary is a very concise summary of your whole report, usually between 1-4 sides, depending on the extent of your research. It is usually the last section of your report to be written.</p>
<p class="MsoNormal">Some people will only ever read this part of your report; it may be circulated as a separate document. It therefore needs to include a brief introduction setting the context, and a very brief description of research aims and methods, and then the key results and conclusions. Recommendations are usually given in full, since they are often the main focus of interest for readers.</p>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>5.</span></strong><!--[endif]--><strong>Methods</strong></h4>
<p class="MsoNormal">In this section you describe the methods you used to collect data, including desk research, surveys and consultations. If relevant, include quotas set, samples achieved, number of people consulted. If there is extensive detail, consider separating it into an Appendix.</p>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>6.</span></strong><!--[endif]--><strong>Results</strong></h4>
<p class="MsoNormal">For a small research project, you include a summary of all your results here. For a larger project, you would separate the full results into an Appendix, with a summary, or series of summaries, in this section.</p>
<p class="MsoNormal">Where possible summarise your results as lists or tables, perhaps enriching with some quotes from respondents.</p>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>7.</span></strong><!--[endif]--><strong>Conclusions and recommendations</strong></h4>
<p class="MsoNormal">Your conclusions summarise the main points emerging from your results, in relation to the research brief.</p>
<p class="MsoNormal">Your recommendations specify the recommended actions, which emerge from your research, justifying why they are being made. They are usually numbered, and made to stand out using bold or a different font.</p>
<h4 class="MsoNormal" style="margin-left: 17.85pt; text-indent: -17.85pt;"><!--[if !supportLists]--><strong><span>8.</span></strong><!--[endif]--><strong>Appendices</strong></h4>
<p class="MsoNormal">Appendices are used to ‘house’ detailed information, which only some people will need to read. This often includes: detailed methodology, and detailed results.</p>
<p class="MsoNormal">The rest of the report should make sense to a reader without reading the Appendices. The main part of your report may well end up being circulated without them.</p>
<h4 class="MsoNormal"><strong>But don’t write it in order!</strong></h4>
<p class="MsoNormal">While the above list defines your content, the order in which you write the sections of your report will probably be quite different – it’s often easiest to start in the middle!</p>
<h4 class="MsoNormal"><strong>House style</strong></h4>
<p class="MsoNormal">Some organisations have a house style for reports, if that’s the case, check it out as it may require some variations to the structure suggested here.</p>
<p class="MsoNormal"><strong>The bottom line: </strong>Outline the structure of your report, before you start writing, and it will be straightforward to slot everything in the right to place, to produce a digestible report.</p>
<address>© May Johnstone, 2009, <a href="http://www.projectperspectives.co.uk/">Project Perspectives.co.uk</a>. Please feel free to circulate this article provided it is used in its entirety, including this acknowledgement.</address>
]]></content:encoded>
			<wfw:commentRss>http://projectperspectives.co.uk/2008/10/a-foolproof-structure-for-your-research-report/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: projectperspectives.co.uk @ 2012-05-19 21:16:10 -->
