Environmental consulting roll-ups: merging EQuIS, lab and field data

Which systems does each add-on bring?#

Each environmental add-on brings its own mix of systems: an EQuIS database or another environmental data management system, electronic data deliverables from contract laboratories, field apps or paper forms, boring log software, GIS projects and years of project files. Founder-owned firms often add a home-grown Access database or one spreadsheet per site, built by a senior scientist who knows every quirk.

The first integration task is a system-by-system inventory for each add-on, with an owner, the clients and sites covered, and an integration action for each system.

Rights by legacy contract#

Rights over environmental data are set contract by contract, and in most consulting work the client owns or controls site data and deliverables while the consultant keeps working files. Some agreements require data to be returned or destroyed at project end, some restrict use for other clients, and public agency contracts often specify data formats and records obligations of their own.

Merging databases across add-ons without this check can put one client's site data in front of staff working for another, or keep data a contract said should have been returned. The rights register should be built from the contracts, not from memory.

Building the unified schema#

A unified schema is the set of shared rules that makes results from different add-ons mean the same thing. Without it, the same analyte appears under three names, the same well under two IDs, and results reported in different units sit side by side in one table.

Build a crosswalk for each add-on instead of editing its original records. The crosswalk translates old codes to platform codes, so the source data stays intact and every translation can be audited later.

• 1Location and sample ID conventions, including how legacy IDs are preserved.
• 2Analyte names tied to CAS numbers, with one preferred name each.
• 3Units and conversion rules, applied on load rather than in the source.
• 4Detection limits, reporting limits and data qualifiers, with definitions.
• 5Analytical method codes and laboratory identifiers.
• 6Coordinate systems and datum for every location.
• 7Validation status, so reviewed and unreviewed results are never mixed silently.

Retention and the read-only archive#

Retention for environmental records is set by the longest of the applicable client contracts, program requirements and laws, so the archive policy has to be built from the rights register rather than a single company rule. Industrial hygiene files deserve their own flag: under OSHA's records access standard, employee exposure records and analyses must generally be retained for at least 30 years, and client agreements may ask the consultant to hold copies.

The read-only archive keeps original database backups, lab EDDs and PDF reports, field forms and GIS projects for each retired system, indexed by client, site and project. Access follows the client, so a project manager working for one client cannot browse another client's archived sites.

The integration checklist for each add-on#

The integration checklist applies the same order to every acquisition, which keeps a buy-and-build platform from relearning the same lessons with each firm.

Loading active sites before closed ones matters for clients with ongoing monitoring programs. Their next sampling event will be reported from the platform system, so trend charts, comparison criteria and report templates have to work on day one. Closed sites can wait for the archive, where nothing needs to be recalculated.

• 1Inventory systems per add-on with owner, clients, sites and date coverage.
• 2Build the rights register from each legacy client contract and task order.
• 3Set retention for each client and program, and place legal holds where needed.
• 4Write the crosswalk from the add-on's codes to the platform schema.
• 5Load active sites first, validating against original EDDs and lab reports.
• 6Archive retired databases and project files read-only with client-level access.
• 7Close old licenses and accounts only after the archive is verified.

Illustrative: a groundwater firm and a remediation firm join one platform#

Illustrative: a fictional environmental platform acquires a groundwater consulting firm that runs an Access database built by its founder, and a remediation contractor with a consulting arm on EQuIS. Both firms have sampled some of the same industrial sites for different owners over the years.

The operating partner orders the rights register before any data moves. It shows that several private client agreements require return or destruction of data at project end, and that one agency contract specifies its own deliverable format. Active sites are loaded into the platform EQuIS instance through crosswalks; closed sites stay in read-only archives under client-level access. The shared industrial sites are kept as separate client records, not merged, because each owner controls its own data.

Where SourceX fits for environmental firms#

Client site data is usually outside what an environmental firm can license, so SourceX's Rights step focuses on records the firm itself controls: QA and QC procedures, internal project reviews, proposal libraries, method decision memos and project management histories with client details removed. Client-controlled datasets are carved out unless a contract clearly allows otherwise.

Each package moves through the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, with a SourceX Evidence Packet recording provenance, licensing rights, permitted use, the privacy record and release authorization. Nothing is shared during the initial assessment.