06_report

The draft expert report

Structured as a summary under Rule 36(9)(b) of the Uniform Rules of Court: assumptions, inputs, method, results, uncertainty, conclusion. Written in the first person so that an independent expert can adopt it — and marked draft until one does.

Draft — not signedNot expert evidenceNames redacted
This is a draft on synthetic data. It is not expert evidence and no expert has adopted it. Its purpose here is to show the structure and the standard of disclosure: every assumption listed with its source and the range it was tested across, and a conclusion confined to what the physics constrains.

Summary of expert opinion - collision reconstruction

DRAFT for expert review

Claim reference CLAIM-A · prepared 26 August 2026 · CapSeal Recon 0.2.0

1 Identification and status

This is a draft summary of expert opinion prepared in the structure of a summary under Rule 36(9)(b) of the Uniform Rules of Court. It has been generated by CapSeal Recon from the sealed evidence listed in section 4 and is placed before an independent reconstruction expert for review, correction and, if the expert is satisfied, adoption and signature.

Until it is adopted and signed by that expert it is a draft and it is not expert evidence. The expert, not the software and not the party, is the witness.

Identification
ItemDetail
Claim reference (anonymised)CLAIM-A
IntersectionMain Road / Church Street (anonymised)
Date and time of collision2023-04-17T07:42:00+02:00
Control at the intersectionSignal-controlled (robot)
Vehicle AVehicle A (eastbound, Main Road) - 2016 Toyota Corolla Quest
Vehicle BVehicle B (northbound, Church Street) - 2019 Volkswagen Polo Vivo
Prepared on26 August 2026
StatusDRAFT - not signed, not expert evidence
Prepared byCapSeal Recon 0.2.0 for PayFar Global Ltd
Reviewing expert[to be appointed]

2 Duty of the expert

The expert who adopts this report does so on the following terms, which are reproduced here so that they are part of the document the court reads.

  • My duty is to assist the court on the matters within my expertise. That duty overrides any obligation to the party by whom or through whom I am engaged.
  • I have set out in this report every assumption on which my opinion depends, and the range over which each assumption was tested.
  • Where the physical evidence does not establish a matter, I have said so rather than expressing an opinion the evidence does not support.
  • I have not been asked to, and do not, express any opinion on the apportionment of fault. Apportionment under the Apportionment of Damages Act 34 of 1956 is a matter for the court.

3 Instructions and scope

I was instructed to determine, so far as the physical evidence allows, the speeds of the two vehicles at the instant of contact, the order in which they entered the intersection, and whether each driver's account of the collision is capable of producing the physical evidence recorded at the scene.

The analysis is a two-vehicle planar reconstruction. It does not address occupant kinematics, injury causation, vehicle defect, or the conduct of either driver beyond what the physical evidence establishes.

4 Evidence considered

Every document and file I considered is listed below. Each was hashed on receipt and recorded in a sealed manifest with a chain-of-custody log; the manifest travels with this report as 00_manifest and can be re-verified independently.

All 10 evidence files in this bundle are intake-sealed. They were hashed and timestamped on receipt by PayFar; integrity is asserted from intake onward only. No file in this bundle is capture-sealed, so capture-time integrity is not asserted for any of them. This is the expected position for a retrospective POC claim.

  • Every file in this bundle is intake-sealed. Capture-time integrity is not asserted for any of them; this is the expected position for a retrospective POC claim (section 6, step 1).
Sealed evidence manifest
ItemCategoryFileProvenanceTimestamp authoritySHA-256
E001vehiclesA_damage_front.pngintake-sealedhttp://timestamp.digicert.com7f1f7e0ba8d71be7...
E002vehiclesB_damage_left.pngintake-sealedhttp://timestamp.digicert.com522d43c86294174b...
E003rest_positionsscene_rest_positions.pngintake-sealedhttp://timestamp.digicert.comadfba5d12f67040e...
E004rest_positionspolice_ar_form.pdfintake-sealedhttp://timestamp.digicert.comae475c85c243ac8f...
E005sceneassessor_measurement_sheet.csvintake-sealedhttp://timestamp.digicert.com76242bdda24a0ca9...
E006statementsdriver_statements.txtintake-sealedhttp://timestamp.digicert.com31d05e9e66c350de...
E007telematicstelematics_A.csvintake-sealedhttp://timestamp.digicert.comd9bbc8d1073f4187...
E008videodashcam_B_frames.pngintake-sealedhttp://timestamp.digicert.comefbbce974c9bffde...
E009outcomeoutcome_record.txtintake-sealedhttp://timestamp.digicert.com5abdcc976f8ead6b...
E000statementsclaim.yamlintake-sealedhttp://timestamp.digicert.coma64d028d93466e03...

