Strategic Project status comes witha documentation burden.

The EU Critical Raw Materials Act sets a defined framework for Strategic Projects across extraction, processing and recycling. INSUS organises technical, environmental and supply-chain documentation against the applicable criteria, surfaces what is missing and keeps the project record ready for review. Qualified teams approve everything before submission.

  • 01

    Evidence mapped to the criteria it is meant to satisfy.

  • 02

    Gaps surfaced before the cut-off, not at it.

  • 03

    Qualified teams approve everything before submission.

The problem

The requirements are defined.The documentation is scattered.

A Strategic Project application pulls together technical project information, environmental documentation, permitting records and supply-chain evidence. Those records sit with different teams in different systems, so nobody holds a single view of what has been documented, what is missing and what still needs review before the next cut-off.

Project documentation distributed across separate teams and systems
01
02
03
  • 01Technical documentation
  • 02Environmental and permitting records
  • 03Supply-chain evidence

The shift

From assembling at the deadlineto continuous readiness.

Instead of reconstructing the evidence base as a cut-off approaches, keep a living record of the project's documentation, its criteria coverage and its outstanding gaps.

Today

Documentation is assembled when the date approaches

  • Technical, environmental and supply-chain records sit apart.
  • Criteria coverage is checked by hand.
  • Missing or inconsistent evidence is found late.

With INSUS

Readiness is visible throughout the cycle

  • Documentation is organised against the applicable criteria.
  • Missing and inconsistent records are surfaced early.
  • Post-approval records stay connected to the application.

How it works

From project documentationto a reviewable readiness record.

Delivered through ExpertFlow AI as document intelligence over the records a project already produces. It organises evidence and flags gaps. It does not certify compliance or submit applications.

  1. Connect

    Bring the project records together

    Connect technical project documentation, environmental and permitting records, supply-chain information, existing application material and the applicable CRMA regulatory and guidance texts.

  2. Understand

    Map documentation to the CRMA criteria

    Analyse the available documentation and map the relevant evidence to the applicable Strategic Project criteria and project category, whether extraction, processing or recycling.

  3. Detect

    Surface missing and inconsistent evidence

    Identify documentation gaps, inconsistencies and incomplete evidence that need attention before the next application cut-off or project milestone.

  4. Advise

    Show what needs attention first

    Gaps are organised into a prioritised readiness view so the team works on the evidence that actually needs completing, rather than searching across separate repositories.

  5. Verify

    Keep qualified teams in control

    Project and compliance teams review and approve every assembled documentation update before it becomes part of the submission or system-of-record version, with the underlying source always available to check against.

Project documentation forming the data foundation for a CRMA compliance workflow

Getting started

Start with one Strategic Projectand the records you already hold.

For project, permitting and compliance teams preparing or maintaining a CRMA Strategic Project record. Delivered through ExpertFlow AI as document intelligence for criteria mapping and gap analysis. Expert Services can help with discovery and validation. It does not perform geological, environmental or engineering studies, certify compliance or submit applications. No new hardware.

  • What we need. Technical project and engineering documentation, environmental assessments and permitting records, supply-chain and sourcing information, existing application material, and the applicable CRMA regulatory text, guidance and Strategic Project criteria.
  • What you see first. One Strategic Project with its documentation mapped to the applicable criteria and a gap analysis the project team can validate against the source records.
  • Where the limits are. It cannot certify that a project satisfies regulatory requirements, and it does not submit applications. Its value depends on the quality and completeness of the project's own documentation.
Explore ExpertFlow AI

Questions project and compliance teams ask us

Strategic Project evidence sits across technical, environmental and supply-chain records. This use case organises that documentation against CRMA criteria and surfaces gaps for project and compliance review.

A project recognised under the EU Critical Raw Materials Act framework as contributing to the EU's critical raw materials objectives. The framework covers relevant extraction, processing and recycling projects.

Existing technical project documentation, environmental and permitting records, supply-chain information, application material and the applicable CRMA regulatory and guidance texts. No new sensors or hardware.

No. It organises and checks documentation your existing technical, environmental and permitting workflows already produce. It does not replace the underlying studies or professional assessments.

It can help assemble a structured application record from existing documentation, but it does not submit applications or certify that a project satisfies regulatory requirements.

Through ExpertFlow AI as document intelligence for criteria mapping and gap analysis. Expert Services can support discovery, integration and validation with your project and compliance teams.

Value depends on the quality and completeness of the project's own documentation. The system organises and flags evidence for human review. It does not make regulatory determinations or replace qualified professionals.

Critical Raw Materials Act

Keep your project documentation ready, not reconstructed.

Start with one project and the documentation you already hold. Map the evidence to the applicable criteria, surface the gaps, and give the team one traceable view of where the application actually stands.