01 / REVIEW

Use stable locations

Assign segment and feature identifiers that match the route plan. Repeat photographs from recognizable viewpoints. A dated observation is more useful when another person can return to the same place.

02 / REVIEW

Describe before diagnosing

Record visible movement, openings, debris, damaged boards or changed surface conditions. Keep severity and safety decisions with the responsible reviewer. Do not infer structural condition from a photograph alone.

03 / REVIEW

Close the action

Record who evaluated the observation, what response was required and when it was completed. Preserve unresolved items and any access restrictions until the authorized owner closes them.

Give the next person a place to return to

A useful log starts with a location another person can find. Divide the route into named segments and identify the feature within each segment: a bench bay, drain, ramp approach, removable panel or numbered board group. Keep those identifiers on the owner’s route drawing. “By the water” and “near the entrance” become ambiguous when a long promenade has several entrances and repeated details.

Use one overview photograph to establish the location and a closer view to show the observation. Retain the original files with date and location references. If a measurement matters, record its units, method and endpoints; a ruler visible at an angle is not a substitute for a recorded measurement. Note the observer’s position so repeat views do not quietly change the apparent condition.

Record the inspection boundary. A surface walk does not establish what is happening beneath decking, inside a connection or behind a curb. Identify inaccessible areas explicitly. “Not observed” is more useful than a blank box that a future reader might interpret as satisfactory.

Describe the condition before naming a cause

Scroll sideways to read all columns. Keyboard: focus the table and use the arrow keys.

Describe the condition before naming a cause
Weak noteMore useful observationQuestion left for review
Deck is slipperyVisible wet leaf residue at the planting edge; rain earlier that morning; no surface test recordedWhat response and evaluation are required under the owner’s operating plan?
The fastener has failedOne visible head stands above the surrounding surface; photograph and board identifier recordedWhat is the exact connection and what does the responsible reviewer need to inspect?
Board is rottenLocalized discoloration and surface loss observed at the stated board end; underside not visibleWhat additional assessment is needed to establish cause and extent?
Gap is too wideOpening measured between identified faces, with units, direction of travel and observation dateWhich governing criteria and product movement requirements apply?

These are fictional wording examples, not diagnoses. Avoid making a field note sound more conclusive than the observation allows. Keep what was seen, what was measured and what somebody later concluded in separate entries. A photograph can support a record of appearance; it cannot by itself verify the substrate, concealed fastening or capacity of the assembly.

The U.S. Access Board’s surface guidance addresses surface characteristics, openings and changes in level. It also explains why slip-resistance values depend on the test method. Use the applicable project requirements when evaluating observations; this log does not turn an appearance check into a compliance result.

Make repeat observations comparable

Weather and use are part of the record. Distinguish a surface observed during rainfall from one observed after drying. Record shade, debris, cleaning since the previous visit and any change in access. If the same location looks different, those details help a reviewer decide whether the observation describes a persistent condition, a temporary deposit or a change that requires further investigation.

Keep the original observation when follow-up begins. Add the later date, evidence reference and action instead of replacing the first note with “fixed.” If a location was inaccessible on the follow-up visit, say so. A later empty field does not erase an earlier concern.

Do not invent a network-wide inspection interval from the wood species or the traffic illustration. The owner’s inspection plan should identify its routine and event-triggered checks, who performs them and who handles concerns. Record the actual trigger for a visit, such as a scheduled review, reported condition, completed work or storm follow-up. The log documents that process; it does not set the facility’s inspection schedule.

Separate observation, work and reopening

Scroll sideways to read all columns. Keyboard: focus the table and use the arrow keys.

Separate observation, work and reopening
Record stageWhat belongs in the recordWhat it does not establish
ObservationLocation, date, visible condition, conditions of observation and supporting referencesCause, concealed condition or approval to continue use
Follow-upReviewer or responsible role, question, requested evidence and next actionThat a response was completed merely because it was assigned
Work recordedWhat was done, where, by whom and the work-record referenceThat work meets the accepted design or resolves every open item
Reopening decision recordedAuthorized decision reference, affected area, conditions and responsible roleA new permission created by selecting an option in this worksheet

Keep access decisions with the owner’s authorized process. If a condition may affect public use, follow that process promptly; do not wait for a complete worksheet to notify the responsible person. Record restrictions and the scope of any decision precisely. A decision about one board or one bay should not be silently expanded to the entire route.

A work order and a reopening record answer different questions. The first describes an intervention; the second identifies the decision about use after the intervention. Record any remaining conditions, future check or deferred work. A green photograph, a completed checklist or a downloaded file is not an independent acceptance record.

Worked example: debris returns at a planting edge

Fictional example: the owner labels an observation point P-03 / planting edge B. On the first visit, an observer records wet leaves collected against the curb, identifies two photographs and refers the observation to the operations lead. No material defect or slip rating is asserted.

Scroll sideways to read all columns. Keyboard: focus the table and use the arrow keys.

Worked example: debris returns at a planting edge
EntryEvidence and actionUnresolved point
1 — ObservationWet leaf residue recorded at P-03 / planting edge B; overview and close-up references retainedOperations review and response not yet recorded
2 — Work recordedCleaning team records debris removal and the work-order reference; follow-up photo taken after dryingA dry photograph does not show behavior during the next wet period
3 — Follow-upDebris observed again after rainfall; same viewpoint and location usedOwner reviews recurring accumulation and the maintenance response
4 — Decision recordedResponsible role and the owner’s actual decision document are identifiedAny conditions or required follow-up remain attached to that decision

The benefit is continuity. Recurrence stays visible instead of being hidden by a succession of separate “cleaned” notes. The example does not tell an owner to reopen the route or prescribe a drainage alteration. Changes to the surface, planting, drainage or connection need the appropriate project review.

Keep the export with the records it references

The location log below is a working draft for one observation point. Add dated observations and actions in the order you record them. Enter source identifiers rather than uploading documents. Empty supporting fields remain visible as missing, and entries remain user-supplied even when every field is filled.

Export before leaving the page. The JSON file contains the entries and missing-field list, but it does not contain the photographs, reports or work orders. Store those originals in the owner’s record system and keep identifiers consistent. Retain earlier downloaded revisions where they are part of the project record; undoing a draft entry here does not change a file already downloaded.

For an observation involving replacement, continue to the replacement-staging guide. For recurring wet conditions, use the wet-condition review. At handover, place the inspection responsibilities and record location in the closeout package.

One location / successive observations

Build a location log

Keep the original observation beside later work and decisions. Entries stay only in this page until you export them; reloading clears the draft. Use document identifiers rather than confidential material. No files are uploaded.

Required: location, date and observation. Empty supporting fields remain listed as missing in the export. A reopening entry needs the actual decision reference and authorized role; selecting that entry type is not an approval.

0 of 24 entries recorded

No observation recorded yet.

0 entries have missing supporting fields. Entries are draft notes, not a verified audit trail.

A public-route planning scenario

Concept example: a transition receives a recurring debris note. The owner links observations across inspections and reviews the maintenance response rather than deleting each old entry.

Use the result

Keep the completed review with the relevant project record. Assign unresolved items before relying on a conclusion. If the material, condition or document changes, revisit the affected questions.

Boardwalk planner
Technical references

General background for the subject. Project worksheets and fictional situations are original review aids, not official agency forms.

Access Board: floor and ground surfaces

Access Board: federal outdoor developed areas

Federal procurement reference: FAR 11.104