Illustrative Developer Development and Capital Advisory Deliverables

Opportunity, development case, capital, transaction, and delivery transition

Illustrative only. This document describes the type and structure of work products Torvane may provide to a developer. The scope, information reviewed, analysis performed, timing, format, and deliverables are defined for each assignment.

Purpose

Torvane advises developers during the period in which an opportunity is evaluated, a development concept is defined, a development case is prepared, capital and counterparties are engaged, and a defined project is transferred into its selected delivery arrangement.

The work is directed to the developer’s position: control of land or development rights; definition of a viable concept; development conditions; market and commercial dependencies; capital requirements; approvals; transaction readiness; and the conditions required to transition a development into delivery.

Torvane does not present this material as a fixed package or a client report. Each assignment is designed around the developer’s project, stage, transaction, available evidence, approval process, and reporting audience.

Engagement architecture

A developer assignment is normally organized in four layers.

1. Executive decision paper

A concise paper for the developer’s executive sponsor, investment committee, board, development committee, or transaction team. It sets out the decision context, work performed, evidence reviewed, material findings, implications, actions, outstanding conditions, and information required for the next approval or external process.

2. Development workstream memoranda

Focused memoranda addressing the development questions relevant to the mandate: site and constraint conditions, development concept, commercial assumptions, capital plan, delivery route, transaction readiness, or transition to delivery.

3. Supporting schedules and registers

Traceable working documents that distinguish established evidence from management assumptions, identify dependencies and information gaps, record actions and owners, and show conditions requiring resolution before a specified development, capital, transaction, or transition event.

4. Executive briefing

A confidential working session in which Torvane presents the findings, implications, decision options, and priority actions to the developer’s designated audience.

Core client deliverables

Executive Decision Paper

Purpose

To provide a concise, evidence-based view of the conditions affecting the developer’s next material decision.

Typical contents

1. Decision context and mandate
2. Scope, methodology, and information reviewed
3. Evidence base, assumptions, and assessment limitations
4. Executive conclusion
5. Material findings and implications
6. Development, commercial, capital, transaction, and transition considerations
7. Priority actions, accountable parties, and required timing
8. Outstanding conditions and information requirements
9. Supporting schedules and registers

Development Workstream Memoranda

Purpose

To record the detailed analysis, evidence, observations, dependencies, and implications underlying the executive decision paper.

Typical structure

1. Questions addressed
2. Scope and source materials
3. Assessment approach
4. Evidence and observations
5. Findings and implications
6. Conditions requiring resolution
7. Recommended actions and information requirements
8. Appendices and supporting schedules

Registers and analytical schedules

Depending on the assignment, the developer may receive:

• Development constraints register
• Critical-path development conditions map
• Third-party study integration matrix
• Commercial assumptions and counterparty dependency register
• Development case assumptions and evidence register
• Capital plan and funding assumptions schedule
• Development-stage approval readiness assessment
• Developer-level risk allocation map
• Conditions-precedent and decision-gate register
• Project information and data-room index
• External diligence question map
• Evidence-gap and response plan
• Development-to-delivery handover index
• Developer-retained obligations register
• Transition governance and decision-rights map

01 — Opportunity, site, and development feasibility

Opportunity and Site Feasibility Review

Purpose

To assess whether the intended development concept is supportable in light of the site, development rights, access, utilities, external infrastructure, entitlement pathway, third-party studies, and other conditions that may affect feasibility, sequencing, cost, timing, or development risk.

Work performed

• Review available land-control, acquisition, option, lease, development-right, or site-control information relevant to the proposed development.
• Review the development concept against site constraints, access, circulation, logistics, utilities, transportation, off-site infrastructure, topography, ground conditions, environmental information, and other available studies.
• Assess the development implications of planning, entitlement, permitting, agency, stakeholder, community, heritage, environmental, utility, access, and third-party conditions identified in the information provided.
• Integrate the implications of third-party technical, environmental, market, legal, land, or specialist reports into a single developer-facing conditions view. Torvane does not replace the underlying regulated or specialist work.
• Identify development conditions that are precedent to land control, development expenditure, external engagement, capital deployment, or transition to the next development stage.
• Review sequencing, dependencies, timing, and critical-path development conditions.

Client receives

• Opportunity and Site Feasibility Review memorandum
• Development Constraints Register
• Critical-Path Development Conditions Map
• Third-Party Study Integration Matrix
• Site, infrastructure, access, utility, and entitlement dependency observations
• Priority actions before land control, material development expenditure, or next-stage approval
• Executive briefing materials

