A contract is an agreement between the contractor and the landlord for the contractor to carry out specified work to agreed assets over a defined period. When adding new contracts onto the system only a minimal amount of mandatory information is required in order to save the core record. Additional information can be appended to the record at any time, as required, although maintaining comprehensive information from the start will reap its own rewards. There are numerous fields that can be stored against each contract and these are combined into logical data tabs. A summary of these data tabs is outlined in the table below:
Field Group |
Description |
Details |
This tab stores the name of the contractor, the contract description, the effective companies, the appointment mechanism supported by the contractor (e.g. on-line diary system) and the default cost appointment (e.g. All to first task, Evenly, Percentage proportion). |
Parameters |
This tab sets minimum and maximum order values that the contractor is able to fulfil within the terms of the contract together with how many concurrent jobs can be active (by order value or number of jobs). |
Pricing |
This tab controls the pricing and inspection rate charges that are permitted against a Schedule Of Rates (SOR) plus any exceptions that are permitted under the terms of the contract. Where a pricing rule is not configured for a specific contract, the default SOR charges will then apply to all related works orders. |
Definition |
In setting up a contract, rules can be applied in the repair contract definitions to specify the nature and scope of the work that will be carried out by the contractor. The scope comprises the relevant trades, repair types, repair priorities and inspection types that will be covered within the definition, and specifically the Schedule Of Rates. Multiple contract definitions can co-exist and therefore the end user has full flexibility on controlling the overall contract definition. |
Rules |
Whilst not mandatory, rules can be defined to inform the award process for a contract. |
Activity |
This tab provides a summary of how individual contracts are progressing. |
Note
For each sub-section of data, the user must record an Effective from date to confirm when the information becomes active; an Effective to date can also be inserted to confirm when the information expires or to reflect a known change of circumstances.
See related topics...
To define contract pricing rules