Match a Loretto Bridge Identifier to a Road-Injury Inquiry

Fix the reported point before choosing an inventory entry

Write down the road, direction of travel and nearest supported landmark from the original account. If a bridge is mentioned, explain whether the event was on its deck, an approach, a nearby intersection or another point, but leave an uncertain relationship unresolved. Keep the location wording from an existing crash document or photograph alongside the person’s description. A mailing address or search result for a similarly named road should not replace the actual scene. Do not stand in traffic, enter a restricted area or revisit a structure simply to force the account to match a database entry.

Use the Church Street entry as an identification example

The state inventory labels bridge 500A4750001 with Church Street, Loretto Branch and Lawrence County, and its bridge-owner field names the City of Loretto. Preserve the identifier with those labels when the available location material supports the match. It can make a question about an existing structure record more precise than asking for everything about a bridge in town. Do not use that field alone to decide who maintained a feature at an incident date, who controlled an approach or who may be responsible for an injury. A database label and an incident investigation serve different purposes.

Separate inventory descriptions from present conditions

An inventory entry may contain engineering labels and numerical fields, but this guide does not interpret their meaning or establish their currency for a particular visit. Do not describe a structure as safe, unsafe, open, restricted or repaired because one value appears in an online report. Record the document title and identifier as the source of the description. If a question concerns a particular inspection, work activity or change, identify that record category and the relevant period instead. The inventory’s existence does not confirm that a requested maintenance item, photograph or incident-specific inspection exists or will be available.

Keep an accident-report inquiry with its report identifier

Loretto’s FAQ describes obtaining an accident report from the Police Department at City Hall. Use that information to verify the current procedure for the particular report sought, rather than treating the bridge identifier as an accident-report number. Preserve any responding-agency name and incident identifier already supplied to the person involved. If the original material names another agency, keep that difference visible and ask that agency about its record. The city’s general pickup instruction does not establish that Loretto Police responded to every event near the city or holds every item connected with a roadway injury.

Distinguish a street concern from a request for an existing file

The same FAQ directs street problems and drainage concerns to the City Manager. A question about an existing record should identify that purpose clearly rather than appearing only as a new report that a road needs attention. Explain the feature, supported dates and type of material you are trying to locate. The city’s contact directory separately labels administrative and police contacts; those labels help select an initial routing question without proving custody. Keep a copy of any new concern separately from earlier documents so it does not become evidence that the city had received the same information before an incident.

Use TDOT’s records route for a defined transportation question

TDOT publishes a Legal Division route for public-records inquiries. When seeking a state-held record, describe the inventory identifier, county, road and particular existing material of interest. If you do not know whether TDOT holds it, make that a routing question instead of assuming state custody because the inventory appears on a state website. Keep the state request distinct from any city accident-report or street-concern inquiry. Follow the current agency instructions concerning how to make the request and any response about availability. The general instructions do not establish the contents of an underlying bridge file or incident record.

Create an index connecting the records without filling gaps

A useful index can pair the reported incident location with the inventory identifier, the separate crash identifier and any specific transportation-record question. Note the source for each connection and mark an uncertain match openly. Retain original photographs, messages and agency responses; put location annotations on copies. Keep care and expense documents separate from the location index so a treatment date is not mistaken for a road-inspection date. This approach lets a reader see what the records actually identify and what remains unresolved, without treating an inventory label as a finding about the cause or legal consequences of an injury.

Official sources and verification notes

Related local and state guidance

Existing city injury guides · Tennessee state resources · More dedicated locality articles