ClickHome manages job data as a set of jobs all related together. The Master Contract record is used to group, all the various job types together. Each Master Contract (contract group) can have 1 of each of Land, Lead, Preconstruction and Construction. Additionally, there can be an unlimited number of maintenance jobs.
If you are using Projects, then the Master Contract can have parent and children Master Contracts.
This is what the data model looks like:
There are a large number of fields against the jobs.
Field | Description |
| Job Type | See Job Types |
| Contract No | Job Number, Contract Number, You know... |
| Common Name | Usually same as the Contract No, but can be changed for convenience of other staff like Supervisors eg Lot Number Client Name is a commonly used alternative |
| Contract Status | See Job Types and Contract Statuses |
| Scheduling Status | Controls how Purchase Order Processing is handled |
| Contract Type | The list of values for Contract Type can be customised - this is consistent for all contracts belonging to the same Master Contract |
| Category | This list of values for Category can be customised - and you can have a different list for each job type. |
| Sales Status | This is used for Spec Sales to determine which jobs appear in the inventory in Spec Sales |
| Client | The client - this could be a family or organisation - each client can have multiple contacts (individual person) |
| Template | The template represents a set of tasks, sequencing, workflow, conditional logic etc. The template tasks are copied to the job when the job is first created, and can be updated if the template changes. You cannot change the template once the job is made. |
| Business Unit | All contracts that form part of the same Master Contract have the same Business Unit |
| Region | Different Job Types have different Regions. |
| Supervisor Status | Supervisor Status works with fields Supervisor 1, 2 and QC to determine who has control or responsibility of the construction and maintenance jobs |
| Supervisor 1 | |
| Supervisor 2 | |
| Supervisor QC | |
| Contract Admin | This can be configured to confer responsibilities for managing the job (at any phase, but typically) during the preconstruction. |
| Sales Person | |
| Referral Source | Referral source is part of marketing. Referral source is used to record why the client to engage with you - eg what influenced them, an advertising campaign, radio, internet advertising, seeing a display home, a sales person etc. |
| Referral Contact Point | Referral contact point is also part of marketing, but this is used to record how they engaged with you - eg your call centre, a display home. your web portal. |
| House Type | The house type the client is interested in (Leads), or that you are building (Preconstruction, Construction), or fixing (Maintenance) |
| Façade | The facade for the house |
| Council | The local government for the location where the house is being built. |
| Estate | The estate where the house is being built, if applicable. |
| Stage | Each job type has a list of stages, every task in the job must belong to a stage. eg in Construction it might be Earthworks, Slab, Bricks, Frame, Roof, Fixing, Handover |
| Summary | Summary is also Milestone |
| Contact | This can be used to refer to one person (contact) of the client that should be used for handling discussions, especially when an organisation or company as the client, or when the family may need language assistance. |
| Project Code | Mostly used for reporting |
| Priority | Used for sorting job lists, and managing hot and cold sales leads. |
| Contract Value | Changes from an idea of a budget during Lead to the actual contract value in Construction |
| Lot Address | The physical address of the construction site. |
| Standard Directions | Any special directions that should be communicated to all trades, suppliers and supervisors to help them navigate, especially where online maps are inaccurate. |
| Standard Instructions | Any special instructions that should be communicated to all trades, suppliers and supervisors - eg Ensure the gate is locked on the main road. |
| Baseline Complete | See baselines and forecasting - not quite perfect world scenario - but based on the standard settings and durations, when the job will complete. |
| Client Advised | A date you should be able to advise the client when they can move in. |
| Start Schedule | When the job was considered started by your company. |
| Estimated Complete | Forecast completion - accounting for delays, slippage and even gaining ground using faster teams or an aggressive schedule. |
| Estimated Client Move In | When the system calculates should be the client move in date. |
| Last Activity Date | Last Activity is a customisable concept, you can determine what actions count as activity, task completion or schedule, adding a note etc. Can also be combined with standard actions to perform on in-active leads. |
| Target Start Date | Can be used to control forecasting of jobs that have not yet started, such as planning out a large project. |
| Target End Date | |
| Sales Person Assigned Date | A record of when the sales person was last changed. |
| Latitude | |
| Longitude | |
| Notes | Notes against the job - this can be used as bucket of additional info that does not fit elsewhere. Not to be confused with other notes where there are many records my many users representing a discussion over time. |
| 10 User Defined Fields | Not shown in the front end, but in the back end there are 10 user defined fields that can be used for reporting and or integration with other systems. |