(Refer to section 6.4 of the Partnerships Victoria Contract management guide for more information.)
The suggested structure for the obligations register is outlined below.
Obligation/issue/ risk | Who? | What? | How? | Status | |
Example: Government party to provide unencumbered land for the project | Confirm that all land required for the project has been acquired and that all interests in that land have been extinguished | By [time/date] (occurrence: once only) | Liaise with [ ]; etc. | Contacted [ ] on [date]. [ ] will check status and respond by [date]. | |
Example: Accuracy of private party's service performance data | Spot check performance data against other information on KPIs | Each calendar quarter (Occurrence: Recurrent) | Review records of end users of services etc. | To commence upon commencement of service delivery phase | |
Example: Serious service delivery interruption occurs | Implement business continuity plan | Within [time] of becoming aware of interruption (occurrence: incident based) | Refer to separate business continuity plan | Service delivery has not commenced | |
etc. |
|
|
|
|
|
Note 1: Identify when the action must be completed, and whether it is required once only, recurs at fixed or variable intervals, or must occur in response to specific events or incidents. Doing this will assist the contract director in identifying actions that remain relevant when the table is updated.