# Memorandum — Dana Ivers / Bracken Professional Engineering Board

## Bottom-line recommendation

**Do not accept the Board’s current “admit all charges” offer before obtaining and reviewing the prior-discipline file.** The offer is procedurally and substantively premature because it requires Dana to admit fraud even though the Board has not yet shown it meets the clear-and-convincing standard, and because the sanction exposure depends on a prior-discipline record that has not been produced.

**Immediate actions:**

1. **Send a written request today** for the Board’s complete prior-discipline file concerning Dana’s eight-years-ago building-envelope matter, and for a certification whether the Board has any other final disciplinary order within the preceding ten years.  
2. **Request that the Board extend the offer** until at least seven days after production of the file.  
3. **Request a continuance or prehearing conference** if the file is not produced promptly. If the Board refuses disclosure, file a motion for an order compelling production under the Board’s disclosure rule, and move to exclude any undisclosed prior-discipline material.  
4. **Do not sign any order admitting all charges.** A negotiated order may resolve some matters while preserving denial of fraud under the Board’s negotiated-order rule.

The final recommendation depends on the contents of the prior-discipline file:

| Prior-discipline file result | Recommended posture |
|---|---|
| **No final disciplinary order within the last ten years** — e.g., only an informal advisory letter, a vacated order, or no final order | Reject the all-admission offer. Counter for a **no-fraud, low-publicity resolution**: confidential advisory letter or, at most, a public reprimand without fraud admission; modest or no penalty; one year of monitoring; education/QC conditions. If the Board insists on fraud admission or an excessive sanction, proceed to hearing. |
| **Final disciplinary order entered within the last ten years and not vacated** | Reject the all-admission offer, but counter for a **no-fraud public reprimand package**: public reprimand, $8,000–$12,000 penalty, two years’ monitoring, accurate-certification and QC conditions. If the Board will accept that, settle. If it insists on a fraud admission, proceed to hearing unless a no-fraud settlement can be obtained. |
| **File is not produced, is incomplete, or is ambiguous** | Seek a disclosure order and continuance. If the Board still refuses, move to exclude the undisclosed prior file, preserve objections, and proceed to hearing while continuing to seek a no-fraud negotiated resolution. |

---

# 1. The fraud charge

## A. The false statement is real but not automatically fraudulent

The footer states:

> “I personally inspected the above structure onsite and certify the findings stated here.”

Dana did not physically visit the bridge. Under the governing rule, that statement is false even though remote supervision was otherwise adequate. So the Board has a false representation.

But the fraud standard is high:

- The Board must prove fraud by **clear and convincing evidence**.
- Fraud requires a **knowingly or recklessly false material representation**.
- A template error supports fraud **only** if Dana knew of the false statement or consciously disregarded a substantial risk that it was false.
- A careless failure to notice may support **negligence**, but not fraud.

The key question is therefore not merely whether the footer was false. It is whether Dana **knew** or **consciously disregarded** that she was signing a statement she had not personally performed onsite.

## B. The evidence supports negligence, not fraud

The following facts strongly undercut fraud:

1. **The footer was embedded in a firm template.**  
   Dana says she focused on the technical tables. That is a classic careless-review scenario, not necessarily deceptive conduct.

2. **Version history shows the same footer in 64 prior reports.**  
   That supports the inference that this was standard boilerplate, not a personalized false statement inserted for this report.

3. **No email or witness states that Dana noticed the footer.**  
   The Board has no direct evidence that Dana read, understood, or intentionally signed the false onsite certification.

4. **There is no prior warning or Board notice that this footer was false.**  
   Dana’s memory of an older “warning” is unknown in character and cannot be assumed. If it was an informal advisory letter or a vacated order, it does not even count as discipline under the governing rules.

5. **The technical findings appear to be based on reviewed data.**  
   Dana reviewed photographs, sensor readings, measurements, held review calls, asked for a second measurement, and independently approved the conclusion. That undermines any inference that she was trying to deceive the municipality about the substance of the inspection.

