Expert report review

Event data recorder data in the opposing reconstruction report: what does the reviewer check?

Recorder speed and delta-V look like measured facts in a reconstruction report, but each has defined coverage, tolerance and timing. A review checks the vehicle against 49 CFR Part 563, the elements and accuracy the rule sets, what the speed measures under braking, why delta-V can run low, which event belongs to the crash and how the module was downloaded. NHTSA's own 2008 analysis said recorder data should always be used with other sources.

A reviewer from behind studies an open module under a dashboard in a garage

What does a review of event data recorder evidence in the opposing report check?

Whether the vehicle's recorder falls under federal rules, which data elements it kept, how accurate each element is, whether the recorded event is this crash, how the data were downloaded, and whether the report used the data with other evidence.

An event data recorder keeps a short window of data around a crash; in the cases discussed below it was read from the airbag or restraint control module. Reconstruction reports cite its speed, brake and delta-V values as measured facts. A review treats them as measurements with defined coverage, accuracy and timing, each of which can be checked against federal rules and published validation studies.

The National Highway Traffic Safety Administration reached that view in its own analysis. Its April 2008 report Analysis of Event Data Recorder Data for Vehicle Safety Improvement, DOT HS 810 935, prepared with the Volpe National Transportation Systems Center, concluded that "EDR data can objectively report real-world crash data" but that, "due to significant limitations however, EDR data should always be used in conjunction with other data sources."

The review follows that sentence. It first establishes what the recorder in this vehicle was required to record and with what tolerance. It then checks which recorded event the report used and how the data came out of the module. Last, it compares the recorder values with the scene, the vehicle damage and the other methods in the report, and states where they agree and where they do not.

Each step below names the rule or study behind it. The same questions apply whether the recorder data appear in the opposing expert's report, in a police reconstruction or in an insurer's file.

Does the federal EDR rule apply to the vehicle in the case?

Part 563 of 49 CFR covers vehicles built on or after September 1, 2012, with a GVWR of 3,855 kg (8,500 pounds) or less and an unloaded weight of 2,495 kg (5,500 pounds) or less, that have an EDR.

Under 49 CFR 563.3, the rule applies to passenger cars, multipurpose passenger vehicles, trucks and buses manufactured on or after September 1, 2012, with a gross vehicle weight rating of 3,855 kg (8,500 pounds) or less and an unloaded vehicle weight of 2,495 kg (5,500 pounds) or less, that are equipped with an event data recorder. Walk-in van-type trucks and vehicles sold only to the U.S. Postal Service are excluded. The rule does not require a recorder; it sets what a recorder must capture if the manufacturer installs one.

Section 563.11 requires the owner's manual of a covered vehicle to include a statement in English about the recorder. The statement begins: "This vehicle is equipped with an event data recorder (EDR)." The owner's manual is therefore a first document for the review: it confirms that the vehicle had a recorder subject to Part 563.

For vehicles built before September 2012, the content of the record depends on the manufacturer and the module generation. The 2008 NHTSA report describes older General Motors modules that recorded no pre-crash data but stored longitudinal delta-V for up to 300 milliseconds, and later modules that recorded pre-crash speed, throttle and brake status for 5 seconds at 1 Hz while capturing only 150 milliseconds of delta-V. It describes Ford modules that did not store travel or impact speed, and newer Takata modules that stored delta-V and acceleration from minus 142 milliseconds, before the airbag algorithm woke up.

A 2004 report for the National Cooperative Highway Research Program, Use of Event Data Recorder (EDR) Technology for Highway Crash Data Analysis (NCHRP Web-Only Document 75, prepared by Rowan University and George Mason Law School), adds that certain Ford recorders "may not, in fact, be capable of storing the entire event" and, describing General Motors modules, that "lateral delta-V is not recorded." A report that treats an older module as if it met Part 563 needs to say which elements that module actually recorded.

Which data elements must a Part 563 recorder keep?

Longitudinal delta-V for up to 250 milliseconds at 100 samples per second, and speed, accelerator position and brake status for 5 seconds before time zero at 2 samples per second in vehicles built before the phase-in.

Table I of 49 CFR 563.7 lists the required elements; the values below are those of the 2023 edition. Longitudinal delta-V is recorded for 0 to 250 milliseconds after time zero, or until the end of the event plus 30 milliseconds if that is shorter, at 100 samples per second. Maximum longitudinal delta-V and the time at which it occurred are recorded for up to 300 milliseconds.

