Identify Aberdeen Bridge Project Papers After a Road Injury

Write the travel account before selecting a project

Describe the direction of travel, bridge or street name visible in existing papers, nearest recognizable approach and the time of the occurrence. Explain whether the person was driving, riding, walking or stopped, using only what is known. Preserve uncertainty if the exact bridge is unresolved. A photograph of a sign may support one label while a later recollection uses another. Keep both with their sources rather than silently choosing the name that appears first in search results. Leave a separate space for the question that a public document might help answer.

Identify the eastbound Heron Street project

WSDOT’s grid-deck page identifies the Heron Street Bridge as eastbound US 12 in Aberdeen. It describes replacement of the driving surface and lists pre-construction status with a late-summer to late-fall 2027 timeline. Save that title and prospective period together. A planned construction window does not describe conditions during an earlier injury. If an account mentions the bridge deck, retain the person’s own description of what was encountered; do not replace it with the project page’s engineering description or assume the work had begun.

Keep the Wishkah mechanical project separate

The Wishkah River Bridge page concerns mechanical rehabilitation and presents a 2027–2028 timeline. Its milestones describe expected bidding, a construction start and completion, rather than an occurrence involving a particular traveler. Record which published milestone is being referenced. Even when two projects concern neighboring river crossings or the same numbered highway, their document sets can serve different purposes. A mechanical-work reference should not become a statement about the driving surface at the location in a photograph. The title, scope and date should travel with every saved excerpt.

Read traffic arrangements as dated planning information

The Heron page describes a future closure and a planned reconfiguration of the westbound Wishkah crossing. That explains why both bridge names can appear within one project description. It does not establish that the arrangement existed when someone was injured. If route instructions are relevant to the file, preserve the actual message, sign photograph or notice associated with that journey and its date. Keep a later planning page in a separate reference section. Neither a projected detour nor a construction schedule proves the route a person actually followed.

Choose between a state project question and a city record

WSDOT’s public-disclosure page identifies its Public Disclosure Request Center and distinguishes agency records from public information available elsewhere. The city’s records page separately routes police, municipal-court and general city requests. Describe the missing item before choosing among those routes. A question about a state project document differs from locating an existing city report. A website link does not establish that either organization holds every relevant photograph, contractor paper or communication. Use the author or receiving organization shown on an actual document as a starting identifier.

Make the document description specific

Aberdeen’s instructions ask for identification adequate to locate the record, including its title and date when known and the department when known. Apply that practical distinction to the file: list the exact project title, relevant period, location wording and the kind of document sought. Keep those details separate from a request for an explanation of why an injury happened. A project plan, an inspection record and a personal occurrence account answer different questions. If a reference is incomplete, mark the missing date or author openly rather than supplying an assumption.

Keep the injury account independent of project conclusions

Organize original photographs, messages and report references alongside a short chronology of the person’s movements. Label later site images with their own dates. Record which public pages were consulted and what question remains, without treating a planned repair as an admission or a finding about responsibility. Documents may clarify names and chronology while leaving the cause of an injury unresolved. Ask Legal Matters is a lead-generation service; this guide helps prepare information for a case-review conversation and does not establish engineering conditions, legal responsibility or a government affiliation.

Official sources and verification notes

Related local and state guidance

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