_One set of records with several applications over it: clients and sites, waste catalog, profiles, manifests, crew, billing, reports and configuration._ # From the client's contract to the certificate of disposal. Mercovi is one set of records with several applications over it. Here is how they relate — each box opens the page that explains it. ## The spine Client portal (request service, characterize waste, see jobs, manifests, invoices, pay) → Client · Site · Waste stream · Profile (MPDS) → HHW event / C&I pickup / Lab pack drum build → Manifest, computed from the waste codes, submitted and signed through EPA e-Manifest → Facility: receive → store (clock) → consolidate → ship → Certificate of disposal → Close-out → Bill → Report (the portal shows the client the same number). The spine: client, site, waste stream and profile set up once; four service lines — HHW events, C&I pickups, lab packs and PaintCare lines — run on them; the manifest is computed from the codes and carries its e-Manifest status; the facility receives, stores, consolidates and ships; the certificate returns; close-out creates the bill and the report. Each box opens its page. ## Eight records. One set of them. In the order they're set up. Each is a page of its own. - 01 — **Clients and sites** 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.)_ [Clients and sites](/platform/clients-sites) - 02 — **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. _(Screen: the waste catalog — one record per stream with its composed DOT shipping description, RCRA codes, cost per measure and designated facility.)_ [Waste catalog](/platform/waste-catalog) - 03 — **Waste profiles** A material profile data sheet per stream, kept as a record rather than a PDF in a folder — and started, for commercial clients, by the person who knows the material. _(Screen: a material profile data sheet (MPDS) — regulatory status, soil determination, chemical composition and physical properties; prints as the document a generator signs.)_ [Waste profiles](/platform/profiles) - 04 — **Manifests** Any RCRA code on a waste makes it a Uniform Hazardous Waste Manifest. Nobody picks the form from a dropdown, and the manifest tracking number lands back on the job. _(Screen: a manifest record — parties with EPA IDs, lines with codes and approvals, signatures, and the EPA e-Manifest status on the record.)_ [Manifests](/platform/manifests) - 05 — **Crew** The expired certification surfaces before the morning of the event, because its status comes from a date rather than from someone remembering. _(Screen: the crew list — capabilities and qualification status derived from each real expiry date.)_ [Crew](/platform/crew) - 06 — **Billing** One number, one source. The bill is priced from the client's own table, the report counts on the same basis, and the portal shows the client the same figure. _(Screen: a bill — Draft, Issued, Paid; each waste priced from the client's own table on the basis it bills on; PaintCare stated separately; lines locked on issue.)_ [Billing](/platform/billing) - 07 — **Reports** A report and an invoice describing the same work cannot disagree, because the report counts each stream the way that client is actually charged for it. _(Screen: a client report over a period — waste by stream counted on the basis the client is billed on, so report and invoice cannot disagree.)_ [Reports](/platform/reports) - 08 — **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. _(Screen: settings — wastes, containers, facilities, methods, qualifications, lab pack categories, floor plans and ordered storage-limit rules, all editable.)_ [Configuration](/platform/configuration) ## What is different about it. ### Configuration, not hardcoding. - Systems in this trade are built for one contractor and bent to fit the next. In Mercovi, your wastes, containers, facilities, management methods, billing methods, qualifications, lab pack categories, floor plan and storage limits are data you edit yourself. [Configuration](/platform/configuration) ### Templates flow into instances. - The site is set up once. Every job there starts from it, and the copy belongs to the job. The draft and the compliance record are never the same record. [Clients and sites](/platform/clients-sites) ### One number, one source. - The close-out creates the bill. The report prices that client's wastes at exactly what the bill charges. Neither is retyped from the other, so they cannot disagree. [Billing](/platform/billing) ### The paper comes out of it. - Manifest, profile sheet, dispatch sheet, load order, pack list, receipt sheet, bill and client report all print and download as PDF — outputs of the record, not assembled alongside it. [Manifests](/platform/manifests) ## The spine records, in the order they're set up. Four service lines and two modules on one set of records. The same waste stream, the same profile, the same facility, the same price, whether it arrived at a Saturday collection event, on a monthly plant pickup, or in a university stockroom. ### Clients and sites (Set up once) The client holds the terms; the site holds the templates. The client carries generator status, who the generator legally is — the client, the site, or the contractor — billing method, PaintCare participation, whether a certificate of disposal is required, bond, and the not-accepted list. Each site holds its own supply and equipment defaults by category, its manifest templates, photos, contacts and job history. [Clients and sites](/platform/clients-sites) ### Waste catalog (Set up once) Each waste is described once, and assembled rather than typed. One record per stream: the composed DOT shipping description — UN number, hazard class, packing group, proper shipping name — the RCRA codes, the EPA management method, the designated facility and its approval number, and the cost per measure (55 DF, 5 GAL, LB, LF). New streams start from a regulatory library, not a blank form. [Waste catalog](/platform/waste-catalog) ### Waste profiles (MPDS) (Set up once) The profile is the document a facility approves. A full material profile data sheet per stream: identity, the soil determination with its analytical tests, regulatory status, chemical composition, physical properties. It reads on screen, prints as the document a generator signs and a facility files, and downloads as PDF. A client's whole profile book comes out as one PDF. [Profiles](/platform/profiles) ### Configuration (Set up once) What is yours to edit. Wastes, containers, facilities, management methods, billing methods, qualifications, pay categories, lab pack categories, floor plan and storage limits are all settings you edit. No developer ticket to add a facility. [Configuration](/platform/configuration) ### Manifests (Run the job) The form is computed from the codes. Templates at the site become instances on the job. Any RCRA code on a waste makes it a Uniform Hazardous Waste Manifest. Continuation sheets when the lines run over. Transporters carry their state registrations with expiry dates. Each manifest carries its EPA e-Manifest status, submission method and tracking number on the record. [Manifests](/platform/manifests) ### Crew (Run the job) Each certification's status comes from its expiry date. People carry capabilities and qualifications, and each qualification's status — current, expiring, expired, missing — derives from its real expiry date rather than from someone remembering. Pay categories, groups, rates, travel. Invitations go out and come back accepted, declined or no-show, with candidates ranked by distance. [Crew](/platform/crew) ### Billing (Settle it) Closing writes the draft bill. Closing a job locks the counts and creates the draft bill, priced from that client's own table, waste by waste — some streams by the container, some by the pound, resolved per stream rather than by one label on the account. PaintCare stated separately. Bond applied. Draft → Issued → Paid, with lines locking the moment it is issued. [Billing](/platform/billing) ### Reports (Settle it) The report counts each stream the way the client is billed. Over any period, for one client or all, at one site or all: jobs run, manifests created, cars served, pounds collected, pieces by container, pounds by waste, the waste mix month by month. **Each stream is counted on the basis that client is actually billed on**, so the report and the invoice cannot disagree. CSV export; the client's copy prints as a document. [Reports](/platform/reports) ## Asked by evaluators. ### What does "one compliance spine" mean? The client, the site, the waste stream, the profile, the manifest, the facility, the container, the crew and the price are one set of records shared by every line and module. A stream characterized for a [lab pack](/lab-pack) job is the same record that prices a [C&I pickup](/commercial-industrial), prints on an [HHW](/hhw) manifest and carries a clock on the [floor](/facility). ### What is configured rather than coded? Wastes, containers, disposal facilities, management methods, billing methods, qualifications, pay categories, lab pack categories, floor plans and storage limits. Each is data edited in [settings](/platform/configuration): adding a disposal facility is a form with its name, EPA ID and approvals, not a developer ticket, and it is available on waste streams and manifests as soon as it is saved. ### How are templates and instances kept apart? A site holds templates — its supply and equipment defaults, its manifest templates. Each job started at that site gets its own copy. The draft on the site and the compliance record on the job are never the same record, so editing one never rewrites history on the other. ### Does Mercovi work with EPA e-Manifest? Each manifest carries its EPA e-Manifest status, submission method and tracking number on the record, so the MTN is found on the job rather than in an inbox. The [e-Manifest page](/e-manifest) explains how the system works and who signs what; the [compliance page](/compliance#emanifest) states exactly what Mercovi does with it, at the precision that is true. ### Is Mercovi installed on site? No. Mercovi is multi-tenant software: nothing to install and nothing to host. A contractor's organization, its clients, sites, wastes, profiles, manifests, crew and bills live in its own tenant, reached from a browser on the office desktop, the warehouse tablet and the phone in the truck. ## 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)