Tracking site assessment projects for firms running several at once

The juggling reality

Site Assessment projects don't run on flexible deadlines. The same structure that makes them repeatable: a standardized process, a defined scope, is what makes their timing rigid. Running several of these at once means running that rigid timing several times over, for different clients, on different clocks.

One person usually carries both sides of that work. As a field scientist, their hours are the cost of doing the job: time spent on-site, samples collected, the work itself. As a PM, their job is the opposite: knowing the specific details of each assignment, which deadline is closest, what's still pending, what's already been sent to the client. Fieldwork asks them to do the work. The PM role asks them to track it. Below 50 employees, one person is usually doing both, with no separate PM standing next to them to split the load.

Two clocks, not one

The regulatory clock

Under ASTM E1527-21 and the EPA's All Appropriate Inquiries rule, five components of a Phase I ESA (interviews, environmental lien searches, records review, site visit, and the environmental professional's declaration) have to be completed within 180 days of closing. Miss that window and the liability protection the assessment was meant to secure doesn't apply. The buyer loses the legal defense that they didn't know about contamination on a site they now own. The firm isn't just late delivering a report. The client closes without the protection they paid for.

The transaction clock

Layered on top is the deal's own closing date, set by the buyer, the lender, or both. When that date moves up, the Phase I has to move with it. Standard turnaround runs two to four weeks. Compressing that window usually means a rush fee, and rush work stacked across several concurrent jobs is where a schedule starts to slip. If any of the five AAI components were completed earlier and the closing date shifts, they may need refreshing within the new 180-day window, one more thing to catch before delivery, not after.

Together, these two clocks mean a Site Assessments PM isn't tracking one deadline per job. They're tracking two, running on different rules, for every job in motion at once.

A quick check for what's actually at risk right now; run it against every engagement currently open:

• Are all five AAI components, interviews, environmental lien searches, records review, site visit, and declaration, on pace to stay current inside the 180-day window
• Does the closing date on file still match what the client last confirmed, and if it moved, do the components completed earlier still fall inside the new 180-day window
• If either clock has less than two weeks of room left, is a rush surcharge already on the table with the client, or still a surprise waiting to happen

Same shape, different site

Fixed-fee Phase I work runs on a fixed template: the same report sections, the same billing codes, the same line items, project after project. That template is what makes the pricing model work. It's also what removes the natural friction that would otherwise stop a mix-up. A project with a different scope, different deliverables, or a different invoice structure forces you to slow down and check which one you're in. A project that looks procedurally identical to the last three doesn't. There's nothing about the file itself that signals "this one's different," because on paper, structurally, it isn't.

Hours logged against the wrong site, or expenses filed under the wrong client, happen because the thing that makes the work efficient, the sameness, is also the thing that would normally cue a person to pay closer attention.

After the engagement closes, the deadline still matters

A closed engagement isn't necessarily a finished question. A lender's audit, a new deal on the same site years later, a dispute over what was found and when, any of these can send someone back looking for proof the work was done, and done on time. At that point, the report itself answers what was found. It doesn't answer whether the deadline was met, or what the engagement's timeline actually looked like.

That's a different record than the report. It's a status history: when each phase happened, whether the window closed on schedule; that has to survive as long as the report does, not just while the job is active. For a PM already juggling several live engagements, keeping that history intact for the closed ones too is easy to deprioritize, since it's not what's due this week.

One view, every engagement

Running both sides of this work, the science and the schedule, needs one place where every live engagement shows its actual position against its deadline, and every closed one still shows its timeline when something sends someone looking for it. EVX Software tracks both clocks per engagement, current and closed, alongside the document trail compliance depends on, instead of a generic due-date field that treats every deadline the same.