<?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>My Project Management Lessons &#187; expenses</title>
	<atom:link href="http://www.myprojectlessons.com/tag/expenses/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.myprojectlessons.com</link>
	<description>Lessons learned in Project Management</description>
	<lastBuildDate>Sat, 28 Nov 2009 02:34:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Submit claims as soon as possible</title>
		<link>http://www.myprojectlessons.com/2009/06/submit-claims-as-soon-as-possible/</link>
		<comments>http://www.myprojectlessons.com/2009/06/submit-claims-as-soon-as-possible/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 09:01:41 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Human Resources]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[claims]]></category>
		<category><![CDATA[expenses]]></category>
		<category><![CDATA[loss]]></category>
		<category><![CDATA[profit]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=465</guid>
		<description><![CDATA[As a project manager you should make sure all your team members submit claims, hours, expenses etc as soon as possible, and definitely before the end of month accounting date.
If that information comes in late the profit/margin on the project can quickly change and affect plans.
The hours must also be made to the correct project. [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/04/good-document-system/" rel="bookmark">Good Document System</a><!-- (7.39162)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/07/resource-schedule/" rel="bookmark">Resource Schedule</a><!-- (5.60235)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>As a project manager you should make sure all your team members <strong>submit claims, hours, expenses etc as soon as possible,</strong> and definitely before the end of month accounting date.</p>
<p>If that information comes in late the profit/margin on the project can quickly change and affect plans.</p>
<p>The hours must also be made to the correct project. You don&#8217;t want hours suddenly being transferred to your project from a few months ago because they were incorrectly allocated. This could make an in profit project suddenly be making a loss. If it was done correctly first time, the losses could have been seen earlier and planned or allowed for.</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/04/good-document-system/" rel="bookmark">Good Document System</a><!-- (7.39162)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/07/resource-schedule/" rel="bookmark">Resource Schedule</a><!-- (5.60235)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2009/06/submit-claims-as-soon-as-possible/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Good Document System</title>
		<link>http://www.myprojectlessons.com/2009/04/good-document-system/</link>
		<comments>http://www.myprojectlessons.com/2009/04/good-document-system/#comments</comments>
		<pubDate>Sat, 11 Apr 2009 03:16:46 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Cost]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[accounting]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[changes]]></category>
		<category><![CDATA[expenses]]></category>
		<category><![CDATA[forecast]]></category>
		<category><![CDATA[labour]]></category>
		<category><![CDATA[statistics]]></category>
		<category><![CDATA[system]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=331</guid>
		<description><![CDATA[If you have control of the system at the start of a project, make sure the project (or even at the program level, project office level, or company level) uses a document and accounting system that can record and output everything.
This would include costs, labour, forecasts, statistics, billing, budget, expenses, changes etc.
It should be able [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-design-changes-and-delays/" rel="bookmark">Document Design Changes and Delays</a><!-- (16.1402)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/08/eliminate-unnecessary-features/" rel="bookmark">Eliminate Unnecessary Features</a><!-- (12.2034)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/04/record-your-achievements/" rel="bookmark">Record Your Achievements</a><!-- (11.0069)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>If you have control of the system at the start of a project, make sure the project (or even at the program level, project office level, or company level) uses a document and accounting system that can record and output everything.</p>
<p>This would include costs, labour, forecasts, statistics, billing, budget, expenses, changes etc.</p>
<p>It should be able to output things like:</p>
<ul>
<li>Weekly reports.</li>
<li> Monthly cost summary</li>
<li> Invoices</li>
<li> Labour costs for a period</li>
<li> Expense breakdowns</li>
<li> Cost to date</li>
<li> Variance</li>
<li> Total cost at completion</li>
</ul>
<p>This should all be available from one package or a number of modules that are automatically linked together. You do not want to have multiple spreadsheets that people record things in that are not linked. The  result should be a significant reduction in paperwork.</p>
<p>Certain inputs could only be allowed by certain people (by log in), such as:</p>
<ul>
<li>Accounts (accountant)</li>
<li> Billing</li>
<li> Labour (site manager)</li>
<li> Design hours (design manager)</li>
</ul>
<p>Individual hours by each person could be input (linked) from time sheets. All staff/employees should have adequate training so that the system is used properly</p>
<p>To start with, I recommend looking at the <a title="List of Project Managem Software" href="http://en.wikipedia.org/wiki/List_of_project_management_software">list of project management software</a> at Wikipedia.</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-design-changes-and-delays/" rel="bookmark">Document Design Changes and Delays</a><!-- (16.1402)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/08/eliminate-unnecessary-features/" rel="bookmark">Eliminate Unnecessary Features</a><!-- (12.2034)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/04/record-your-achievements/" rel="bookmark">Record Your Achievements</a><!-- (11.0069)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2009/04/good-document-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