## C. The signature alone is not enough for clear-and-convincing proof

The Board may argue that by signing the report, Dana certified the entire document, including the footer. That is a plausible argument for **negligence**, but it is not enough to establish fraud by clear and convincing evidence.

Signing a report certifies professional responsibility for its conclusions. It does not necessarily prove that the signer noticed and adopted every embedded template line, especially where:

- the footer was long-standing;
- the same footer appeared in many prior reports;
- no evidence shows Dana noticed it;
- no evidence shows she altered or approved that particular language;
- and the actual technical review was otherwise supported by data.

Under the template-error rule, this looks like **careless failure to notice**, not knowing or reckless falsification.

## D. Materiality is also contestable

The Board may argue that the personal-inspection certification was material. That is arguable, but weaker than the Board might hope.

The governing rule permits remote supervision where the licensee:

- sets the plan;
- remains available;
- reviews underlying data and images;
- resolves material discrepancies;
- and independently approves the conclusion.

Dana appears to have done all of that. So the substantive inspection was not per se defective merely because she was not onsite. The false footer is a certification-language problem, not proof that the bridge assessment was fabricated.

That does not make the footer true. It remains false. But it weakens the inference that Dana intended to mislead the public or the municipality about the reliability of the report.

## E. Likely result on fraud

The fraud charge should be dismissed, or at least should not be sustained at hearing, unless the Board can produce evidence beyond the signature and template history showing that Dana:

- knew the footer was in the report;
- knew or should have subjectively known it was false in light of her remote-only involvement;
- and consciously disregarded the risk of falsity.

On the current facts, the Board’s fraud proof is more likely an inference from inattention than clear-and-convincing evidence of knowing or reckless fraud.

---

# 2. Negligent supervision and the technical decision not to close the bridge

## A. Remote supervision was facially adequate

The rule permits remote supervision when the supervising licensee:

1. sets the inspection plan;  
2. remains available;  
3. reviews underlying data and images;  
4. resolves material discrepancies; and  
5. independently approves the conclusion.

Dana appears to satisfy each element:

- She designed the inspection plan.
- She assigned a licensed junior engineer.
- She remained available by video.
- She reviewed 146 photographs, sensor readings, and measurements.
- She held two review calls.
- She asked for a second measurement when the junior engineer identified a 2.8 mm crack.
- She accepted a second measurement of 1.9 mm with an explanation that the first reading may have been due to camera scale.
- She independently concluded that monitoring, rather than immediate closure, was appropriate.

That is not rubber-stamping. It is the kind of documented remote review the rule appears to allow.

## B. The technical decision not to close is defensible

The Board’s “failure to close” theory depends heavily on hindsight:

- Three months later, a different crack grew near another connection.
- The municipality then closed the bridge.
- Its expert says the later crack was **not visible in the original images**.
- The expert also says the later crack was **not caused by the 1.9 mm crack**.
- No injury occurred.

That weakens the failure-to-close charge significantly.

Dana was not charged with failing to detect a crack that was not visible in the original images. She was charged with a decision made based on the data available at the time. A 1.9 mm crack, by itself, does not automatically require closure. Whether it required closure depends on the structure, location, load path, environmental conditions, structural criteria, and reasonable professional judgment.

The Board must prove negligence by a preponderance. That means it must show that a reasonable structural engineer, acting on the same data, would more likely than not have closed the bridge. The later crack’s existence does not prove that, especially where the later crack was not visible in the original images and was not caused by the 1.9 mm crack.

## C. The 2.8 mm to 1.9 mm discrepancy does not support negligence without more

The junior engineer initially noted a 2.8 mm crack. Dana did not ignore it. She requested a second measurement. The junior reported 1.9 mm and attributed the first reading to camera scale. Dana accepted the second reading and concluded monitoring was appropriate.

That is a reasonable response to a measurement discrepancy, not evidence of negligent supervision. If the Board wants to argue that Dana should have demanded a third measurement, an onsite recheck, or closure, it should do so through expert evidence, not hindsight.

## D. The supervision charge may overreach

