SiteThread · in development

Connect the records. Keep the property history traceable.

SiteThread is planned as a private workspace where environmental consultants can connect reports and regulatory correspondence, trace a property's history, and identify what is missing or uncertain.

The member workflow is not operational yet. This overview describes planned behavior; property records are not being collected or stored here.

A source-first property history

01

Add a property

Keep a private property name, address, state, and member-entered identifiers together. Nationwide locations are planned.

02

Connect source references

Reference environmental reports and regulatory correspondence by title, type, source URL or document reference, and page or section when known. Uploads are not offered.

03

Build a traceable timeline

Link multiple evidence items to one event. Keep the event date distinct from the date a source was checked, and leave unknown dates visible.

04

Surface open questions

Separate documented facts from member interpretation and flag identifier, date, or status conflicts, unknown gaps, findings, and questions for technical review.

What it is intended to preserve

  • Source title, type, URL or reference, event date, date checked, and supplied page or section citation.
  • Missing provenance, missing dates, and source uncertainty instead of treating them as verified facts.
  • Member notes and interpretations, clearly distinguished from documented facts.
  • Historical or resolved records kept separate from active consulting leads; no property history copied automatically into enforcement briefs or member tasks.

Professional review still matters

SiteThread will not establish contamination clearance, legal applicability, or PG certification. A history may be incomplete and does not replace ESA or PG review. Member-entered interpretations remain interpretations; no AI-generated conclusions or automated retrieval are part of this in-development workspace. The planned workspace sends no email or notifications. Any future optional link to another workflow would require explicit member action and retain source uncertainty.