Provenance tiers: capture-sealed material was hashed at the moment of capture; intake-sealed material was hashed on receipt and no assertion is made about its integrity before that moment.

5 Assumptions

The table below lists every numerical assumption the analysis depends on, the value adopted, the range over which the analysis was repeated, how confident I am in the value, and where it came from. Nothing else was assumed.

The following parameters were not documented for these vehicles and were taken from a specification database or a segment-class default: cg_from_front_axle_ratio, cg_height_m, front_overhang_share, height_m, kerb_mass_kg, length_m, occupant_mass_kg, payload_mass_kg, track_m, wheelbase_m, width_m, yaw_inertia_factor. Each was swept across the range shown, so the effect of that estimation on the answer is visible in section 9 rather than hidden in a single figure.

Assumptions and the ranges over which they were tested
Applies toParameterAdoptedRange testedConfidenceSource
Vehicle Akerb_mass_kg1215 kg1142 to 1288indicativeManufacturer published specification (indicative) [toyota_corolla_quest_2016]
Vehicle Aoccupant_mass_kg75 kg70.5 to 79.5indicativeclaim file: 1 occupant(s) at 75 kg unless stated
Vehicle Apayload_mass_kg0 kg0 to 0indicativenot recorded on the claim file; taken as zero
Vehicle Alength_m4.53 m4.258 to 4.802indicativeManufacturer published specification (indicative) [toyota_corolla_quest_2016]
Vehicle Awidth_m1.76 m1.654 to 1.866indicativeManufacturer published specification (indicative) [toyota_corolla_quest_2016]
Vehicle Aheight_m1.46 m1.372 to 1.548indicativeManufacturer published specification (indicative) [toyota_corolla_quest_2016]
Vehicle Awheelbase_m2.6 m2.444 to 2.756indicativeManufacturer published specification (indicative) [toyota_corolla_quest_2016]
Vehicle Atrack_m1.48 m1.391 to 1.569indicativeManufacturer published specification (indicative) [toyota_corolla_quest_2016]
Vehicle Acg_from_front_axle_ratio0.45 -0.396 to 0.504class-defaultclass default [c_segment] - C-segment / compact sedan or hatch
Vehicle Acg_height_m0.54 m0.4752 to 0.6048class-defaultclass default [c_segment] - C-segment / compact sedan or hatch
Vehicle Afront_overhang_share0.55 -0.45 to 0.65indicativeCapSeal default: share of total overhang ahead of the front axle
Vehicle Ayaw_inertia_factor0.9 -0.8 to 1indicativeCapSeal default: k in Izz = k*m*(L^2+W^2)/12
Vehicle Bkerb_mass_kg1070 kg1006 to 1134indicativeManufacturer published specification (indicative) [vw_polo_vivo_hatch_2018]
Vehicle Boccupant_mass_kg150 kg141 to 159indicativeclaim file: 2 occupant(s) at 75 kg unless stated
Vehicle Bpayload_mass_kg0 kg0 to 0indicativenot recorded on the claim file; taken as zero
Vehicle Blength_m3.97 m3.732 to 4.208indicativeManufacturer published specification (indicative) [vw_polo_vivo_hatch_2018]
Vehicle Bwidth_m1.68 m1.579 to 1.781indicativeManufacturer published specification (indicative) [vw_polo_vivo_hatch_2018]
Vehicle Bheight_m1.47 m1.382 to 1.558indicativeManufacturer published specification (indicative) [vw_polo_vivo_hatch_2018]
Vehicle Bwheelbase_m2.47 m2.322 to 2.618indicativeManufacturer published specification (indicative) [vw_polo_vivo_hatch_2018]
Vehicle Btrack_m1.46 m1.372 to 1.548indicativeManufacturer published specification (indicative) [vw_polo_vivo_hatch_2018]
Vehicle Bcg_from_front_axle_ratio0.44 -0.3872 to 0.4928class-defaultclass default [b_segment] - B-segment / small hatch or sedan
Vehicle Bcg_height_m0.53 m0.4664 to 0.5936class-defaultclass default [b_segment] - B-segment / small hatch or sedan
Vehicle Bfront_overhang_share0.55 -0.45 to 0.65indicativeCapSeal default: share of total overhang ahead of the front axle
Vehicle Byaw_inertia_factor0.9 -0.8 to 1indicativeCapSeal default: k in Izz = k*m*(L^2+W^2)/12
Scenedrag factor0.750.65 to 0.85published rangepublished range for asphalt / dry - no site measurement
Impactrestitution0.080.00 to 0.20published rangeStructural vehicle-to-vehicle impact at this closing speed.
Impactimpulse ratio0.450.30 to 0.70published rangeInter-vehicle tangential impulse ratio; not directly measurable.

