Every environmental workflow. One place to know what matters.

Knoy connects reports, spreadsheets, field records, requirements, decisions and reviews across your projects—so specialists spend less time searching and reconstructing context, and more time applying professional judgment.

Trace the original source
Return to the document, page, section and quote behind a working conclusion.
Keep judgment human
Specialists interpret, verify and approve. Knoy helps connect the manual trail.
Your documents, as they are
Work with PDF, DOCX, XLSX, CSV and TXT sources, with source references preserved.
Across the project lifecycle
Connect assessment, management and compliance. Broader lifecycle tracking is being designed.

Environmental work runs on evidence. Yet the evidence is scattered across reports, spreadsheets, inboxes and project drives.

Follow the evidenceIllustrative project data
Choose a source to explore its evidence.
  1. 01

    Searching page 247.

    A 600-page EIS. Three superseded studies. An agency letter, field spreadsheet and marked-up plan. Your expertise should not be spent finding them again.

  2. 02

    Reconstructing the trail.

    Before: reopen PDFs, compare versions and ask who reviewed the conclusion. With Knoy: retrieve supplied project evidence and return to its original source.

  3. 03

    Repeating the same work.

    Before: copy findings between reports, registers and email. Knoy connects cited working outputs and reviews; wider change propagation is product direction.

Find, organise, retrieve, trace, compare and connect. Coordinate, draft, review, track, reuse and export—with professional judgment at the centre.

From first field record to management and compliance.

Discover, scope, assess, review, deliver, manage, monitor, audit and learn. Six interactive examples show how the source travels with the work. Reporting is one stage, not the end.

See what the environmental work needs.

Bring requirements, risks, evidence gaps and specialist responsibilities into project context. Approvals sit alongside assessment, construction, management and compliance work.

Project requirements and evidence
Requirements matrix
Requirement
R-018Assess impacts on threatened species and ecological communities.BiodiversityCovered12
R-024Describe erosion and sediment controls for each construction stage.SoilsCovered7
R-042Assess water quality impacts during construction and operation.Surface waterIn review6
R-063Assess traffic and access impacts on the local road network.TrafficCovered5
R-077Describe noise and vibration impacts on nearby receivers.NoiseGap0
R-102Assess bushfire risk and asset protection zones.HazardsIn review2

Requirements with evidence83%

Illustrative workflow with synthetic project data. Wider lifecycle capabilities are product direction.

Every source, anchored to the page.

Find supplied reports, field records, spreadsheets and correspondence. Source anchors keep document, page, section and quote context visible; exact row and record views vary by format.

Evidence
IndexedPDF · 132 pages
HYD-03 Surface water baselinePage 47 · 3.2 Turbidity
Turbidity exceeded the 50 NTU trigger value at SW2 and SW4 following rainfall events greater than 20 mm.
Quote hash 7f3a 9c1e

Illustrative workflow with synthetic project data. Wider lifecycle capabilities are product direction.

Drafts that cite as they go.

Prepare source-backed working sections, registers and responses. Identify possible evidence gaps and verify every statement; AI assistance is not professional advice or a finished assessment.

§ 8.4 Surface water · Draft
Chapter 8 · Surface water8.4 Water quality during construction

The access road crosses two ephemeral drainage lines that feed Wattle Creek.

Baseline monitoring recorded turbidity above the 50 NTU trigger after rainfall events greater than 20 mm.

Groundwater interaction is expected to be minor. Needs source

2 of 3 sentences cited
Hover or focus a citation to see its source.

Illustrative workflow with synthetic project data. Wider lifecycle capabilities are product direction.

Specialist review, with the source beside it.

Qualified specialists interpret, verify, accept, revise or reject with the source in view. Output review states exist; complete review-history coverage varies by workflow.

Review · § 8.4
  1. Drafted, Completed
  2. Specialist review
  3. Approved, Not started
Step 2 of 3: Specialist review

§ 8.4 Water quality during construction

