What does a typical "Contract Lifecycle" look like in Cenefits?

Last updated by Tom Inglis on November 12, 2020 08:34

Before a contract can be added to Cenefits, an Admin should create Benefit Category, Benefit Priority, Contract Category, Contract Priority, Department, Location and Portfolio filters for the organisation, as well as creating any Benefit Templates that they have and inviting any Employees they would like to be able to assign to Contracts or Benefits.

1. An Admin can then create a new Contract, filling in at least the Contract Title, Reference Number, one or more Contract Managers, Contract Status, and leaving it Unpublished.

2. An Admin or one of the assigned Contract Managers can then create and associate one or more Benefits with the Contract. These can either be created by selecting a Benefit Template, and filling in the details that make it unique to that Contract, or by creating a Unique Benefit just for use in that Contract. They should fill in at least the (Benefit Template Title), Contract, (Unique Benefit Outcome), Quantity, Supplier, Final Delivery Date, and Benefit Status.

3. Once they are happy that all of the Benefits have been successfully created, an Admin or one of the assigned Contract Managers can then mark the Contract as Published, which will send an email to any Project Managers, Suppliers or Delivery Partners assigned to the Benefits associated with that Contract to let them know it is live.

4. Project Managers, Suppliers and Delivery Partners will receive emails a week and a day before and a week after each Delivery Date for each Benefit they are associated with, with a link to a view which lets them type in some evidence and attach any documents or photos which demonstrate what is going to be done or has been done so far.

5. When they submit that evidence for approval, the assigned Contract Managers will receive an email with a link to a view which lets them approve or reject the evidence. If they approve it, the submitter receives an email confirming that it has been approved. If they reject it, they must type in a reason why, and the submitter receives an email confirming that it has been rejected, including the reason why, and with a link to a view which lets them update their evidence and resubmit it.

6. Once all of the evidence for an Benefit has been submitted, the assigned Contract Managers will mark it as Complete. This will trigger an email to Project Managers and Suppliers but not Delivery Partners with a link to a view which lets them select a feedback score, type in an explanation for that score and attach any documents or photos which demonstrate how well the Benefit went.

7. When they submit that score for approval the same process happens as in step 5 above.

8. Once all of the Benefits associated with a Contract have been completed and have been given a score, and the main project associated with the Contract has been completed, an Admin or one of the assigned Contract Managers can then mark it as Complete.

At any point, after a Contract has been published, an Admin, Contract Manager or Project Manager can view its performance and Red / Amber / Green statuses on an intuitive dashboard; or download the information about the Contract or its associated Benefits by filtering the Download Contracts or Download Benefits views and clicking to download a spreadsheet file in the XLS or ODS file format.