6 Inputs

The scene was modelled to scale from the source stated below together with the assessor's site measurements. Accuracy is bounded by those measurements; no survey-grade scan was carried out.

  • friction: no site measurement; a published range for asphalt / dry is used and swept. This is expected for a retrospective claim and is stated in the report.
Scene and impact geometry
ItemValue
Coordinate frameLocal plane, origin at the intersection centre, +x east, +y north, metres
Scene basisMunicipal orthophoto tile 2023-06 (demonstration reference)
MeasurementsAssessor site visit, tape and hand laser, per CapSeal measurement protocol v1 (demonstration)
Plan uncertainty+/- 0.20 m
Surfaceasphalt / dry
Light and weatherdaylight / clear
Rest position A(0.20, 6.10) m, heading 334 deg, +/- 1.0 m and 10 deg - SAPS Accident Report sketch and tow record, located from the datum by the assessor
Rest position B(5.40, 11.90) m, heading 20 deg, +/- 1.2 m and 12 deg - Scene photographs supplied by the insurer, located from the datum by the assessor
Contact point(-1.75, 5.25) m - Located from the gouge mark recorded in the scene photographs and the upstream edge of the debris field.
Impact plane normal270 deg (bearing), acting from B onto A
Vehicles
ItemVehicle AVehicle B
Description2016 Toyota Corolla Quest2019 Volkswagen Polo Vivo
Mass at collision (kg)12901220
Yaw inertia (kg.m^2)22851700
Length x width (m)4.53 x 1.763.97 x 1.68
Damaged facefrontleft
Crush-energy analysisnot available - momentum onlynot available - momentum only

Where no published crush stiffness coefficients exist for a model, no crush-energy analysis was performed for that vehicle and the reconstruction rests on momentum and trajectory matching alone.

7 Method

The reconstruction was carried out in four steps.

  • Impact. A planar impulse-momentum analysis of the two vehicles at the contact configuration recorded in section 6, with a coefficient of restitution along the impact-plane normal and an impulse-ratio condition along the tangent. Linear and angular momentum are conserved exactly; the analysis rejects any solution that would create kinetic energy.
  • Separation. Each vehicle was then integrated to rest as a planar rigid body on four tyre contact patches, each patch developing friction opposing its own slip velocity. The final heading of each vehicle is therefore an output of the analysis, not an assumption.
  • Fit. The pre-impact speeds were solved by repeating the above until the simulated rest positions and headings matched the documented ones, each weighted by the uncertainty recorded for that document. The fit was started from 25 different starting points to test whether the answer is unique; 1 distinct solution(s) were found.
  • Uncertainty. Every assumption in section 5 was then varied, first one at a time and then all together by Monte Carlo, with the whole fit re-run each time. The speed ranges in section 8 come from that sweep, not from an error estimate placed around a single answer.
