# Glossary > Every term Open ADMS uses, in its exact meaning - from active window to zone. Source: /docs/reference/glossary/ The words below are used in exactly these meanings, across the product, the API and these pages. | Term | Meaning | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Active window** | A project's start and end dates. A ticket outside it is flagged "project not active", judged by a load's time (its collection's end) | | **Assignment** | One person's work for one day: a project, their work (ticket types, unit rate pay items, certifying), one site where the work is at one, optionally a phone. Written on the dispatch board, or on the phone with the master passcode when there is none (an _unplanned assignment_, marked). Never expires, never stops work | | **Audit record** | One entry in the append-only audit log: a change's prior and new values, who, from where and why, written by the database itself | | **Badge** | Carries the cert number; scanned at **New** to load the truck's or crew's certification | | **Certification** | A one-time inspection of a **container** (measured, capacity in CY, five photographs) or a **crew** (not measured), never a vehicle. Never ends on its own; tag expiry, revocation and replacement flag later tickets | | **Cert number** | One number: cert = placard = badge. Issued from the project's series or taken from pre-printed paper; unique per project; copied onto every field event | | **Citizen drop-off log** | A record, not a ticket, that a resident dropped debris at a site. No quantity, number or cost | | **Client** | The jurisdiction or agency paying for cleanup, such as Bayline County. A record, reused across disasters | | **Client package** | The deliverable: a project's final tickets, photographs, receipts and transactions, assembled by hand from the exports and zipped. There is no invoice record | | **Client user** | A read-only viewer login that belongs to a client | | **Completed load / haul-out** | `CLT` / `CHO`: the record the worker concludes from a ticket's field events. Not an event itself; the only load record that is QC'd and locked | | **Contract** | A name, its prime and an optional link to the signed copy. A rule names one and runs only on its prime's tickets | | **Contractor** | A hauling company: a **prime** holds a contract; a **sub** works under one prime, at most two tiers, typed in at certification | | **Control ticket** | A pre-printed, barcoded ticket number, from ranges entered at setup. The alternative is numbers the phones make, in blocks | | **Crew time** | A unit rate ticket listing items with hours to the quarter hour; it bills the highest item's hours, once | | **Debris type** | What a load or haul-out monitor picks on Complete, at both ends: an entry on the project's form, named as the contract names the work (Vegetative, C&D, Mulch…). A difference between the two field events is flagged | | **Declaration event** | The disaster and its reference, such as Hurricane Delphine, `DR-9001-FL`. One shared record; many clients' projects point at it. Never shortened to "event" | | **Dispatch board** | The back office's daily plan of assignments | | **Disposal site** | Where debris legally goes: a site type (TDSR/DMS, Final Disposal, Transfer Station, Other) plus its facts (_Takes loads_, _Haul-outs leave here_, _Charges a tipping fee_, _Ineligible site_), a permit, GPS, an area and its dates | | **FDS / TDSR** | Final disposal site / temporary debris staging and reduction site (DMS means the same). Debris is reduced at a TDSR and hauled out to an FDS | | **Field event** | What one monitor records under a ticket number: collection `COL`, disposal `DIS`, haul-out collection `HOC`, haul-out disposal `HOD`, unit rate `URT`. The evidence: never edited by the monitor after submitting, corrected in place by permission | | **Field monitor** | A field observer who records field events on an enrolled phone; has a system **Monitor ID** such as `M004127` | | **Field tag** | A project list the firm fills (such as _Mixed_), read by the _Field tag_ rule criterion and exports. No phone asks for one | | **Firm** | The organisation that installs Open ADMS and runs its own installation, usually a debris monitoring firm | | **Flag** | How every problem is raised after setup: a plain message ("Ticket 101008: debris type mismatch. Flagged for review."), never a refusal. Fixed, or accepted with a reason | | **Form** | What a project uses for one kind of document (load, haul-out, unit rate, truck certificate, ROE, survey, incident, drop-off log); debris types are added to it | | **Haul-out** | The second leg: debris leaving a TDSR for final disposal, its load call taken at the loading end | | **Installation** | One firm's running copy of Open ADMS | | **Invoice lock / batch** | Locking QC Approved tickets as invoiced, optionally in a named batch. A locked ticket is unlocked, audited, before any change | | **Load call** | The percentage of a container's certified capacity a monitor sees filled, a whole number 0–100. Billable CY = capacity × load call | | **Login list** | The sign-in checks a set-up phone holds for its project's monitors, for signing in offline | | **Master passcode** | One per firm: it enrols and sets up phones and opens the supervisor's actions | | **Mileage** | The road distance of the shortest route on public roads from the collection's end to the disposal site's own GPS, from the installation's own routing server; with no route, the straight line, flagged | | **Pay item** | A priced line of the contract as set up: its code (unique on its project), its description, payable type, unit of measure, size band, capture settings and a rate for each prime. The only place a rate lives | | **Payable type** | The work a pay item prices, from the firm's list (Vegetative, C&D, Hangers, Stumps, Crew time, Tipping fee…) | | **Preload** | A load collected one day and dumped the next. Normal, not flagged; it counts on its collection's day | | **Program type** | The kind of work (ROW, PARKS, PPDR, WATERWAY, the firm's own), each with a _Requires ROE_ setting | | **Project** | One body of work for one client under one declaration event: the hub everything hangs off | | **QC status** | QC Review, QC Approved, QC Issues, QC Void: the back office's own mark, set by hand, separate from the status | | **Quarantine** | Where a sync puts a second field event of one kind on one ticket: kept in full, for a person to resolve. Never dropped | | **Read-only viewer** | A client user, a contractor user or an auditor, who reads but never changes | | **Reconciliation** | The worker's run: group a ticket's field events, check them, attach zone and mileage, price, write | | **ROE** | Right of entry: a record (number, parcel, owner, signed date, scope, photograph); on a project whose program type requires it, every collection, unit rate ticket and survey carries one | | **Rule** | The firm's pricing, per form: one contract, its criteria, and actions _Add transaction #n_, _Remove transaction #n_, _Void ticket_. All passing rules run in # order | | **Scale receipt** | The paper a final disposal site's scale house hands the tower; not a ticket. Hand-transcribed, only where the contract pays by weight | | **Split load** | One truck gathering from several properties: collections `-A`, `-B`… and one disposal on the base number; each property's share priced on its own | | **Status** | `PENDING`, `COMPLETED`, `MANUAL_REVIEW`, `VOID`. Review still bills; only a person (with a reason) or a rule voids | | **Stump** | A unit rate ticket: diameter two feet up (under 24 in flagged), root-ball diameter, half or more exposed; paid by the stump or by the fill | | **TBN** | To be negotiated: a pay item whose price isn't agreed; it bills nothing until it is | | **Ticket** | A ticket number and the field events recorded under it. Paper and printouts are receipts, never records | | **Time clock** | An optional per-project add-on for workers' own hours, on their assignment; never related to crew-time billing | | **Transaction** | One priced line created by a rule: pay item, quantity, the named contract's prime's rate, prime and operating sub. Regenerated when its ticket changes | | **Unit rate work** | Work billed per each, per pound or per hour rather than per load: one monitor, one place, one ticket, no pairing | | **Zone** | A named shape on the project's map. No monitor records it: reconciliation attaches it from the GPS |