The supervision charge should be distinguished from the report-certification issue.

- The **supervision of the inspection** appears adequate under the remote-supervision rule.
- The **failure-to-close** technical judgment appears defensible based on the current facts and the municipal expert’s statement.
- The most likely remaining issue is the **inaccurate certification footer**, which may support a negligence finding but not fraud.

So the Board may have a modest case for a quality-control or report-certification negligence issue, but not necessarily a strong case for negligent supervision or failure to close the bridge.

---

# 3. Evidentiary value of the anonymous complaint and the junior engineer’s records

## A. The anonymous complaint has weak evidentiary value

The anonymous complaint states that Dana “never reviews anything and rubber-stamps junior work.”

That is:

- anonymous;
- unverified;
- conclusory;
- contradicted by the junior engineer;
- and not reliable hearsay.

Under the governing rule, reliable hearsay may supplement other evidence, but **no violation may rest solely on an uncorroborated anonymous complaint**.

Here, the complaint is worse than “unreliable hearsay that may supplement.” It is directly contradicted by the junior engineer’s records. The complaint may explain why the Board opened the case, but it should not be treated as substantive proof of a violation.

The Board should not be allowed to use the complaint as a substitute for proof of:

- knowledge or recklessness;
- negligent supervision;
- failure to close;
- or imminent public danger.

If the Board relies on the complaint, Dana should demand that the Board identify the complainant if it treats the complaint as material evidence. If it will not, the complaint should be given little or no weight, and any violation should not rest on it.

## B. The junior engineer’s records are strongly exculpatory

The junior engineer contradicts the complaint and has supplied:

- review calls;
- marked images;
- Dana’s questions;
- the second-measurement request;
- and the technical review trail.

Those records are likely admissible, or at least highly reliable, as business records and/or party admissions, depending on form and authentication. They are materially exculpatory because they show:

- Dana did review the work;
- she asked targeted technical questions;
- she requested a second measurement;
- she engaged with the data;
- she was not merely rubber-stamping.

These records also help defeat the Board’s fraud narrative. They show that Dana was focused on the technical content, which supports her explanation that she did not notice the embedded footer.

## C. Practical use of the junior engineer’s records

At hearing or in settlement, the junior engineer’s records should be used to:

1. rebut the anonymous complaint;
2. show adequate remote supervision;
3. show that the 2.8 mm discrepancy was addressed;
4. show that the final conclusion was independently reached;
5. support the absence of reckless disregard for the report’s accuracy;
6. and support mitigation by showing the firm and Dana are responsive and capable of effective QC.

If the Board calls the junior engineer, Dana should be prepared to cross-examine. If the Board relies on the junior’s records without calling him, Dana should seek authentication and have a custodian or the junior engineer confirm the records’ reliability.

---

# 4. Whether emergency suspension is supportable

## A. Emergency suspension is not supportable on these facts

Emergency suspension before hearing requires **specific findings** of an **imminent and substantial threat to public safety**. Past error alone is insufficient where:

- current practice is controlled;
- no active unsafe project is identified;
- and the relevant structure is closed or under repair.

Here:

- The bridge has been closed for repair.
- The later crack was not visible in the original images.
- The later crack was not caused by the 1.9 mm crack identified in the report.
- No injury occurred.
- Dana has stopped using the template.
- Dana completed eight hours of supervision training.
- Dana adopted a two-reviewer signoff for field-certification language.
- There is no identified active unsafe project under Dana’s control.

That is not a present, imminent, substantial threat. It is a past report issue followed by a later, unrelated crack.

## B. The “imminent public danger” charge should not support emergency relief

The Board’s charge of “conduct creating an imminent public danger” is not enough by itself. The Board must point to a specific present danger. The bridge closure is evidence of a later problem, not proof that Dana’s current practice creates an imminent threat.

If the Board moves for emergency suspension, the opposition should demand:

- a specific unsafe project;
- a specific unsafe condition;
- a causal connection to Dana’s current or recent work;
- and proof that the threat is imminent, not merely possible.

