_The client carries generator status, billing method, PaintCare and the certificate requirement. Each site holds its defaults and templates; jobs inherit them._ # Set the client and its sites up once. Every job inherits it. The client is where the terms live. The site is where the templates live. A job at that site starts as a copy of both, and the copy belongs to the job. _Screen: a client profile — generator status, who the generator legally is, billing method, PaintCare, certificate of disposal requirement, and sites with their own defaults and manifest templates._ - **The client carries the terms.** Generator status — VSQG, SQG, LQG — and who the generator legally is: the client, the site, or the contractor. Billing method. PaintCare participation. Whether a certificate of disposal is required on the bill. The bond, and the not-accepted list. - **The site carries the templates.** Supply and equipment defaults by category, manifest templates, photos, contacts and the job history at that address. Every event, pickup or lab pack run there starts from these. - **Templates flow into instances.** The job's supplies, equipment and manifests are the site's templates, copied. Editing the site later never rewrites a closed job; editing the job never rewrites the site. - **One client, every line.** A client is a client whether it runs collection events, monthly plant pickups or a lab pack. Its sites, wastes, profiles, prices and bills are one set of records across all of them. ## The client record, with its sites. Generator status, who the generator is, billing method, PaintCare, the certificate requirement, the not-accepted list — and each site with its own defaults and manifest templates. _Screen: a client profile — generator status, who the generator legally is, billing method, PaintCare, certificate of disposal requirement, and sites with their own defaults and manifest templates._ ## Questions ### Who is the generator on a manifest for an HHW event? It depends on the contract. The client record says who the generator legally is — the client, the site, or the contractor — and the manifest is built from that, so nobody decides it on the morning of the event. ### What does a site hold? Its supply and equipment defaults by category, its manifest templates, its photos, contacts and job history. Every job at that site starts as a copy of these, so the load list and the [manifests](/platform/manifests) for the next event are already drafted before anyone types; what changed on the day is edited on the job, not on the site. The eight records: [Clients and sites](/platform/clients-sites) · [Waste catalog](/platform/waste-catalog) · [Waste profiles](/platform/profiles) · [Manifests](/platform/manifests) · [Crew](/platform/crew) · [Billing](/platform/billing) · [Reports](/platform/reports) · [Configuration](/platform/configuration) - ‹ Previous — **Configuration** Systems in this trade are built for one contractor and bent to fit the next. In Mercovi, the things that differ between contractors are settings. [Configuration](/platform/configuration) - Next › — **Waste catalog** The catalog is where a waste is described once — its shipping description, its codes, where it goes and what it costs per measure — and then used by every line. [Waste catalog](/platform/waste-catalog) ## See it run a job end to end. Tell us what you run — events, plant pickups, lab packs, a floor — and we'll show you the screens that matter to you. [Book a demo](/demo)