<?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>Staff Rosters &#187; scheduling</title>
	<atom:link href="http://staffrosters.com.au/category/scheduling/feed" rel="self" type="application/rss+xml" />
	<link>http://staffrosters.com.au</link>
	<description>Staff Rosters - Rostering should be this easy</description>
	<lastBuildDate>Sun, 23 Feb 2020 22:10:43 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.29</generator>
	<item>
		<title>Managing unavailability in retail</title>
		<link>http://staffrosters.com.au/managing-unavailability-in-retail.html</link>
		<comments>http://staffrosters.com.au/managing-unavailability-in-retail.html#comments</comments>
		<pubDate>Sun, 23 Feb 2020 22:10:43 +0000</pubDate>
		<dc:creator><![CDATA[Peter Morrissey]]></dc:creator>
				<category><![CDATA[award interpretation]]></category>
		<category><![CDATA[cloud rostering]]></category>
		<category><![CDATA[Mobile Phone Rostering]]></category>
		<category><![CDATA[Rostering Demonstration]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[StaffRosters Blog]]></category>
		<category><![CDATA[XERO Payroll]]></category>

		<guid isPermaLink="false">http://staffrosters.com.au/?p=566</guid>
		<description><![CDATA[How you manage unavailability today could be a mixture of text messages, Facebook posts, spreadsheets, notes on your PC and even writing on your hand. Do you feel like this some days? Especially when you have the schedule all sorted and another person calls in sick! The guy behind I reckon has seen this before! [&#8230;]]]></description>
		<wfw:commentRss>http://staffrosters.com.au/managing-unavailability-in-retail.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>2020 time to upgrade your employee time keeping software</title>
		<link>http://staffrosters.com.au/2020-time-to-upgrade-your-employee-time-keeping-software.html</link>
		<comments>http://staffrosters.com.au/2020-time-to-upgrade-your-employee-time-keeping-software.html#comments</comments>
		<pubDate>Mon, 20 Jan 2020 22:27:41 +0000</pubDate>
		<dc:creator><![CDATA[Peter Morrissey]]></dc:creator>
				<category><![CDATA[award interpretation]]></category>
		<category><![CDATA[Deputy Implementation]]></category>
		<category><![CDATA[MYOB Payroll]]></category>
		<category><![CDATA[Online Time Sheets]]></category>
		<category><![CDATA[Rostering Demonstration]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[StaffRosters Blog]]></category>
		<category><![CDATA[XERO Payroll]]></category>

		<guid isPermaLink="false">http://staffrosters.com.au/?p=558</guid>
		<description><![CDATA[2020 is the time to make the change, if you have not previously upgraded your employee time and attendance system or you are still running schedules through spreadsheets 2020 is the time to change. How can you improve your current employee timekeeping processes? Schedule employees into the future &#8211; visibility for all employees, managers, and [&#8230;]]]></description>
		<wfw:commentRss>http://staffrosters.com.au/2020-time-to-upgrade-your-employee-time-keeping-software.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>28 day rotating roster 8 hour or 10 hour days? Which one works better?</title>
		<link>http://staffrosters.com.au/28-day-rotating-roster-8-hour-or-10-hour-days-which-one-works-better.html</link>
		<comments>http://staffrosters.com.au/28-day-rotating-roster-8-hour-or-10-hour-days-which-one-works-better.html#comments</comments>
		<pubDate>Thu, 21 Nov 2019 05:16:40 +0000</pubDate>
		<dc:creator><![CDATA[Peter Morrissey]]></dc:creator>
				<category><![CDATA[12 hour shifts]]></category>
		<category><![CDATA[Rostering Demonstration]]></category>
		<category><![CDATA[Schedling open shifts]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[StaffRosters Blog]]></category>
		<category><![CDATA[cloud rostering]]></category>
		<category><![CDATA[rostering]]></category>
		<category><![CDATA[scheduling open shifts]]></category>
		<category><![CDATA[staff rosters]]></category>
		<category><![CDATA[time and attendance]]></category>

		<guid isPermaLink="false">http://staffrosters.com.au/?p=411</guid>
		<description><![CDATA[If you have ever worked one of these schedules or had to organise staff around one of these schedules you will understand the amount of work that goes into keeping the schedule in place. I have seen two common types of 28 day rotating rosters. 28-day rotating roster 8 hour day 28-day rotating roster 12 hour [&#8230;]]]></description>
		<wfw:commentRss>http://staffrosters.com.au/28-day-rotating-roster-8-hour-or-10-hour-days-which-one-works-better.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>George Calombaris rips $7.8 Million from his employees</title>
		<link>http://staffrosters.com.au/george-calombaris-rips-7-8-million-from-his-employees.html</link>
		<comments>http://staffrosters.com.au/george-calombaris-rips-7-8-million-from-his-employees.html#comments</comments>
		<pubDate>Fri, 19 Jul 2019 05:04:01 +0000</pubDate>
		<dc:creator><![CDATA[Peter Morrissey]]></dc:creator>
				<category><![CDATA[award interpretation]]></category>
		<category><![CDATA[rostering]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[Time & Attendance]]></category>

		<guid isPermaLink="false">http://staffrosters.com.au/?p=550</guid>
		<description><![CDATA[George Calombaris has been caught out with poor systems. While his OCD applied nicely for preparing food that skill did not transfer to admin. Poor systems for employee timekeeping and payroll has led to this situation where George has shortchanged staff $7.8 million dollars. Did he do this knowingly? How could George have avoided this [&#8230;]]]></description>
		<wfw:commentRss>http://staffrosters.com.au/george-calombaris-rips-7-8-million-from-his-employees.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Royal Botanic Gardens expand employees scheduling with Time &amp; People</title>
		<link>http://staffrosters.com.au/the-royal-botanic-gardens-expand-employees-scheduling-with-time-people.html</link>
		<comments>http://staffrosters.com.au/the-royal-botanic-gardens-expand-employees-scheduling-with-time-people.html#comments</comments>
		<pubDate>Fri, 28 Jun 2019 05:47:55 +0000</pubDate>
		<dc:creator><![CDATA[Peter Morrissey]]></dc:creator>
				<category><![CDATA[cloud rostering]]></category>
		<category><![CDATA[Deputy Implementation]]></category>
		<category><![CDATA[Mobile Phone Rostering]]></category>
		<category><![CDATA[Onboard employees]]></category>
		<category><![CDATA[Schedling open shifts]]></category>
		<category><![CDATA[scheduling]]></category>
		<category><![CDATA[department rostering]]></category>
		<category><![CDATA[employee rostering]]></category>
		<category><![CDATA[mobile phone rostering]]></category>
		<category><![CDATA[rostering for payroll]]></category>
		<category><![CDATA[staff rosters]]></category>

		<guid isPermaLink="false">http://staffrosters.com.au/?p=544</guid>
		<description><![CDATA[This week after a successful pilot across 5 locations that make up the Botanic Gardens in and around Sydney and the Blue Mountains from 2018 with 120 employees The Botanic Gardens have expanded the employee scheduling software to assist with staff rosters by adding 80 specialist teachers to the system. Prior to going digital everything [&#8230;]]]></description>
		<wfw:commentRss>http://staffrosters.com.au/the-royal-botanic-gardens-expand-employees-scheduling-with-time-people.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