Three pre-crash elements cover the five seconds before time zero at 2 samples per second: indicated vehicle speed, engine throttle percent full or accelerator pedal position, and service brake on or off. At 2 samples per second the recorder gives ten values for each element, half a second apart. The 2024 and 2026 rules changed Table I to show 20 seconds at 10 samples per second for these elements, with a footnote that keeps the interval of minus 5.0 to 0 seconds at 2 samples per second for vehicles manufactured before September 1, 2031, except the share of production that the phase-in brings under the new values.

Other required elements are recorded once: the ignition cycle count at the time of the crash and at the time of download, driver safety belt status and frontal airbag warning lamp status one second before time zero, frontal airbag deployment times for the driver and the right front passenger, the number of events, the time between event 1 and event 2, and whether the complete file was recorded.

The review checks which elements the report relies on and whether the recorder in this vehicle captured each of them. An opinion about steering or yaw built on a recorder that did not capture those elements has no recorder basis. For each element the report uses, the review lists the recording interval and the sample rate from Table I, so that the reader of the review sees what the recorder could and could not show.

How accurate are the recorded values under the federal rule?

Table III of 49 CFR 563.8 sets indicated speed accuracy at plus or minus 1 km/h, delta-V at plus or minus 10 percent and accelerator position at plus or minus 5 percent. Brake status has no accuracy requirement.

Section 563.8 sets the format of the data. Indicated vehicle speed is reported with an accuracy of plus or minus 1 km/h and a resolution of 1 km/h. Delta-V elements carry an accuracy of plus or minus 10 percent and a resolution of 1 km/h. Accelerator pedal percent full carries plus or minus 5 percent and a resolution of 1 percent. Service brake status is recorded as on or off, without an accuracy figure. A footnote to Table III says the accuracy requirement only applies within the range of the physical sensor.

A plus or minus 10 percent tolerance on delta-V matters in arithmetic. A recorded longitudinal delta-V of 30 km/h is consistent, under the rule's tolerance, with a true value between 27 and 33 km/h. A report that carries a single recorded value into a momentum calculation without that range overstates its precision, and the review recalculates at both ends.

The speed tolerance applies to the element the rule names "speed, vehicle indicated." It does not by itself say how closely that indicated speed matches speed over the ground in every condition. The next section covers when the two diverge.

The review also checks resolution and rounding in the download report. A speed reported in whole kilometers per hour and converted to miles per hour in the expert's report can acquire decimals the recorder never produced.

What does the recorded pre-crash speed actually measure?

The speed the vehicle's own systems indicate. Under hard braking, wheel slip can make the recorded speed lower than the true speed over the ground, and validation studies report such underreporting.

A 2016 SAE technical paper by W. Bortles, W. Biever, N. Carter and C. Smith of Kineticorp, A Compendium of Passenger Vehicle Event Data Recorder Literature and Analysis of Validation Studies (SAE 2016-01-1497), reviewed published tests. It concluded that "reported values of vehicle velocity change (ΔV) and Pre-Crash vehicle speed tend to be less than the actual values." For steady-state pre-crash speed it found low variability with slight underreporting.

The same paper identified braking as a cause of larger errors: "the high level of wheel slip during braking underreported the true over-the-ground speed of the vehicle." It also listed three outliers well below the rest of the data: speed differences of minus 12 at 35 mph, minus 7.8 at 34.8 mph and minus 7 at 50 mph.

Crash tests by the National Research Institute of Police Science in Japan, reported by N. Takubo and co-authors in Evaluation of Event Data Recorder Based on Crash Tests, found that "pre-crash velocities of EDRs were very accurate and reliable," with an average difference of 4.2 percent and a root mean square of 9.2 percent against reference speeds, and identified braking before impact as a likely influence on accuracy.

A training handout for law enforcement and prosecutors by John B. Kwasnoski, posted by the Warren County, New York, District Attorney, lists among expected defense points that "wheel sensor speeds may not be the same as actual vehicle speeds." The review therefore reads the brake status column next to the speed column. If the brake was on in the last samples, the recorded speed in those samples is the speed most exposed to slip, and the report should say how it treated them.

Why can the recorded delta-V understate the crash?

Because the recorder may stop before the event ends, ignores acceleration before the trigger, and can clip peaks above the sensor range. Studies report delta-V underreporting of a few percent in some tests and about 30 percent in one.

