<?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>Idea Salad with Yong Lee &#187; lawsuit</title>
	<atom:link href="http://omtiblog.com/ideasalad/tag/lawsuit/feed/" rel="self" type="application/rss+xml" />
	<link>http://omtiblog.com/ideasalad</link>
	<description>Sure you have a lot on your plate, but leave room for your salad.</description>
	<lastBuildDate>Wed, 20 Jul 2011 00:44:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Are you in Word Index trouble?</title>
		<link>http://omtiblog.com/ideasalad/industry-news/word-index-trouble/</link>
		<comments>http://omtiblog.com/ideasalad/industry-news/word-index-trouble/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 02:07:39 +0000</pubDate>
		<dc:creator>Yong Lee</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Industry news]]></category>
		<category><![CDATA[court reporting]]></category>
		<category><![CDATA[lawsuit]]></category>
		<category><![CDATA[transcripts]]></category>
		<category><![CDATA[word index]]></category>

		<guid isPermaLink="false">http://omtiblog.com/ideasalad/?p=77</guid>
		<description><![CDATA[The way you handle word indexes can lead to lawsuits. <a href="http://omtiblog.com/ideasalad/industry-news/word-index-trouble/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fomtiblog.com%2Fideasalad%2Findustry-news%2Fword-index-trouble%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fomtiblog.com%2Fideasalad%2Findustry-news%2Fword-index-trouble%2F&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<h3>Avoid a lawsuit by following this advice</h3>
<p>When it comes to handling word indexes, does your agency fall under one of the following categories?</p>
<ol>
<li>You provide word indexes (usually with condensed transcripts) to clients free of charge.</li>
<li>You provide word indexes (usually with condensed transcripts) for a flat fee (e.g., $25).</li>
<li>You provide word indexes (as part of standard transcripts) at the same per page rate as you charge for the transcripts themselves.</li>
</ol>
<p>If you answered “#3,” then you could be vulnerable to lawsuits unless your rate sheet fully discloses your billing policies concerning word indexes.</p>
<h2>Lawsuits have already been filed</h2>
<p>This is already happening to other firms. Several class action lawsuits are pending in federal courts that contend that court reporting firms are padding their bills by charging full per-page prices for word indexes without full disclosure.</p>
<p>Here are my observations as to why it will be difficult to justify the practice of charging full price without disclosing that up-front:</p>
<ul>
<li>The word index is not a part of the record prepared by a court reporter.</li>
<li>The word index is generated by a computer program, not by a court reporter.</li>
<li>The court reporter usually is not paid for the word index.</li>
<li>The total page count is different from what the reporter turned in.</li>
<li>The client usually isn’t aware of the practice.</li>
</ul>
<h2>Protect yourself</h2>
<p>I recommend that you go for peace of mind with full disclosure even though it might hurt your bottom line. Include word indexes for free with condensed transcripts, and use that as your marketing edge. You’ll be more attractive to clients and less attractive to lawsuits.</p>
]]></content:encoded>
			<wfw:commentRss>http://omtiblog.com/ideasalad/industry-news/word-index-trouble/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

