Method / Overview

Methods and evidence

How Greenophy analyses company disclosures and physical climate hazards, with examples, data sources and limitations.

01 / Business Model Engine

From disclosures to a business profile

The engine identifies the activities a firm describes, who it serves and the quantities it reports. Findings retain the legal entity, reporting period and supporting evidence.

Data sources. Official identity records; annual reports, Pillar 3 and relevant sustainability disclosures; and the firm’s official business and product pages. Availability varies by firm. Website evidence may have no reporting year.

  1. Find and scopeMatch the entity and collect sources. Keep the bank, subsidiaries and wider group distinct.
  2. Read and extractCapture passages and tables: activities, customers, locations and reported amounts.
  3. Classify and checkMap supported descriptions to business lines; check evidence, scope, units and period. Retain review items.
  4. Show the evidenceReturn a profile with source links and gaps. A missing disclosure is not a zero or an absent business.

A country total and an industry total do not disclose their intersection. Without a joint disclosure, the country–industry amount is not disclosed.

From public disclosures to a business modelA 36-second authored, fictional Northbank example, not a live engine run. Establish the reporting entity, read passages in context, identify the provider, activity and customer, and map disclosed activities to standard business lines. Borrower industries retain company-wide scope. Fictional operating locations connect London to the head office, Manchester to corporate lending and Leeds to asset finance. These are separate from the UK-wide mortgage book and do not establish property locations. A 2025 table reports loans and advances in GBP billions: home loans 8.2 and business finance 1.4. The business finance balance is not split between corporate lending and asset finance. Select a completed finding to inspect its illustrative evidence. UK outline: Natural Earth, public domain. FICTIONAL EXAMPLE Northbank Profile07 / 07 Offices · London, Manchester, Leeds Select a result for evidence.

Business model / Examples

Follow a finding back to its source

The Northbank animation is fictional and illustrates the workflow. The full guide uses real HSBC UK report passages and a saved review item to show what the evidence can establish.

Explore the HSBC UK worked example Source passage · Interpretation · Checks · Result

02 / Climate Hazard Engine

From a place to a hazard measure

The engine samples observed records and modelled data for a resolved location. Each hazard has its own calculation and units; these readings are not combined into a single risk score.

Data sources. Published flood maps; NASA NEX-GDDP-CMIP6 climate projections; NOAA cyclone tracks; NASA fire detections; Hydro-JULES drought data; IPCC sea-level projections; Copernicus coastal water levels and soil moisture; and ISRIC soil properties.

  1. Resolve the placeUse a point or stated boundary. Record the source resolution and any nearby-point fallback.
  2. Select the inputKeep the observation period or projection scenario, horizon and baseline with the data.
  3. Calculate the measureFor example, count wet cells, average threshold days, or summarise depths. The reduction depends on the hazard.
  4. Report the limitsShow the value, units, coverage and source. No data is distinct from a measured zero.

Hazard describes a physical condition. Exposure locates people, assets or activities in that condition. Risk also depends on vulnerability and consequences; these hazard readings do not estimate financial loss.