The SAE compendium names three mechanisms. Quoting Gabler, it says that "EDRs that do not record the entire event will underestimate the delta V." "Any acceleration of the vehicle prior to the threshold trigger will not be included in the ΔV calculation." And peak accelerations above the sensor limit, which the paper puts at 40 to 50 G, are clipped, which also lowers the computed delta-V.

The paper collects results. In collinear motorcycle tests reported by Beck, the recorder underreported delta-V by 0.53 mph (about 6 percent) and 0.86 mph (about 12 percent). In a pole test reported by Ishikawa under the Japanese NCAP program, it "underreported the ΔV in a frontal pole impact by 7.3 m/s (16.3 mph) or 29.4%." In an Exponent test of a Lexus ES-350 the recorder underreported delta-V by approximately 20 mph. In sled tests reported by Carr, the average error magnitude per recorder ranged between 0.3 and 4.3 percent.

The Japanese crash tests found that maximum delta-V differed by more than 10 percent in five of twenty-five events and by more than 20 percent in two, with an average difference of about 4 percent. The 2008 NHTSA report cites an analysis by Niehoff and co-authors that identified sources of delta-V error: isolated acceleration point errors, calibration point errors, rotation-induced acceleration errors and incomplete pulses.

Delta-V is a change in velocity, not a speed. The Kwasnoski handout lists a defense expert's assertion that cumulative delta-V is the same as impact speed and notes that this "may not be true." The same caution binds the other side: a report that converts delta-V into impact speed has to show the momentum or energy analysis that connects them, with the mass and the other vehicle's motion.

How is time zero defined, and why does the reviewer check it?

Time zero is the reference point for all recorded intervals, defined in 49 CFR 563.5 by the start of the airbag algorithm or a deployment. Pre-crash samples are counted back from it.

Section 563.5 defines an event as a crash or other physical occurrence that meets the trigger threshold, or a non-reversible restraint deployment, whichever comes first. The trigger threshold is a longitudinal velocity change that "equals or exceeds 8 km/h within a 150 ms interval." Time zero is the earliest of several markers, such as the activation of a wake-up airbag control algorithm or the deployment of a non-reversible restraint. The end of the event is reached when the resultant cumulative delta-V within a 20 millisecond period falls to 0.8 km/h (0.5 mph) or less, or when the crash detection algorithm resets.

The NCHRP report describes time zero as "sometimes referred to as the time of algorithm enable." The 2008 NHTSA report adds that pre-crash timing can be asynchronous, which affects the reported speed and brake status. A sample labeled minus 0.5 seconds may not correspond exactly to half a second before first contact.

The State v. Logsdon opinion of the Ohio Court of Appeals, decided on May 15, 2026, shows the practical form of the question. The recorder data, presented through a police officer, showed 53 mph three seconds before the airbag deployed and 42 mph one second before. A crush analysis put the impact speed at approximately 41 mph. Each figure refers to a different moment, and a review states which moment each describes before comparing them.

For avoidability opinions the timeline is decisive. If the report places the start of braking, the driver's perception of the hazard and the point of impact on one time axis, the review checks that the recorder samples were placed relative to time zero and that the half-second spacing was carried into the calculation.

Which recorded event belongs to this crash?

The one whose timing, direction and severity match the crash, confirmed by the event count, the time between events and the ignition cycle values. Deployment events are locked, but non-deployment events can be overwritten or cleared.

Under 49 CFR 563.9, when a frontal airbag deploys the recorder must capture the deployment data and lock that memory so it cannot be overwritten. For other events the recorder records up to two events in an available empty buffer. If no empty buffer exists, the manufacturer may overwrite earlier non-deployment event data or may choose not to record the new event. A buffer that holds earlier deployment data may not be overwritten.

Older modules followed their own rules. The 2008 NHTSA report states that General Motors non-deployment event data is typically cleared after 250 ignition cycles, which it estimates at roughly 60 days of driving. A non-deployment record from a vehicle that was driven for weeks after the collision may be from another event or may be gone.

Table I gives the tools for matching. The number of events and the time between event 1 and event 2 show whether the module recorded a multi-impact sequence. The ignition cycle count at the crash and at the download show how many times the vehicle was started in between. The Kwasnoski handout lists the claim that "the EDR data is from a different crash" among points a prosecutor should expect, which is the same question a reviewer asks of any report.

The 2008 report also found mismatches between recorder data and crash databases: in 23 cases the recorder reported a deployment that the crash database did not show, and in 15 the reverse. It attributed some to improper airbag reinstallation, electrical failures and replacement of the recorder after repairs. A vehicle with a repair history needs the repair records before its recorder data are assigned to the crash in suit.