Engine
ItemDetail
EngineCapSeal Recon reference solver
VendorPayFar Global Ltd
Version0.2.0
Court-accepted commercial engineNO
Validated against published staged testsNO
StatementCapSeal Recon reference solver is a transparent solver built by PayFar Global Ltd and used to develop and test the pipeline. It is NOT a court-accepted commercial engine and it has NOT been validated against published staged collisions. A bundle produced with it must not be presented to an independent expert as the primary analysis (scope document section 6, step 4).

8 Results

The reconstruction reproduces the documented rest positions to within the figures in the second table. That agreement is what gives the speeds their weight: they are not read off a formula, they are the speeds that put both vehicles where they were actually found.

Vehicle B crossed its stop line 1.14 s before vehicle A crossed its own, on a 5th-to-95th percentile interval of 1.02 to 1.27 s. The interval does not include zero, so the entry order is established by the physical evidence at this confidence.

Signal phase timing was requested from the municipality and was not obtained. Conclusions are framed on entry order and speed, not on light colour. No clip in this bundle shows a signal head, so this reconstruction makes no statement about which vehicle had a green light. It establishes entry order and speed.

  • Sight line, vehicle A. The view became clear 3.9 s before impact and remained clear to impact. Earlier in the window it was obstructed. Plan-view test at an eye height of 1.10 m; obstructions recorded as lower than that are ignored. This states geometric availability of a view, not what a driver observed.
  • Sight line, vehicle B. The view became clear 3.9 s before impact and remained clear to impact. Earlier in the window it was obstructed. Plan-view test at an eye height of 1.10 m; obstructions recorded as lower than that are ignored. This states geometric availability of a view, not what a driver observed.
Reconstructed quantities
QuantityValueRange across all tested assumptions
Speed of A at contact52 km/h49 to 56 km/h
Speed of B at contact40 km/h37 to 43 km/h
Change of speed (delta-V) of A28 km/h-
Change of speed (delta-V) of B30 km/h-
Energy dissipated in the impact81 kJ-
Vehicle A crossed its stop line0.30 s before contact0.26 to 0.33 s
Vehicle B crossed its stop line1.43 s before contact1.29 to 1.59 s
Agreement with the documented rest positions
ItemPosition errorHeading error
Vehicle A rest position0.05 m0.4 deg
Vehicle B rest position0.06 m0.3 deg

The threshold adopted for this work is 1.5 m and 15 degrees. This reconstruction is within that threshold.

9 Uncertainty

No single figure is offered for either speed. The ranges in section 8 are the 5th to 95th percentile of a Monte Carlo sweep in which every assumption in section 5 was drawn from its stated range simultaneously and the whole reconstruction re-solved for each draw.

The combined uncertainty leaves a workable speed range; the bundle presents the range, not a single figure.

120 of 120 Monte Carlo draws produced a usable solution; draws that failed to converge are excluded and counted, not replaced.

Which assumption moves the answer most
AssumptionSwing in A's speed (km/h)Swing in B's speed (km/h)
Tyre-road drag factor (post-impact)6.25.0
Impact-plane normal bearing5.22.5
Coefficient of restitution1.64.1
Vehicle A yaw inertia factor1.80.8
Contact point along the impact plane0.71.6
Vehicle A kerb mass1.20.1
Vehicle B kerb mass1.10.1
Impact-plane impulse ratio1.00.4
Vehicle B yaw inertia factor0.60.2

Each assumption was moved to each end of the range in section 5 with all others held at their adopted values, and the whole reconstruction re-solved.

Full one-at-a-time sensitivity table
AssumptionSettingValueA (km/h)B (km/h)Rest residual (m)
Tyre-road drag factor (post-impact)low0.6549370.09
Tyre-road drag factor (post-impact)high0.8555420.17
Coefficient of restitutionlow052391.02
Coefficient of restitutionhigh0.250431.32
Impact-plane impulse ratiolow0.353400.12
Impact-plane impulse ratiohigh0.752400.06
Vehicle A kerb masslow114252400.15
Vehicle A kerb masshigh128851400.17
Vehicle B kerb masslow100651400.17
Vehicle B kerb masshigh113452400.13
Vehicle A yaw inertia factorlow0.851400.23
Vehicle A yaw inertia factorhigh153400.27
Vehicle B yaw inertia factorlow0.852400.09
Vehicle B yaw inertia factorhigh152400.06
Contact point along the impact planelow-0.552390.51
Contact point along the impact planehigh0.551410.45
Impact-plane normal bearinglow26057370.63
Impact-plane normal bearinghigh28052400.17

