reports

TuxReportWebFrame

Long-form, web-hosted narrative canvas. Same family as TuxReportFrame — finished narrative, read top-to- bottom — but rendered as an HTML page rather than an 8.5×11 sheet. Reach for it when the deliverable lives at a permanent URL (annual report, research findings, accreditation summary) instead of leaving the app as paper.

Distinct from Visualizations: a web-hosted report is still read, not pivoted. If the reader is meant to filter and drill, it's a Visualization, not a Report.

basic

Cover · TOC rail · body · footer

annual report · fy2026

Sponsored research — TTI corridor program

A web-hosted summary of corridor program work, written for sponsors and the public. Distinct from the printed quarterly: this version lives at a permanent URL and updates between print cycles.

TTI Roadway Safety Program April 2026 12 min read

Executive summary

FY26 Q1 closed with awarded funding 12.4% above the same quarter in FY25, driven primarily by a $9.2M IH-35 corridor-safety renewal from TxDOT and a $4.8M FHWA work-zone classifier grant. Headcount on sponsored projects rose 6.1%; equipment capex held steady.

The headline metric: 412 active projects across the corridor program, a record for the institute in any single quarter.

Key findings

412

active projects

$84.2M

total awarded

36.8%

TxDOT share

Crash-rate reductions held in three of four corridors under active retrofit; the fourth (US-290 between Hempstead and Brenham) showed a 4% rise associated with construction-zone congestion, consistent with modeling. The interim signage refresh is on track for completion in the May steering review.

Methods

All metrics use TxDOT CRIS-2 records joined against the TTI corridor classifier. Confidence intervals are bootstrap percentile (B = 2,000) at the 95% level.

Data and methods

Source datasets, classifier versions, and reproducibility pointers live in the program's Landscape workspace. Sponsor access is provisioned via Entra ID; public extracts are published to data.tti.tamu.edu in CSV and Parquet.

What's next

Q2 work continues on the classifier-refresh roadmap and the FHWA work-zone deliverables. The next public update lands at the end of the fiscal quarter.

<tux-report-web-frame
  eyebrow="annual report · fy2026"
  title="Sponsored research — TTI corridor program"
  lede="A web-hosted summary of corridor program work, written
        for sponsors and the public. Distinct from the printed
        quarterly: this version lives at a permanent URL."
  byline="TTI Roadway Safety Program"
  date="April 2026"
  reading-time="12 min read"
  :toc="toc"
  width="default"
>
  <section id="summary">
    <h2>Executive summary</h2>
    <p>…narrative…</p>
  </section>

  <section id="findings">
    <h2>Key findings</h2>
    <tux-factoid :items="factoid" />
    <p>…narrative…</p>
  </section>

  <template #footer>
    <span>Source: tti.tamu.edu · Published April 2026</span>
  </template>
</tux-report-web-frame>

props

Three measure widths

Web reading degrades fast past ~75 characters per line. width="default" caps the body at ~70ch (the recommended editorial measure); narrow drops to ~56ch for very prose-heavy pieces; wide lifts to ~82ch when the body interleaves data tables or charts that need horizontal room.

when not to reach for this

Three near-neighbors that aren't this

TuxReportFrame — paper / PDF / print. Same family; different output medium. If the deliverable has to leave the app on paper, use the page-sized canvas.
TuxPageHeader + free composition — most landing pages don't need the cover/TOC/byline rhythm. Reach for the page header and compose normally.
A Visualization — if the reader pivots, filters, or drills in, it isn't a Report. Use /visualizations.