EterShieldDocs
etershield.com
PTLog in
Guide/Operations and IT

e2morrow

e2morrow is Eter's sustainability module inside EterShield, which provides each person's identity and role: there is no need to create another account. The module must be active for the organisation. The previous external application was switched off: while the module is being updated, the page shows "e2morrow is being updated and will be back soon".

Opening the e2morrow module

  1. In the menu, open e2morrow
  2. Click Open the e2morrow module

Entry requires your session to have MFA (two-factor authentication). A session started through SSO counts as having MFA. If MFA is not active, the notice "e2morrow requires two-factor authentication" appears: turn it on in your profile and sign in again. Entry is also unavailable during privileged (support) access to the organisation, and if you have not been given access (ask your administrator).

Managing access per member (administrators)

SUPER_ADMIN and ADMIN manage who can enter in Settings, e2morrow access. For each member of the organisation you see their EterShield role, the Access switch (With access / No access) and the e2morrow role: Administrator, Editor, Analyst or Reader.

If you do not choose a role, the default map applies: EterShield administrators enter as Administrator and everyone else as Reader. Every change is recorded in the audit log.

e2morrow: navigation and home page

Inside the module, the top bar shows the organisation and your user menu, and the side bar lists the areas in the same order as the previous e2morrow, with the three new areas (Waste and packaging, Lots and origin and SDS) in their groups: Dashboard, Emissions, CO₂ Budget, Targets, Waste and packaging, Social S1, Governance G1, Biodiversity E4, Lots and origin (EUDR), SDS, Assets, OHS / ISO 45001, Materiality, CSRD Reports, Frameworks, Import Hub, Applications, ESRS Copilot, Data integrity, Audit Log and Settings. Assets, OHS / ISO 45001, Audit Log and Settings open the matching EterShield pages. Back to EterShield takes you to the main dashboard. On narrow screens the menu opens from the button at the top.

Areas that are not ready yet show "Coming soon" and a line about what they will offer.

To open the module from EterShield, use Open the e2morrow module on the e2morrow page (it appears when the module is active and you have access).

On the Dashboard you choose the year (by default, the last full year) and see: electricity in MWh, gas and fuels by unit, scope 1 emissions, scope 2 by location and scope 2 by market in tCO2e, and the mean and median pay gap. Anything without records shows "No data". Below are the module areas, with the number of records and the date of the last update where there is data. All roles, including Reader, see these totals (they are aggregates). At the end, the Session section confirms the organisation of the session.

Emissions, Social S1 and CSRD Reports have tabs. Energy invoices are in Emissions, Energy invoices; the pay gap in Social S1, Pay gap; the VSME Basic report in CSRD Reports, VSME Basic. Old links still work and lead to the right tab.

In Energy invoices you see the yearly totals by energy type, filter by year and type, and page through the list 20 at a time. In Pay gap the list also has 20 per page; each record has a "..." menu with Delete, and Delete all records of the year is in the filter bar, with confirmation.

e2morrow: energy invoices

In Emissions, on the Energy invoices tab, you import the organisation's electricity, gas and fuel invoices. Each invoice keeps the consumption, the calculated emissions and the invoice file as evidence, and the emissions are added to the ESG hub.

Who can. Administrator and Editor import invoices. Analyst and Reader only view the list. Without access to e2morrow, or with the module switched off, you see nothing.

Importing an invoice.

  1. Click Import invoice.
  2. Choose the Entity and the Energy type: Electricity, Natural gas, Diesel, Petrol, LPG or Fuel oil.
  3. Enter the Quantity and the Unit shown on the invoice. Electricity in kWh; natural gas in Nm3, kWh NCV or kWh GCV; diesel and petrol in litres or kWh NCV; LPG in kg or litres; fuel oil in kg. Gas in m3 is not accepted: use the unit shown on the invoice.
  4. Choose the Start and End of the period (the end cannot be before the start). Supplier, invoice number and amount are optional.
  5. Attach the invoice (PDF, JPEG, PNG or WebP, up to 10 MB) and click Import invoice.