What should the reviewer get from the download?

The complete report generated by the retrieval software, the original download file, the software version, the vehicle identification and the ignition cycle values, and the name and training of the person who performed the download.

Section 563.12 requires each manufacturer, by licensing or other means, to make a retrieval tool that can access and retrieve the required data commercially available no later than 90 days after the first sale of the vehicle for purposes other than resale. For covered vehicles the question is therefore not whether the data could be read, but whether they were read correctly and completely.

Downloads do fail. The 2008 NHTSA report estimated a 60 percent successful download rate for applicable vehicles in NASS field collection, and of 3,459 recorder files originally counted, 2,541 were analyzed; others were excluded because they were empty, did not match the vehicle identification numbers or were missing. The NCHRP report described the Vetronix crash data retrieval system as able to download two versions of the Ford restraint control module; tool coverage depended on the module.

The Kwasnoski handout lists the points a defense can raise about the download: that the examiner "did not use most recent version of the CDR software," the difference between a witness certified as a technician and one certified as an analyst, and that the vehicle computer was not checked for recalibration. Each is a document request: the software version and release date, the certification of the person, and the vehicle's service records.

In civil cases, Rule 26(a)(2)(B)(ii) of the Federal Rules of Civil Procedure requires a retained expert's report to contain "the facts or data considered by the witness in forming" the opinions. A recorder download the expert used falls in that category, and the review asks for the original file in addition to the printed summary. Under Rule 26(b)(4)(C), communications that identify facts, data or assumptions the attorney provided and the expert relied on are also discoverable, so an assumed speed or event supplied by counsel can be traced.

What do the brake and throttle columns tell the reviewer?

Whether the driver was braking or accelerating in the last five seconds, sampled every half second. Brake status is on or off with no accuracy requirement, and accelerator position carries a tolerance of plus or minus 5 percent.

Table I of 49 CFR 563.7 requires the service brake status and the engine throttle percent full or accelerator pedal position for the five seconds before time zero, at 2 samples per second, in vehicles built before the phase-in. Table III of 563.8 gives the accelerator element an accuracy of plus or minus 5 percent and a resolution of 1 percent. The brake element is recorded as on or off, and the rule sets no accuracy for it.

An on or off flag at half-second intervals does not say how hard the driver braked or exactly when braking began. A sample showing the brake off at minus 1.5 seconds and on at minus 1.0 seconds places the brake application somewhere in that half second. A report that states the moment of braking to a tenth of a second from these data claims more resolution than the recorder provides.

The 2008 NHTSA report adds that pre-crash timing can be asynchronous, which affects reported speed and brake status. The review therefore treats the brake column as a range of times, not a single instant, and carries that range into any perception-reaction or avoidance calculation.

Throttle and accelerator values work the same way. A recorded accelerator value of zero followed by brake on is consistent with a driver who lifted and braked; a value above zero with the brake on calls for an explanation in the report, such as two-foot driving or a timing offset between the channels.

What do the belt and airbag elements add to the review?

Driver belt status one second before time zero, the airbag warning lamp status, the deployment times and the event count. In injury cases they bear on occupant motion, and in every case they help tie the record to the crash.

Table I requires the driver safety belt status and the frontal airbag warning lamp status at minus 1.0 seconds, the frontal airbag deployment times for the driver and the right front passenger, the number of events, the time between event 1 and event 2, and a flag showing whether the complete file was recorded.

Deployment times connect the record to the crash pulse. A recorded deployment that the vehicle's condition does not show, or a deployed airbag with no deployment in the record, is the kind of mismatch the 2008 NHTSA report found in 38 cases, and which it attributed in part to improper reinstallation, electrical failures and replacement of the recorder after repairs.

In an injury case the recorded driver belt status bears on the claimed injuries, and the review compares it with the condition of the belt hardware and with the occupant's account. A lit airbag warning lamp before the crash shows a fault the system itself had reported. The review notes it and asks whether the fault could affect the recorded data, and whether service records explain it.

The complete file flag is a short entry with a large effect. If the flag records that the file was not completely recorded, every value after the break is suspect, and the report should say which values it used and why they precede the break.

What should counsel request at an inspection of the vehicle?

The owner's manual statement, the module and its connectors, the vehicle identification as it appears in the download, the ignition cycle reading, service and repair records, and photographs of the module location before removal.