2 comments
  • Hydrology lead2h

    The turbidity finding checks out against HYD-03 page 47. Can we add quarterly sampling at SW2 to the commitments?

    • Project planner1h

      Added as C-027 and linked to R-042.

Illustrative workflow with synthetic project data. Wider lifecycle capabilities are product direction.

See what a change touches.

Keep owners, dependencies and decisions close to the source. Document-version comparison exists; the wider coordination dashboard, operational tracking and downstream change propagation are product direction.

Change impact · Agency letter 14
Today, 2 updates
  1. North Coast Planning Office requested an updated drainage designAGL-14
Owners to notify
R-042 and section 8.4
R-018 and section 7.2
Commitment C-027

Illustrative workflow with synthetic project data. Wider lifecycle capabilities are product direction.

Carry reviewed working material into delivery.

Export supported working outputs to Word, Excel, PDF or CSV. The generated-output route checks citations and approval; formats, review history and checks vary across other export paths.

Export · Review pack
Citations resolved100%
Specialist reviews approved88%
1 review still open

Illustrative workflow with synthetic project data. Wider lifecycle capabilities are product direction.

Useful outputs, across the life of a project.

Assessments, management plans, compliance records and project controls. Source-backed working material, with professional approval required. The full library is product direction.

  • Keep assumptions, specialist findings and source references beside each working section.

  • Connect each issue to the evidence, response owner and review decision behind it.

  • Carry reviewed measures into practical working plans, with responsibilities and source context.

  • Assemble evidence for professional assessment; a generated pack is not a compliance determination.

  • Keep the source, the current revision and the person responsible attached to the work.

  • Your old reports are valuable project knowledge, with their sources and permissions attached.

  • One field record can support assessment, management and compliance without losing its context.

  • Project management, with the evidence attached: owners, dependencies, reviews and affected work.

Mangrove channels braiding through a tidal estuary

The environment is interconnected. Environmental work should be too.

Start with the work you do.

From BAM assessors and water specialists to environmental auditors and project leads. Open a discipline group to explore the manual work, how Knoy helps and what remains human.

Biodiversity and BAM, water, waste, contamination, heritage, and marine and coastal work.

Approvals and EIS, air quality, noise, social impact, climate, hazards and risk.

Management plans, construction, compliance, monitoring, auditing and multidisciplinary leadership.

Professionals make the environmental judgment.

Knoy handles the manual trail. Qualified professionals design investigations, interpret and verify evidence, assess impacts, resolve uncertainty, apply legislation and policy, recommend mitigation, approve and certify deliverables.

Professional interpretation, verification and approval remain human responsibilities.
Knoy does not replace BAM assessors, auditors, scientists, engineers, planners or other qualified environmental professionals.
  • Named project rolesOwner, editor and reviewer roles are checked for project actions.Implemented
  • Access checked at the data layerProject-membership policies are defined in the database. Confirm deployment and customer boundaries before sensitive use.Implemented
  • Review checks for generated outputsThe generated-output export route checks citations and approved output status. This does not guarantee every export path or technical correctness.Implemented
  • Minimum necessary contextStructured AI requests limit evidence excerpt count and length. Complete task-by-task disclosure is still in development.Partly implemented
  • Activity and source trailProject audit events and source anchors are recorded. This is not a complete, immutable audit-trail guarantee.Partly implemented
  • Deletion and retentionProject deletion is supported. Backup, retention and deletion-verification arrangements still need to be agreed.Partly implemented
  • Visible processing and authorised reuseConfirm provider, model route, location, processors and retention before restricted processing. Cross-project reuse and complete client isolation are not yet complete.Being designed for

Statuses describe controls found in the codebase, not an independent assurance of every deployed environment. Not every control is implemented yet.

Handling sensitive material?

Confirm hosting, model route, processors and retention before uploading restricted material: commercially confidential, personal, cultural heritage or government-sensitive information, unpublished field data, draft legal positions and client intellectual property. Read our privacy approach.

Bring your environmental work into one connected workspace.

Tell us about the work. We’ll explore how Knoy can connect its evidence, specialist workflows, decisions, reviews, delivery and compliance.