Part 4 — Reference · Chapter 27

Glossary

The manual’s terms, defined once, alphabetically. Where two words get confused, the entry says which one this manual, and the product, means.

Access level. What kind of user a login is: internal, technician, customer, site, partner, and the purchasing-side levels (supplier, warehouse, shipper). A login can hold several. Chapter 4.

Alert. A project-defined notification: a trigger (event or timer) plus recipients plus an email. Chapter 13.

Assignment. Placing a technician or an assignable asset onto a work order’s schedule entry. Also called dispatch. Deliberately not called scheduling; see Asset scheduling. Chapter 16.

Asset. A piece of equipment registered at a customer site, with its own custom fields, documents, and histories. Chapter 20.

Asset scheduling. The engine that automatically generates recurring maintenance work orders for assets on a cadence. The only thing this manual calls “scheduling” besides a work order’s own schedule entries. Chapter 20.

Asset type. The class an asset belongs to, defining its fields, statuses, standard documents, and whether its assets appear as resources on the calendar. Chapter 20.

Audit trail. The per-record change history: who, when, what. On every major record. Chapter 23.

Billing address. One of possibly several addresses a customer can be invoiced through. Chapter 8.

Combine. Consolidating a duplicate customer into the one you keep, moving all children across. Distinct from Delete. Can be undone with Reverse Combine. Chapter 8.

Comment prefill. A canned comment text insertable instead of typing. Chapter 5.

Contract. A project’s billing arrangement: its rate schedule and default rate. Chapter 11.

Credit memo. The document that adjusts an invoice downward after the fact. Chapter 19.

Custom field. A field you define on a record type, at global or narrower scope, grouped and role-restrictable. Chapter 10.

Customer. Who you do work for; a business or an individual. Owns sites. Chapter 8.

Deliverable. A required document, defined by name, tracked to completion per work order (or asset). A document is whatever got uploaded; a deliverable is a named obligation. Chapter 12.

Delete (customer or site). Soft removal, offered only for records with no work order or payment history. Records with history are combined, not deleted. Chapter 8.

Document template. A Word file with merge fields, generated into a filled document from a work order. Chapter 12.

Duplicate detection. The advisory check at customer creation matching on address, ID, name (nickname-aware), and phone. Chapter 8.

Field code / merge field. The bracketed tokens resolved with live data in templates, emails, and filenames. Chapter 26.

Issue. A logged punch-list item riding a work order, categorized by project-defined issue types. Chapter 22.

Partner. A company you exchange work with, holding its own contacts, technicians, and portal access. Chapter 21.

Project. A line of work in your business, carrying the statuses, fields, templates, rates, and alerts that work obeys. Can be dedicated to one customer when that customer’s work genuinely runs differently. Chapters 1 and 9.

Project manager. The designated owner on a project’s team. Chapter 9.

Rate. An agreed price for a service, held in a project’s contract. Chapter 11.

Region. A customer-defined grouping of sites (the label is customizable per customer), driving region assignments for dispatchers. Chapter 8.

Report window. A named recurring period used to slice recurring reporting consistently. Chapter 23.

Reverse Combine. Undoing a combine, restoring the folded-in customer as its own record with the children that moved. Chapter 8.

Role. A named permission set: per-screen read/create/update rights plus custom field restrictions. Chapter 4.

Schedule entry. When a work order (or its activity or task) is planned to happen, with scheduled and actual dates kept separately. Chapter 16.

Site. A physical location belonging to a customer, keyed by the customer’s own Site ID. A second property is a second site, not a second customer. Chapter 8.

Site tracking. A project’s pipeline view: work orders counted by status. Chapter 22.

Status. The single value saying where a work order stands, defined per project (seeded from Status Defaults), driving alerts, billing, portals, and pipelines. Chapter 7.

Status action button. An emailed link that, once confirmed, moves a work order to a named status. The engine of automated quote approval. Chapters 13, 18, 26.

Tag. A label on a work order, global or per project, counted by the Tag Report. A flag, not a step and not data. Chapter 10.

Technician. A person assignable to work, employee or partner-side, with their own record, badge, rates, and time off. Chapters 6 and 17.

Time category. The classification of entered time (standard, overtime, and kin) that prices labor correctly. Chapters 11 and 17.

View. A saved grid layout: columns plus sort, optionally shared and initial. The unit of ad-hoc reporting. Chapter 3.

Work order. One job at one site, tracked from creation through payment, and the record almost everything else attaches to. Chapter 15.

Workflow. A process instance riding a work order, project, asset, or technician, routing between originator, department, or project team queues per its workflow type. Chapter 7.

Work order template. A per-project pre-fill for new work orders: description, dispatcher notes, deliverables. Chapter 9.

A historical note: integrations with the legacy Work Market marketplace still exist behind an integration flag for companies that used them; new setups should ignore them.