Skip to content

PTEN

Artificial intelligence applied to environmental engineering

Structured reading of documents, requirement matrices and evidence traceability, checked by the responsible engineer on every deliverable.

In
Permits · agency opinions · terms of reference · regulations
Out
Matrices · comparisons · evidence dossiers
Validation
The responsible engineer, on every deliverable

The problem

The volume of documents has grown faster than the capacity to reread them.

A permitting process accumulates permits, agency opinions, official letters, studies and versions of studies. The risk usually sits in the item nobody reread: the condition whose deadline runs from the date of issue, the requirement repeated in another document, the parameter that changed between two versions.

We use artificial intelligence as an internal tool of technical work: it reads everything, structures it and points to the source; the engineer checks, interprets and signs. We do not sell software, and we deliver nothing that has not been read by the person technically responsible.

Who it is for

  • Projects with many permits, sites or permit conditions
  • Teams that inherited a process with no organized record
  • Anyone who has to answer an agency requirement on a short deadline
  • Anyone heading into an audit, a renewal or a transaction who needs the dossier

Demonstration

From legal text to a requirements matrix.

Article 4 of Brazil's Forest Code (Law 12,651/2012) read and structured: each row points to its source provision and to the data the spatial analysis needs. It is the same rule applied in the map of the GIS demonstration.

Demonstration · synthetic documents

  1. Step 1 of 5

    Input

    Documents as they arrive: license, technical opinion, request for information, terms of reference. Here, synthetic documents written for the demonstration.

  2. Step 2 of 5

    Reading

    In each document, the obligation and the deadline are identified in the text and classified by theme, with the source item noted.

  3. Step 3 of 5

    Structuring

    What was identified becomes a row of the matrix: the requirement, where it came from and when it is due. What the text does not say stays blank.

  4. Step 4 of 5

    Traceability

    Each row points to the document, the item and the source passage. Anyone can check the matrix against the source.

  5. Step 5 of 5

    Review

    The engineer in charge reviews it row by row and sets who answers for each obligation. Only then does the matrix become a deliverable.

Operating licenseSynthetic document

Conditions

  1. 3

    Maintain self-monitoring of liquid effluents and submit an annual report to the environmental agency, by March 31 of each year.

    Effluents
  2. 4

    Carry out environmental noise monitoring at the boundaries of the facility, every six months.

    Noise
  3. 5

    Submit, within 120 days of the issue of this license, the updated solid waste management plan.

    Waste

Technical opinionSynthetic document

Recommendations

  1. 7

    Carry out the riparian strip restoration project along the watercourse, within 180 days of issue.

    Flora

Draft · awaiting reviewReviewed by the engineer in charge

Requirements matrix extracted from the synthetic documents
RequirementSourceDeadlineOwnerStatus
Annual effluent self-monitoring reportsubmit an annual report to the environmental agency · by March 31 of each yearOperating license, item 3Annual, by March 31To be set at reviewOperationsDraftReviewed
Environmental noise monitoringCarry out environmental noise monitoring · every six monthsOperating license, item 4Every six monthsTo be set at reviewEnvironmentDraftReviewed
Updated solid waste management planthe updated solid waste management plan · within 120 days of the issue of this licenseOperating license, item 5120 days from issueTo be set at reviewEnvironmentDraftReviewed
Execution of the riparian strip restoration projectCarry out the riparian strip restoration project · within 180 days of issueTechnical opinion, item 7180 days from issueTo be set at reviewEnvironment · contractorDraftReviewed

4 requirements · 2 source documents · 2 deadlines counted from issue · all with the source stated

Artificial intelligence applied to technical analysis, with traceability and professional validation.

Documents written for this demonstration. They do not reproduce any real case, agency or project.

How the work moves

  1. 01

    Input

    The document as it is: a permit PDF, an agency opinion, terms of reference, a regulation.

  2. 02

    Extraction

    Items separated and classified, each with its document, page and source provision.

  3. 03

    Review

    The engineer checks against the source and adds the reading the text alone does not give.

  4. 04

    Output

    A matrix, comparison or dossier, as a spreadsheet and a report, ready for the routine.

