Intelex ESG software: how it works, what your team owns

What the vendor says Intelex ESG software does

Worth reading Intelex's claims with the attribution attached: some describe what the platform actually does, some are promises, and knowing which is which tells you what to test in a demo.

On collection, the sustainability page says you can "collect data monthly, quarterly, semi-annually or annually with predefined forms, built in data validation and automatic escalations for late or missing data." On emission factors, the same page claims "more than 20,000 pre-loaded integrated emissions factors, a patent-pending emission calculation engine." A 2023 vendor blog put the number differently: "a comprehensive library of more than 40,000 emission factors." Two vendor figures, two different dates, and there's no reconciling them here. On frameworks, the ESG page says "pre-configured content packs provide structured forms and reporting indicators that guide data collection for popular frameworks such as the European Sustainability Reporting Standards (ESRS) for the Corporate Sustainability Reporting Directive (CSRD), Carbon Disclosure Project (CDP) and more." On quality, it says "ESG data now must be accurate, valid for compliance needs, free of duplicates, consistent, timely and auditable."

Read that framework sentence closely. It promises forms that guide collection, which is true. It does not promise a finished CSRD report. What a content pack hands you, and what you still have to build, is in the ESRS content pack, and which datapoints have no home in the platform at all is in ESRS datapoints that do not fit.

One line on the ESG product page hasn't aged well. It cites the US SEC's climate disclosure rules as a reason to buy. The SEC voted on 27 March 2025 "to cease the Commission's involvement in the defense of the costly and unnecessarily intrusive climate change disclosure rules." Where every regime actually stands today is in ESG disclosure after the rollback.

The building blocks

Every Intelex application is built the same way: objects that hold records, fields on those objects, workflows made of stages with action buttons, action handlers that run logic when something is created, updated, deleted or on a schedule, business rules, and inventory and detail views. Two things about that architecture do most of the work for ESG.

Every record belongs to a location. You see the records for your location and everything underneath it in the tree, and nothing else. That's how one deployment can cover a global estate without anyone seeing a site that isn't theirs. Action handlers protect data quality too, refusing a bad save outright with a clear message instead of letting it in and flagging it later.

On that foundation, the ESG application has six tabs: Data Entry, Data Corrections, Administration, Configuration, System and Checks. There are two access levels too. Administrators get full access and see the configuration. Contributors get standard access and see only the Data Entry tab. As a configurator, these are the objects you will actually meet:

• Reporting periods, such as a quarter or a year.
• Themes, groupings such as Scope 1, Scope 2, Input/Output, Refrigerants and

Other Emissions.

• Indicator sets, the forms that get collected, each with a frequency of

monthly, quarterly or annual. Stationary and mobile energy, grid electricity and third-party heat, water, waste, production and logistics are the shape of them.

• Indicators and indicator values, the individual metrics and their reported

numbers.

• Indicator set assignments, which decide which location reports which set.
• Data entry forms, one per location, indicator set and period, built by a

form generator that creates them for each period from the assignments.

• Factor objects, factor types, classifications and regions, and global,

regional and local factor values, with a Recalculation Center.

A few more objects exist that the brief behind this library only confirms are there, without saying what they do: objective and target plans by location, historical data, a migration center, and published indicator sets tied to theme versions. They're named here so you know to ask about them. How the building blocks fit together is its own piece on the object model, and which indicators you can configure from them is in the ESG KPIs you can configure.

Coming from EHS rather than sustainability? Here's what the scopes mean, in EPA's own definitions: Scope 1 emissions "occur from sources that are controlled or owned by an organization," and Scope 2 are "indirect GHG emissions associated with the purchase of electricity, steam, heat, or cooling." What each scope asks of the data owner is in Scope 1, 2 and 3 for the data owner.

Who owns what after go-live

No vendor page tells you this part, and most buyers find it out the hard way.

Your implementer builds the plumbing: the objects and indicator structures, the workflows, the rules that block a bad save, the permissions, the integrations and the imports. Once you're live, that layer should change rarely and only on purpose, because a change to an indicator set changes every site's form.

Your ESG team owns what goes on top: creating the reporting periods, entering and reviewing values, approving data, deciding which metrics actually matter. That's the quarterly and annual work, and it falls to the people who have to stand behind the numbers. The team also owns the emission factor decisions, which is where most of the surprises live, and that has its own article in emission factors in Intelex.

If a buyer expects the implementer to run the periods, or an implementer expects the ESG team to change an indicator set, somebody has misread the split. That's how a rollout stalls, and what stalls an Intelex ESG rollout walks through it.

How a number becomes a reported figure

The mechanic, button by button, is in the ESG data entry workflow.

A form gets created for a location, a set and a period. If no values exist yet, the platform creates the empty indicator value records and moves the form to data entry. A contributor fills in the values and submits. A completeness check blocks the submission if any required indicator hasn't been answered, and names the ones that haven't. A complete form goes to review if a reviewer is named on it, straight to approval if only an approver is named, and validates automatically if neither is.