Read the invoice with AI. After attaching the invoice, click Read invoice with AI. The AI reads the file and proposes the supplier, the invoice number, the energy type, the period, the quantity and unit, and the amount; if the invoice shows the CPE or CUI code, it is displayed as a reference only (it is not saved). The proposed fields appear filled in and marked "Proposed by AI, confirm". Only fields that were empty are filled, and the mark goes away when you edit the field. The AI can be wrong: check each marked field against the invoice and only then click Import invoice. Nothing is saved until you confirm, and the emissions are always calculated with the emission factor table, never with values from the AI. Anything the AI cannot read (or reads with an invalid value) stays empty for you to fill in by hand. Notes: a scanned PDF with no text must be uploaded as an image (JPEG, PNG or WebP); each reading uses one AI credit of the plan (none if the organisation uses its own key) and only works if AI is switched on in Settings, Data and AI, otherwise e2morrow says that AI is off and you can fill in the fields by hand. Only Administrators and Editors can read invoices with AI.

What is recorded. The file is stored as evidence with a fingerprint (SHA-256) that lets you prove later that it was not changed. Emissions are calculated with the emission factor table in force (see "Where emission factors come from" in ESG) and the factor version is saved on each invoice. For electricity, the list shows two values: the location-based method, which is the one that feeds the ESG hub, and the market-based method, for reference only. The import is recorded in the audit log.

The list shows the period, the type, the quantity, the kgCO2e, the kgCO2e by the market-based method (electricity only) and the start of the evidence fingerprint.

e2morrow: emission records

In Emissions, on the Emission records tab, you see the year's emissions by scope (scope 2 by the location-based method), filter by entity and scope, and page through the list 20 at a time. Each row shows the month, the scope, the source (energy invoice, fleet, manual record or import), the quantity, the factor used and the tCO2e.

Who can. Administrator and Editor record and import. Analyst and Reader only view. Without access to e2morrow, or with the module switched off, you see nothing.

New record.

  1. Click New record.
  2. Choose the Entity, the Scope and the Month. For scope 3 also choose the value chain Category. For scope 2 choose the Method: location or market (the market method is not added to the location totals, budgets or targets, and feeds the scope 2 by market figure on the Dashboard and in the report).
  3. Choose the factor. Table factor: scopes 1 and 2 have a versioned factor table, with the source of each; the unit is the factor's and is not converted. Manual factor: enter the factor in kgCO2e per unit and the Factor source (required). Scope 3 only has a manual factor. No factor is ever assumed: without a factor nothing is saved.
  4. Enter the Quantity. You immediately see the calculated emission in tCO2e (quantity times factor, divided by 1000) and click Save record.

Scope 2 method. Choose location or market. The market method adds to scope 2 by market (Dashboard and VSME Basic report) and never to scope 2 by location, budgets or targets. The ESG hub PDF also leaves scope 2 by market out of the totals and out of the location table.

Possible duplication. If an energy invoice already exists for the same month and source, the record is saved and a warning appears: if the consumption is the same, delete the manual record.

Deleting. Only records created here (manual records and CSV imports) can be deleted, from the row's "..." menu. Emissions that come from an invoice are handled on the invoice, and fleet emissions in the fleet. Every save and every removal is recorded in the audit log.

e2morrow: CO₂ Budget

In CO₂ Budget you set the carbon budget for each month, by entity and by scope (all scopes, scope 1, 2, 3, or scopes 1 and 2), and compare it with the recorded emissions. Choose the year, the entity and the scope.

Setting the budget. Click Set budget, choose the year, the month and the scope, and enter the budget in tCO2e (greater than zero) and the alert threshold as a percentage (80 by default). If the month already has a budget for that scope, the value is updated. Only Administrator and Editor set and delete budgets; Analyst and Reader view.

What you see. The summary compares only the months that have both a budget and recorded emissions: the budget of those months, the actual of those months, the usage percentage and how many months were compared. The year total is shown separately and is not part of the comparison. The chart shows the budget and the actual by month. The table shows, by month, the budget, the actual, the usage and the status: Within budget, Alert (from the threshold), Over budget, No budget or No data. A month without recorded emissions shows as "No data", never as zero. The emissions of the chosen entity itself count, by the location-based method.

e2morrow: Targets

In Targets you set emission reduction targets and follow the status of each.

New target. Click New target and enter the entity, the name, the Scope (the target compares only the emissions of that scope), the Target reduction as a percentage, the Base year, the Target year and the Base value in tCO2e. If you leave the base value empty, e2morrow uses the emissions recorded in the base year, but only if that year has ended and has all 12 months recorded. The base value is fixed when you save: data imported later does not change it. The Framework (voluntary target, declared carbon neutrality, externally validated, or linked to a regulatory framework) is declared by the organisation and e2morrow does not verify it; an externally validated target requires the validation reference. Only Administrator and Editor create and delete targets.