Demonstration · public data
Permanent preservation areas: parameters of Article 4 of Law 12,651/2012
ProvisionFeatureParameterStrip or criterionData needed for the map
Art. 4, I, aNatural perennial or intermittent watercourseLess than 10 m wide30 m on each bankHydrography and the edge of the regular channel
Art. 4, I, bWatercourse10 to 50 m wide50 m on each bankHydrography and channel width
Art. 4, I, cWatercourse50 to 200 m wide100 m on each bankHydrography and channel width
Art. 4, I, dWatercourse200 to 600 m wide200 m on each bankHydrography and channel width
Art. 4, I, eWatercourseMore than 600 m wide500 m on each bankHydrography and channel width
Art. 4, II, aNatural lake or pond in a rural zoneSurface of up to 20 ha, or larger50 m, or 100 mWater surface and zoning
Art. 4, II, bNatural lake or pond in an urban zone—30 mWater surface and urban perimeter
Art. 4, IVPerennial springAny topographic position50 m radiusSpring locations surveyed in the field
Art. 4, VHillsideSlope greater than 45°The whole hillside or part of itElevation model and slope map

What the review adds

The text gives the strip; applying it depends on the case. In consolidated urban areas, municipal law may set riparian strips different from those in item I (paragraph 10, added by Law 14,285/2021). Channel width and spring locations come from a survey, not from the map. And some cases in the article are not in this table: reservoirs, palm swamps (veredas), hilltops.

Source: Law No. 12,651 of May 25, 2012, consolidated text on the Brazilian Presidency's legislation portal (Planalto), checked on October 8, 2026.

H·MARIZ · 2026

Where it has been applied

  • Regulatory matrix and documentary-requirements matrix prepared to meet permit conditions at more than one site of the same client
  • Comparison between the agency requirement, the contracted scope and a laboratory proposal, to find gaps before fieldwork
  • Monitoring report with a field protocol and tracked revisions

Scope and deliverables

Engineering supported by AI, not a software license.

Six services, each with a deliverable that goes into the project's routine.

  1. Structured extraction from documents

    Permits, agency opinions, notices and terms of reference converted into items, each with its source.

    Deliverable

    Spreadsheet of items with document, page and provision.

  2. Permit-conditions matrix

    Conditions and requirements from every permit in a single matrix, with deadline, owner and expected evidence.

    Deliverable

    Permit-conditions matrix and obligations calendar.

  3. Requirement analysis and classification

    Legal and regulatory requirements applicable to the activity, classified by subject, type of obligation and frequency.

    Deliverable

    Requirements matrix, with the source provision.

  4. Version comparison

    What changed between two versions of a study, a draft or an agency opinion.

    Deliverable

    Difference report, flagging what changes an obligation or a risk.

  5. Evidence organization and traceability

    Each piece of compliance evidence linked to the obligation it proves.

    Deliverable

    Compliance dossier, ready for an audit, a renewal or a transaction.

  6. Cross-checking information

    Requirement, contracted scope, supplier proposal and field data read side by side.

    Deliverable

    Schedule of gaps and pending items by owner.

How the work is organized

How a pile of documents becomes a matrix.

  1. 01

    Understand

    What will be decided with the result and which documents count.

  2. 02

    Structure

    The matrix model: fields, classification and source rule, before processing.

  3. 03

    Deliver

    AI-assisted extraction and the engineer's check against the document.

  4. 04

    Manage

    A living matrix: when a new document comes in, the difference shows.

Proven experience

An internal tool, a signed deliverable.

  • Internal tool

    An in-house system for reading project documents: it answers with the source and the excerpt, builds the matrix of requirements and permit conditions, and flags conflicting deadlines and evidence gaps across documents. Whatever it writes comes out as a draft; it does not sign, file or send.

  • H·MARIZ · 2026

    The method was applied in 2026 to monitoring reports and to matrices for meeting permit conditions.

  • Demonstration · public data

    This page's demonstration: a matrix extracted from public legal text and checked against the source.

  • ART · engineer of record

    Technical responsibility stays where it has always been: with the engineer, under an ART when the service requires one.

Experience from 2009 to 2023 belongs to the responsible engineer and is recorded in ARTs (technical responsibility records) filed with CREA-MG; the 2026 work was contracted by H·MARIZ. Clients are not named. The list of ARTs is available on request.

Next

Related portfolio and capabilities.

Related portfolio

A cross-cutting capability: it applies to both sectors and has no presentation of its own.

Contact

How many permit conditions does your project have today, and where is the evidence for each one?

Send the permits. The first matrix shows the size of the problem.

Henrique Marizhenrique@hmariz.comWhatsApp (31) 99791-8003Belo Horizonte, Minas Gerais