27 October 2024 - Copy previous timesheets and improve people cost calculations and margins

We are making timesheeting easier for time and expense users!

Included in this release:

Feedback or questions? 
Email us at support@projectworks.io and one of the team will get back to you!

Copy previous timesheet

We’re making it easier for those of you who enter the same time entries on a regular basis to add time entries to your timesheets. You can now copy time entries from the previous week (or day) into the current timesheet for which you are entering time.

If you have already added any time into the timesheet, copying from the previous week (or day) will over-ride that time (unless the existing time entries have already been reviewed, locked, invoiced or written-off).

Read more about copying previous timesheets →

Improve people cost calculations and margin reporting

Fixed/salaried people’s costs are now calculated based on their working capacity, so if you have a number of people who are part-time, their costs will be more accurately calculated over a specified timeframe, and therefore their margin reporting will be more accurate.

This change also removes the dependency on Financial Years, so these will be removed and all reporting (including deriving costs, margins, and expenses) that is based on a financial year will be driven by the single fiscal year setting. 

Read more about employee costs and people margin reporting →

For Users who are using an SQL connection for reporting ONLY

As we are changing the way Financial years are calculated, we have changed how the Financial Year IDs work. There are no schema changes for this, however the Financial Year IDs values will be changed. This should not affect pre-existing queries using FinancialYearID to join to DimFinancialYear.

As CostPerMonth is no longer a static cost, it will be zeroed out - this change will not break existing SQL report. It is zeroed out on the following views:

  • FactUserCostByDay

We plan to remove CostPerMonth from FactUserCostByDay by Sunday 15th December. So please update your BI reports to no longer include this column.