The owner's manual statement required by 49 CFR 563.11 confirms that the vehicle had a recorder subject to Part 563. The manual is requested with the vehicle.

The ignition cycle count at the crash and at the download, both required elements, show how many times the vehicle was started between the two. The review compares the difference with the vehicle's history after the crash. A large difference means the vehicle was driven or started repeatedly, which bears on whether a non-deployment event could have been overwritten under 563.9 or cleared, as the 2008 NHTSA report described for older General Motors modules after 250 ignition cycles.

The prosecutors' monograph by Kwasnoski advises that the recorder "should be secured in anticipation of being able to read the computer memory at a later time," and the Kwasnoski handout lists the defense point that the vehicle computer was not checked for recalibration. Service records answer both: when the module was installed, whether it was replaced, and whether any software update or recalibration changed the vehicle's speed signals.

Photographs of the module in place, of its connectors and of the download setup, with the time of each step, show the chain of handling. The engineer lists for counsel what needs to be measured and downloaded, so that the inspection produces a record the other side cannot dispute later.

How does the reviewer compare recorder data with the other evidence?

Value by value, with the moment each value refers to. NHTSA's 2008 analysis found police-estimated speed within 20 percent of the recorder value in only about 44 percent of 361 paired cases.

The 2008 NHTSA report compared police-reported travel speed with recorder speed and found that only about 44 percent of the 361 paired cases fell within plus or minus 20 percent of the recorder value. The report did not treat the recorder as automatically right; it recommended pairing recorder data with other crash data sources, and it warned that its results "are not nationally representative."

The Japanese crash tests add a lesson for multi-vehicle crashes. In multiple rear-end tests the recorder data of the leading and middle cars were valuable, but a reconstruction using only the following car's recorder was not accurate. A report that reconstructs a chain collision from one vehicle's module has a gap the review names.

The comparison runs in three directions. Recorder speed is checked against scene evidence such as tire marks and rest positions. Recorder delta-V is checked against crush measurements and the other vehicle's damage. Recorder brake and throttle status are checked against the driver accounts and any video. Where all three agree, as the Logsdon court noted for the crush estimate and the recorder values, the agreement itself is evidence.

The Logsdon figures also show the arithmetic a review performs. A drop of 11 mph, about 4.9 m/s, between the samples three seconds and one second before deployment is an average deceleration of about 2.5 m/s², roughly 0.25 g, over those two seconds. The review compares that figure with the brake status in the same samples and with any tire marks, and the crush estimate of about 41 mph with the last recorded value of 42 mph.

Where they disagree, the review explains the disagreement using the known limits: wheel slip, clipping, incomplete recording, timing offsets or a mismatched event. A report that resolves the disagreement by choosing the recorder value without discussing these limits does not apply the method reliably.

What if the module was not downloaded or the data are incomplete?

The review states what the report used instead and whether it supports the opinion. A federal court in Michigan excluded a reconstruction report that had no recorder download and no analysis behind its conclusions.

In Fields v. Ashford, decided on November 5, 2019, in the Eastern District of Michigan, the plaintiff's reconstructionist reported that the module he called the ACM "black box" "was damaged to the extent that it could not be downloaded with the CDR tool." Judge Matthew F. Leitman found that the one-page report listed conclusions without causation analysis, that perception-reaction time was never factored in and that many calculations were completed nearly a year after the report. He excluded the causation testimony in its entirety under Rule 702.

The absence of recorder data does not by itself defeat a reconstruction. Speed can be reached from scene evidence and crush. But the report has to say which method replaced the recorder and show it. The NCHRP report's note that some Ford recorders may not store the entire event, and the Part 563 element "complete file recorded," both tell the reviewer to check whether a download that exists is complete.

A prosecutors' monograph, Crash Reconstruction Basics for Prosecutors by John Kwasnoski (American Prosecutors Research Institute, 2003), advises that "the EDR should be secured in anticipation of being able to read the computer memory at a later time." The Kwasnoski handout lists the defense point that the "EDR was not secured and made available to defense." Where the module was not preserved, the review records that the data cannot be checked and why.

Partial data raise a further point. The handout lists as a defense claim that "if one piece of EDR data is invalid or missing it invalidates all the data." A review does not adopt that rule. It states which elements are missing or suspect and which remain usable, element by element.

What changes with the 20-second pre-crash recording rule?

