Web-forensics use case
Acquire construction and project-management portal evidence
Eviquire can preserve authorized construction and project-management records presented through a browser, including project and package context, tasks, RFIs, submittals, approvals, change orders, drawings, document versions, site reports, communications and visible audit history. It complements rather than replaces the common data environment, native project export, signed contract record, endpoint or provider backend.
What this use case means
Eviquire can preserve authorized construction and project-management records presented through a browser, including project and package context, tasks, RFIs, submittals, approvals, change orders, drawings, document versions, site reports, communications and visible audit history. It complements rather than replaces the common data environment, native project export, signed contract record, endpoint or provider backend.
Project portals connect drawings, revisions, workflows and correspondence across organizations with different permissions. A later revision may supersede a displayed plan without removing it, and opening or responding to an item can change workflow status. Evidence must connect each document or decision to the project, package, version, role, approval state and chronology.
Common situations
When this workflow is useful
- Delay, defect, variation, payment, design, safety, responsibility or disclosure disputes
- Preserving an RFI, approval, drawing revision or site report before workflow changes
- Documenting what an authorized project participant could see
Recommended process
A documented acquisition workflow
- Define project scope
Identify project, organizations, packages, item IDs, dates, versions, workflows and privileged exclusions.
- Record role and configuration
Preserve tenant, company, role, project, timezone, filters and navigation.
- Acquire linked records
Navigate from project or package to RFI, submittal, change, drawing, report, message and visible audit history.
- Preserve native documents
Download authorized drawings, models, reports, correspondence and exports in supplied formats.
- Verify versions and authority
Hash originals, record superseded state, and correlate with signed contracts or certified project records.
Technical guidance
Conditions that affect project-portal evidence
Confirm these points during a short pre-acquisition validation on the authorized workstation.
Versions and supersession
Current, published, approved, superseded and as-built documents may coexist.
- Record document and revision IDs.
- Capture workflow state.
- Preserve each relevant native version.
Cross-organization permissions
Owner, designer, contractor and consultant roles see different fields and history.
- Record role and company.
- Do not infer hidden records are absent.
- Separate privileged material.
Workflow effects
Viewing, acknowledging, assigning or responding may change status or create events.
- Use review views.
- Avoid action controls.
- Document unavoidable events.
Reviewable output
What the evidence package should explain
Project context
Tenant, project, company, role, package, item, filters and timezone.
Workflow chronology
RFIs, approvals, changes, reports, communications and visible audit events.
Native project files
Authorized drawings, reports, correspondence and exports preserved with hashes.
Review package
Version relationships, session history, limitations and custody records.
The exact artifacts depend on the source, plan, configuration, authority, and investigation. A report should identify what was and was not collected.
Professional considerations
Authority, proportionality, and limitations
- Project portals contain commercially sensitive designs, worker data and safety information.
- Portal approval labels should be interpreted with contract and governance rules.
- Keep native files unchanged and perform markup or conversion on controlled derivatives.
Important: Eviquire supports a documented technical process. It does not establish identity, truth, culpability, infringement, or admissibility, and it does not replace legal advice or a validated organizational procedure.
Standards and primary guidance
Online evidence procedures should be validated for the organization and matter. Useful starting points include SWGDE guidance for acquiring online content, ISO/IEC 27037:2012, and NIST digital-evidence resources.
Frequently asked questions
Can drawing revisions be preserved?
Yes when available, with document, revision and workflow context.
Does an approved label prove contractual acceptance?
Not necessarily; contract rules and authoritative records determine effect.
Can opening an RFI change it?
It may create a view or workflow event; document the effect.
Should native drawings be downloaded?
Yes when relevant and authorized, preserving originals with hashes.
Does Eviquire acquire the whole project database?
No. It preserves selected browser-presented evidence.
Who uses this workflow?
Relevant professional roles
This acquisition workflow is commonly relevant to these teams. The appropriate authority, scope, procedure, and review requirements still depend on the matter.
Forensic experts
Acquire online evidence with technical context, integrity verification, custody records, and reporting.
See role-specific guidance →
Law firms
Preserve websites and online content for litigation, disclosure, legal holds, and expert review.
See role-specific guidance →In-house legal teams
Preserve early evidence for disputes, compliance, legal holds, and outside-counsel review.
See role-specific guidance →
HR and due-diligence teams
Preserve relevant online material for employment, compliance, fraud, and diligence matters.
See role-specific guidance →