Understanding the GeoCRM record model

This is the most useful page in these docs. GeoCRM keeps a lot of record types, and they nest inside each other in a specific way. Once you understand the shape, the rest of the application is straightforward.

The core chain

Client → Project → Job → Docket

• A Client is the company or individual you work for. Clients are either an Organisation or an Individual.
• A Project is a site. It has a project number (for example 12274) and a site address. A client usually has several projects.
• A Job is a scheduled piece of work at a project. It has a job number (for example #13167), a start and end time, and an assigned crew. A project usually has several jobs.
• A Docket is created automatically with every job. It is the field record — work entries, photos, time on site — and it is what gets signed, reported on and invoiced. One job, one docket.

The important thing to remember: you don't create dockets. Creating a job creates its docket for you.

Records that hang off a job

Depending on the kind of work, a job also produces:

• Ground Log (GL-13159-01) — a subsurface investigation. One ground log holds several investigation locations: boreholes, trial pits, CPTs and monitoring wells.
• DCP Test (DCP-00003) — a dynamic cone penetrometer field record. It can stand alone or be linked to a ground log.
• Work Request (WR-4001) — a laboratory job. It holds samples, and each sample holds worksheets (the individual tests).

Records that sit above the work

• Calculation (CALC-00005) — a saved engineering design check, such as a bearing capacity assessment. Calculations keep a full revision history.
• Report (RB-12272-001) — a document built in the Report Builder that assembles narrative, calculations, logs, test results and images into something you can issue.

Numbering reference

You can paste any of these numbers into the global search to jump straight to the record.