In the alternative, Dana can offer less restrictive conditions, such as:

- no use of “personally inspected onsite” language unless physically present;
- second-reviewer signoff for field-certification language;
- firm QC audit of recent remote-inspection reports;
- immediate notice to the Board of any active bridge or safety-critical project;
- and completion of additional training if the Board requires it.

But emergency suspension itself is not supportable under the governing rule.

---

# 5. Significance of the template history

The version history showing the same footer in 64 prior reports is central.

## A. It supports the template explanation

The 64 prior reports suggest that the footer was not a one-off false statement. It was likely embedded in a standard form. That supports Dana’s account that she focused on the technical tables and did not individually approve the onsite certification language.

This is important because the fraud rule specifically addresses template errors:

- Template error supports fraud only if the licensee knew of the false statement or consciously disregarded a substantial risk that it was false.
- Careless failure to notice may support negligence without proving fraud.

The template history is therefore one of the best pieces of evidence distinguishing negligence from fraud.

## B. It weakens the inference of deliberate falsity

If Dana had inserted a false “personally inspected onsite” statement into an otherwise remote-inspection report, that would be serious. But the same footer appearing in 64 prior reports suggests a systemic form issue, not a deliberate false certification in this particular report.

The Board may argue that the repeated use of the footer shows Dana should have known it was wrong. That is an argument for negligence, not necessarily fraud. The rule requires more for fraud: knowledge or conscious disregard.

## C. It also supports mitigation

Even if the Board finds some violation, the template history supports mitigation because:

- the error was form-driven;
- it was not isolated;
- it was not accompanied by evidence of intent to deceive;
- it was corrected promptly;
- and the firm adopted stronger controls.

## D. Potential adverse use

The Board may try to use the 64 prior reports to argue that Dana signed the same language repeatedly and therefore had notice. Dana should be prepared for that.

The response is:

- the footer was embedded;
- no evidence shows she noticed it was false;
- no prior Board warning is known or produced;
- the technical review was otherwise supported;
- and the governing rule treats careless template failure as negligence, not fraud, absent knowledge or conscious disregard.

---

# 6. Remedial measures and how to present them without admitting fraud

Dana has:

- stopped using the template;
- completed eight hours of supervision training;
- adopted a two-reviewer signoff for field-certification language.

Under the governing rule, remedial training and corrected quality controls may mitigate sanction but do **not** require an admission of fraud.

## A. How to frame the remedial measures

Do not say:

- “I admit I fraudulently certified that I personally inspected.”
- “I admit I knowingly signed a false statement.”
- “I admit I recklessly disregarded the footer.”
- “I admit the report was deceptive.”

Instead, frame the remedial measures as voluntary quality-control improvements:

> “In response to the Board’s concerns, Dana and the firm strengthened report-certification controls to ensure that certification language accurately reflects the scope of the inspection. These measures are prudent risk-management steps and do not constitute an admission of fraud.”

That is accurate and appropriate.

## B. Specific language for settlement or mitigation

A safe formulation is:

> “Dana did not personally visit the Wren River bridge. The report used a standard template footer that included onsite-inspection language. Dana has stopped using that template, completed supervision training, and implemented a two-reviewer signoff procedure for field-certification language. These corrective measures are offered as mitigation and as evidence of present responsibility. They are not an admission of knowing or reckless false certification.”

That admits the factual absence of onsite inspection, which is not in dispute, but does not admit knowledge, recklessness, or fraud.

## C. Use of remedial measures in the sanction phase

The remedial measures support:

- no emergency suspension;
- no suspension at hearing;
- lower penalty;
- shorter monitoring;
- public reprimand rather than suspension if a public sanction is required;
- confidential advisory letter if no countable prior discipline exists;
- and a negotiated order with conditions instead of severe personal sanctions.

They should also be presented as evidence that the risk of recurrence is low.

---

# 7. The prior-discipline issue

This is the most important unknown.

Dana remembers receiving “some kind of warning” from the Board eight years ago after a building-envelope report. She does not know whether it was:

- an informal advisory letter;
- a final reprimand;
- a later-vacated order;
- something else.

The Board’s charging letter says only that “disciplinary history may be offered in aggravation.” Current counsel has not requested the file.

That is a serious gap.

## A. Why the file matters

Under the governing rules:

- A **final disciplinary order entered within the preceding ten years** is an aggravating factor.
- It may raise a reprimand-range case to suspension.
- An **informal advisory letter is not discipline**.
- A **vacated order does not count**.

So the character of the prior file can change the entire sanction calculus.

If the prior file contains no countable final order, the current matter is likely a reprimand-range case at worst, assuming the Board proves some negligence. If the prior file contains a final order within the last ten years, the Board may argue that a reprimand-range case can be raised to suspension.

That is why the prior file must be obtained before any settlement decision.

## B. The exact file that must be obtained

The request should be specific. Counsel should demand:

> “Please produce the complete prior-discipline file in the Board’s possession concerning Dana Ivers’s building-envelope report matter from approximately eight years ago, including:  
>   
> 1. all complaint, inquiry, and investigative files;  
> 2. all notices, advisory letters, warning letters, reprimands, consent orders, final orders, hearing transcripts, and sanctions;  
> 3. all docket entries showing the matter’s status;  
> 4. any document showing whether the matter was informal advisory, final, vacated, stayed, sealed, or expunged;  
> 5. the date of entry of any order;  
> 6. any payment or penalty records;  
> 7. any monitoring or education completion records;  
> 8. any Board classification of the prior matter; and  
> 9. a certification whether the Board has any other final disciplinary order for Dana Ivers within the preceding ten years.”

The request should also ask the Board to identify any document it intends to offer in aggravation.

If the Board claims the file is confidential, request in camera review or a redacted but legally sufficient version. If the Board claims it does not intend to use the file, Dana still needs the file for sanction analysis because the charging letter expressly reserved the possibility of aggravation.

## C. Why the file could change sanction advice

### 1. If the file shows no final disciplinary order

Examples:

- informal advisory letter;
- vacated order;
- no final order;
- order entered more than ten years ago.

Then the prior file is not an aggravating factor under the rule. The current case is more likely to be treated as a first-time, template-related, negligence-type issue.

In that scenario:

- the Board’s leverage is lower;
- suspension is less likely;
- a confidential advisory letter or modest public reprimand is more defensible;
- the current offer of public reprimand, $12,000, and two years’ monitoring is likely excessive;
- and Dana should not admit fraud to obtain a public package.

### 2. If the file shows a final disciplinary order within ten years

Examples:

- final reprimand;
- final consent order;
- final public or private order not vacated.

Then the prior matter is an aggravating factor. The Board may argue that a reprimand-range case can be raised to suspension.

In that scenario:

- the current offer’s sanction may be closer to the low end of the Board’s potential range;
- but the required fraud admission is still unacceptable;
- the goal should be a no-fraud public reprimand package that caps suspension risk;
- and a hearing may be riskier because the prior order could support a harsher sanction even if fraud is not proven.

### 3. If the prior order was for a similar certification issue

If the older building-envelope matter involved a similar report-certification or scope-of-inspection issue, the Board may argue that Dana was on notice. That weakens the fraud defense somewhat, but it still does not lower the proof standard. The Board must still prove current knowledge or reckless disregard by clear and convincing evidence.

In that scenario, a no-fraud settlement becomes more attractive because the prior order may make the Board more aggressive at hearing.

### 4. If the prior order was for unrelated conduct

If the prior order was unrelated to report accuracy or supervision, it is less relevant to the fraud charge but still relevant to sanction if it is final and within ten years.

### 5. If the file is ambiguous or incomplete

If the Board produces only a fragment, or describes the prior matter without producing the controlling document, Dana should not guess. The correct posture is:

- demand the complete file;
- seek a continuance;
- seek in camera review if needed;
- and move to exclude any undisclosed prior-discipline material.

---

# 8. Whether to accept the current offer, counter, seek a continuance or disclosure order, or proceed to hearing