A December 18, 2024 NHTSA rule extends required pre-crash recording to 20 seconds at 10 samples per second. A May 18, 2026 rule phases it in, beginning September 1, 2028 and reaching all covered vehicles in 2031.

The final rule published in the Federal Register on December 18, 2024 (Doc. 2024-29862) states that it will extend the recording period for timed data metrics, compared with 5 seconds of pre-crash data at 2 Hz, to "20 seconds of pre-crash data at a frequency of 10 Hz." It took effect on January 17, 2025, and responded to section 24303 of the Fixing America's Surface Transportation Act, which directed NHTSA to establish the appropriate recording period. It originally set a compliance date of September 1, 2027.

A rule published on May 18, 2026 (Doc. 2026-09849) delays and phases in that requirement without changing it. For most manufacturers, 25 percent of applicable vehicles produced between September 1, 2028 and August 31, 2029 must comply, then 50 percent in the following year, 75 percent in the year after, and 100 percent on and after September 1, 2031. Small-volume and limited-line manufacturers comply beginning September 1, 2032, and multistage and altered vehicles beginning September 1, 2033. The rule takes effect on June 17, 2026.

For cases litigated now, covered vehicles built before the phase-in are required to record only 5 seconds at 2 samples per second. If a report describes the last 20 seconds before a crash from such a vehicle's recorder, the review asks whether the module recorded more than the rule requires or whether the extra seconds came from another source.

When 20-second, 10 Hz records reach casework, the review questions stay the same: what the recorded speed measures, how the samples relate to time zero, which event they belong to and how they compare with the scene. More samples narrow the gaps between them without removing those questions.

How do courts treat reconstruction opinions built on recorder data?

Under Rule 702 the opinion must rest on sufficient facts or data and apply a reliable method reliably. Courts have admitted opinions where recorder values and other methods agreed, and excluded reports that rested on conclusions without analysis.

Rule 702 of the Federal Rules of Evidence, as amended in 2023, requires the proponent to show the court that it is more likely than not that the testimony is based on sufficient facts or data, is the product of reliable principles and methods, and applies them reliably to the case. The committee note says the amendment clarifies that the preponderance standard applies to these three requirements.

Logsdon and Fields mark two ends. In Logsdon the Ohio court found no plain error in admitting a police officer's crush-based speed estimate, noting that it was consistent with the recorder testimony. In Fields the federal court excluded a report that gave conclusions without analysis after the module could not be downloaded.

Rule 705 lets an expert give an opinion without first testifying to the underlying data, but "the expert may be required to disclose those facts or data on cross-examination." For recorder evidence the underlying data are the download file and its report. A review gives counsel the specific values, tolerances and time references to put to the witness.

Rule 26 governs the civil exchange: the report must state the facts or data considered, and a rebuttal report on the same subject matter is due within 30 days after the other party's disclosure unless the court orders otherwise (Rule 26(a)(2)(D)(ii)). The review is scheduled with that deadline in mind, and the download file is requested early enough for the reviewer to read it in the original format.

What does IAE do when the opposing report relies on event data recorder data?

IAE reviews the opposing reconstructionist's report, including its use of recorder data, and gives counsel a list of what to measure and download at an inspection. Delivery takes up to 5 business days, with a 48-hour rush.

IAE's page for accident reconstruction reviews describes the work for counsel facing the other side's reconstructionist in injury and property damage cases in US courts. The engineer asks whether the opposing reconstructionist applied the intellectual rigor that practice in the field requires: inputs, reaction times, calculations, tests and the limits of engineering opinion. The engineer checks the recorder download against the scene evidence and lists for counsel what needs to be measured and downloaded.

IAE confirms the questions, the format and the deadline with the client before work starts. The secretariat confirms receipt of the materials the same day, and within one business day IAE confirms the format, the cost, the deadline and the specialist from its registry. The client approves the candidate and the CV before work begins.

Every specialist is a member of the public IAE registry, verified by Member ID or QR code, and confirms in the document that he or she has no interest in the outcome. Materials are sent through the contact form or by email and are not passed to third parties without the client's consent. The court weighs a review with the other evidence, and neither IAE nor the reviewer guarantees the outcome. IAE is not a law firm and does not advise on case strategy.

Sources

Read also

All articles

Expert report review

Ready to discuss your case?

Send the materials: the secretariat will confirm the format, cost, deadline and the specialist within one business day.

Expertise request

Received

Cost and timeline estimate

WorkReview of an opinion
TimelineUp to 5 business days
ExpertIAE registry member