<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: There is no order but chronological order (III)</title>
	<atom:link href="http://etclaims.co.uk/2009/05/there-is-no-order-but-chronological-order-iii/feed/" rel="self" type="application/rss+xml" />
	<link>http://etclaims.co.uk/2009/05/there-is-no-order-but-chronological-order-iii/</link>
	<description>tactics &#38; precedents</description>
	<lastBuildDate>Mon, 01 Mar 2010 13:50:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Naomi</title>
		<link>http://etclaims.co.uk/2009/05/there-is-no-order-but-chronological-order-iii/comment-page-1/#comment-1561</link>
		<dc:creator>Naomi</dc:creator>
		<pubDate>Sun, 17 May 2009 15:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://etclaims.co.uk/?p=1870#comment-1561</guid>
		<description>This is a fair point. Sometimes in the witness statement there is no sensible alternative to finishing one strand of a story before you embark on another, even if that means that you have to go back in time a bit when you switch to a new subject. It&#039;s not ideal, but it&#039;s better than telling a hopelessly fragmented story in strict chronological order. 

There are various things you can do to reduce confusion. Present each strand in careful chronological order. Use a heading for each strand, and put the date range that you&#039;re going to be talking about in the heading: e.g. &#039;Flexible working requests: July 2007 - December 2008.&#039;  Put dates in wherever you can. Don&#039;t say &#039;a few days later&#039; unless you&#039;ve mentioned a date in the same paragraph. Don&#039;t ever say &#039;a few weeks later&#039;: if you don&#039;t know the exact date, say something like &#039;in about late April or early May 2009...&#039;  Provide a complete chronology or timeline alongside your statement. 

If you do all this, both your story and the underlying chronology should be reasonably clear.</description>
		<content:encoded><![CDATA[<p>This is a fair point. Sometimes in the witness statement there is no sensible alternative to finishing one strand of a story before you embark on another, even if that means that you have to go back in time a bit when you switch to a new subject. It&#8217;s not ideal, but it&#8217;s better than telling a hopelessly fragmented story in strict chronological order. </p>
<p>There are various things you can do to reduce confusion. Present each strand in careful chronological order. Use a heading for each strand, and put the date range that you&#8217;re going to be talking about in the heading: e.g. &#8216;Flexible working requests: July 2007 &#8211; December 2008.&#8217;  Put dates in wherever you can. Don&#8217;t say &#8216;a few days later&#8217; unless you&#8217;ve mentioned a date in the same paragraph. Don&#8217;t ever say &#8216;a few weeks later&#8217;: if you don&#8217;t know the exact date, say something like &#8216;in about late April or early May 2009&#8230;&#8217;  Provide a complete chronology or timeline alongside your statement. </p>
<p>If you do all this, both your story and the underlying chronology should be reasonably clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: claimant</title>
		<link>http://etclaims.co.uk/2009/05/there-is-no-order-but-chronological-order-iii/comment-page-1/#comment-1559</link>
		<dc:creator>claimant</dc:creator>
		<pubDate>Fri, 15 May 2009 13:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://etclaims.co.uk/?p=1870#comment-1559</guid>
		<description>I am interested in this rule, as I have a tribunal claim which is quite complicated and which has many strands.  I feel that it will be almost impossible for the tribunal to see the issues clearly if it&#039;s presented in purely chronological order.  I think it might work if each strand is explained in chronological order; otherwise it&#039;s going to be a tedious string of events from which it will be very hard to draw out the important points.

Wonder what I should do...</description>
		<content:encoded><![CDATA[<p>I am interested in this rule, as I have a tribunal claim which is quite complicated and which has many strands.  I feel that it will be almost impossible for the tribunal to see the issues clearly if it&#8217;s presented in purely chronological order.  I think it might work if each strand is explained in chronological order; otherwise it&#8217;s going to be a tedious string of events from which it will be very hard to draw out the important points.</p>
<p>Wonder what I should do&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