From a place to a traceable hazard readingA 73-second explanation of the Climate Hazard Engine. Type London, resolve its real GHS urban boundary and select appropriate sources. Real examples from the methodology page: JRC 100-year undefended river flood, 44,140 wet cells out of 347,789, 12.69%, median wet-cell depth 1.758 metres; England FIRMS 2025, 2,017 vegetation-fire detections out of 3,979, density 0.0423 per 1,000 square kilometres per day; London SoilGrids 60–100 cm, 418 predicted cells out of 1,864, 22.4% coverage and 35.3% median clay; the nearest central London Hydro-JULES cell, first-decade mean SPEI -0.0124 and last-decade mean 0.3354, change +0.3478. Point and boundary readings remain distinct. Cyclone uses the existing real IBTrACS Vamco example near Manila in November 2020: two recorded positions within 100 km count as one storm, retaining the closest recorded pass at 64.9 km. The coastline, search-radius geometry and track positions are copied from the full method page. Connecting segments add no observations. Heat days and soil-water shortfall use explicitly hypothetical method illustrations, not local hazard results. The coastal section is schematic, with actual Hull example values: AR6 SSP2-4.5 in 2100 has medium-confidence median rise 0.586 m and low-confidence median 0.573 m, each with its own 17th–83rd range. The GTSM 100-year height is 5.735 m; adding the medium-confidence rise gives a conditional 16.2-year recurrence under fixed storm climate. GTSM and AR6 baseline periods differ and the offset is unadjusted. Neither illustration maps inundation or flood defences. Flood defences are not represented in the JRC example. The final three graphics retain each example’s spatial scope: boundary flood cells, sorted clay coverage cells and nearest-point SPEI change. Source references remain on the full methodology page. No composite score is calculated.PlaceUrban boundaryLondonLondon · urban footprintHazardsNine hazard categoriesFloodExtent & depthHeatHot daysDroughtWater-balance anomalyWildfireThermal detectionsCycloneNearby storm tracksSea levelMean sea-level riseExtreme waterHeight & recurrenceSubsoil clayClay at depthSoil deficitBelow a local thresholdFloodLondon · 100-year model44,140wet cells347,789boundary cells12.69%wet cells1.76 mmedian wet-cell depthUndefended river floodHeatIllustrative weekDry bulb> 35 °C323536363838343737353 / 7 daysWet bulb> 31 °C2830313232293333312 / 7 daysStrictly above the thresholdWildfireEngland · 20253,979 detections2,017vegetation fire1,962other · excluded130,541.3 km² × 365 days0.0423detections / 1,000 km² / dayDetections ≠ distinct firesSubsoil clayLondon · 60–100 cm418 predicted1,446 unpredicted35.3%median clay22.4%coverageSorted cells · not a geographic mapMap unshadedDroughtLondon · nearest point cellMean SPEI1981–19902013–2022−0.012+0.3350 = local normal+0.348SPEI change · wetterPoint reading · not a boundary averageSoil deficitMethod illustrationSoil-water indicatorLocal 5th percentileRelative to local historyTotal shortfallTropical cycloneVamco · Manila · November 2020Manila100 km2 nearby records1 stormClosest recorded pass · 64.9 kmNearby observations · not a local wind or damage mapSea levelHull · 2100 · SSP2-4.5 Reference mean level Mean rise+0.586 mHull coastMedium- and low-confidence projectionsMedium confidence0.586 mMedian · 17th–83rd rangeLow confidence0.573 mMedian · 17th–83rd rangeSchematic section · mean change, not flood depthExtreme water levelHull · 2100 · SSP2-4.5 · medium confidence Reference mean level Same extreme height · 5.735 mMean rise+0.586 mReturn period at the same heightPresent day100 yearsWith mean sea-level rise16.2 yearsSchematic section · conditional recurrenceFixed storm climate · baseline offset unadjustedLondonSelected resultsFlood12.69%Wet cells within the boundary100-year · undefended river floodPredicted / unpredicted cellsSubsoil clay35.3%Clay · predicted cells only60–100 cm · 22.4% coverageFirstLastFirst vs last decade · SPEIDrought+0.348 SPEIWater-balance changeNearest point cell · 1981–2022

Climate hazard / Examples

See how the result is calculated

In the London flood example, 44,140 wet cells divided by 347,789 sampled boundary cells gives 12.69%. This is a cell-count share of an undefended flood model, not a share of a bank’s assets.

Inspect the London inputs and calculation JRC · Present-day river flooding · 100-year return period

The animation also contains labelled method illustrations. The guide distinguishes them from measured source outputs.

Seven places a model reads, each checked and labelledAn 86-second authored, fictional Northbank example, not a live engine run. Seven places where a language model reads, each with its source, the model’s reading, one code check and the label it earns: finding a missing Pillar 3 report and refusing a candidate whose cover names another company; identifying the reporting entity of a sustainability report by exact name; withdrawing an asset management activity that rests only on a template row; attributing life cover to Harbour Life Assurance Ltd after a word-for-word quotation check and a second reading; counting Leeds as an office but not Spain, mentioned in passing; drafting a climate target whose values are checked against the quotation, with an unsupported “on track” claim dropped; and a note on a London flood reading whose figures must all appear in the reading. The film ends on a workbench list of the seven labelled results; select one to read its evidence. FICTIONAL EXAMPLE Northbank Finding reports01 / 08

03 / Use of AI

How AI is used and checked

Language models read company disclosures where fixed rules cannot. Every answer must point to its source, is checked by code and is labelled as AI in the workbench. Hazard figures, amounts and identifiers stay with code.

Example · Where AI is used · Checks · Labels