At review, the reviewer validates it or rejects it, and a rejection goes back to data entry with a message attached. At approval, two things get checked: has every required indicator been answered, and is anything still marked as an estimate? A form with an estimated value gets blocked, and you get a list of which indicators are holding it up, until every one is actual. Once it's approved, the form is validated, the approver is recorded, and the assignment and due date clear.

Which gates a form passes through depends entirely on who's named responsible for it, and that is worth pausing on. The estimated-values check only runs at approval, so a form with neither a reviewer nor an approver named skips straight to validated and never meets it. If you need your validated figures to actually be actual, naming one of the two isn't optional. The platform won't warn you if you skip it.

Automated imports with human sign-off

In one deployment, a scheduled import ran hourly through the Event Service and filled in indicator values on its own, with the workflow above sitting on top as governance. People checked what came in, corrected it where needed, commented on it, and signed it off.

That hybrid setup is where most large estates end up. Automation gives scale and consistency, and review and approval give accountability for a number nobody actually typed. It also changes what data entry is for: the person responsible is reviewing, not entering, which needs different training. The Event Service is the same scheduler that runs due-date reminders elsewhere on the platform, and once configured it needs nobody to touch it.

Correcting data without losing the trail

You can't edit a validated form in place, and you can't create a second form for the same location, set and period either. So corrections get their own workflow, the data correction request. Whoever's requesting it lists the values to change, with a reason for each one. They can't submit without at least one line, and can't submit without a reason on every line. The request goes to a named group of correction approvers, who mark which corrections they're approving. They get a warning that any unapproved lines won't be applied, and closing the request records a completion date and notifies whoever asked.

That design exists because an assurance provider asks four questions about any correction: who asked, why, who approved it, and when. All four end up on the record. What that looks like against the assurance standards, and when a correction is really a restatement instead, gets its own article.

The Checks tab: catching stale factors before disclosure

The Checks tab is a data quality dashboard. It flags any calculation still using an outdated global or regional emission factor and needing a recalculation, and shows you the location, the indicator, the period, and the current emission next to the actual emission. It lists year-to-date data issues too.

That's the proactive half of data quality, the half that runs before a disclosure is drafted instead of after an auditor starts asking questions. It's also the fix for a trap this library has already flagged: overwrite a factor value in place, and every figure that used it silently changes too. Why that happens, and how to version factors instead, is in emission factor libraries and the recalculation trap.

ESG inside an EHS platform: the case and the counter-case

The case for Intelex ESG is that it isn't a separate system bolted on. The environmental data, the emission factors and the waste records sit on the same location hierarchy and the same permission model as the legal register, the compliance tasks, the audits, the findings and the corrective actions. A site lead who can already see the site's incidents can see its obligations and its emissions too, with one login and one picture of what that site is. Regulatory content and applicability screening, including the climate and greenhouse gas domains, arrives through that same hierarchy. That's an inference from how the platform is built, not a measured outcome, and it's why a company already running Intelex for EHS tends to look at its ESG application first.

The counter-argument is real too. Dedicated carbon and ESG tools go deeper on emissions analytics, and the analyst view of ESG reporting has shifted. Intelex's own product page still carries a 2023 badge: "Intelex Named a Leader in ESG Reporting and Data Management Software in All New Green Quadrant Report." The 2025 edition of that same Verdantix report assessed 21 vendors and named 15 Leaders: "AMCS, Benchmark Gensuite, Cority, EcoOnline, IBM, Nasdaq, Novisto, osapiens, Schneider Electric, Sphera, Sweep, UL Solutions, Watershed, Wolters Kluwer and Workiva." Intelex isn't on that list. Its exact placement in the 2025 report sits behind a paywall, so this article won't guess at it. In the separate 2026 Verdantix report on EHS software, Intelex is named a Leader, scoring highest in "audits and inspections, incident management, and safety management."

Put plainly: a strong EHS platform with an ESG application riding on top. That's rewarded by the analyst category for EHS, and it wasn't rewarded by the analyst category for ESG reporting, in the most recent public edition. Whether that trade works for you is a selection question, not a product question, and the comparisons with Enablon, Sphera and Cority are where to weigh it. The governance case rests on things you can check in a demo: location binding, save-blocking validation, stage permissions, the estimated-values gate and the reasoned correction. Ask to see every one.

The location hierarchy carrying all of this has to be designed for the job, and location hierarchy design covers that. The consolidation boundary a disclosure needs isn't the same tree, and consolidation boundary versus location hierarchy covers that too. Who can see and do what across that tree is in rights versus permissions, and the segregation of duties an assurance provider expects is in the segregation of duties assurance trap.

What this does not tell you

Intelex's exact placement in the 2025 Verdantix ESG report, beyond the fact that it was assessed and not named a Leader. Which of the two emission factor counts is current, since the vendor's own pages disagree with each other. Whether "Corporate Reporting for ESG" is still the commercial name, since one vendor page uses it and the product page uses neither name. What objective and target plans, historical data, the migration center and theme versions actually do, since they exist and nothing in the material this library is written against describes them. The price. And what the "automatic escalations for late or missing data" the vendor promises actually look like in configuration, since that's a vendor claim this article is repeating, not confirming.