The status. It is always calculated with the last full calendar year after the base year and not after the target year, never with the current year. The required path is linear between the base year and the target year. The statuses are: On track, At risk, Achieved (the full year is already at the target value), Not achieved (the target year has passed without reaching the target value), Incomplete data (the year has fewer than 12 months with records) and No data (the year has no records or there is not yet a full year after the base year).

e2morrow: Import Hub

The Import Hub gathers the bulk data entries: energy invoice, emissions CSV, consumption CSV and payroll records CSV. Only Administrator and Editor use them.

Emissions CSV. It has 10 columns, in this order: ambito (1, 2 or 3), categoria_ambito3 (1 to 15, scope 3 only), periodo (YYYY-MM), quantidade, unidade, fator_chave (key of the table factor), fator_manual, fonte_fator, descricao and metodo (optional: localizacao or mercado, scope 2 only; empty means location). Only ambito, periodo, quantidade and unidade are required in the header. Each row carries either the key of a table factor (with the factor's exact unit) or a manual factor with its source, never both.

Consumption CSV. Columns: type (eletricidade, gas natural, gasoleo, gasolina, gpl or fueloleo), unit, month, quantity and description. The factor is always the table one and electricity uses the location-based method. Each row creates an emission without evidence: if you have the invoice, import the invoice. Do not import here what you already imported as an invoice: the emissions would be counted twice. If an invoice exists for the same month and source as any manual record or imported row, e2morrow saves anyway and warns that the consumption may be duplicated; check the list and delete what is left over.

How it works. The file is CSV in UTF-8, with a header, comma or semicolon separator, up to 1 MB and 2000 rows. Choose the entity and the file. The import is all or nothing: if any row is invalid, nothing is saved and the report gives the row and the reason. The same file cannot be imported twice for the same entity. Reading invoices with AI is on the Import invoice form (see "e2morrow: energy invoices"); this CSV file does not use it.

e2morrow: pay gap

In Salaries and pay gap you keep the payroll records of each year and see the pay gap between women and men, per hour.

Who can. Administrator and Editor create, import and delete records. The Analyst sees the list and the result. The Reader sees only the result (the gap and the counts), not the list by code.

No data that identifies people. Each record uses a code defined by your organisation (for example P-001), never the name or the email. The code may only contain letters, digits, full stop, hyphen and underscore, no spaces, at least one digit and no 9 or more digits in a row (which would look like a tax number). The category is chosen from a fixed list: Management, Senior staff, Technicians, Administrative, Production, Logistics, Laboratory, Sales or Other. Your organisation, outside EterShield, knows which person each code belongs to.

Creating a record.

  1. Click New record.
  2. Choose the Entity and the Year, enter the Person code and choose the Gender (Woman, Man, Other or Not declared).
  3. Enter the Annual gross pay (EUR) and the Annual hours. The category is optional and chosen from the list.
  4. Click Save record. If a record with the same code already exists for that entity and year, it is updated instead of duplicated.

Importing a CSV.

  1. Click Import CSV, choose the Entity and the Year and attach the file (up to 1 MB).
  2. The first row has the columns ref,genero,categoria,remuneracao_anual,horas_anuais (the category can be empty; if filled, use one from the list, by key, for example TECNICOS, or by name). The gender is F, M, OUTRO or NAO_DECLARADO. Pay and hours use a full stop or a comma as the decimal, with no thousands separator. A comma or semicolon separator is accepted.
  3. If any row has an error, nothing is saved and the list of rows with the reason is shown. Fix the file and import again. Importing the same file again does not duplicate records.

Deleting. On each row, Delete removes the record; with an entity chosen, Delete all records of the year removes all those of that entity and year. It asks for confirmation and cannot be undone. It is recorded in the audit log, without pay figures.

CSV file. It must be in UTF-8 (in a spreadsheet, save as "CSV UTF-8").

What is calculated. Hourly pay is the annual gross pay divided by the annual hours. The gap is the difference between the mean (and between the median) of men and women, divided by that of men: a positive value means men earn more per hour. Only women and men are included; records with gender Other or Not declared are counted separately. Records with missing pay or hours, or equal to zero, are left out and counted in Excluded records. Without records of women, or without records of men, there is no gap and the page says why. The value is shown with one decimal place.

e2morrow: social indicators

In Social S1, on the S1 indicators tab, you record by entity and year the organisation's social figures: employees, women, people under 30 and over 50, hours worked, training hours, days of absence, turnover and satisfaction. The Pay gap tab is still where you see the gap between women and men.

Who can. Administrator and Editor record, update and delete. The other roles with access to e2morrow only view.

Recording. Click Record indicators, choose the Entity and the Year and fill in what you have measured. Leave blank what you did not measure: blank is not zero. If a record already exists for that entity and year, it opens with the saved values and Save indicators updates it (there is never a second record). Women cannot exceed the total, and the people in the two age bands cannot add up to more than the total. Turnover is a percentage from 0 to 100. The satisfaction score uses whatever scale the organisation uses (for example 0 to 10): say which in the notes.

Work accidents. They are not entered here: the number of accidents and the working days lost come from the EterShield accident register, by detection date, in the chosen year. If there are accidents without days lost filled in, the sum may be incomplete and the page warns you. Accidents without an assigned entity appear in a notice and are not counted in the per-entity rows.

Accident rate. It shows the number of accidents recorded in the year divided by the hours worked you declared and multiplied by 1,000,000, that is, accidents per million hours worked. Without the hours worked, only the counts are shown and the line says the hours are missing: the platform does not estimate hours. It counts all work accidents recorded in EterShield. Working days lost are shown as a number.

Deleting. On each row, Delete indicators blanks the values for that entity and year, after you confirm. It cannot be undone and is recorded in the audit log.

e2morrow: governance indicators

In Governance G1 you record, by entity and year, governance and business conduct indicators: whether there is an anti-corruption policy, whether there is an active whistleblowing channel, ethics training sessions, suppliers (total and assessed), fines of the year in euros, lawsuits and the percentage of women on the administrative body.

Who can. Administrator and Editor record, update and delete. The other roles with access to e2morrow only view.

Declared values. The values are those the organisation declares and each point is shown for what it is. The two yes or no answers stay at "no" when not answered. Assessed suppliers cannot exceed the total, and the percentage of assessed suppliers is calculated from the two numbers.

Recording. Click Record indicators, choose the Entity and the Year, fill in what you have and click Save indicators. If a record already exists for that entity and year, it opens with the saved values and is updated. Delete indicators, on the row, removes the record after you confirm and is recorded in the audit log.

e2morrow: biodiversity

In Biodiversity E4 you record, by entity and year, land use (total area and the agricultural, industrial, urban and natural plots, plus the sealed area and the rehabilitated one), the deforested and restored area, whether it operates in a protected area, the threatened species affected, whether it has a biodiversity policy and whether it has a no net loss target.

Who can. Administrator and Editor record, update and delete. The other roles with access to e2morrow only view.

Units. Land use areas are written in m² or hectares, your choice (the conversion is exact: 1 hectare is 10,000 m²). Deforestation and restoration are always written in hectares. In the list you can see the areas in hectares or in m².

Checks. All values are zero or positive. If you fill in the total area, the sum of the four plots (agricultural, industrial, urban and natural) cannot exceed the total; the sealed area and the rehabilitated one are not part of that sum. The land balance (restored minus deforested) is only calculated when both values exist.

Not measured is not zero. Leave blank what you did not measure. In the yes or no fields you can choose "Not stated". The record is per entity: for separate sites, use one entity per site.

Recording. Click Record indicators, choose the Entity and the Year, fill in what you have and click Save indicators. If a record already exists for that entity and year, it opens with the saved values and is updated. Delete indicators, on the row, removes the record after you confirm and is recorded in the audit log.

e2morrow: lots and origin

In Lots and origin (EUDR) you record the raw material lots the organisation receives: soy, palm oil, cocoa, coffee, cattle, wood or rubber. Each lot has the reference, the quantity and unit, the supplier, the country of origin, the harvest or production date, the plot geolocation and the due diligence status.

Who can. Administrator and Editor record, update and delete. The other roles with access to e2morrow only view.

Geolocation. Give the latitude and longitude (between -90 and 90, and between -180 and 180), or paste the plot polygon as GeoJSON (Polygon, MultiPolygon or Feature, with closed rings). You can use both. Latitude and longitude always go together. Lots without geolocation are marked "To complete" and counted in the summary.

Due diligence status. Choose between "Not assessed", "Negligible risk", "Non-negligible risk" and "Mitigated", and, if you want, write the due diligence statement reference. The status is what your team records: the application does not assess or classify the risk.

Reference and evidence. The lot reference is unique per entity. You can link an evidence record from your organisation by entering its identifier.

Recording. Click Record lot, fill in the form and click Save lot. Edit and Delete lot, on the row, change or remove the lot (after you confirm) and are recorded in the audit log.

e2morrow: waste and packaging

Waste and packaging has two tabs, by year and by entity. In Waste you record the period, the EWC code (six digits), the description, whether it is hazardous, the quantity in kg or tonnes, the destination operation (R1 to R13 for recovery, D1 to D15 for disposal), the waste operator and, if there is one, the e-GAR number. In Packaging you record the period, the material (plastic, paper and cardboard, glass, metal, wood, composite or other), the type (primary, secondary or tertiary), the quantity placed on the market in kg, the recycled percentage and whether it is reusable.

Who can. Administrator and Editor record, update and delete. The other roles with access to e2morrow only view.

Yearly summary. At the top of each tab you see the yearly totals in kg: for waste, the total, recovery, disposal and hazardous; for packaging, the total, the recycled share (weighted by quantity) and the total per material. The year counts by the start of each record's period.

Not declared is not zero. The recycled percentage can stay blank, and the weighted average only uses the records where it was declared.

Recording. Click Record waste or Record packaging, choose the entity and the period, fill in the form and save. Edit and Delete record, on the row, change or remove the record (after you confirm) and are recorded in the audit log.

e2morrow: safety data sheets (SDS)

In SDS you record the safety data sheets of the substances and mixtures you use: the name, the supplier, the CAS number (optional), the GHS01 to GHS09 hazard pictograms, the H statements, the version and date of the sheet, the next review date, the storage location and, if you want, the evidence.

Who can. Administrator and Editor record, update and delete. The other roles with access to e2morrow only view.

Checks. The CAS number must have the right format and the correct check digit (for example 7732-18-5). The next review date cannot be before the sheet date. H statements are written one per line, for example H315.

Review. The list shows first the sheets whose review is overdue and those due in the next 30 days. The status is worked out with today's date and is not stored.

Recording. Click Record sheet, fill in the form and click Save sheet. Edit and Delete sheet, on the row, change or remove the sheet (after you confirm) and are recorded in the audit log.

e2morrow: VSME Basic report

In VSME Basic report you download, as a PDF, a summary of one entity and one year. All roles with access to e2morrow can download.

  1. Choose the Entity and the Year.
  2. Click Download PDF.

The PDF has the identification, energy consumption (with consumption in MWh by type and the invoice total in kWh), greenhouse gas emissions (scope 1, scope 2 by location and by market, and the total), the emission factors used with the table version, the source and the address, the workforce by gender and the pay gap. The sections carry the codes B1, B3, B8 and B10 of the Basic module of the voluntary VSME standard. The report uses only the data you have already recorded: anything without data appears as "No data recorded". The PDF text follows the language you chose in the application.

e2morrow: materiality

In Materiality you record, by entity and by year, a topic-by-topic preliminary assessment. It is not a double materiality assessment: the platform neither calculates nor suggests values, it stores what your organisation enters.

  1. Choose the Year and the Entity. If there is no assessment yet, Create assessment (Administrator and Editor) creates one with all topics empty.
  2. On each topic, Edit opens a page with the impact scores (scale, scope, irremediable character and, when the impact is potential, likelihood), the financial scores (magnitude and likelihood), from 1 to 5, the Stakeholders and the Justification. Leave empty what you have not yet assessed.
  3. On the same page, under Decision, choose Material, Not material or To be decided. The decision is yours and always carries the Reason.
  4. Thresholds and method lets you write, if you wish, an impact threshold, a financial threshold (from 0 to 5) and a note on the method used. They stay empty until you set them and the platform does not apply them.

Statuses. The assessment starts as Draft; Send for review moves it to In review and Approve (Administrator only) to Approved. Scores can only be edited in draft; decisions also in review. An approved assessment only changes after the Administrator Reopens it. Analyst and Reader view.

The summary at the top counts the topics with a decision, material, not material and to be decided.

e2morrow: frameworks

Frameworks shows the correspondence between GRI disclosures and ESRS requirements, and between ESRS and ISSB. Each row gives the source document, who publishes it, the address and the date it was read, and opens the source in a new window. All roles with access to e2morrow can view.

  • GRI and ESRS: for each GRI disclosure, the ESRS standard and the disclosure requirements that the interoperability index indicates. It is a selection of GRI standards, and the page says which; the other disclosures in the index are not in the table, which does not mean they have no correspondence. The ESRS standard filter shows only one standard.
  • No correspondence: GRI disclosures that the index lists as outside the topic list of the ESRS standards.
  • ESRS and ISSB: only what the interoperability guide states (climate and the definition of financial materiality).

The correspondences are a guide: they do not replace reading the standards and the platform does not apply them to your data. A correspondence that no source read confirms does not appear (for example, there is no correspondence by sustainable development goal).

e2morrow: reports

In Reports, the CSRD tab lists the reports by entity and period. Administrator and Editor create, edit and send for review; only the Administrator publishes. Analyst and Reader view and download the PDF.

  1. New report: choose the Entity, the Title, the Reference year and the period (by default, the full year).
  2. On the report page write the Narratives (Introduction, Materiality, E1, S1 and G1). They are your text: the platform does not write narratives. The text of a section without data is kept, but only appears in the PDF when the section has data; the Introduction appears when at least one section has data.
  3. PDF sections shows what goes in: only the sections with data recorded for that entity and period. A section without data does not appear in the PDF, and with no section with data it cannot be downloaded or published. The data comes from the emissions, the social and governance indicators, the payroll records and the year's materiality assessment.
  4. Download PDF generates the file. In draft and in review the PDF carries the status in the header.
  5. Publish (Administrator only, with the report in review) generates the PDF once, stores it and records its SHA-256. Once published, the report can no longer be edited, change status or be deleted, and Download PDF always delivers the same file, after checking the recorded SHA-256.

A draft can be deleted. Changes are recorded in the audit log (the narratives are not copied there).

e2morrow: ESRS Copilot

In ESRS Copilot you ask questions about the organisation's ESG data (emissions by scope, electricity, social and governance indicators, pay gap and active targets) and get a short answer, with the sources it used (for example "Emissions 2025"). All roles with access to e2morrow can ask, including Reader: the Copilot only reads totals within its scope, the same ones the Dashboard shows, never pay or person codes.

  1. Choose the Year and, if you wish, the Entity.
  2. Write the question (or click a suggestion, which only fills in the field) and click Ask.

The answer is a proposed reading of your data, not a decision: it changes nothing and does not say what the law or the standards require (check the official source). If the answer is not in the data, the Copilot says it is not recorded. Each question uses AI credits from the plan (or the organisation's own AI key) and does not work with AI switched off. Questions and answers stay in your history (only you see them); the text is deleted after 90 days, and you can delete it now with Delete history.

e2morrow: applications

In Applications you see the organisation's applications, with the status and the percentage of required fields filled in, and the template catalogue. Read: all roles. Create and edit: Administrator and Editor.

  1. In New application, choose the template, the entity, the data year and the title.
  2. Fields with data (for example emissions by scope or number of employees) fill themselves in from the records of the chosen year, and each says which year it comes from and from how many records. Without data, the field stays empty (never zero). You can redo the filling with another year in Update with this year: it does not change what you wrote or accepted.
  3. In long text fields, Suggest text with AI shows a proposal. It only enters the field if you click Accept; you can also Edit before accepting or Reject. The field is marked as an accepted AI proposal (or edited by you).
  4. Move the status forward: Start, Submit for review (requires the required fields filled in), Mark as submitted and then approved or refused. You can only edit in "In preparation".

For now the catalogue has one sample template, which does not match any real programme. Real programmes will be added once an official source has been read.

e2morrow: data integrity

In Data integrity you see the alerts from the checks on ESG data. Each alert asks you to confirm the data: it is not an accusation or a conclusion. The checks are: a drop in emissions (12 full calendar months against the previous 12) without an active reduction target, a published report without scope 3, an inactive whistleblowing channel with fines, an emission without a factor, the same quantity repeated six months in a row, data changed after the report was published and payroll records outside the expected range (counts only, never values or person codes).

The checks run every day. Administrator and Editor can click Check now. The same problem does not create two alerts, and a resolved or confirmed alert does not reopen for the same situation (new data creates a new alert). In the alert detail you see the data that raised it and choose the status: Open, Under review, Resolved (you fixed or confirmed it) or Data confirmed (it is correct and stays). Closing requires a note, which is recorded in the audit log. Explain this alert asks the AI, only when you want, for a plain-language explanation and what to confirm; it is a proposal and does not change the alert.

EterShield, an Eter Growth platform