## A. Do not accept the current offer as written

The current offer is:

- public reprimand;
- $12,000 penalty;
- two years’ monitoring;
- in exchange for admission of **all** charges.

That is not acceptable before the prior file is produced, and it is not acceptable as written in any scenario because it requires admission of fraud, negligent supervision, failure to close, and imminent public danger.

Dana should not admit:

- fraud;
- negligent supervision of the inspection;
- failure to close the bridge;
- or imminent public danger.

Those charges are weak on the current facts, and the Board has not satisfied the relevant proof standards.

## B. The current offer should be countered, not accepted

The Board can obtain the same practical result — a public reprimand, penalty, monitoring, and QC conditions — without requiring a fraud admission. Under the negotiated-order rule, the Board may resolve some charges while preserving a denial of others.

A better order would say, for example:

- fraud not proven or not sustained;
- no finding of negligent supervision of the inspection;
- no finding of failure to close the bridge;
- no finding of imminent public danger;
- a limited finding, if needed, of negligent use of an inaccurate certification template;
- public reprimand or confidential advisory letter depending on prior history;
- penalty and monitoring tailored to the prior-discipline file;
- conditions requiring accurate certification language and second-reviewer QC.

## C. Seek a continuance or disclosure order now

Because the hearing is in twenty days and the offer expires in seven days, Dana cannot make an informed decision without the prior file.

Counsel should:

1. request the prior-discipline file in writing;
2. ask the Board to extend the offer until seven days after production;
3. request a prehearing conference;
4. if the Board does not produce the file promptly, file a motion for an order compelling disclosure;
5. request a continuance sufficient to review the file, consult with experts, and negotiate;
6. if the Board refuses disclosure, move to exclude the prior file from sanction analysis.

The Board’s own disclosure rule supports this. It must disclose evidence on which it relies and allow a reasonable request for records necessary to sanction analysis. The prior-discipline file is directly sanction-relevant.

## D. Proceed to hearing only if necessary

Proceeding to hearing is not the first choice, but it remains a strong option if:

- the Board refuses to produce the prior file;
- the Board insists on a fraud admission;
- the prior file shows no countable discipline and the Board still demands an excessive package;
- or the Board will not accept a no-fraud negotiated order.

At hearing, the strategy should be:

1. move to dismiss or defeat the fraud charge for failure of clear-and-convincing proof;
2. move to dismiss or defeat the failure-to-close charge for lack of expert support and causation;
3. move to dismiss or defeat the imminent-danger charge for lack of present threat;
4. use the junior engineer’s records to show adequate supervision;
5. use the template history to show negligence rather than fraud;
6. use the municipal expert’s statement that the later crack was not visible in the original images and not caused by the 1.9 mm crack;
7. use the remedial measures as mitigation;
8. and move to exclude any undisclosed prior-discipline file.

---

# 9. Concrete recommendation conditioned on the prior file

## Step 1: Before any settlement decision

Send a letter to the Board today requesting:

1. the complete prior-discipline file described above;
2. a certification that the Board has identified all prior discipline within the last ten years;
3. extension of the offer until seven days after production;
4. a prehearing conference to discuss disclosure and continuance;
5. and confirmation that the Board will not rely on any prior-discipline material not produced to Dana.

Do not accept the offer while the file is unknown.

## Step 2: If the file shows no countable final order

Examples:

- informal advisory letter;
- vacated order;
- no final order;
- final order outside the ten-year window.

Then:

- reject the current offer;
- move to dismiss fraud and imminent danger;
- argue no negligent supervision or failure to close;
- counter for a no-fraud resolution.

Suggested counter:

- confidential advisory letter, if possible;
- if the Board insists on public sanction, public reprimand without fraud finding;
- no penalty or $2,500–$5,000;
- one year of monitoring;
- education/QC conditions;
- no admission of fraud, negligent supervision, failure to close, or imminent danger;
- limited acknowledgment, if required, that the template footer did not accurately reflect the scope of inspection and has been corrected.