Typical use

• Before land acquisition, option exercise, land-control commitment, or early development expenditure
• Before selecting among alternative sites, concepts, or development sequences
• When site, access, utilities, entitlement, or external infrastructure conditions are uncertain
• When management requires an integrated view of development constraints before proceeding

02 — Market, commercial, and project concept

Development Concept and Commercial Assumptions Review

Purpose

To assess whether the proposed development concept, product definition, market assumptions, commercial counterparties, phasing, and value drivers form a coherent basis for the development case.

Work performed

• Review the proposed development concept, intended product or asset definition, capacity, phasing, user or customer proposition, and stated value drivers.
• Assess how market, customer, tenant, offtake, user, revenue, price, volume, utilization, operating-cost, and timing assumptions are reflected in the development case.
• Review the implications of available market research, commercial studies, offtake arrangements, customer information, leasing assumptions, or specialist analyses without replacing the work of market, broker, financial, or legal advisers.
• Identify commercial interfaces, counterparties, strategic partners, anchor users, customers, purchasers, or offtakers that are material to the development case.
• Assess dependency concentration, timing assumptions, conditions precedent, and potential points of value leakage or commercial misalignment.
• Compare alternative concept, phasing, and commercial scenarios where this is within the engagement scope.

Client receives

• Development Concept and Commercial Assumptions Review memorandum
• Market and Revenue Assumptions Register
• Counterparty and Commercial Dependency Map
• Value-driver and value-leakage observations
• Development phasing and scenario comparison
• Executive decision materials

Typical use

• Before a development concept is advanced for approval
• Before major commercial terms, customer commitments, offtake arrangements, or partner discussions
• When market, revenue, operating, utilization, or phasing assumptions change materially
• When an investment committee requires a clear view of commercial dependencies

03 — Development case, capital plan, and approvals

Development Case and Capital Plan Review

Purpose

To assess whether the development case coherently connects scope, phasing, cost, timing, capital requirements, commercial assumptions, external dependencies, and approval conditions.

Work performed

• Review the development business case and the relationship among project definition, development scope, phasing, cost assumptions, schedule assumptions, capital requirements, commercial drivers, and intended outcomes.
• Assess the sequencing of development expenditure, enabling work, capital deployment, contingency, funding sources, and approval requirements.
• Review how uncertainty, assumptions, conditions precedent, and dependencies are represented in the development case and executive materials.
• Identify the development assumptions most likely to affect capital requirement, capital timing, development duration, commercial viability, or required approvals.
• Review approval-stage readiness, including evidence available to decision-makers, outstanding information, decision rights, escalation pathways, and conditions requiring resolution before approval.
• Prepare a clear distinction between established evidence, management assumptions, unresolved dependencies, and actions in progress.

Client receives

• Development Case Review memorandum
• Capital Plan and Funding Assumptions Review
• Development-stage Approval-Readiness Assessment
• Assumptions, Dependencies, and Evidence Register
• Capital-deployment sequencing observations
• Conditions and information requirements for the next approval
• Executive decision paper and briefing materials

Typical use

• Before developer investment-committee, board, or development-committee approval
• Before material development expenditure or capital deployment
• When the development budget, capital plan, phasing, or commercial case has changed
• When management requires an independent review of the development case before proceeding

04 — Development strategy, delivery route, and risk allocation

Development Strategy and Delivery-Route Review

Purpose

To assess the developer’s strategic options for progressing the development and the implications of each option for control, timing, capital, commercial returns, risk retention, counterparties, and transition into delivery.

Work performed

• Review development alternatives, which may include self-development, phased development, joint venture, strategic partnership, sale, build-to-suit, development management, or another structure defined by the developer.
• Assess how each development route affects developer control, capital deployment, timing, partner roles, approvals, commercial returns, risk retention, and exposure to external dependencies.
• Review developer-level risk allocation across land and site control, entitlement, utilities, infrastructure, market, commercial counterparties, capital, inflation, supply chain, timing, completion exposure, and operating transition.
• Identify high-level implications of the intended delivery arrangement for the development case, without administering procurement, evaluating contractor bids, or directing delivery execution.
• Review conditions precedent, decision gates, development milestones, critical dependencies, and retained obligations associated with the selected route.
• Compare options and identify actions required before selection, partner engagement, capital deployment, or transition to delivery.

Client receives

• Development Strategy and Delivery-Route Review memorandum
• Developer-Level Risk Allocation Map
• Conditions-Precedent and Critical Dependency Register
• Development Phasing and Decision-Gate Plan
• Development option comparison
• Executive options paper and briefing materials