10 The parties' accounts tested against the physical evidence

Each driver's account was then run through exactly the same physics, with the same masses, the same impact geometry and the same road surface. The only thing changed was the speeds each account asserts. The question asked is narrow: does that account put the vehicles where they were found?

The account of the driver of vehicle A cannot produce the documented rest positions. Run through the same physics, with the same masses, the same impact geometry and the same road surface, it leaves vehicle B 15.8 m from where it was found (and the worst heading error is 54 degrees), against a tolerance of 2.4 m and 24 degrees. The gap is what the animation shows.

The account of the driver of vehicle B can produce the documented rest positions: run through the same physics it leaves both vehicles within 0.06 m and 0.3 degrees of where they were found. This account is not excluded by the physical evidence. It does not follow that it is what happened - more than one account can be consistent with the same evidence.

An account that is not excluded by this test is not thereby established. More than one account can be consistent with the same physical evidence, and where that is so this report says so rather than choosing between them.

Alternative-scenario test
AccountSpeeds asserted (A / B)Worst rest-position errorWorst heading errorResult
The account of the driver of vehicle A50 / 75 km/h15.8 m54.5 degnot physically consistent
The account of the driver of vehicle B52 / 40 km/h0.1 m0.3 degphysically consistent

Tolerance applied: 2.4 m and 24 degrees, being the consistency threshold widened by the recorded uncertainty in the rest positions themselves.

11 Conclusion

On the physical evidence recorded at the scene, the collision is reconstructed as follows. The reconstruction reproduces both documented rest positions to within 0.06 m and 0.4 degrees.

  • Vehicle A was travelling at between 49 and 56 km/h at the instant of contact.
  • Vehicle B was travelling at between 37 and 43 km/h at the instant of contact.
  • Vehicle B crossed its stop line before vehicle A, by between 1.0 and 1.3 seconds.
  • The account of the driver of vehicle A is not capable of producing the documented rest positions and is therefore excluded by the physical evidence.
  • The account of the driver of vehicle B is capable of producing the documented rest positions and is not excluded by the physical evidence.

11.1 Matters on which I express no opinion

I express no opinion on which driver was at fault, or on the apportionment of damages between them. What the physical evidence constrains is set out above; the legal consequences of those facts are for the court.

Nor do I express an opinion on which vehicle had a green light, except to the extent stated in section 8.

12 Limitations

The following limitations apply to this analysis and should be read with the conclusion.

  • This is a two-vehicle planar analysis. It does not model occupant motion, pedestrian or cyclist multibody dynamics, motorcycle dynamics, rollover, or structural crush by finite element analysis.
  • The scene was measured by tape and hand laser against aerial imagery. It was not surveyed. Plan accuracy is +/- 0.20 m.
  • The tyre-road drag factor was not measured at the site. A published range for the surface and condition was used and swept.
  • Signal phase timing was requested from the municipality and was not obtained. Conclusions are framed on entry order and speed, not on light colour.
  • Telematics, where present, is treated as corroboration of the reconstruction, not as its basis. Its resolution is stated per vehicle in 04_timeline.
  • I express no opinion on apportionment of fault.

12.1 What this analysis does not assert

The following are recorded so that no reader takes them as implied.

  • That any bundle will be admitted in any court, or that a court will prefer it over an opposing expert.
  • That all eight claims will produce a tight speed solution; one or two may be momentum-only with wide ranges, and will be labelled so.
  • That the POC pipeline is the production platform; it is an internal tool built to test the concept and to measure unit economics.
  • That a fault percentage will be produced; the bundle constrains physical facts and the animation demonstrates which account is physically consistent.

Declaration and signature

I have read this report. It reflects my own opinion, formed on the material listed in section 4 and on my own examination of the analysis. I understand that my duty is to assist the court and that this duty overrides any obligation to the party engaging me.

Expert: [to be appointed]

Qualifications:

Registration:

Signature and date