Getting Started
Project types available in Jobpac
An overview of the main project contract types in Jobpac and when to use each one.
Overview
Jobpac supports several different project contract types. Each type has its own settings in job maintenance and can use different processes for budgets and progress claims.
Choosing the right project type helps ensure that budgeting, revenue recognition and progress claiming align with the contract structure.
Project contract types at a glance
| Type | When to use |
|---|---|
| Lump sum | Fixed price contract for an agreed scope of works. The default type if no other option is selected. |
| Schedule of rates | Contract based on an agreed list of items and rates. Requires additional configuration and training. |
| Cost plus | Client pays actual costs plus an agreed margin or percentage fee. |
| Small order | Revenue is directed to cost centres rather than the project as a whole. |
Note: Property development projects are also available in Jobpac but should only be used when a consultant who understands this process is available to guide the setup.
Lump sum projects
Lump sum is the default project type. The contract is for a fixed price and agreed scope of works, with changes handled as variations.
- Contract value, contract margin and contract budget are entered in job maintenance before the budget is finalised.
- A work breakdown structure is created, cost centres are assigned and the budget is spread over cost centres.
- Supports earned budget with options to use cost code sub items and cost centres only.
- Uses the standard progress claim module to set up a claim structure.
Suitable when scope and price are clearly defined and variations are the main mechanism for change.
Cost plus projects
Used when the client agrees to pay the actual cost of the work plus an agreed percentage or fee.
- In job maintenance, mark the project as a cost plus project.
- Enter a mark-up percentage for transactions if required. These settings are carried through to each cost centre created for the project.
- Cost plus projects operate similarly to lump sum for subcontracts, purchase orders and standard forecasting. The main difference is in progress claiming — cost plus projects use a dedicated cost plus progress claim process.
Important: Only mark a project as cost plus if you intend to use the cost plus progress claim process. If you are not using cost plus claims, treat the project as a standard lump sum project.
If cost centres are created before the cost plus flag is set, existing cost centres will not be automatically updated. A utilities function can be used to update them if needed.
Small order projects
Used when revenue is directed to cost centres instead of the project as a whole. Individual orders or activities are represented using cost codes within an overarching small order job.
- Revenue is directed to cost centres — not to the job number as with most other project types.
- There is usually one cost type used for revenue on these projects.
- Overall contract value, project budget and margin are not entered in job maintenance — they are built up from cost centre budgets and revenue.
Revenue controls are managed in cost type validation and related setup screens.
Schedule of rates projects
Used when the contract is based on an agreed list of items and associated rates rather than a single lump sum. Contract value, overall budget and margin are built up from item maintenance or uploaded schedules of rates.
Processing is significantly different from standard lump sum projects — schedule of rates projects use different progress claim, forecasting and variation functions.
Warning: Schedule of rates projects require additional configuration and training. Do not adopt this project type without appropriate guidance and understanding of the specialised processes.
Training and eLearning
eLearning
Project Setup
Choosing the right project type
The project type you select influences how you:
Comments
Article is closed for comments.