Dated evidence for the markets discussed
World Bank WDI source update and observation years are retained below. Checked 2026-11-22. The method that follows does not infer project demand from these national observations or report unperformed fieldwork.
| Country | Population | GDP (current USD) | Real GDP growth (annual %) | CPI inflation (annual %) |
|---|---|---|---|---|
| Canada | 41,651,653 (2025) | 2,319,899,772,425.92 (2025) | 1.74 (2025) | 2.07 (2025) |
| Mexico | 131,946,900 (2025) | 1,832,641,364,775.52 (2025) | 0.56 (2025) | 3.81 (2025) |
Scope and analytical frame
This workpaper addresses a common investor mandate applied to specific metros in Canada and Mexico, but it does not assume that national narratives are sufficient for asset-level or site-level judgment. The question is whether a defined business model can operate at a defined property or facility under documented conditions, with the relevant market boundary built from the asset catchment rather than from a national average.
The analysis must be run separately for each contemplated use case, because an office acquisition, a manufacturing expansion, a distribution facility and an energy-service site draw from different labor pools, utility systems, logistics routes, lease structures and regulatory touchpoints. A single comparison deck should therefore begin by naming the use case, the metro, the property type, the local operating model and the investment date, then hold those items constant across jurisdictions.
All conclusions are provisional unless they are tied to source records that can be reconciled to the same reporting period and to the same geography. Where bilingual Canadian or Mexican source material exists, the translation step must preserve legal and commercial meaning, not merely language equivalence.
- Define the asset or operating site, the intended use, the target customer or occupier and the planned hold period.
- Define the market boundary by commute shed, delivery radius, utility catchment or port and border access, as relevant.
- State the functional currency of the investor model and separately identify the operating currency of each contract and cost stream.
Record base and evidence requirements
The minimum record set differs by asset class, but the principle is the same: every claimed market fact must be traceable to a document that can be matched against a second source. For acquisitions, the core records are the rent roll or customer contract schedule, lease abstracts or service agreements, arrears and collection history, operating statements, vendor invoices, maintenance logs and any broker memoranda that describe incentives, concessions or uncommitted space.
For development, the core records are approved plans, permits, zoning or land-use confirmations, construction contracts, draw schedules, milestone certificates, utility connection letters and evidence of preleasing or precommitment. If competing supply is being assessed, the record base must include announced projects only if the announcement is supported by a completion path, financing evidence or construction status that can be checked independently.
For operating projects, the evidence base must also include wage quotations, payroll records or staffing agency quotes; utility tariffs or bill samples; freight quotes or route studies; tax registrations or local tax advice summaries; and any customs, border or port documents that affect timing or landed cost. The aim is not to collect everything, but to collect enough to test whether the project is financeable on the facts rather than on a headline market story.
- Property records: title or occupancy evidence, site plan, usable area, specification sheet, as-built drawings and service capacities.
- Revenue records: contracts, invoices, receipts, collections aging and any incentive or abatement agreement.
- Cost records: payroll inputs, utility bills, logistics quotations, insurance quotes, maintenance history, taxes and local professional memoranda.
Reproducible step-by-step method
Begin by fixing the decision date and creating a source register. Each document receives a source type, date, geography, currency, counterparty and reliability note. Documents that refer to different reporting periods or different geographies are not merged until the boundary problem is resolved.
Next, build a same-asset, same-period operating bridge. For an acquisition, bridge billed rent or service revenue to cash receipts, then deduct identified incentives, abatements, credit losses and nonrecurring items to determine sustainable income. For a development, bridge planned area to approved area, approved area to under-construction area, and under-construction area to deliverable area, then compare deliverable area to the demand assumptions actually supported by signed commitments.
Then convert all monetary inputs into a working table that preserves the original currency, the conversion assumption used in the model and the purpose of the conversion. This prevents the common error of translating only the terminal metric while leaving operating costs, debt service and capex in a different unit. The method must also isolate fixed and variable costs, because a wage-heavy or utility-heavy site may respond differently to occupancy than a rent-heavy office asset.
After that, compare local supply and competition on a specification-adjusted basis. Space that differs in ceiling height, power load, dock count, lot configuration, transit access, parking or regulatory status is not directly comparable until the differences are normalized. The normalization logic should be written down before any ranking is attempted, because the choice of comparator set is itself a substantive assumption.
Finally, test the project against the investor mandate using scenario logic rather than point estimates. The questions are whether the project remains operable, whether it remains correctly specified, whether its funding structure matches the local cash-flow profile and whether there is a documented path from today’s evidence to the projected stabilization case.
- Fix the date, geography, asset type and functional currency.
- Create a source register and reject mixed-period comparisons until boundaries are reconciled.
- Build a revenue-to-cash bridge and a planned-to-deliverable bridge.
- Normalize supply by specification, access and service readiness.
- Run scenario checks on operability, funding fit and stabilization logic.
Verification and triangulation protocol
Reconciliation must be conducted at the level of a named field, not at the level of a whole spreadsheet. A lease line item should be checked against the signed lease, the landlord statement, the receipt ledger and bank evidence where available. A customer contract should be checked against invoices, shipping records, cash collections and any documented credit memo activity. A wage assumption should be checked against employment records, staffing quotations or payroll data, and then cross-checked for seasonal or bilingual labor effects if those are material to the site.
For Canadian cases, where municipal, provincial and federal terminology may differ from local market practice, the analyst should reconcile the source language to the operative legal and commercial term used in the model. The translation note should explain any shift in meaning between French and English source terms, especially when the term affects zoning, permitting, labor category, tax treatment or construction status.
For Mexican cases, the analyst should reconcile broker claims, occupier letters and utility representations to documentary proof of service readiness, delivery access and occupancy status. If a land parcel is presented as available for near-term use, the file should contain enough evidence to decide whether the site is merely marketable, conditionally deliverable or actually ready for the intended operation. Where a discrepancy remains unresolved, the model should carry the more conservative assumption until the missing record is obtained.
A triangulated finding is only reliable if at least two independent records point to the same operational conclusion and the remaining discrepancy is explained. When the records disagree, the discrepancy itself becomes a diligence issue, not a reason to average the answers.
- Use one field at a time: area, rent, receipt, utility, wage, tax, delivery or service status.
- Require two independent records or one primary record plus a credible operating trace.
- Preserve translation notes where language affects legal or commercial meaning.
- Carry the more conservative assumption when a discrepancy remains unresolved.
Downside analysis and adverse-case reasoning
Downside analysis should ask what breaks first if the market underperforms, not whether the headline thesis remains attractive. For a Canadian office or industrial asset, the downside may arise from vacancy persistence, tenant rollover, cost inflation, service interruptions, delayed approvals or an unfavorable debt reset. For a Mexican industrial site, the downside may arise from utility unreliability, delivery bottlenecks, labor turnover, customs or border friction, concession erosion or a mismatch between building specification and the actual occupier process.
The analyst should therefore map each major revenue driver to its most likely failure mode, then identify the evidence that would have to change for the adverse case to be ruled out. For example, if a supposed demand pool depends on one anchor customer, the downside case should assume partial or full non-renewal until there is a signed commitment or equivalent proof of durable demand. If a project depends on heavy power use, the downside case should assume service constraints until a utility document and installation evidence confirm capacity.
Currency and financing risk must be handled separately from operations. A project can operate well and still underperform if debt service, capex or distributions are mismatched to the local currency of revenue. The downside model should therefore track the currency of each major inflow and outflow and identify the point at which a mismatch would force restructuring, additional equity or delayed execution. No conclusion should rely on a simple translation of exit value without first proving the resilience of the operating cash flow.
- Assume the weakest supported case for occupancy, demand and timing until documents prove otherwise.
- Separate operational downside from currency and debt-structure downside.
- Identify the specific record that would remove each adverse assumption.
Investigation stop conditions and data sufficiency gates
The investigation should stop only when the file can support a documented yes, a documented no or a documented defer pending specific missing evidence. A yes requires that the business model is operationally coherent, the records align on the same geography and period, and the adverse-case logic has been addressed with source evidence rather than belief. A no requires that a core feasibility issue is documented and not cured by available mitigation. A defer requires that the current file is insufficient but a small set of named records could resolve the uncertainty.
Stop conditions should be explicit. If the asset boundary is still unclear, stop. If the contract stack, lease stack or supply stack is missing primary documents, stop. If the local specification cannot be reconciled to the intended operating process, stop. If the funding model cannot match the currency and timing of cash flows, stop. If material facts depend on an unsupported broker assertion, stop until the assertion is replaced by documentary proof.
The point of a stage gate is not to generate delay; it is to prevent a false precision output. When the missing evidence would not change the conclusion, the issue can be logged but not escalated. When the missing evidence could change the conclusion, the file remains open.
- Stop if boundary, contract stack, supply stack or funding fit is unresolved.
- Stop if a material assumption rests only on an unsupported assertion.
- Continue only when the missing evidence is unlikely to change the conclusion or can be obtained and reconciled quickly.
Limitations and analyst cautions
This method does not substitute for local professional advice on law, tax, valuation, engineering, title, permitting or customs. It is a diligence framework, not a jurisdictional opinion. The analyst should avoid mixing national statistics with site-level decisions unless the data can be localized and reconciled to the asset’s catchment.
The framework is also limited by source quality. Broker materials, marketing decks and summary presentations are useful leads but not primary evidence. Even official documents can be internally inconsistent or stale. The correct response is not to average away uncertainty but to identify which fact is uncertain, which record would resolve it and whether the uncertainty is material enough to stop the work.
Another limitation is comparability. A Toronto office opportunity, a Montreal manufacturing expansion and an Alberta energy-service facility do not share the same operating logic, just as a Monterrey distribution building and a border manufacturing plant do not share the same demand and utility profile. Cross-market comparison is therefore useful only after each case has been normalized to its own operating model.
- Do not substitute this framework for local professional advice.
- Treat broker material as leads, not proof.
- Compare only after normalizing each case to its own operating model.
Decision workpaper template
The final workpaper should answer a narrow set of questions in plain language. What is the exact asset, site or expansion scope? What records were obtained, and which were missing? How were conflicting records reconciled? What assumptions were retained, what assumptions were rejected and why? Which downside case remains live? Which local issues require counsel, valuation, engineering or tax review before closing or proceeding?
The decision note should then state whether the evidence supports proceeding to the next gate, pausing for named records or stopping the file. If proceeding, the rationale should be tied to a specific record chain, not to macro enthusiasm. If pausing, the note should list the exact missing records and explain how each one could change the conclusion. If stopping, the note should identify the unreconciled issue and explain why additional search effort is unlikely to cure it without a material change in facts.
For this Canada and Mexico comparison, the workpaper should preserve separate conclusions by metro and asset type. The final recommendation, if any, must remain project-specific and conditional on verified local records, because a national narrative cannot by itself establish site readiness, funding fit or operating feasibility.
- State the exact scope, records, reconciliations and unresolved issues.
- Name the next gate: proceed, pause or stop.
- Keep conclusions separate by metro and asset type.
Scope, provenance and professional limitations
Wert-Berater Financial provides independent analytical decision support. We do not provide or arrange financing, broker securities, solicit investments or guarantee returns. Every engagement is subject to scope, data availability, geographic coverage, professional qualifications, applicable local law, regulatory restrictions, sanctions, counterparty and payment-risk review. Market coverage does not imply a local office, licence, professional designation or partnership. Local legal, tax, engineering and regulated professional conclusions require appropriately qualified advisers.