If the Board will not accept that, proceed to hearing.

## Step 3: If the file shows a final disciplinary order within ten years

Examples:

- final reprimand;
- final consent order;
- final order not vacated.

Then:

- reject the current offer as written;
- do not admit fraud;
- counter for a no-fraud public reprimand package.

Suggested counter:

- public reprimand;
- no fraud finding;
- no finding of negligent supervision of the inspection;
- no finding of failure to close;
- no finding of imminent public danger;
- limited finding, if required, of negligent use of an inaccurate certification template;
- $8,000–$12,000 penalty;
- two years’ monitoring;
- conditions requiring:
  - accurate inspection-scope certification language;
  - no “personally inspected onsite” language unless physically present;
  - two-reviewer signoff for field-certification language;
  - periodic QC audits;
  - completion or maintenance of supervision training.

If the Board accepts that, settle. If the Board insists on a fraud admission, proceed to hearing unless the Board offers a no-fraud package that caps suspension risk.

## Step 4: If the file is not produced or is ambiguous

Then:

- file a motion for an order compelling production;
- request a continuance;
- if the Board still refuses, move to exclude the prior file;
- proceed to hearing with objections preserved;
- and continue seeking a no-fraud negotiated order.

Do not let the offer deadline force a decision without the file.

---

# 10. Practical hearing/settlement exhibits to assemble now

Even while seeking disclosure and continuance, begin assembling the record:

1. **Report and footer**
   - final report;
   - exact footer;
   - report version history;
   - template metadata.

2. **Remote-supervision proof**
   - inspection plan;
   - video call records;
   - two review call logs;
   - marked images;
   - Dana’s questions;
   - measurement logs;
   - second-measurement request;
   - junior engineer’s explanation of camera scale.

3. **Technical data**
   - 146 photographs;
   - sensor readings;
   - measurements;
   - metadata showing dates and locations;
   - expert analysis supporting monitoring rather than closure.

4. **Later-crack evidence**
   - municipal expert report or statement;
   - confirmation that later crack was not visible in original images;
   - confirmation that later crack was not caused by the 1.9 mm crack;
   - bridge closure records;
   - no-injury certification, if available.

5. **Template history**
   - 64 prior reports;
   - who created the template;
   - when footer was added;
   - whether it was standard firm language;
   - whether any prior Board or client complained about it.

6. **Remedial measures**
   - template retirement documentation;
   - training certificate for eight hours;
   - two-reviewer signoff policy;
   - firm QC procedure for certification language;
   - any recent reports showing corrected language.

7. **Prior-discipline file**
   - complete Board file;
   - classification;
   - finality;
   - vacatur status;
   - dates;
   - sanctions;
   - any confidentiality designation.

---

# Final conclusion

The Board’s strongest evidence is the false footer and Dana’s signature. But under the governing rules, that is not enough for fraud by clear and convincing evidence. The template history, lack of notice, absence of direct evidence that Dana read the footer, and the junior engineer’s records all support a theory of **careless report certification**, not knowing or reckless fraud.

The negligent-supervision and failure-to-close charges are also weak. Dana’s remote supervision appears compliant, the 2.8 mm discrepancy was addressed, and the later crack was not visible in the original images and was not caused by the 1.9 mm crack.

The anonymous complaint is unreliable and contradicted. The junior engineer’s records are reliable and exculpatory. Emergency suspension is not supportable because there is no identified active unsafe project and Dana’s current practice is controlled.

The single biggest wildcard is the prior-discipline file. If it contains no countable final order, Dana should reject the current offer and press for a no-fraud, low-publicity resolution or proceed to hearing. If it contains a final order within the last ten years, Dana should still reject the all-admission offer but should be prepared to accept a no-fraud public reprimand, penalty, and monitoring package that avoids suspension.

**The concrete recommendation is: obtain the prior-discipline file first; extend the offer or continue the matter if necessary; do not admit fraud; and choose the settlement or hearing strategy based on the file, not on Dana’s uncertain memory of an old “warning.”**