<?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>HRMorning.com &#187; documentation</title>
	<atom:link href="http://www.hrmorning.com/tag/documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hrmorning.com</link>
	<description>Your daily dose of HR</description>
	<lastBuildDate>Fri, 20 Nov 2009 21:44:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Company sued over president&#8217;s napkin</title>
		<link>http://www.hrmorning.com/company-sued-over-presidents-napkin/</link>
		<comments>http://www.hrmorning.com/company-sued-over-presidents-napkin/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 11:00:22 +0000</pubDate>
		<dc:creator>Sam Narisi</dc:creator>
				<category><![CDATA[Age discrimination]]></category>
		<category><![CDATA[Employment law]]></category>
		<category><![CDATA[HR Tech]]></category>
		<category><![CDATA[In this week's e-newsletter - Tech]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[firing]]></category>
		<category><![CDATA[notes]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/?p=6189</guid>
		<description><![CDATA[Warnings about bad documentation often involve high-tech situations &#8212; for example, watch what you e-mail, since it creates a permanent record. But managers need to be careful of how they handle more primitive documents, too. 
In this recent case, notes scrawled on a napkin ended up getting a company dragged into court:
The company&#8217;s VP of [...]]]></description>
			<content:encoded><![CDATA[<p>Warnings about bad documentation often involve high-tech situations &#8212; for example, watch what you e-mail, since it creates a permanent record. But managers need to be careful of how they handle more primitive documents, too. <span id="more-6189"></span></p>
<p>In this recent case, notes scrawled on a napkin ended up getting a company dragged into court:</p>
<p>The company&#8217;s VP of Technology worked for the employer for 17 years with no problems &#8212; until a new president was brought in.</p>
<p>The VP disagreed with the president on several things, and received an uncharacteristically negative review from the president.</p>
<p>Faced with financial problems, the company brought in a management consultant to meet with the president and other decision-makers. One decision that came from that meeting: The VP of Technology was fired.</p>
<p>He was told it was because he wasn&#8217;t the type of leader the company wanted. But he thought it was because of his age (he was 58 at the time, and the company replaced him with a 45-year-old) and sued. He won. Why?</p>
<p>Evidence presented included notes the president wrote on a napkin while meeting with the consultant. The scribblings included a note that the company&#8217;s execs should be &#8220;young, energetic&#8221; &#8220;future people.&#8221;</p>
<p>After seeing that, the judge agreed age likely influenced the president&#8217;s decision.</p>
<p><strong>Cite: </strong><em>Inman v. Klockner Pentaplast Of America, Inc.</em></p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=6189&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/company-sued-over-presidents-napkin/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Company to judge: &#8216;The dog ate our investigation&#8217;</title>
		<link>http://www.hrmorning.com/company-to-judge-the-dog-ate-our-investigation/</link>
		<comments>http://www.hrmorning.com/company-to-judge-the-dog-ate-our-investigation/#comments</comments>
		<pubDate>Fri, 21 Aug 2009 11:00:45 +0000</pubDate>
		<dc:creator>Dan Wisniewski</dc:creator>
				<category><![CDATA[HR Tech]]></category>
		<category><![CDATA[In this week's e-newsletter - Tech]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Sexual harrassment]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[eeoc]]></category>
		<category><![CDATA[investigations]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/?p=3415</guid>
		<description><![CDATA[The excuse &#8220;The dog ate my homework&#8221; didn&#8217;t work in school &#8212; was there any chance it&#8217;d hold up in federal court? 
Shortly after starting her job at an auto parts retailer, a female employee in Mesa, Arizona said she was subjected to sexual harassment over the course of a year by her store manager. [...]]]></description>
			<content:encoded><![CDATA[<p>The excuse &#8220;The dog ate my homework&#8221; didn&#8217;t work in school &#8212; was there any chance it&#8217;d hold up in federal court? <span id="more-3415"></span></p>
<p>Shortly after starting her job at an auto parts retailer, a female employee in Mesa, Arizona said she was subjected to sexual harassment over the course of a year by her store manager. The store manager allegedly forced the worker&#8217;s head down to his genitals, exposed himself to her and made crude sexual remarks toward her.</p>
<p>Allegedly, HR investigated these incidents, and even interviewed five witnesses. (Take note of the &#8220;allegedly.&#8221;)</p>
<p>The last of these incidents was fortunately caught on a security camera at the store, and the regional HR manager forced the store manager to resign.</p>
<p>The female employee filed suit with the EEOC. When the EEOC asked the company for the documentation of the investigation, the store had some bad news &#8212; they simply didn&#8217;t have records of the employee&#8217;s sexual harassment claim.</p>
<p>Okay, said the EEOC. How about the records of the employee interviews HR did with the five witnesses to the harassment? Sorry, said the company. We are unable to locate that document at this time.</p>
<p>And the videotape of the store manager sexually harassing the employee? You guessed it &#8212; lost as well.</p>
<p>With all the documentation missing, the jury wasn&#8217;t buying the company&#8217;s story &#8212; and hit it with a $65,000 verdict.</p>
<p>The lesson for managers here? No documentation is just as harmful as bad documentation. Stress to your managers the importance of not only keeping good documentation, but also keeping organized records &#8212; you never know when your company will need to produce the paperwork again.</p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=3415&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/company-to-judge-the-dog-ate-our-investigation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Court: Alcoholic employee should&#8217;ve been cut some slack</title>
		<link>http://www.hrmorning.com/court-alcoholic-employee-shouldve-been-cut-some-slack/</link>
		<comments>http://www.hrmorning.com/court-alcoholic-employee-shouldve-been-cut-some-slack/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 11:00:46 +0000</pubDate>
		<dc:creator>Sam Narisi</dc:creator>
				<category><![CDATA[FMLA]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Leave]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[performance review]]></category>
		<category><![CDATA[returning from leave]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/?p=3109</guid>
		<description><![CDATA[Even the best employees occasionally turn into poor performers. What should managers be wary of when disciplining or firing employees who&#8217;ve gotten positive reviews in the past? 
If an employee has taken FMLA leave, that can make the situation even more complicated. Take this recent case as an example:
A sales rep had been highly regarded [...]]]></description>
			<content:encoded><![CDATA[<p>Even the best employees occasionally turn into poor performers. What should managers be wary of when disciplining or firing employees who&#8217;ve gotten positive reviews in the past? <span id="more-3109"></span></p>
<p>If an employee has taken FMLA leave, that can make the situation even more complicated. Take this recent case as an example:</p>
<p>A sales rep had been highly regarded by his employer. Three out of his four most recent performance evaluations rated him as &#8220;exceeding expectations.&#8221;</p>
<p>That changed after he took a month of FMLA leave to be treated for alcoholism.</p>
<p>Two weeks after he came back, it was time for his next review. His boss noted that his sales had dropped and there had been problems with his communication skills. The review concluded the employee failed to meet expectations, and he was placed on a 30-day performance improvement plan.</p>
<p>When he failed to bring his numbers back up in time, he was fired &#8212; and he sued the company. He claimed he was a good employee and was unfairly terminated because he took FMLA leave.</p>
<p>The employer argued that despite his previous success, his performance started to slip, as his most recent review showed.</p>
<p>But the company lost the case.</p>
<p>The reason: The court wasn&#8217;t convinced he would&#8217;ve gotten a poor review if he hadn&#8217;t taken leave. As the judge noted, missing a month of work must have caused his sales to suffer. The company should have adjusted its standards to account for the time he was gone.</p>
<p>Managers need to be careful about how they evaluate employees who return from medical leave. Even if bias isn&#8217;t intentional, companies can still get in trouble when an adverse action is in any way tied to an employee&#8217;s use of FMLA.</p>
<p><strong>Cite: </strong><em>Burris v. Novartis Animal Health U.S., Inc.</em></p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=3109&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/court-alcoholic-employee-shouldve-been-cut-some-slack/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The manager&#8217;s guide to great documentation</title>
		<link>http://www.hrmorning.com/the-managers-guide-to-great-documentation/</link>
		<comments>http://www.hrmorning.com/the-managers-guide-to-great-documentation/#comments</comments>
		<pubDate>Fri, 21 Nov 2008 11:00:10 +0000</pubDate>
		<dc:creator>Jim Giuliano</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Complaint investigation]]></category>
		<category><![CDATA[Discipline]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Records documentation]]></category>
		<category><![CDATA[Special Report]]></category>
		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/?p=407</guid>
		<description><![CDATA[
You&#8217;ve probably mentioned it to managers a hundred times: When there&#8217;s a problem with an employee, make sure we have good documentation to back up any discipline. Employment law attorney Penelope Phillips explains a few hints that will make documentation better than &#8220;good.&#8221; 
Phillips says the clues lie in several court cases she&#8217;s seen and [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.hrmorning.com/wp-content/uploads/good-job.jpg"><img class="alignnone size-full wp-image-194" title="good-job" src="http://www.hrmorning.com/wp-content/uploads/good-job.jpg" alt="" width="360" height="240" /></a></p>
<p>You&#8217;ve probably mentioned it to managers a hundred times: When there&#8217;s a problem with an employee, make sure we have good documentation to back up any discipline. Employment law attorney Penelope Phillips explains a few hints that will make documentation better than &#8220;good.&#8221; <span id="more-407"></span></p>
<p>Phillips says the clues lie in several court cases she&#8217;s seen and how the right words have meant the difference between a win for the manager and a big cash settlement for an employee with a complaint. She says solid documentation relies on three pieces that every manager should understand. Here&#8217;s how they&#8217;re broken down:</p>
<p><strong>1. Timing.</strong> Even good documentation can hurt your cause if too much time elapses between the incident and the date of the documentation. Two reasons:</p>
<ul>
<li>In the employee&#8217;s mind, the connection between the incident and the documentation becomes fuzzy. When that happens, employees start to believe they&#8217;re being treated unfairly.</li>
<li>If an employee does decide to file a lawsuit over the incident, a judge might perceive that the supervisor was relying on a dim memory of old events.</li>
</ul>
<p>There&#8217;s no hard-and-fast rule about timing, but the longer it&#8217;s put off, the greater the risk to the employer. All the better if the documentation is dated the same day as the incident.</p>
<p><strong>2. Accuracy.</strong> Getting the story straight in writing is as much about what&#8217;s <em>not said</em> as what&#8217;s said.</p>
<p>Yes, managers should follow the reporter&#8217;s creed of The Five W&#8217;s &#8211; who, what, when, where, why &#8211; when putting together documentation. But most mistakes occur in the &#8220;why&#8221; stage.</p>
<p>Reason: too much &#8220;editorializing&#8221; about events. Examples:</p>
<ul>
<li>&#8220;Bob showed up late because he was drunk.&#8221; That leaves the documentation open to questions such as, &#8220;How do you know? Did you take his alcohol-blood level?&#8221;</li>
<li>&#8220;You have a bad attitude about deadlines.&#8221; How do you define that? Better to describe a measurable behavior: &#8220;You failed to meet three important deadlines.&#8221;</li>
<li>&#8220;I may not approve of your lifestyle, but that has no bearing on this problem.&#8221; Then why mention it? If circumstances are unrelated, there&#8217;s no need to bring them up.</li>
<li>&#8220;You sexually harassed Carol three times.&#8221; That&#8217;s a legal conclusion made only by judges and juries. More accurate: &#8220;Carol complained three times that you spoke to her or touched her in a way she thought was inappropriate.&#8221;</li>
</ul>
<p><strong>3. Desired results.</strong> The point of any discipline and accompanying documentation is to change behavior. That desired change is another key to good documentation.</p>
<p>What&#8217;s a common mistake in this area? Consider, as an example, the situation of the employee who&#8217;s habitually late for work. Some supervisors in that instance will write &#8220;must be on time for 90 consecutive days&#8221; as an acceptable change in behavior.</p>
<p>So, what ends up happening? On the 91st day, the employee shows up late and says, &#8220;Hey, I followed the rules of your documentation.&#8221; And a judge will most likely agree.</p>
<p>Best bet: Establish a standard for long-term behavior and set out the next disciplinary step for any violation of that standard: &#8220;If you&#8217;re late again, we will consider suspending you without pay for a period to be determined.&#8221;</p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=407&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/the-managers-guide-to-great-documentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My best HR management idea: Taking some of the headache out of FMLA</title>
		<link>http://www.hrmorning.com/my-best-hr-management-idea-taking-some-of-the-headache-out-of-fmla/</link>
		<comments>http://www.hrmorning.com/my-best-hr-management-idea-taking-some-of-the-headache-out-of-fmla/#comments</comments>
		<pubDate>Thu, 31 Jul 2008 10:00:56 +0000</pubDate>
		<dc:creator>Jim Giuliano</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Employment law]]></category>
		<category><![CDATA[FMLA]]></category>
		<category><![CDATA[In this week's e-newsletter]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Leave]]></category>
		<category><![CDATA[My best management idea]]></category>
		<category><![CDATA[Records documentation]]></category>
		<category><![CDATA[policies]]></category>
		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/?p=285</guid>
		<description><![CDATA[HR manager Holly Thomas and her supervisors got tired of continually making decisions &#8211; which often got disputed by employees &#8212; about who was eligible for FMLA leave. Then she hit on an idea that made the process easier on everyone. 
Administering FMLA leave is painful enough, but it&#8217;s worse when employees question decisions about who&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>HR manager Holly Thomas and her supervisors got tired of continually making decisions &#8211; which often got disputed by employees &#8212; about who was eligible for FMLA leave. Then she hit on an idea that made the process easier on everyone. <span id="more-285"></span></p>
<p>Administering FMLA leave is painful enough, but it&#8217;s worse when employees question decisions about who&#8217;s eligible and for what reasons.</p>
<p>Sure, the FMLA regs lay it all out, and in a lot of instances it&#8217;s pretty clear, but there are gray areas.</p>
<p>For instance: Are we really sure that Bob needs to stay home for two weeks to take care of his sick wife?</p>
<p>We wanted to avoid conflicts and stay within the law. We also wanted to make sure we were being fair to all employees.</p>
<p><strong>New documentation<br />
</strong>We found we could do that, at least in the case of employees who wanted time off to care for ill or injured family.</p>
<p>We set up a rule that those employees would have to obtain medical certification, just the same as if they were providing documentation for their own illness or injury &#8211; with one exception. The doctor&#8217;s documentation had to indicate that the sick family member needed someone to provide care pretty much full time.</p>
<p>Requiring documentation like that took the decision out of our hands and avoided any appearance of being arbitrary or showing favoritism to some employees.</p>
<p>Now our employees know the rule, and they know it&#8217;s applied consistently and fairly. And no one complains when we go by the rule.</p>
<p><em>(By Holly Thomas, Plumstead, PA)</em></p>
<p><em>Got your own best HR management idea? Send it to <a href="mailto:jgiuliano@pbp.com">jgiuliano@pbp.com</a> and we&#8217;ll consider it for publication in an upcoming edition of HR Morning.</em></p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=285&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/my-best-hr-management-idea-taking-some-of-the-headache-out-of-fmla/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Four dumb documentation mistakes – and how to avoid them</title>
		<link>http://www.hrmorning.com/four-dumb-documentation-mistakes-%e2%80%93-and-how-to-avoid-them/</link>
		<comments>http://www.hrmorning.com/four-dumb-documentation-mistakes-%e2%80%93-and-how-to-avoid-them/#comments</comments>
		<pubDate>Fri, 21 Mar 2008 11:00:40 +0000</pubDate>
		<dc:creator>Jim Giuliano</dc:creator>
				<category><![CDATA[Discipline]]></category>
		<category><![CDATA[Employment law]]></category>
		<category><![CDATA[In this week's e-newsletter]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Records documentation]]></category>
		<category><![CDATA[alcohol]]></category>
		<category><![CDATA[attitude]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[penelope phillips]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/four-dumb-documentation-mistakes-%e2%80%93-and-how-to-avoid-them/</guid>
		<description><![CDATA[There are two kinds of documentation: good and bad. And small changes can make the difference between the two.

Employment-law attorney Penelope Phillips says if you can just convince your managers to avoid four common errors, you’ll be miles ahead of a lot of other companies when it comes to effective documentation.
1. Flat “because” statements that [...]]]></description>
			<content:encoded><![CDATA[<p>There are two kinds of documentation: good and bad. And small changes can make the difference between the two.</p>
<p><span id="more-68"></span></p>
<p>Employment-law attorney Penelope Phillips says if you can just convince your managers to avoid four common errors, you’ll be miles ahead of a lot of other companies when it comes to effective documentation.</p>
<p><strong>1. Flat “because” statements that can’t be backed up by fact.<br />
</strong>Example: “Bob showed up late because he was drunk.”<br />
Problem: Unless someone took a blood-alcohol level test, there’s nothing to back up the statement.<br />
Fix: “Bob showed up late and appeared to be slurring his words when he spoke.”</p>
<p><strong>2. Criticisms that amount to opinions.<br />
</strong>Example: “You have a bad attitude about deadlines.”<br />
Problem: How do you define “bad attitude”?<br />
Fix: “You missed three deadlines this month.”</p>
<p><strong>3. Unnecessary statements<br />
</strong>Example: “I may not approve of your lifestyle, but that has no bearing on the dispute.”<br />
Problem: Then why mention it?<br />
Fix: “Here are your performance- and behavior-related deficiencies.”</p>
<p><strong>4. Drawing legal conclusion or condemnations</strong><br />
Example: “You sexually harassed Carol three times.”<br />
Problem: That implies a level of guilt that can be verified only by a proper investigation or admission by the charged employee.<br />
Fix: “Carol complained three times that you spoke to her or touched her in an inappropriate way.”</p>
<p><em>(Based on a presentation by Phillips at the Upper Midwest Law Institute)</em></p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=68&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/four-dumb-documentation-mistakes-%e2%80%93-and-how-to-avoid-them/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who won this case? He complains, then gets fired</title>
		<link>http://www.hrmorning.com/who-won-this-case-he-complains-then-gets-fired/</link>
		<comments>http://www.hrmorning.com/who-won-this-case-he-complains-then-gets-fired/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 11:00:03 +0000</pubDate>
		<dc:creator>Jim Giuliano</dc:creator>
				<category><![CDATA[Complaint investigation]]></category>
		<category><![CDATA[Employment law]]></category>
		<category><![CDATA[Latest News & Views]]></category>
		<category><![CDATA[Terminations]]></category>
		<category><![CDATA[Who won?]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[firing]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[retaliation]]></category>
		<category><![CDATA[safety]]></category>
		<category><![CDATA[termination]]></category>

		<guid isPermaLink="false">http://www.hrmorning.com/who-won-this-case-he-complains-then-gets-fired</guid>
		<description><![CDATA[A poor-performing employee gets fired shortly after filing a complaint about company safety. He sues the company for retaliation. Who won this real-life case?

The facts: 
An employee sued after being fired for documented poor performance. Basis for the suit: About 60 days before the firing, the employee had filed a complaint with a state agency about [...]]]></description>
			<content:encoded><![CDATA[<p>A poor-performing employee gets fired shortly after filing a complaint about company safety. He sues the company for retaliation. Who won this real-life case?</p>
<p><span id="more-64"></span></p>
<p><strong>The facts:</strong> <br />
An employee sued after being fired for documented poor performance. Basis for the suit: About 60 days before the firing, the employee had filed a complaint with a state agency about safety violations as the company. He charged that the company fired him in retaliation for the complaint, and not because of performance.</p>
<p><strong>The employer said:<br />
</strong>The supervisor had a record of the employee’s poor performance, including low performance appraisals. That kind of documentation proved that the firing was warranted and had nothing to do with the complaint.</p>
<p>Who won the case?</p>
<p><strong>Answer:</strong> The employee.</p>
<p><strong>Why:</strong> A judge agreed that the company had adequate documentation for the termination – if there were no other relevant factors involved. The complaint itself and the timing of the firing were relevant factors that made the termination look suspicious.</p>
<p>The fact that there was only two months between the time of the complaint and the firing raised some red flags, according to the judge. When events are that close, it’s reasonable to conclude that one affected the other.</p>
<p>And the law gives special protections to complaints about safety, since they cover matters of “public policy,” meaning they affect other workers besides the one who complained.</p>
<p><em>Cite: Kohrt v. MidAmerican Energy Co.</em></p>
<img src="http://www.hrmorning.com/?ak_action=api_record_view&id=64&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.hrmorning.com/who-won-this-case-he-complains-then-gets-fired/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
