Solutions
Cortex Cowork handles the mechanical work in each workflow — matching, modeling, authoring, validating, auditing — and returns control to the practitioner or programme operator at every point where a judgment call determines the result.
For LCA practitioners
BOM matching
Upload a Bill of Materials in any format. Cortex matches each row against fourteen LCA databases and returns a four-sheet workbook — every dataset cell a hyperlink, every proxy and gap documented. Minutes, not hours, for a BOM of any size.
See the workflow →Product carbon footprint
Cortex drives openLCA directly — dataset matching, product system construction, LCIA calculation — and writes every modeling decision into an append-only project log. Functional unit, system boundary, and allocation method are decided once and carried forward across every session.
See the workflow →LCA dataset authoring
Cortex guides the full authoring workflow inside HiQ Editor: metadata, flow entry, mass-balance validation, DQI scoring across all five Pedigree Matrix dimensions, and review submission. Every decision on record before anything is published.
See the workflow →ILCD validation and conversion
Validate ILCD packages against schema requirements and convert between ILCD and JSON-LD. Every error reported by location and severity. Every mapping choice documented. Converted output validated against the target schema before delivery.
See the workflow →For programme operators
EPD audit
Cortex audits EPDs against ISO 14025, EN 15804+A2, the applicable PCR, and EU CPR 2024/3110 — returning a structured report where every finding cites the clause, quotes the EPD text, and states the registration consequence. Critical issues block; warnings are split by severity so programme operators can prioritise.
See the workflow →Across all workflows
Every Cortex workflow shares the same operating principle: Cortex handles the work that is mechanical — searching databases, driving software, checking schemas, scoring DQI — and returns control to the practitioner at every point where a judgment call would determine the result.
Decisions made in one session carry forward to the next. The project log accumulates assumptions, confirmations, and resolved pitfalls across sessions. A verifier arriving at a finished deliverable can trace any result back to the session in which the underlying choice was made — without re-running the model or contacting the author.
All workflows run locally. No files leave the machine unless the practitioner initiates the action.
Cortex Cowork is available for macOS, Windows, and Linux. Sessions run locally — files stay on the machine.