Typical use

• Before selecting a development route or strategic partner
• Before establishing a joint venture, sale process, build-to-suit arrangement, or phased development strategy
• When project economics, capital availability, timing, or risk appetite changes
• Before a material transition from development activity into a selected delivery arrangement

05 — Capital raising, partner diligence, and transaction readiness

Transaction and Capital-Raising Readiness Review

Purpose

To help the developer organize and assess project information for equity, debt, strategic-partner, purchaser, joint-venture, or other external transaction processes from the developer’s perspective.

Work performed

• Review the organization, completeness, consistency, and traceability of the project information expected to be examined by prospective capital providers, partners, purchasers, or their advisers.
• Identify project assumptions, constraints, dependencies, and open matters likely to be tested through external diligence.
• Prepare a developer-side view of the information available, evidence gaps, outstanding questions, responsible parties, and response requirements.
• Review the consistency of development narrative, concept, site conditions, commercial assumptions, capital plan, delivery route, and transaction materials.
• Identify transaction timeline dependencies, conditions precedent, approval requirements, third-party consents, and development matters that require closure or disclosure.
• Support preparation of factual, traceable materials for management discussions without providing securities, legal, tax, underwriting, valuation, or investment advice.

Client receives

• Transaction and Capital-Raising Readiness Review memorandum
• Project Information and Data-Room Index
• External Diligence Question Map
• Evidence-Gap and Response Plan
• Transaction conditions and dependency register
• Developer management briefing pack for capital-provider or partner discussions

Typical use

• Before equity raising, debt discussions, partner selection, sale, joint venture, or strategic-capital processes
• Before opening a data room or responding to early diligence questions
• When prospective capital providers or partners request a clearer development evidence base
• When management needs to organize material project information before an external process

06 — Development-to-delivery transition

Development-to-Delivery Transition Review

Purpose

To assess whether the developer has completed the work required to transfer a sufficiently defined development into its selected delivery arrangement and to identify the obligations, decisions, conditions, and information that remain under developer control.

Work performed

• Review whether project definition, development approvals, capital arrangements, development conditions, external interfaces, commercial decisions, and governance requirements are sufficiently organized for transition.
• Identify the developer’s retained obligations, including land, rights, permits, utilities, off-site infrastructure, stakeholder commitments, commercial commitments, capital conditions, or other matters defined by the project.
• Review the handover of development information, assumptions, conditions, third-party agreements, approvals, dependencies, and open matters to the selected delivery arrangement.
• Assess transition governance, decision rights, reporting requirements, escalation routes, and the interfaces between developer leadership and the future delivery organization.
• Identify items that require closure, assignment, validation, funding, decision, or continuing developer oversight after transition.
• Prepare an executive view of transition readiness and remaining development conditions.

Client receives

• Development-to-Delivery Transition Review memorandum
• Project Definition and Handover Index
• Developer-Retained Obligations Register
• Open Conditions and Dependencies Register
• Transition Governance and Decision-Rights Map
• Transition action plan and executive briefing materials

Typical use

• Before a defined project moves into its selected delivery arrangement
• Before transfer to a project entity, development partner, delivery organization, purchaser, or joint venture
• When developer and delivery responsibilities require formal separation and handover
• When management requires visibility of development matters that remain open after transition

Example register architecture

Development Conditions Register

Development Assumptions and Dependencies Register

Evidence and Information-Gap Log

Executive briefing and next steps

A developer assignment normally concludes with a confidential executive briefing. The briefing is designed to answer five practical questions:

1. What has been examined?
2. What is established by the available evidence?
3. What assumptions, dependencies, or information gaps remain material?
4. What are the implications for the development, capital, transaction, or transition decision?
5. What action, information, approval, or escalation is required next?

Where included in the assignment, Torvane records agreed actions, responsible parties, target dates, and closure evidence in a final Development Conditions Register. Follow-up review of action closure may be included where it is part of the agreed mandate.

Engagement terms

The content shown here is illustrative. Each assignment is defined by its agreed mandate, development stage, available information, review questions, reporting audience, work plan, deliverables, timing, fee, and engagement terms.

Torvane does not present this document as a client report, a fixed service package, a certification, or a substitute for the developer’s legal, tax, financial, valuation, market, environmental, planning, design, construction, insurance, or other specialist responsibilities.

Torvane Partners

Independent advisory for developers evaluating opportunities, defining development cases, preparing capital and transaction processes, selecting development routes, and transitioning defined developments into delivery.