Purpose
Torvane helps counsel and clients understand project records, establish chronology, assess project condition, analyze schedule and delivery events, evaluate productivity and cost evidence, and prepare technically rigorous materials for negotiation, mediation, adjudication, arbitration, litigation, or other dispute-resolution processes.
The work is evidence-based and directed to the project questions in issue. It may involve scope, progress, schedule, critical path, delay, disruption, productivity, change, cost, completion, quality, procurement, project controls, reporting, turnover, or remaining-work matters.
Torvane does not provide legal advice, interpret contracts as a legal matter, determine entitlement, determine liability, advocate legal positions, adjust claims, or make tribunal, court, arbitration, adjudication, insurance-coverage, or settlement decisions. Counsel and the client retain responsibility for legal theory, privilege, procedural strategy, pleadings, disclosure obligations, witness preparation, settlement, and all legal or forum decisions.
Engagement posture
Consulting support
Torvane may provide confidential technical and project consulting support to counsel or a client, subject to the engagement structure and applicable law. The work may include early issue assessment, document strategy, chronology development, project-condition analysis, schedule and productivity review, cost-record analysis, technical questions, opposing-position review, and dispute-prevention advice.
Independent expert services
Where an independent opinion, report, or testimony is required, Torvane will determine whether an appropriately qualified independent expert can be engaged for the specific matter. The expert’s discipline, credentials, experience, independence, conflicts status, methodology, instructions, disclosure obligations, forum requirements, and scope are established for that assignment.
An independent expert’s duty is to provide objective opinion evidence to the relevant tribunal or process. Independent expert work is not advocacy and is not assumed to be confidential in the same manner as non-testifying consulting support.
Engagement architecture
A legal and technical consulting assignment is normally organized in five layers.
1. Case-development memorandum
A concise memorandum for counsel, client leadership, claims leadership, or other designated audiences. It identifies the matter, scope, evidence reviewed, chronology, material project conditions, analysis performed, evidence gaps, technical questions, assumptions, limitations, and priority actions.
2. Focused technical analyses
Detailed analyses addressing the questions relevant to the assignment. Depending on the mandate, this may include record preservation and case assessment, project condition, schedule and delay, productivity and disruption, quantum and cost, opposing analysis, or dispute-prevention controls.
3. Evidence and analysis schedules
Traceable registers that record the relevant project evidence, chronology, schedule events, productivity data, cost records, assumptions, data limitations, analysis requirements, and follow-up actions.
4. Counsel working sessions
Confidential working sessions with designated counsel and client representatives to clarify technical questions, review the evidence, identify gaps, evaluate alternative interpretations, and establish next analysis or document requirements.
5. Independent expert process, where applicable
Where an appropriately qualified independent expert is engaged, the work may include a defined expert mandate, methodology, source-material review, report preparation, opposing-expert review, joint-expert process, and testimony support consistent with the applicable forum and engagement terms.
Core client deliverables
Case-Development Memorandum
Purpose
To provide a concise, evidence-based view of the project record, technical issues, analytical questions, information gaps, and next actions relevant to counsel or client decision-making.
Typical contents
- Matter context and engagement role
- Scope, methodology, and source materials
- Project chronology and relevant conditions
- Key technical, schedule, productivity, cost, quality, completion, or project-controls issues
- Evidence observations, assumptions, and limitations
- Alternative interpretations or scenarios where relevant
- Information requirements and priority actions
- Supporting schedules and registers
Focused technical analyses
Purpose
To record detailed evidence, methodology, observations, analysis, limitations, and project implications supporting the case-development memorandum.
Typical structure
- Questions addressed
- Scope and source materials
- Assessment or analytical approach
- Evidence and chronology
- Observations and analysis
- Assumptions, limitations, and alternative interpretations
- Information requirements and next steps
- Supporting schedules, calculations, or demonstratives
Evidence and analysis schedules
Depending on the assignment, counsel or the client may receive:
- Project Chronology and Evidence Register
- Evidence Map and Document-Gap Log
- Schedule, Cost, Change, Correspondence, and Field-Record Index
- Technical Issue and Evidence Matrix
- Status-at-Date and Remaining-Work Register
- Schedule Event and Critical-Path Register
- Productivity and Disruption Evidence Register
- Quantum and Cost Evidence Register
- Assumptions, Limitations, and Alternative-Interpretations Schedule
- Technical Question and Document-Request Schedule
- Claim, Counterclaim, or Project-Record Consistency Review
- Opposing Position and Analysis Review
- Dispute-Prevention and Record-Improvement Action Register
01 — Record preservation, case assessment, and document strategy
Record Preservation and Case Assessment Memorandum
Purpose
To identify the project record available, establish the early chronology, assess evidence quality, identify material gaps, and define the information required for a technically rigorous assessment before evidence degrades or positions become fixed.
Work performed
- Review available schedules, updates, reports, logs, correspondence, meeting minutes, change records, cost records, invoices, time sheets, field records, test records, quality records, photographs, data environments, and other project material relevant to the assignment.
- Assess record completeness, chronology, source reliability, contemporaneity, version control, authorship, metadata, consistency, accessibility, and gaps.
- Identify records requiring preservation, collection, indexing, validation, or further inquiry without providing legal advice regarding preservation obligations or disclosure requirements.
- Prepare a project chronology and identify key dates, decisions, notices, changes, milestone movements, field conditions, progress events, quality matters, procurement conditions, testing, completion, and other material events.
- Map technical issues to the records that support, contradict, or leave unresolved the relevant questions.
- Define further document, data, interview, and project-information requirements for a fuller project-condition, schedule, productivity, cost, or technical analysis.
Client receives
- Record Preservation and Case Assessment Memorandum
- Project Chronology
- Evidence Map and Document-Gap Log
- Schedule, Cost, Change, Correspondence, and Field-Record Index
- Preliminary Technical Issue Map
- Technical Question and Document-Request Schedule
Typical use
- At the first indication of a material project dispute or technical disagreement
- Before termination, suspension, default, major claim notice, or project transfer
- During early counsel assessment and dispute strategy development
- Before document production, mediation, adjudication, arbitration, litigation, or an independent expert process
02 — Project condition and technical delivery analysis
Project Condition Analysis
Purpose
To establish the condition of the project at a relevant date and assess what the contemporaneous records show about scope, progress, resources, procurement, quality, controls, completion, and remaining work.
Work performed
- Review project scope, deliverables, interfaces, assumptions, changes, responsibilities, and status as reflected in the project record.
- Review progress, quantities, work fronts, manpower, equipment, procurement, materials, productivity, field reports, photographs, and other contemporaneous evidence.
- Review project controls, estimates, budgets, cost-to-complete, forecasts, risks, change logs, reporting, governance, and management records.
- Review quality, nonconformance, testing, defects, corrective action, completion, punch list, turnover, and operational-readiness records where relevant to the matter.
- Review contractor, supplier, owner, consultant, and other project-party activities as reflected in the available records, without making legal conclusions about contractual responsibility.
- Establish a status-at-date view, including remaining work, completion condition, outstanding dependencies, information gaps, and cost or schedule exposure reflected by the evidence.
Client receives
- Project Condition Analysis
- Status-at-Date Report
- Scope, Progress, Resource, Procurement, and Completion Evidence Review
- Project-Controls and Forecast-Reliability Assessment
- Remaining-Work and Completion Condition Register
- Technical Issue and Evidence Matrix
Typical use
- Termination, default, suspension, insolvency, and project-transfer matters
- Completion, cost-to-complete, defect, quality, commissioning, turnover, and handover disputes
- Fact development before a schedule, productivity, cost, or expert assignment
- Negotiated resolution, mediation, adjudication, arbitration, or litigation
03 — Forensic schedule, delay, and disruption analysis
Forensic Schedule and Delay Analysis Memorandum
Purpose
To assess the schedule record, project chronology, relevant events, critical-path conditions, and available evidence in relation to delay, extension-of-time, acceleration, disruption, completion, or milestone issues.
Work performed
- Review baseline schedules, schedule updates, narratives, logic, calendars, constraints, progress, revisions, reporting, and available schedule-control records.
- Identify critical and near-critical path conditions, milestone movements, logic changes, progress changes, float conditions, constraints, and schedule-quality issues over the relevant period.
- Review delay events, change, access, design information, procurement, productivity, weather, client actions, contractor actions, third-party events, testing, commissioning, and other matters reflected in the record.
- Compare planned and actual sequence where the records permit and identify relevant schedule conditions, event timing, and potential project effects.
- Consider concurrency, pacing, mitigation, acceleration, recovery, resequencing, and alternative causes as reflected in the evidence.
- Select and apply an analytical approach appropriate to the available record and questions posed, while identifying methodology limits, data-quality issues, assumptions, and alternative interpretations.
Client receives
- Forensic Schedule and Delay Analysis Memorandum
- Schedule Reconstruction and Data-Quality Assessment
- Event Chronology and Critical-Path Map
- Delay, Concurrency, Mitigation, and Recovery Analysis
- Methodology and Assumptions Statement
- Supporting schedule exhibits and demonstratives
Typical use
- Extension-of-time, delay damages, liquidated-damages, disruption, acceleration, and completion matters
- Internal claim or counterclaim assessment
- Mediation, adjudication, arbitration, litigation, dispute-board, or negotiated-resolution processes
- Independent expert work where an appropriately qualified independent expert is separately engaged
04 — Productivity, disruption, and execution-impact analysis
Productivity and Disruption Analysis Memorandum
Purpose
To assess whether contemporaneous records support a measurable effect on the planned manner, efficiency, productivity, sequence, duration, or resource use of the work.
Work performed
- Review labor hours, quantities, production rates, crew composition, workfront availability, overtime, shifts, rework, stacking of trades, access, congestion, weather, changes, late information, procurement, and equipment availability.
- Review planned productivity, quantity, sequence, resource, and workfront assumptions against actual records where available.
- Assess the quality, consistency, granularity, and reliability of labor, quantity, production, payroll, timekeeping, progress, and field records.
- Identify disruption pathways and assess the relationship between relevant events or conditions and observed performance changes.
- Review acceleration, mitigation, resequencing, out-of-sequence work, extended hours, resource changes, and other execution responses reflected in records.
- Consider affected and unaffected work, other explanatory factors, data limitations, and alternative interpretations before reaching an analytical conclusion.
Client receives
- Productivity and Disruption Analysis Memorandum
- Labor, Quantity, and Production-Rate Assessment
- Disruption Event and Impact Matrix
- Productivity Baseline and Measured-Mile Observations, where applicable
- Acceleration, Resequencing, and Mitigation Review
- Supporting calculations and demonstratives
Typical use
- Lost-productivity, disruption, acceleration, inefficiency, and extended-duration matters
- Change, scope-growth, access, interference, resequencing, and resource-impact matters
- Internal technical assessment, negotiation, mediation, adjudication, arbitration, or litigation
- Independent expert work where an appropriately qualified independent expert is separately engaged
05 — Quantum, cost, and damages-support analysis
Quantum and Cost Analysis Memorandum
Purpose
To assess cost records and project financial information in order to organize and analyze the financial consequences associated with specified project events, assumptions, periods, work packages, or conditions.
Work performed
- Review cost ledgers, job-cost reports, WIP records, invoices, payroll, time sheets, commitments, change records, budgets, forecasts, equipment records, subcontracts, payment information, and other financial project records.
- Review cost coding, cost capture, allocation, contemporaneous cost control, reconciliation, record reliability, and linkage to scope, schedule, change, productivity, procurement, or completion conditions.
- Organize direct cost, extended general conditions, prolongation, acceleration, disruption, change, rework, repair, cost-to-complete, and termination-related information where relevant to the assignment.
- Assess linkage between costs and relevant events, time periods, work packages, assumptions, and project conditions without determining legal entitlement.
- Identify counterfactual assumptions, alternative quantification approaches, exclusions, mitigation, credits, double-counting risk, and data limitations.
- Prepare clear supporting schedules and calculations for counsel or client use, subject to the defined role and engagement structure.
Client receives
- Quantum and Cost Analysis Memorandum
- Cost Record and Data-Reliability Assessment
- Cost, Time, Change, and Event-Linkage Analysis
- Prolongation, Acceleration, Disruption, Rework, Repair, or Cost-to-Complete Schedules
- Assumptions, Exclusions, Credits, and Sensitivity Schedule
- Supporting calculations and demonstratives
Typical use
- Claims, counterclaims, termination, completion, defect, delay, disruption, and damages matters
- Settlement evaluation, mediation, adjudication, arbitration, litigation, or internal management assessment
- Development of financial evidence after relevant factual and legal assumptions are identified by counsel and the client
- Independent expert work where an appropriately qualified independent expert is separately engaged
06 — Counsel support and dispute-prevention advisory
Counsel Support and Dispute-Prevention Memorandum
Purpose
To help counsel and clients understand the record early, test technical issues, structure evidence, evaluate project positions, and strengthen project controls and records before a matter escalates.
Work performed
- Provide confidential technical and project consulting support to counsel or client, subject to the engagement structure and applicable law.
- Review claim narratives, schedules, cost materials, notices, change records, correspondence, project reports, quality records, and other evidence for consistency and technical support.
- Prepare technical questions, document requests, chronology issues, and information requirements for counterparties, project personnel, fact witnesses, or other relevant parties.
- Assess project records, technical positions, schedule analyses, productivity analyses, cost materials, completion evidence, and opposing positions for factual consistency, data quality, and analytical support.
- Support early issue assessment, negotiation preparation, mediation preparation, settlement scenario analysis, and dispute-prevention review without providing legal advice or advocacy opinion.
- Identify project-control, recordkeeping, notice, change, schedule, evidence, quality, and reporting practices that can be improved to reduce recurrence or escalation.
Client receives
- Counsel Support and Dispute-Prevention Memorandum
- Technical Question and Document-Request Schedule
- Claim, Counterclaim, or Project-Record Consistency Review
- Early Issue, Evidence, and Exposure Map
- Opposing Position and Analysis Review
- Dispute-Prevention and Record-Improvement Actions
Typical use
- Before a dispute is formally filed
- During early counsel assessment and negotiation
- Before mediation, settlement meetings, adjudication, arbitration, or litigation
- When counsel requires a non-testifying technical adviser
- When a client needs to improve project records and controls to avoid recurring disputes
07 — Independent expert services where appropriately qualified and engaged
Independent Expert Services Protocol
Purpose
To establish a disciplined pathway for independent expert reports and testimony only where an appropriately qualified independent expert is engaged for the specific matter.
Work performed
- Define the expert question, relevant discipline, forum requirements, independence requirements, conflicts review, scope, instructions, source materials, methodology, assumptions, and disclosure requirements.
- Determine whether an appropriately qualified independent expert can be engaged for the specific matter and whether the proposed role is consistent with independence and professional requirements.
- Prepare independent technical, schedule, productivity, cost, completion, project-controls, or project-condition opinion evidence only within the engaged expert’s competence and agreed scope.
- Prepare expert methodology, source-material, assumption, limitation, and supporting-analysis schedules.
- Review and critique opposing expert analyses where within scope and consistent with the expert role.
- Support expert meetings, joint statements, deposition, arbitration, adjudication, hearing, and testimony preparation where specifically engaged.
Client receives
- Independent Expert Report, where appropriate
- Expert Methodology, Assumptions, and Source-Material Schedule
- Opposing-Expert Critique or Rebuttal Memorandum, where appropriate
- Expert Meeting, Joint Statement, Deposition, Arbitration, or Hearing Preparation Materials
- Exhibits, Demonstratives, and Supporting Analysis
- Oral evidence and testimony, where specifically engaged
Typical use
- Litigation, arbitration, adjudication, expert determination, dispute boards, mediation, and negotiated resolution
- Review or rebuttal of an opposing expert report
- Independent opinion on technical, delay, disruption, quantum, completion, or project-controls issues
- Only after an appropriately qualified independent expert is identified, engaged, and cleared for the specific matter
Example register architecture
Project Chronology and Evidence Register
| Field | Content |
|---|---|
| Reference | Traceable identifier |
| Date or period | Relevant date, period, or event window |
| Event or record | Project event, document, schedule update, correspondence, meeting, change, field condition, or other evidence |
| Source | Author, record type, system, file, witness, or data source |
| Reliability observation | Contemporaneous, revised, incomplete, inconsistent, unsupported, or requires verification |
| Relevance | Schedule, productivity, cost, scope, quality, completion, causation, quantum, or other issue relevance |
| Project implication | Potential effect or question raised by the record |
| Required follow-up | Document, clarification, analysis, witness question, or verification required |
Schedule Event and Critical-Path Register
| Field | Content |
|---|---|
| Reference | Traceable identifier |
| Event | Delay, change, access, design, procurement, weather, productivity, testing, or other event |
| Date or period | Relevant occurrence period |
| Schedule evidence | Baseline, update, narrative, progress record, logic, calendar, or other schedule evidence |
| Critical-path observation | Critical, near-critical, non-critical, concurrent, or requires analysis |
| Causation question | Project question requiring analysis; not a legal conclusion |
| Mitigation or response | Recovery, resequencing, acceleration, extension, notice, or other response reflected in records |
| Data limitation | Missing update, unreliable progress, logic issue, or other analytical limitation |
| Required analysis | Schedule reconstruction, chronology, method application, sensitivity, or further evidence required |
Productivity and Disruption Evidence Register
| Field | Content |
|---|---|
| Reference | Traceable identifier |
| Work activity or area | Work package, system, location, crew, or trade |
| Planned basis | Planned quantity, labor, productivity, sequence, access, resource, or other basis |
| Actual evidence | Labor hours, quantities, daily logs, reports, schedules, payroll, field records, or other evidence |
| Event or condition | Change, congestion, access, late information, rework, procurement, weather, acceleration, or other condition |
| Impact observation | Potential effect on productivity, sequence, duration, cost, or resource use |
| Alternative factors | Other conditions requiring consideration |
| Data limitation | Missing, inconsistent, incomplete, or unreliable information |
| Required analysis | Measurement, comparison, causation analysis, or further evidence required |
Quantum and Cost Evidence Register
| Field | Content |
|---|---|
| Reference | Traceable identifier |
| Cost item | Labor, material, equipment, subcontract, overhead, change, repair, completion, or other cost |
| Source record | Ledger, invoice, time sheet, commitment, report, payment record, forecast, or other evidence |
| Time period or work package | Relevant period, activity, change, or work package |
| Event linkage | Relevant event, assumption, period, or project condition |
| Cost observation | Direct, indirect, allocated, forecast, incurred, duplicated, unsupported, credit, or mitigation issue |
| Data limitation | Missing, incomplete, inconsistent, or requires reconciliation |
| Required analysis | Allocation, reconciliation, causation linkage, sensitivity, exclusion, or further evidence required |
Expert Opinion and Assumptions Register
| Field | Content |
|---|---|
| Reference | Traceable identifier |
| Question or opinion area | Technical, delay, disruption, quantum, completion, project controls, or other expert question |
| Instruction or assumption | Instruction, factual premise, legal assumption, or scenario used for analysis |
| Evidence considered | Records, data, witness evidence, reports, schedules, or other material |
| Methodology | Analytical approach and basis for selection |
| Limitation or alternative | Data limitation, competing interpretation, scenario, sensitivity, or alternative method |
| Opinion status | Preliminary consulting observation, draft opinion, final expert opinion, or rebuttal issue |
| Required disclosure | Assumption, source, limitation, methodology, or independence disclosure required |
Counsel and expert briefing
A legal and technical consulting assignment normally concludes with a confidential briefing for the designated counsel or client audience. The briefing is designed to answer six practical questions:
- What records and project conditions have been reviewed?
- What does the available evidence establish, and what remains incomplete, inconsistent, or unverified?
- What are the relevant project, schedule, productivity, cost, completion, quality, or controls questions?
- What assumptions, limitations, alternative interpretations, or data issues affect the analysis?
- What documents, analysis, questions, witnesses, or records are required next?
- What actions may help the client and counsel clarify the record, evaluate the matter, prepare for a dispute process, or reduce further escalation?
Where included in the mandate, Torvane maintains agreed chronology, evidence, schedule, productivity, cost, assumptions, and follow-up registers through the relevant consulting phase. Counsel and the client retain all legal, procedural, settlement, claims, and forum decisions.
Engagement terms
The content shown here is illustrative. Each assignment is defined by the matter, engagement posture, client and counsel instructions, available information, review questions, confidentiality arrangements, reporting audience, work plan, deliverables, timing, fee, and engagement terms.
Torvane does not present this document as legal advice, a legal opinion, contract interpretation, an entitlement determination, liability determination, claims-adjustment service, insurance-coverage opinion, fixed service package, or guarantee of dispute outcome.
Independent expert reports and testimony are provided only where an appropriately qualified independent expert is engaged for the specific matter and the engagement terms address independence, conflicts, scope, methodology, disclosure, forum requirements, and any applicable professional obligations.