<?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>On A Wait &#187; labor</title>
	<atom:link href="http://www.onawait.com/tag/labor/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onawait.com</link>
	<description>Restaurant operations - tips, advice, and discussions</description>
	<lastBuildDate>Thu, 24 Sep 2009 20:03:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Food Costs Make Restaurants Re-Think Labor Relationship</title>
		<link>http://www.onawait.com/food-costs-make-restaurants-re-think-labor-relationship/</link>
		<comments>http://www.onawait.com/food-costs-make-restaurants-re-think-labor-relationship/#comments</comments>
		<pubDate>Mon, 28 Apr 2008 13:57:31 +0000</pubDate>
		<dc:creator>Larry</dc:creator>
				<category><![CDATA[Controlling Costs]]></category>
		<category><![CDATA[costs]]></category>
		<category><![CDATA[labor]]></category>
		<category><![CDATA[value]]></category>

		<guid isPermaLink="false">http://www.onawait.com/food-costs-make-restaurants-re-think-labor-relationship/</guid>
		<description><![CDATA[The restaurant and hospitality industry must go back to the basics when looking at menu items. Over the last few years, as labor costs were increasing, restaurants were moving to pre-prepped and packaged food items to reduce labor intensive preparation costs. Now, as food costs are escalating, the food service operator has to review every [...]]]></description>
		<wfw:commentRss>http://www.onawait.com/food-costs-make-restaurants-re-think-labor-relationship/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
