Introduction
Valuation is an evidence and judgement process. Comparable transactions, trading multiples, operating forecasts, discount rates and scenario assumptions become useful only when they are tied to a defined asset, valuation date, unit of account, purpose and market-participant perspective. Artificial intelligence can accelerate evidence collection, normalisation, comparable screening, model execution, sensitivity analysis and narrative production. It cannot decide the legal perimeter of the asset, make weak evidence reliable, remove market uncertainty or assume the accountable valuer's authority.
This paper addresses AI-Augmented Valuation: From Comparable Analysis to Scenario Modelling for two Matchpoint Partners target audiences. A2 Family-Office CIOs and Heads of Alternatives include investment professionals at single-family offices, multi-family offices, private wealth firms, private banks and external asset managers across the GCC, United Kingdom, Switzerland, Singapore and the European Union. B1 UAE/GCC Real Estate Developers and Sponsors include founders, chief executives, chief financial officers and capital-markets teams raising debt, mezzanine or joint-venture equity and monetising assets. A2 teams need consistent portfolio and transaction decisions across public and private evidence. B1 teams need defensible values for capital raising, development decisions, refinancing, joint ventures and asset sales.
The governing question is: how can an organisation multiply valuation productivity and decision coverage while preserving evidence quality, uncertainty, professional judgement and accountability? The answer is a governed valuation system. It separates source evidence from transformations, comparable screening from adjustment, point estimates from scenario distributions, model output from decision authority and measured productivity from attributed commercial value.
IFRS 13 defines fair value as an exit price in an orderly transaction between market participants at the measurement date. It requires valuation techniques appropriate to the circumstances, maximisation of observable inputs and minimisation of unobservable inputs [1]. The International Valuation Standards effective from 31 January 2025 contain dedicated standards for data and inputs, valuation models, documentation and reporting [2]. The 2025 IPEV Valuation Guidelines apply this fair-value discipline to private capital [3]. RICS describes automated valuation models as a spectrum that can support or form part of a valuation process, with professional involvement depending on purpose, market, data and risk [4-5].
These requirements support augmentation, provided every material transformation remains reviewable. A comparable engine can find candidates rapidly. The valuer still needs to establish why each transaction is relevant, which adjustments are supportable and whether the resulting range reflects the subject asset. A forecasting engine can calculate hundreds of cases. The decision-maker still needs to approve the economic states, dependencies, management actions and probability treatment. A language model can draft a memorandum. It still needs a controlled evidence pack and human approval.
Regional evidence is expanding. Dubai Land Department provides open real-estate data covering transactions, rents, projects and valuations [11]. It reported 60,303 real-estate transactions with a value of AED 252 billion in the first quarter of 2026 [12]. Those data improve market observability for selected questions. They do not make every asset homogeneous, eliminate related-party effects, identify every commercial term or establish a value without adjustment.
AI adoption also changes the control perimeter. The Central Bank of the UAE's Model Management Standards require governance, traceable data, documented development, approval, independent validation and ongoing monitoring for models used in decision-making [6]. The DFSA reported in 2025 that 52 per cent of 661 authorised firms responding to its survey were actively using AI; governance maturity varied, with 21 per cent reported as lacking clear accountability [9]. NIST's AI Risk Management Framework organises controls around Govern, Map, Measure and Manage [7-8]. The Federal Reserve's April 2026 revised model-risk guidance and the PRA's April 2026 supervisory statement reinforce risk-based inventory, governance, development, validation, monitoring and mitigants within their banking scopes [14-15].
The contribution is a practical system that provides:
- a defined valuation perimeter for A2 and B1 decisions;
- an evidence ledger and source-to-output lineage;
- a comparable-selection and adjustment protocol;
- a hybrid modelling architecture that combines transparent methods with machine learning;
- a governed scenario engine;
- validation, uncertainty and abstention gates;
- two unverified illustrative scenarios;
- an evidence-gated productivity and revenue bridge; and
- a ninety-day adoption roadmap.
The analysis reviews primary academic studies, official standards, regulator publications and official market-data sources available through 1 August 2026. Regulatory and accounting applicability depends on entity, jurisdiction, purpose, client, asset and reporting basis. Empirical studies are reported within their studied samples. No approved observed Matchpoint or client evidence was supplied for T27 revenue, cash cost reduction, loss reduction or alpha. Those attributed values remain USD 0.
The Valuation Perimeter
Purpose precedes method
A valuation process should begin with a signed instruction, not a model choice. The instruction should specify the subject interest, legal and economic rights, unit of account, valuation date, currency, purpose, basis of value, intended users, restrictions, material assumptions and reporting standard. A shareholding, property, development project, debt instrument, fund interest and operating business can require different evidence even when a dashboard presents them in one portfolio.
| Perimeter field | Minimum question | Failure if unresolved |
|---|---|---|
| Subject interest | What right, asset, liability or enterprise is being valued? | Model addresses the wrong economic object |
| Unit of account | Which aggregation or disaggregation is measured? | Portfolio and asset values are mixed |
| Valuation date | What information was known or knowable at the date? | Hindsight contaminates the conclusion |
| Purpose | Investment, transaction, reporting, lending or internal decision? | Controls and basis are mismatched |
| Basis | Fair value, market value, investment value or another defined basis? | Users interpret a different concept |
| Market | Which principal or most advantageous market and participants apply? | Comparables reflect the wrong buyer set |
| Currency | Which reporting and transaction currencies apply? | FX and inflation assumptions are hidden |
| Authority | Who develops, reviews, approves and relies on the output? | Model output becomes unauthorised advice |
IFRS 13's fair-value framework is specific to measurements required or permitted by other IFRS standards [1]. It does not create a general requirement to fair-value every decision. The SEC's Rule 2a-5 addresses good-faith fair-value determinations by registered investment companies and business development companies in the United States [13]. Its framework is useful comparative evidence for risk assessment, methodology selection, testing, pricing services, oversight and records. Its legal applicability is confined to its stated scope.
Price, value and decision are separate outputs
An observed price records a transaction under its actual terms. A valuation estimates a defined basis at a date. An investment decision compares the estimated distribution of outcomes with mandate, liquidity, risk, alternatives and required return. A price may be a valid data point and an unsuitable comparable. A fair-value estimate may be supportable and unattractive to a particular family office. A developer's land value may differ under an orderly market-participant assumption and a sponsor-specific strategic plan.
The system should therefore retain three outputs:
- Evidence output: verified transactions, quotes, rents, costs, rates and operating observations.
- Valuation output: method-specific indications, ranges, weights, overlays and conclusion.
- Decision output: approved action, limits, conditions, timing and accountable owner.
The separation prevents the model from silently converting a prediction into an investment recommendation or a financing commitment.
A2 and B1 decision rights
| Dimension | A2 family-office team | B1 developer or sponsor | Shared control |
|---|---|---|---|
| Primary decision | Allocate, hold, sell or restructure | Acquire, build, finance, partner or exit | Defined purpose and approval owner |
| Evidence focus | Manager, asset, cash flow, market and liquidity | Land, sales, lease, cost, programme and capital stack | Dated source ledger |
| Comparable focus | Securities, funds, transactions and portfolio marks | Land, unit, building, project and corporate transactions | Relevance and adjustment record |
| Scenario focus | Return, liquidity, concentration and downside | Absorption, price, cost, timing, leverage and exit | Dependent drivers and state logic |
| Key overlay | Mandate and concentration | Execution and planning constraints | Independent challenge |
| Final authority | CIO and investment committee | Board, investment committee and financing authority | Recorded decision |
The adviser can structure evidence, models and options. The client's authorised body owns the decision. Engagement terms should state the valuation purpose, data access, reliance, limitations, conflicts and approval workflow.
What Current Standards Require
Market evidence and calibrated technique
IFRS 13 recognises market, income and cost approaches and permits one or multiple techniques [1]. The technique should be appropriate to the circumstances and supported by sufficient data. Inputs should maximise relevant observable evidence. A model used to value an unobservable input at initial recognition should be calibrated so that it is consistent with the transaction price when that price represents fair value. Techniques should be applied consistently, while a change can be appropriate when it produces a measurement equally or more representative of fair value.
This creates a test for AI use. More variables, faster calculation or a lower in-sample error does not establish a more representative valuation. The team needs evidence that the technique fits the subject, market, date and intended use.
Data, model, documentation and reporting
IVS effective from 31 January 2025 introduced a revised general-standard structure including IVS 104 Data and Inputs, IVS 105 Valuation Models and IVS 106 Documentation and Reporting [2]. The structure supports a lifecycle view:
- define the scope and basis;
- source and evaluate data;
- select and apply models;
- exercise professional judgement;
- retain material documentation; and
- report a conclusion with assumptions and limitations.
The IPEV 2025 Guidelines provide current private-capital good practice [3]. Private markets frequently require unobservable inputs, calibration, consideration of company performance, market evidence and judgement. AI can improve consistency and coverage. A model's opacity or a vendor label cannot remove the requirement to understand the material drivers of the conclusion.
Automated valuation models
RICS treats AVMs as a spectrum rather than a single product [4]. At one end, a model can deliver an automated estimate with no case-specific professional intervention. At the other, analytics support a professional valuation. RICS bank-lending guidance states that an AVM may be appropriate where property is sufficiently uniform, markets are active and data are adequate, subject to validation and the agreed instruction [5]. Unique, development, specialised or thinly traded property needs stronger case-specific review.
The control implication is a three-level taxonomy:
| Level | Output | Human role | Permitted use |
|---|---|---|---|
| Screening | Rapid candidate range or anomaly flag | Review exceptions and relevance | Triage, pipeline and monitoring |
| Assisted valuation | Model indications plus evidence pack | Select method, adjust, reconcile and approve | Defined internal or professional process |
| Automated decision | Output triggers an action or limit | Approve policy, thresholds and exceptions | Only within validated, bounded use case |
Marketing should describe the actual level. An AI-assisted memorandum should not be represented as an independent professional valuation unless the engagement, standard, competence and approval support that description.
The Valuation Evidence Ledger
Evidence objects
A governed process stores evidence as structured, dated objects. A number in a spreadsheet should retain its source, observed date, effective date, currency, unit, geography, asset attributes, transaction status, relationship status, confidence, transformations and reviewer.
| Evidence class | Examples | Minimum provenance | Common defect |
|---|---|---|---|
| Executed transaction | Sale, funding round, asset disposal | Instrument, parties, date, consideration, terms | Headline value omits debt or conditions |
| Market quote | Listed price, yield, spread, rent | Venue, timestamp, bid or ask, liquidity | Stale or non-executable indication |
| Operating evidence | Revenue, occupancy, churn, margin | Source system, period, accounting policy | Management forecast presented as actual |
| Asset evidence | Area, use, location, age, specification | Registry, survey, contract, inspection | Unverified listing attribute |
| Cost evidence | Construction, fit-out, operating cost | Contract, tender, invoice, index | Scope and inflation mismatch |
| Macro evidence | Rates, inflation, FX, sector activity | Official release and vintage | Revised data or wrong vintage |
| Expert assumption | Adjustment, probability, overlay | Named owner, rationale, date | Judgement hidden as model output |
Dubai Land Department's open-data service is an official source for selected transaction, rental, project and valuation fields [11]. The dataset should be profiled before use: missing fields, duplicates, changes in coding, transaction type, unit conventions, geography and time lags can affect results. The existence of a field does not establish that it is complete or economically comparable.
Source-to-output lineage
Every material output should be reproducible through five links:
- source file, record or endpoint;
- immutable ingestion snapshot;
- transformation code and version;
- model and parameter version; and
- report cell, chart or paragraph.
The evidence ledger should record manual changes separately from source values. If an analyst excludes a transaction, changes a cap rate or applies a quality adjustment, the system should retain the prior value, new value, owner and reason. This design supports review and permits a future reviewer to recreate the information set available at the valuation date.
AI extraction boundary
Language and document models can extract lease dates, rent reviews, covenants, cap tables, transaction terms and operating metrics. Extraction should be treated as a proposed structured record until verified against the source passage. The record should include the document identifier, page or cell, extracted text, normalised value, model version, confidence and reviewer disposition.
The system should abstain or require manual review where:
- the source is scanned, incomplete or internally inconsistent;
- an amount lacks currency or unit;
- a clause depends on definitions elsewhere;
- a table merges actual, budget and forecast periods;
- a transaction value depends on debt, earn-outs or contingent consideration;
- a property attribute conflicts with official evidence; or
- the model's confidence or rule-based validation falls below the approved threshold.
Abstention is a control outcome. It directs scarce expert time to the cases where automation is least reliable.
Comparable Analysis As A Controlled Pipeline
The comparable question
A comparable is an observation that helps estimate how market participants would price the subject after relevant differences are considered. Similar names, sectors or postcodes are insufficient. The pipeline should define the economic relation between subject and candidate.
For an enterprise, dimensions can include business model, geography, revenue quality, growth, margin, capital intensity, leverage, size and transaction date. For property, dimensions can include submarket, permitted use, tenure, size, age, specification, occupancy, income quality, lease duration, development status and sale terms. For a fund interest, dimensions can include strategy, vintage, remaining life, unfunded commitment, concentration, NAV date and transfer restrictions.
Candidate generation and eligibility
The first stage maximises coverage within written boundaries. Search can use databases, registries, semantic document retrieval and structured filters. The second stage applies hard eligibility rules. The third stage ranks relevance. The fourth stage requires analyst review.
| Stage | Machine contribution | Human contribution | Evidence retained |
|---|---|---|---|
| Universe | Search and ingest eligible sources | Approve source list | Query, source and timestamp |
| Eligibility | Apply date, type, geography and status rules | Resolve ambiguous cases | Rule result and exception |
| Similarity | Score attributes and economic drivers | Challenge omitted variables | Feature vector and score |
| Adjustment | Estimate time, scale and quality effects | Approve rationale and bounds | Raw and adjusted indication |
| Reconciliation | Calculate ranges and diagnostics | Weight evidence and conclude | Method bridge and sign-off |
The original universe should remain visible. A final report that shows only selected transactions can hide selection bias. Reviewers need excluded candidates and coded reasons such as wrong instrument, different market, distress, related party, incomplete terms, stale date or incompatible rights.
From direct matching to feature adjustment
Hedonic analysis models price as a function of characteristics. Rosen's 1974 framework established the economic basis for implicit prices in differentiated products [17]. Modern comparable systems can extend the idea through regularised regression, tree ensembles and other nonlinear methods. Random forests combine de-correlated trees and provide flexible prediction and variable-importance tools [18]. Gradient boosting builds an additive function through sequential optimisation of a loss function [19].
These methods can identify nonlinear relations and interactions. Their use still requires controls:
- the target variable must match the valuation question;
- training observations must precede or be valid at the valuation date;
- leakage from future or derived outcome fields must be removed;
- feature engineering must reflect economically available information;
- cross-validation should respect time, entity and geography;
- error should be reported by relevant segment, not only in aggregate;
- out-of-distribution subjects should be flagged; and
- the model should support review of material drivers.
Lundberg and Lee's SHAP framework assigns feature contributions to individual predictions within an additive explanation class [20]. An explanation shows how a model produced an output. It does not prove causal effect, data quality, fairness or valuation appropriateness. A large positive feature contribution can reveal reliance on a variable that should have been excluded.
Adjustments and ranges
An adjustment should state direction, basis, magnitude and uncertainty. A property transaction six months earlier can require a time adjustment supported by an index or paired evidence. A smaller company can require a size or liquidity consideration. A development land transaction can require planning, infrastructure and payment-term adjustments. A private-company transaction can require analysis of security rights and capital structure.
| Adjustment | Evidence hierarchy | Required challenge |
|---|---|---|
| Time | Repeat sales, official index, same-market model | Does the index match the asset segment? |
| Scale | Matched transactions, model partial dependence | Is scale proxying for quality or location? |
| Quality | Physical or operating attributes | Are attributes measured consistently? |
| Rights | Legal documents and security terms | Does headline consideration include preference? |
| Liquidity | Executed secondary evidence and restrictions | Is the discount double-counted elsewhere? |
| Control | Voting and governance rights | Is the observed deal strategically motivated? |
| Financing | Cash-equivalent consideration | Are deferred terms and debt normalised? |
The output should be a distribution or range, not artificial precision. The range can combine model uncertainty, input uncertainty and scenario uncertainty. Wider ranges should trigger greater review, lower reliance or an explicit decision to abstain.
The Hybrid Valuation Architecture
Transparent core, machine support and approved overlays
The architecture should keep the economic method visible. Machine learning can support evidence discovery, comparable ranking, nonlinear adjustment and error detection. A transparent core retains the market, income and cost logic required for review.
The minimum architecture contains:
- source layer: official, vendor, client and market evidence with access controls;
- evidence layer: versioned observations, normalisation and quality flags;
- model layer: direct comparable, regression, tree model, DCF, residual land and cost models;
- scenario layer: states, dependencies, management actions and probability treatment;
- control layer: inventory, approval, validation, thresholds, overrides and monitoring;
- decision layer: report, committee paper, conditions and accountable sign-off; and
- learning layer: realised outcomes, errors, exceptions and remediation.
Model inventory and intended use
CBUAE Model Management Standards define expectations across governance, data, development, validation, implementation and use [6]. The Federal Reserve's SR 26-2 superseded SR 11-7 in April 2026 and emphasises a risk-based approach tailored to the organisation's model profile, size and complexity [14]. The PRA's current SS1/23 sets five principles covering identification and classification, governance, development and use, independent validation and mitigants within its stated banking scope [15].
The valuation inventory should include statistical, financial, rules-based and generative components. A comparable-ranking algorithm can materially influence value even if it does not calculate the final number. A spreadsheet with judgemental macros can be a model. A vendor API remains within the user's governance perimeter.
| Inventory field | Minimum content |
|---|---|
| Identifier | Unique model and component ID |
| Owner | Business owner and technical owner |
| Purpose | Approved decision and users |
| Scope | Asset, geography, date and value range |
| Method | Theory, algorithm and transformation |
| Data | Sources, fields, lineage and restrictions |
| Materiality | Exposure, frequency, judgement and consequence |
| Validation | Reviewer, date, tests and findings |
| Limits | Unsupported cases and abstention rules |
| Monitoring | Error, drift, override and incident metrics |
| Version | Code, parameters, model and prompt |
| Status | Development, approved, restricted or retired |
Generative AI as an interface layer
Generative AI can query the evidence ledger, draft comparable summaries, explain scenario differences and create committee-paper sections. It should retrieve from controlled sources and cite the underlying record. Deterministic calculations should run in controlled code or financial models. The language model should not be the sole calculator for material values, probabilities or covenants.
NIST's Generative AI Profile identifies risks such as confabulation, data privacy, information integrity and human-AI configuration [8]. A safe design constrains the model's tools, data domains, output schema and permissions. It logs prompts, retrieved evidence and outputs where legally and operationally appropriate. Material statements require source checks.
Scenario Modelling
Scenarios are coherent states
A sensitivity changes one input while holding others constant. A scenario describes a coherent state in which several drivers move together and may trigger management actions. A probability distribution describes a broader set of outcomes under a defined stochastic structure. These tools answer different questions.
For a developer, slower absorption can coincide with greater incentives, lower cash collections, longer construction financing and a later exit. For a family office, lower exit multiples can coincide with weaker earnings, delayed liquidity and a changed FX or interest-rate environment. Independent one-variable sensitivities can understate these dependencies.
Driver map
The scenario engine should start with causal and contractual links that management can review.
| Driver class | B1 example | A2 example | Dependency |
|---|---|---|---|
| Demand | Unit absorption and price | Portfolio-company revenue | Macro, segment and competition |
| Delivery | Construction programme | Company execution plan | Cost, staffing and permissions |
| Cost | Materials, contractor and finance | Margin and follow-on capital | Inflation, scale and timing |
| Capital | Loan-to-cost, covenant and draw | Commitment, call and liquidity | Value, cash flow and rates |
| Exit | Asset sale timing and yield | Multiple, IPO or secondary sale | Market state and performance |
| FX/rates | Debt and imported cost | Reporting return and discount rate | Currency and hedge policy |
| Management action | Rephase, reprice or refinance | Reserve, sell or follow on | Authority and execution lag |
The model should prevent internally inconsistent combinations unless the purpose is to test an extreme dislocation. A rapid sales case with severe price cuts can be valid. It needs an explicit elasticity assumption. A low-rate case with a higher discount rate can be valid if risk premia widen. It needs the decomposition.
Scenario construction protocol
- Define the decision, horizon and valuation date.
- Select material economic and contractual drivers.
- Establish a central case using approved evidence.
- Define alternative states with coherent driver movements.
- Add management actions with authority, cost and delay.
- Calculate cash flows, financing, covenants and terminal values.
- Reconcile results to market and cost evidence.
- Assign probabilities only where governance and evidence support them.
- Report unweighted cases where probabilities would create false precision.
- Record the action thresholds triggered by each state.
AI-supported scenario generation
AI can scan official releases, market evidence, operating reports and contracts to propose risk drivers. It can cluster historical states and search for omitted dependencies. It can generate candidate narratives and challenge assumptions. Candidate scenarios remain proposals until a responsible owner approves them.
The system should distinguish:
- observed state: supported by dated evidence;
- management case: approved plan or budget;
- market-participant case: assumptions consistent with the defined basis;
- stress case: deliberately severe but coherent;
- reverse stress: state that breaches a value, liquidity or covenant threshold; and
- exploratory case: low-evidence possibility retained for strategic discussion.
Probabilities should not be generated from language-model fluency. They require a stated statistical, market or governance basis.
Validation, Uncertainty And Abstention
Validation is independent challenge
Validation should cover concept, data, implementation, performance, use and reporting. Independence should be proportionate to materiality. The reviewer needs sufficient authority, competence and access to challenge the model and restrict use.
| Validation dimension | Test | Evidence |
|---|---|---|
| Concept | Economic rationale and intended use | Method paper and benchmark |
| Data | Completeness, provenance, leakage and representativeness | Data profile and lineage |
| Implementation | Code, formula, integration and access | Reperformance and code review |
| Performance | Error, calibration, ranking and stability | Out-of-sample results |
| Segment | Geography, size, type and time | Segment scorecard |
| Uncertainty | Coverage and interval behaviour | Coverage and width tests |
| Explainability | Driver consistency and reviewer comprehension | Case-level explanations |
| Use | Overrides, exceptions and decision adherence | Usage and override log |
| Reporting | Claims, limitations and reproducibility | Report checklist |
Error measures
Mean absolute error is interpretable in currency units. Median absolute percentage error reduces the influence of extreme percentage errors. Root mean squared error penalises large misses. Rank correlation can test screening performance. Calibration tests whether stated intervals contain realised outcomes at the expected frequency. No single measure is sufficient.
Kok, Koponen and Martinez-Barbosa reported a 9 per cent absolute error for their automated model on a defined sample of US multifamily assets [22]. The result is relevant evidence that an AVM can outperform selected appraisal benchmarks in a particular setting. It should not be transferred to GCC development projects, private companies or every property segment without new validation.
Prediction intervals
Point estimates hide uncertainty. Conformal prediction can create distribution-free prediction intervals with finite-sample marginal coverage under its assumptions, using a calibration set around a chosen predictive model [21]. Coverage can deteriorate under distribution shift, and marginal coverage does not guarantee equally strong coverage for every subgroup or asset.
An institutional report should show:
- central indication;
- approved valuation range;
- statistical prediction interval where applicable;
- scenario range;
- material unobservable inputs;
- comparable dispersion;
- out-of-distribution status; and
- decision threshold.
Abstention matrix
The engine should return manual valuation required when evidence or model fitness falls outside its approval.
| Trigger | Example | System response |
|---|---|---|
| Sparse evidence | No recent similar transactions | Widen range and escalate |
| Unique asset | Specialised property or unusual security | Disable automated conclusion |
| Material conflict | Registry and client data disagree | Stop and resolve source |
| Distribution shift | New regime or geography | Restrict use and revalidate |
| High leverage | Small value change breaches covenant | Add financing and reverse stress |
| Unverified legal right | Security terms incomplete | Hold valuation conclusion |
| Model disagreement | DCF and market approach diverge materially | Reconcile methods and assumptions |
| Excess override | Frequent analyst changes | Investigate model or process |
The Before-And-After Operating Model
Current fragmented workflow
Many valuation processes distribute work across email, folders, spreadsheets, PDF reports and market databases. Analysts rekey information, rebuild comparable tables, manually change dates and trace figures after a reviewer asks a question. The same work is repeated for monitoring, committee papers and lender materials. Control depends on individual file discipline.
Controlled target workflow
| Stage | Current pattern | Controlled target |
|---|---|---|
| Instruction | Email and inherited template | Structured purpose, date, basis and authority |
| Evidence | Manual search and copy | Versioned ledger with provenance |
| Comparables | Analyst-selected table | Full universe, rules, ranking and exclusions |
| Forecast | Separate spreadsheet versions | Approved drivers and scenario graph |
| Review | Comments on static output | Case-level evidence, diagnostics and overrides |
| Report | Manual narrative | Source-linked draft with human approval |
| Monitoring | Calendar-driven rerun | Data, market, error and event triggers |
| Learning | Informal experience | Realised outcome and remediation register |
The target process shifts expert time from retrieval and reformatting toward perimeter decisions, evidence challenge, adjustment, scenario design and conclusion. That shift should be measured through accepted outputs, not raw drafts.
Two Unverified Illustrative Scenarios
Scenario A: B1 development decision
[Unverified illustrative scenario] A UAE/GCC developer is evaluating a mixed-use project. All figures, dates and outcomes in this subsection are unverified management assumptions created to demonstrate the framework. They are not a valuation, forecast or transaction recommendation.
| Input | Central | Downside | Upside |
|---|---|---|---|
| Net sellable area | 500,000 sq ft | 500,000 sq ft | 500,000 sq ft |
| Average realised price | AED 2,250/sq ft | AED 1,950/sq ft | AED 2,450/sq ft |
| Sales absorption period | 36 months | 54 months | 27 months |
| Hard and soft cost | AED 720m | AED 790m | AED 700m |
| Financing and holding cost | AED 95m | AED 155m | AED 75m |
| Other project cash outflow | AED 115m | AED 125m | AED 110m |
The central gross development revenue is AED 1.125 billion before incentives, cancellations, taxes, fees and other adjustments. The downside case combines lower price, slower absorption, cost escalation and longer financing. The upside case combines stronger price, faster absorption and lower financing duration. The dependencies prevent the model from treating each driver as an isolated sensitivity.
The comparable module searches official and approved vendor evidence for land, unit and completed-asset transactions. It retains the full candidate universe, then filters for location, use, status, date and transaction type. The reviewer approves adjustments for payment plan, view, specification, completion stage, title and bulk terms. The scenario module then translates price and absorption into collections, construction funding, debt use and equity requirements.
Decision thresholds can include maximum peak equity, minimum interest coverage, covenant headroom and minimum return under the downside state. The model should show which assumption first causes a breach. AI may draft the variance explanation. The finance and investment authorities approve the scenario, financing treatment and decision.
Scenario B: A2 private-asset decision
[Unverified illustrative scenario] A family office is evaluating a minority investment in a private operating company. All figures, dates and outcomes in this subsection are unverified management assumptions. They are not a valuation, allocation recommendation or expected return.
| Input | Central | Downside | Upside |
|---|---|---|---|
| Current revenue | USD 40m | USD 40m | USD 40m |
| Three-year revenue CAGR | 18% | 5% | 28% |
| Year-three EBITDA margin | 20% | 12% | 25% |
| Entry enterprise value / revenue | 4.0x | 4.0x | 4.0x |
| Exit enterprise value / revenue | 4.5x | 2.8x | 6.0x |
| Follow-on capital | USD 0 | USD 8m | USD 0 |
| Exit timing | Year 4 | Year 6 | Year 3 |
The comparable engine screens listed and private transactions for business model, geography, growth, revenue quality, margin, size, security rights and date. It shows the effect of each exclusion and adjustment. The income approach uses a driver-based forecast. The scenario engine combines operating performance, capital need, dilution, exit timing and market multiple.
The family office's decision output adds mandate fit, liquidity reserve, concentration, governance rights, information rights and follow-on capacity. A supportable company value does not establish portfolio suitability. The investment committee approves the allocation and conditions.
Scenario evidence boundary
The scenario inputs have no observed validation. Their values should not appear in marketing, tracker claims, case studies or performance attribution. Attributed Matchpoint or client revenue, cash cost reduction, loss reduction and alpha from these scenarios remain USD 0.
Productivity And Revenue
Productivity unit
The productivity unit should be an accepted, decision-ready output. Draft text, retrieved documents, generated comparables and model runs are intermediate work. A faster draft that creates additional review or error cost is not a productivity gain.
| Measure | Definition | Control |
|---|---|---|
| Cycle time | Instruction to approved conclusion | Same scope and quality threshold |
| Analyst hours | Human time per accepted output | Time capture by workflow stage |
| Coverage | Assets or scenarios reviewed per period | Stable materiality threshold |
| Rework | Hours after review rejection | Coded defect reason |
| Acceptance | Outputs approved without material correction | Independent reviewer |
| Error | Difference to realised or later evidence | Defined outcome and horizon |
| Exception rate | Cases requiring manual resolution | Segment and cause |
| Decision latency | Evidence event to approved action | Named decision owner |
External productivity evidence
Brynjolfsson, Li and Raymond studied a staggered deployment to 5,172 customer-support agents and reported a 15 per cent average increase in issues resolved per hour, with heterogeneous effects [23]. Noy and Zhang's experimental study of professional writing tasks found shorter completion times and higher output quality under its design [24]. Dell'Acqua and co-authors studied 758 consultants and reported gains for tasks inside the tested AI capability frontier, with weaker performance on a task outside that frontier [25].
These studies provide credible evidence that generative AI can improve selected knowledge-work tasks. They do not establish a T27 valuation productivity rate. Valuation involves different evidence, professional standards, models, consequences and review. Matchpoint and client productivity should be measured in a controlled pilot.
Unverified illustrative business-case bridge
[Unverified illustrative scenario] Assume a team completes 20 accepted valuation or monitoring packs per month. Assume a controlled pilot reduces median human time from 24 hours to 18 hours while acceptance, material correction and error measures remain within approved thresholds. The illustrative released capacity is 120 hours per month. This is a planning calculation, not an observed Matchpoint or client result.
Released capacity can be used for more coverage, faster decisions, higher-quality challenge or client work. Revenue arises only if the capacity supports a signed engagement, accepted deliverable and collected fee. A revenue formula can be written as:
Collected revenue = accepted paid outputs x approved price x collection rate - refunds and credits
Every term needs observed evidence. Until that evidence is approved, attributed T27 collected revenue remains USD 0.
Revenue architecture by ICP
For B1 developers, a service can include an evidence and valuation diagnostic, capital-structure scenario pack, lender or investor case, model remediation and monitored scenario update. For A2 family offices, it can include private-asset valuation review, portfolio mark challenge, liquidity scenario pack, transaction underwriting and ongoing monitoring. Commercial terms require separate approval and engagement documentation.
The website and research paper should describe capabilities and controls. Client-specific outcome claims require observed evidence, approval and appropriate disclosure.
Failure Modes And Control Responses
Data failure
Stale, duplicated, selectively reported or wrongly normalised evidence can dominate model quality. A higher-capacity model can reproduce data defects more consistently. Controls include source priority, effective dates, completeness checks, unit validation, relationship flags, duplicate detection, reconciliation and reviewer sampling.
Comparable-selection failure
Similarity algorithms can learn proxies that look statistically useful and are economically inappropriate. Analysts can also cherry-pick comparables. Controls include a written universe, hard eligibility, full exclusion log, feature review, alternative ranking methods and out-of-sample performance.
Forecast and scenario failure
Scenarios can hide inconsistent dependencies, double-count risks, apply probabilities without evidence or ignore financing constraints. Controls include a driver graph, accounting and cash reconciliation, management-action logic, reverse stress and independent challenge.
Automation bias
Polished narrative and precise numbers can increase user confidence. The report should visibly distinguish observed evidence, model estimates, management assumptions, overlays and unverified scenarios. Reviewers should see model disagreements and missing evidence before the conclusion.
Model drift
Market regimes, data coverage, incentives and asset mix change. Monitoring should test input distribution, error, interval coverage, override rate, missingness and segment performance. A threshold breach should trigger restriction, recalibration, redevelopment or retirement.
Cyber, privacy and vendor failure
Valuation systems can contain confidential financial, ownership, property and transaction data. Controls include minimum access, encryption, region and retention analysis, vendor diligence, incident response, prompt and tool permissions, output filtering, backup and export capability. A vendor service should not become the sole evidence repository.
Governance And Release Gates
Govern, Map, Measure and Manage
NIST AI RMF organises AI risk work into four functions [7]. Applied to valuation:
- Govern: set accountability, policy, inventory, risk appetite and escalation.
- Map: define the decision, users, subject, context, harms and dependencies.
- Measure: test data, model, uncertainty, security, explainability and human use.
- Manage: approve, restrict, monitor, remediate, communicate and retire.
ISO/IEC 42001 specifies requirements for an AI management system and supports a wider organisational framework for responsible development and use [16]. Adoption or certification should not be represented as proof that a specific valuation is correct.
Release gates
| Gate | Minimum approval evidence | Stop condition |
|---|---|---|
| Perimeter | Purpose, basis, date, subject and users | Instruction incomplete |
| Data | Source register, lineage and quality profile | Material conflict unresolved |
| Method | Rationale, calibration and benchmark | Technique unfit for use |
| Validation | Independent findings and remediation | Critical finding open |
| Uncertainty | Range, interval and scenario treatment | Precision unsupported |
| Human authority | Reviewer and decision owner | No accountable approver |
| Technology | Access, security, logging and fallback | Material control gap |
| Reporting | Claims, sources and limitations | Misleading output |
| Commercial | Engagement and reliance terms | Scope or authority unclear |
The approval can restrict the model to a market, asset type, time range, value range or use. A successful pilot supports only the tested perimeter.
Ninety-Day Adoption Roadmap
Days 0-15: perimeter and inventory
- select one bounded A2 or B1 use case;
- document purpose, basis, date, users and decision rights;
- inventory existing data, models, spreadsheets and vendors;
- map confidential data and access;
- define acceptance, error and productivity measures; and
- record the current baseline.
Gate: approved instruction, owner, baseline and data-access plan.
Days 16-30: evidence ledger
- create the source hierarchy and data dictionary;
- ingest a dated evidence snapshot;
- build provenance, transformation and exclusion fields;
- test completeness, units, duplicates and leakage;
- define AI extraction review; and
- prepare a representative case set.
Gate: evidence can be traced from source to normalised field.
Days 31-45: comparable and scenario prototype
- implement eligibility and ranking rules;
- build transparent benchmark methods;
- add feature-adjusted alternatives;
- create the scenario driver graph;
- define abstention and override logic; and
- produce source-linked draft outputs.
Gate: every conclusion can be reproduced and challenged.
Days 46-60: independent validation
- test concept, data, code and output;
- run time-aware and segment performance tests;
- test prediction intervals and out-of-distribution flags;
- review explanations and adverse cases;
- test security, access and vendor fallback; and
- remediate findings.
Gate: no critical open finding; approved restrictions recorded.
Days 61-75: shadow operation
- run the new and current processes in parallel;
- capture time, acceptance, correction and exception data;
- compare model and reviewer decisions;
- record override reason and outcome;
- test committee reporting; and
- refine thresholds.
Gate: evidence supports controlled use within the stated perimeter.
Days 76-90: controlled release
- approve model, data and user permissions;
- train users and reviewers;
- activate monitoring and incident workflow;
- define change and retirement processes;
- release only the approved use case; and
- schedule post-implementation review.
Gate: accountable authority signs the release and limitations.
Claims Register And Limitations
Permitted claims
The evidence supports the following bounded claims:
- AI and machine learning can support evidence extraction, comparable analysis, modelling and scenario production.
- Official valuation standards require defined scope, appropriate data, method, judgement, documentation and reporting [1-5].
- Model-risk frameworks emphasise inventory, governance, validation, monitoring and control [6-8,14-16].
- Primary studies demonstrate productivity improvement in selected customer-support, writing and consulting tasks [23-25].
- A commercial-real-estate AVM study reported favourable error performance within its specific US multifamily sample [22].
- Official Dubai data improve access to selected market observations [11-12].
Unsupported claims
The evidence does not establish that:
- an AI output is a valuation or investment decision;
- one model is accurate across all GCC assets and regimes;
- more data remove the need for judgement;
- explanation proves causality or fairness;
- a point estimate is more decision-useful than a range;
- external productivity percentages apply to valuation;
- faster production creates collected revenue; or
- T27 has generated Matchpoint or client revenue, cash saving, loss reduction or alpha.
Empirical limitations
No Matchpoint or client T27 pilot dataset, realised valuation outcomes, time study, error series, acceptance record or revenue evidence was supplied. The illustrative B1 and A2 scenarios are not observed cases. The paper therefore proposes a system and test protocol. It does not report a deployed model's performance.
Regulatory and professional limitations
Accounting, valuation, securities, lending, data, AI and professional requirements vary by entity, asset, jurisdiction, instruction and date. The cited SEC, Federal Reserve and PRA materials have defined institutional scopes. They are used as comparative control evidence outside those scopes, not as statements of universal legal obligation.
Technical limitations
Model performance depends on source coverage, coding, feature design, regime, subject and intended use. Prediction intervals depend on their method and assumptions. Generative models can produce unsupported content. Vendor models can change. The production system needs version control, validation, monitoring, access controls and fallback.
Commercial limitations
No forecast of demand, pricing, conversion or collection has been approved. Service packaging and fees require CK approval and client engagement terms. Attributed T27 revenue, cash cost reduction, loss reduction and alpha remain USD 0.
Conclusion
AI-augmented valuation should be designed as an evidence-to-decision system. The system begins with purpose, rights, basis, date and authority. It stores market and operating evidence with provenance. It keeps the comparable universe, eligibility, ranking, adjustments and exclusions visible. It combines transparent valuation methods with bounded machine support. It models coherent scenarios and management actions. It reports uncertainty and abstains outside the approved perimeter. It assigns final authority to accountable humans.
For A2 family-office CIOs and heads of alternatives, the system can increase the consistency and coverage of private-asset decisions while preserving mandate, liquidity and concentration review. For B1 UAE/GCC real-estate developers and sponsors, it can connect market evidence, development assumptions, capital structure and decision thresholds in one governed process. In both cases, productivity should be measured through accepted outputs and attributed value through approved observed commercial evidence.
The central implementation discipline is traceability. A reviewer should be able to move from conclusion to method, assumption, transformation and dated source. A committee should be able to see uncertainty, scenario dependence and model disagreement before approving an action. A future outcome should update the model and the control record. That is how AI can multiply analytical coverage without obscuring valuation judgement.
References
[1] IFRS Foundation. IFRS 13 Fair Value Measurement. Issued Standards, 2024 edition. https://www.ifrs.org/issued-standards/list-of-standards/ifrs-13-fair-value-measurement/
[2] International Valuation Standards Council. New edition of the International Valuation Standards published. 31 January 2024; effective 31 January 2025. https://ivsc.org/new-edition-of-the-international-valuation-standards-ivs-published/
[3] International Private Equity and Venture Capital Valuation Board. International Private Equity and Venture Capital Valuation Guidelines. 2025. https://www.privateequityvaluation.com/Valuation-Guidelines
[4] Royal Institution of Chartered Surveyors. Automated valuation models. Insight paper, 2022. https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/valuation-standards/automated-valuation-models
[5] Royal Institution of Chartered Surveyors. Bank lending valuations and mortgage lending value, 2nd edition. December 2025. https://www.rics.org/content/dam/ricsglobal/documents/standards/Bank-lending-valuations-and-MLV_2nd-edition_Dec2025.pdf
[6] Central Bank of the UAE. Model Management Standards. Notice 5052/2022. https://www.centralbank.ae/en/rulebook/banking/risk-management/risk-management/model-management-standards/
[7] National Institute of Standards and Technology. Artificial Intelligence Risk Management Framework (AI RMF 1.0). NIST AI 100-1, January 2023. https://www.nist.gov/itl/ai-risk-management-framework
[8] National Institute of Standards and Technology. Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile. NIST AI 600-1, July 2024. https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf
[9] Dubai Financial Services Authority. New DFSA AI survey: generative AI adoption has nearly tripled within DIFC; governance continues to develop. 2025. https://www.dfsa.ae/news/new-dfsa-ai-survey-generative-ai-adoption-has-nearly-tripled-within-difc-last-12-months-governance-continues-develop
[10] International Organization of Securities Commissions. Artificial Intelligence in Capital Markets: Use Cases, Risks, and Challenges. 2025. https://www.iosco.org/library/pubdocs/pdf/IOSCOPD788.pdf
[11] Dubai Land Department. Real Estate Data: Open Data. Accessed 1 August 2026. https://dubailand.gov.ae/en/open-data/real-estate-data/
[12] Dubai Land Department. Dubai's real estate transactions surge 31% to reach AED 252 billion in Q1 2026. 2026. https://dubailand.gov.ae/en/news-media/dubai-s-real-estate-transactions-surge-31-to-reach-aed-252-billion-in-q1-2026/
[13] U.S. Securities and Exchange Commission. Good Faith Determinations of Fair Value: Small Entity Compliance Guide. 2020. https://www.sec.gov/resources-small-businesses/small-business-compliance-guides/good-faith-determinations-fair-value-small-entity-compliance-guide
[14] Board of Governors of the Federal Reserve System. SR 26-2: Revised Guidance on Model Risk Management. 17 April 2026. https://www.federalreserve.gov/supervisionreg/srletters/SR2602.htm
[15] Bank of England, Prudential Regulation Authority. SS1/23: Model risk management principles for banks. Current version, April 2026. https://www.bankofengland.co.uk/prudential-regulation/publication/2023/may/model-risk-management-principles-for-banks-ss
[16] International Organization for Standardization. ISO/IEC 42001:2023, Information technology - Artificial intelligence - Management system. 2023. https://www.iso.org/standard/42001
[17] Rosen, S. Hedonic Prices and Implicit Markets: Product Differentiation in Pure Competition. Journal of Political Economy, 82(1), 34-55, 1974. https://doi.org/10.1086/260169
[18] Breiman, L. Random Forests. Machine Learning, 45, 5-32, 2001. https://www.stat.berkeley.edu/~breiman/randomforest2001.pdf
[19] Friedman, J. H. Greedy Function Approximation: A Gradient Boosting Machine. Annals of Statistics, 29(5), 1189-1232, 2001. https://doi.org/10.1214/aos/1013203451
[20] Lundberg, S. M., and Lee, S.-I. A Unified Approach to Interpreting Model Predictions. Advances in Neural Information Processing Systems 30, 2017. https://arxiv.org/abs/1705.07874
[21] Angelopoulos, A. N., and Bates, S. A Gentle Introduction to Conformal Prediction and Distribution-Free Uncertainty Quantification. 2021. https://arxiv.org/abs/2107.07511
[22] Kok, N., Koponen, E.-L., and Martinez-Barbosa, C. A. Big Data in Real Estate? From Manual Appraisal to Automated Valuation. Journal of Portfolio Management, 43(6), 202-211, 2017. https://doi.org/10.3905/jpm.2017.43.6.202
[23] Brynjolfsson, E., Li, D., and Raymond, L. Generative AI at Work. Quarterly Journal of Economics, 140(2), 889-942, 2025. https://doi.org/10.1093/qje/qjae044
[24] Noy, S., and Zhang, W. Experimental Evidence on the Productivity Effects of Generative Artificial Intelligence. Science, 381(6654), 187-192, 2023. https://doi.org/10.1126/science.adh2586
[25] Dell'Acqua, F., McFowland, E. III, Mollick, E., Lifshitz-Assaf, H., Kellogg, K. C., Rajendran, S., Krayer, L., Candelon, F., and Lakhani, K. R. Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality. Organization Science, 2026. https://doi.org/10.1287/orsc.2025.21838
Appendix A. Minimum Valuation Evidence Record
| Field | Requirement |
|---|---|
| Record ID | Unique, immutable identifier |
| Source | Provider, document, endpoint or system |
| Source location | URL, file, page, cell or record key |
| Observation | Original text or value |
| Observed date | Date the market or operating fact occurred |
| Available date | Date available to the valuer |
| Effective date | Date from which the term or value applies |
| Unit and currency | Explicit unit, scale and currency |
| Subject attributes | Geography, asset, instrument and segment |
| Relationship | Arm's-length, related, distressed or unknown |
| Transaction status | Completed, conditional, announced or quote |
| Transformation | Normalisation, inflation, FX or adjustment |
| Quality | Completeness, confidence and conflict flag |
| Review | Reviewer, date and disposition |
| Version | Source snapshot and transformation version |
Appendix B. Comparable Review Checklist
- Is the subject interest and unit of account defined?
- Is the valuation date enforced in the evidence query?
- Is the complete candidate universe retained?
- Are hard eligibility rules written before ranking?
- Does each excluded comparable have a coded reason?
- Are transaction terms and security rights normalised?
- Are time, size, quality, rights and financing adjustments evidenced?
- Does the model avoid future information and target leakage?
- Are errors reported by material segment and time?
- Is the subject within the validated data distribution?
- Are method indications reconciled rather than averaged mechanically?
- Are reviewer overlays, reasons and prior values retained?
- Does the report show dispersion, uncertainty and limitations?
Appendix C. Scenario And Release Checklist
- Is the decision and horizon defined?
- Are central, downside, upside and reverse-stress states coherent?
- Are driver dependencies documented?
- Are management actions assigned authority, cost and delay?
- Do cash, financing, tax and accounting flows reconcile?
- Are probabilities supported or omitted?
- Are decision thresholds and first-breach drivers visible?
- Has independent validation covered data, method, code and use?
- Are access, confidentiality, logging and vendor fallback approved?
- Are abstention and restriction rules active?
- Are users trained on model limits and automation bias?
- Is monitoring active for drift, error, overrides and incidents?
- Is the final decision owned by an authorised human?
Appendix D. Glossary
Abstention: a controlled outcome that withholds an automated conclusion and routes the case to manual review.
Automated valuation model: a mathematical or statistical system that estimates value from property or market data with a defined degree of automation.
Basis of value: the fundamental measurement assumptions under which a value is estimated.
Calibration: adjustment of a model so that its output is consistent with relevant observed evidence, including transaction price where appropriate.
Comparable: an observed transaction, instrument or asset used to inform value after relevance and differences are analysed.
Conformal prediction: a family of methods that constructs prediction sets or intervals using calibration data and defined coverage properties.
Evidence ledger: a versioned register connecting every material input to its source, date, transformation, reviewer and output use.
Explainability: information describing how inputs influenced a model output; it does not itself establish correctness or causality.
Model risk: potential adverse consequence from decisions based on incorrect, misused or poorly controlled models.
Out-of-distribution: a subject or input materially outside the population represented in model development and validation.
Prediction interval: a range designed to contain a future or unobserved outcome at a stated coverage level under the method's assumptions.
Scenario: a coherent set of linked economic, operating and financing assumptions used to evaluate an outcome or decision.
Sensitivity: the effect of changing one or more assumptions, often without asserting a complete state of the world.
Valuation overlay: a documented human adjustment applied to a model or method indication for evidence or risks not adequately captured.
Source Register
The full paper records the scope, evidence setting and limitations applied to these sources.
- [1] IFRS Foundation. **IFRS 13 Fair Value Measurement.** Issued Standards, 2024 edition. Open source
- [2] International Valuation Standards Council. **New edition of the International Valuation Standards published.** 31 January 2024; effective 31 January 2025. Open source
- [3] International Private Equity and Venture Capital Valuation Board. **International Private Equity and Venture Capital Valuation Guidelines.** 2025. Open source
- [4] Royal Institution of Chartered Surveyors. **Automated valuation models.** Insight paper, 2022. Open source
- [5] Royal Institution of Chartered Surveyors. **Bank lending valuations and mortgage lending value, 2nd edition.** December 2025. Open source
- [6] Central Bank of the UAE. **Model Management Standards.** Notice 5052/2022. Open source
- [7] National Institute of Standards and Technology. **Artificial Intelligence Risk Management Framework (AI RMF 1.0).** NIST AI 100-1, January 2023. Open source
- [8] National Institute of Standards and Technology. **Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile.** NIST AI 600-1, July 2024. Open source
- [9] Dubai Financial Services Authority. **New DFSA AI survey: generative AI adoption has nearly tripled within DIFC; governance continues to develop.** 2025. Open source
- [10] International Organization of Securities Commissions. **Artificial Intelligence in Capital Markets: Use Cases, Risks, and Challenges.** 2025. Open source
- [11] Dubai Land Department. **Real Estate Data: Open Data.** Accessed 1 August 2026. Open source
- [12] Dubai Land Department. **Dubai's real estate transactions surge 31% to reach AED 252 billion in Q1 2026.** 2026. Open source
- [13] U.S. Securities and Exchange Commission. **Good Faith Determinations of Fair Value: Small Entity Compliance Guide.** 2020. Open source
- [14] Board of Governors of the Federal Reserve System. **SR 26-2: Revised Guidance on Model Risk Management.** 17 April 2026. Open source
- [15] Bank of England, Prudential Regulation Authority. **SS1/23: Model risk management principles for banks.** Current version, April 2026. Open source
- [16] International Organization for Standardization. **ISO/IEC 42001:2023, Information technology - Artificial intelligence - Management system.** 2023. Open source
- [17] Rosen, S. **Hedonic Prices and Implicit Markets: Product Differentiation in Pure Competition.** Journal of Political Economy, 82(1), 34-55, 1974. Open source
- [18] Breiman, L. **Random Forests.** Machine Learning, 45, 5-32, 2001. Open source
- [19] Friedman, J. H. **Greedy Function Approximation: A Gradient Boosting Machine.** Annals of Statistics, 29(5), 1189-1232, 2001. Open source
- [20] Lundberg, S. M., and Lee, S.-I. **A Unified Approach to Interpreting Model Predictions.** Advances in Neural Information Processing Systems 30, 2017. Open source
- [21] Angelopoulos, A. N., and Bates, S. **A Gentle Introduction to Conformal Prediction and Distribution-Free Uncertainty Quantification.** 2021. Open source
- [22] Kok, N., Koponen, E.-L., and Martinez-Barbosa, C. A. **Big Data in Real Estate? From Manual Appraisal to Automated Valuation.** Journal of Portfolio Management, 43(6), 202-211, 2017. Open source
- [23] Brynjolfsson, E., Li, D., and Raymond, L. **Generative AI at Work.** Quarterly Journal of Economics, 140(2), 889-942, 2025. Open source
- [24] Noy, S., and Zhang, W. **Experimental Evidence on the Productivity Effects of Generative Artificial Intelligence.** Science, 381(6654), 187-192, 2023. Open source
- [25] Dell'Acqua, F., McFowland, E. III, Mollick, E., Lifshitz-Assaf, H., Kellogg, K. C., Rajendran, S., Krayer, L., Candelon, F., and Lakhani, K. R. **Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality.** Organization Science, 2026. Open source
