16 Aug 2018

This major change in this release is the introduction of resource leveling - a new (optional) way to align your project resourcing against task allocation. Not everyone will want to use this feature, and it won't apply to every project, but it is a very powerful enhancement to the resourcing engine.

Two key bugs relating to setting rates on tasks when assigning people to them have been squashed. As always, there are a number of minor tweaks and bug fixes - read on for details.

There have also been updates to the API.


Please contact support@projectworks.io if you have any questions or feedback. 

API Updates:

See notes on API Updates included as part of Version 1.40


  • Notifications: The Invoice Payment notification has been updated to include the amount paid (was previously only included in the email).


  • Upcoming: Objectives which are due are now included.
  • Directory: CSV export now includes the Start Date and End Date of employees.
  • Timesheet Log: Timesheet log export can now be for the "current month" or "all months".


  • Tasks: When assigning users to a task the focus goes to the "Assign new a user" field making it faster to add multiple people.
  • Tasks: Bug fixed. The correct rate is automatically populated when assigning a user to a task (it was being left blank).
  • Tasks: Bug fixed. The allocated amount shown on a task and module has been corrected (weekly allocations were not being calculated).
  • Month End: The calculation of recoverability can be toggled to "include/exclude discounts.

Pro Tip: Recoverability is calculated using these formula:

  • Including Discount: (Total services invoiced + Total Discounts Invoiced)  /  (Total Billed Work)
  • Excluding Discount: (Total services invoiced)  /  (Total Billed Work)
  • Including Discount: (Total services invoiced + Total Discounts Invoiced)  /  (Total Billed Work)
  • Excluding Discount: (Total services invoiced)  /  (Total Billed Work)
  • Details: The process for archiving a project has been improved:
    • Any open risks will automatically be closed
    • Projects can be archived when there is resourcing for the current week (but not in future weeks).
  • Invoicing: The format of hours worked on the Invoice Timesheet CSV export has been changed to present as decimals (rather than time) decimals
  • Resourcing: Hovering over the rate will show how the average rage has been calculated (either using average of allocated tasks or a rate card).
  • Recoverability: The recoverability screen will show NA in the Margin column unless you have permissions to see margin 
  • A Save" button has been added (so you don't have to always "save & close").
  • Self Service of Tasks from a Timesheet: Bug fixed. When a person self served a task from their timesheet it automatically sets the rate to their default carded rate. This has been changed and now will use the rate from the Project Rate Card (if it exists), otherwise the default carded rate will be used.


Project Resourcing - New Visual Indicators & comparisons

The Project Resourcing screen has been updated to provide four different views of the resource allocations on a project. 

Selecting a different "Indicator" will change the colour coding of the resourcing to be measured against a different measure.

Resourced vs Capacity

Resourcing visuals will be measured against the the total resourcing for a person against their total capacity.

Allocated Tasks vs Resourced

Resourcing visuals will be based on comparing the hours allocated to project tasks for the week against the allocated resourcing for the week.

Resourced to this Project

Resourcing visuals will be based on comparing the resourcing of this project against a persons total resourcing.

Allocated Tasks in this project

Resourcing visuals are based on the the hours allocated to tasks on this project against a persons capacity for the week.

Resource Leveling

The ability to level resourcing has been introduced and allows resourcing for a person to be "leveled":against the hours they have allocated on tasks. It's a pretty complicated concept and can only be performed against tasks that have a start and end date, 

The leveling is calculated by summing all the hours allocated to tasks, spreading that over the duration of the task (start to end date) and comparing the allocated resourcing against allocation of tasks. 

Pro Tip: Resource leveling will only work when tasks are created with start and end dates. Leveling cannot be calculated for open ended tasks.


Project resourcing screen

When using the " Allocated Tasks vs Resourced" indicators you will have the ability to "Level Resourcing" on a person by person basis.


Level Resourcing for a person

After clicking Level Resourcing for a person, the weekly resourcing will be automatically adjusted to align to the hours allocated to tasks across the weeks. The leveling will disregard a persons total capacity and any "bench" they have - leveled resourcing could exceed a persons weekly availability. You can adjust the numbers before you save your changes.

API Updates

The following updates have been made to the API, making it easier for integration with other systems.

  1. API | Module & Task Validation Changes
  2. API | Delete & Archive Changes
  3. API | PUT Custom Fields
    1. Endpoints for setting/replacing custom field data for an entity PUT /Clients/clientID/Fields [data]
  4. API | GET Custom Fields
    1. Endpoints for querying fields GET /CustomFields
    2. Endpoints for querying fields and data for an entity GET /Clients/ ?includeCustomFields=true