Part 5 — Reference · Chapter 5.4

Glossary

This page defines the manual’s terms in alphabetical order. Where two words are easy to confuse, the entry says which one the manual and the product use.

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 1.4.

Adjust Quantities. Changing the part quantities, and the unit costs, of one Assembly line on one work order. Parts cannot be added or removed this way, and the change never reaches the Assembly in the catalog. Chapter 3.4.

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

Assembly. A recipe an estimator adds to a quote in one step: materials, labor by service, and other Assemblies, each with a quantity. It has no price of its own. Each part is priced on the work order’s rates, and the Assembly’s price is the sum. Other estimating tools call this a kit or a bundle. Chapter 2.7.

Assembly category. A folder in the tree that organizes Assemblies, such as Residential › Receptacles. It has no effect on price. Not the same as a rate category, which sets a material’s markup. Chapter 2.7.

Assembly line. One use of an Assembly on a work order’s quote or invoice. It keeps its own copy of the recipe, taken when it was added. The customer sees its Customer Description, split into a labor price and a materials price. Chapter 3.4.

Assignment. Placing a technician or an assignable asset on a work order’s schedule entry. Also called dispatch. The manual does not call this scheduling; see Asset scheduling. Chapter 3.2.

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

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 3.6.

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 3.6.

Audit trail. A record’s change history: who changed what, and when. Every major record has one, and Setup has one for company settings. Chapter 3.9.

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

Combine. Merging a duplicate customer into the one you keep. The duplicate’s sites, work orders, payments and other records move across. Reverse Combine undoes it. Chapter 2.4.

Comment prefill. Stock comment text a user inserts instead of typing it. Chapter 2.1.

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

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

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

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

Department. A group of office staff, set under Setup › Details. A workflow sent to a department waits there for anyone in it. Chapter 2.2.

Deliverable. A required document, defined by name, that BigWave tracks until each work order (or asset) has it. Chapter 2.8.

Delete (customer or site). Removing a record made in error. Offered only when a customer has no work orders or payments, or a site has no work orders. Combine records that have history. Chapter 2.4.

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

Duplicate detection. The check BigWave runs when you add a customer. It compares address, customer ID, name (with nicknames) and phone, and you decide what to do with any match. Chapter 2.4.

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

Issue. A punch-list item logged on a work order and sorted by the project’s issue types. Chapter 3.8.

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

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 2.5.

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

Region. Two things share this name. A company region, set under Setup › Details, groups your territory; people assigned to it see its work under Region Assignments (chapter 2.2). A customer’s regions group that customer’s sites, under a label you choose for each customer (chapter 2.4).

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

Replace Part. Swapping one material for another in every catalog Assembly you leave ticked, each keeping its quantity. Assembly lines already on work orders keep the old material. Chapter 2.7.

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

Role. A named set of permissions. For each screen and panel it sets Show, Modify, Add and Delete, and it can hide single custom fields. Chapter 1.4.

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

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 2.4.

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

Status. The one value that says where a work order stands. Each project has its own list, copied at first from Status Defaults. Alerts and billing lists key off it. Chapter 2.3.

Status type. The stage a status belongs to: Planning, Quoting, Active, Completed, Billing or Closed. Chapter 2.3.

Status action button. A button in an email that moves a work order to a named status when the reader confirms it. Emailed quote approval uses it. Chapters 13, 18, 26.

Tag. A label on a work order, global or per project. The project’s Tags tab counts them. Use a tag for a fact about a job that isn’t a step. Chapter 2.6.

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 and sort order. A view can be shared and can open by default. Most quick reporting starts from one. Chapter 1.3.

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

Workflow. A request attached to a work order, project, asset or technician. Each step sends it to the originator, a department or the project team. Chapter 2.3.

Workflow type. The template for one kind of workflow: its steps, custom fields and opening text. Global or per project. Chapter 2.3.

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

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.