Core concepts

Everything in Elevate Team is one of seven records. Learning what each one means makes the rest of the product, and the API, predictable.

Client

A person or an organisation you bill. Holds contacts, billing details, tax treatment and a payment history. A client has one or more properties.

Property

A place work happens. Holds an address, access notes, equipment and the history of every visit made there. Properties belong to a client, and a property can move to a different client without losing its history.

Request

An inbound ask for work, from any channel: email, web form, phone note or the client portal. A request has a status and an owner. It becomes a quote or a job, or it is declined, which is also an outcome worth recording.

Quote

A priced proposal built from offerings. Quotes carry optional and alternative line items, an expiry, and an e-signature when accepted. An accepted quote creates a job.

Job

The unit of work you are paid for. A job holds the accepted quote, one or more visits, the parts consumed, the photos and notes, and the invoices raised against it. A job is not a calendar event. A job that needs a diagnosis today and a return with a part next week is one job with two visits.

Visit

A scheduled appearance by a crew at a property, on a date, for a duration. Time entries, checklists and photos attach to a visit. Visits are what the schedule board moves around.

Invoice

A demand for payment against a job. An invoice can cover a whole job, a phase of it, or a deposit taken before work starts. Payments attach to invoices, and invoices attach to jobs, which is what makes revenue-by-job reporting possible.

How they connect

Client
└── Property
    └── Request  →  Quote  →  Job
                              ├── Visit ── Time entries, checklist, photos
                              ├── Visit
                              └── Invoice ── Payment

Every screen in the product is a view of some slice of that graph, and every API endpoint addresses one of those nouns.