Card listing roadside design options and owner record keeping steps. Modern roadside design options: how owner records hold up in 2027
Image: Roadside Edit

Guides

Part of How to compare modern roadside design options before you decide

Modern roadside design options: how owner records hold up in 2027

Modern roadside design options for 2027 include MASH guardrail, cable barrier, Road Zipper, FlexPost, and Silva Cell, plus owner record rules for baselines.

What to take away

  • Preserve the baseline before editing options.
  • Name each option, source, and status.
  • Keep changes in a correction log.
  • Make a public record that removes sensitive details and labels commercial roles.

Name the roadside options

EPA's City Green case-study guidance notes that planning can address constrained space, historic context, regulatory obstacles, and long-term maintenance. Read EPA's City Green options resource. It does not decide what works at one roadside site.

  • MASH-compliant guardrail and terminals. AASHTO's Manual for Assessing Safety Hardware sets crash test criteria. FHWA requires MASH for new installations on the National Highway System.
  • Cable median barrier. Trinity Highway CASS is a high-tension cable system. These barriers stop cross-median crashes on divided highways.
  • Road Zipper by Lindsay Transportation Solutions. This movable barrier shifts lanes for peak travel. It is used on the Golden Gate Bridge and other corridors.
  • FlexPost flexible delineator posts. These posts bend on impact and rebound. They suit bike lanes, edge lines, and median edges.
  • Silva Cell by DeepRoot. Modular soil cells support pavement and give tree roots soil. They suit urban tree pits and stormwater goals.
  • Filterra by Contech Engineered Solutions. This bioretention tree box filter treats stormwater runoff. It suits tight roadside sites and NPDES permit goals.

Keep an option register

A comparison record should let a new reader see what was considered and why. Retain the baseline, each option's purpose, evidence, evidence limits, and decision.

Field What it records
Baseline Existing condition and known information limit
Option Proposed direction, not an approval
Purpose User task the option is intended to address
Evidence Dated source or observation
Assumption Information not confirmed
Status Proposed, referred, advanced, set aside, or revised
Decision Date, responsible role, and next action

Add a correction path

If a current record changes a comparison, add a dated correction instead of overwriting the old entry. Note what source changed, what option field changed, and what public copy needs review. Keep vendor statements, paid placements, and editorial examples separate from the factual option record.

For publication, remove private contacts, bid terms, security details, and access procedures. The public version should explain the decision boundary without exposing private project material.

At handoff, include the source register, the current comparison, open questions, and the correction log. The next editor should locate the basis of an option before updating public copy.

Assign a next review date for any active public comparison. The register should identify the role that can publish the next revision. That owner should check that the stated source still supports the nearby public claim.

Preserve source roles in the record

The National Archives guidance for digital photographic records explains why image records need identifying and descriptive information. Retain the source page, date, location, record ID, and caption. A media credit identifies origin and does not prove an unrelated current condition.

The NPS documentation standards require reliable sources with stated limits. Identify each record role: observation, concept, decision, correction, or media credit. Reported completion is a separate role. The role shows what claim it can support.

The NPS historical documentation guidelines discuss source identification and reporting results. A correction entry should name the old statement, new source, date, and exact change.

Before a handoff, compare the draft with the register and remove private details from public material. Use stable IDs across the draft, source register, image folder, and correction log. Stable IDs catch mismatches after a file rename.

Keep a short update note at the top of the register. It should list records added, changed, or withdrawn since the last review. The public version may be shorter than the project file. It should preserve source dates, media credits, and stated limits. Do not remove an uncertainty just to make the article smoother.

Review the register before publishing. Confirm that every record has the correct role, date, source ID, and public-use status. When an option is withdrawn, label it with the decision date and reason in the internal record. Keep that detail out of public copy unless it is relevant and supported.

Common questions

What record is most important?

The baseline, because it explains the condition each option was intended to address.

Can a provider profile serve as an option record?

No. It may describe a service, but it does not document the site condition or decision.

When should a record be revised?

When evidence, scope, decision ownership, or the public claim supported by the record changes.

More in Guides

Latest from Preservation Desk