A clear aerial view of the lower Willamette River can show a shoreline, vessel, dock, construction footprint, material barge, riverbank, or changing patch of water. It cannot show contaminant concentration, remedy approval, sampling sufficiency, design percentage, source control, public-health risk, responsible-party status, or cleanup completion. That is the central problem for Portland Harbor Superfund aerial documentation: the camera records a place, while the cleanup record determines what that place means.

Portland Harbor is not moving through one uniform phase. EPA’s June 2026 update divides the river into project areas with different working parties and different remedial-design milestones. Oregon agencies separately address upland sources, state-owned waterways, and authorizations. The City, Tribes, community organizations, property owners, businesses, and affected residents hold other necessary knowledge and responsibilities. One frame can cross several of those boundaries without displaying any of them.

This guide gives public agencies, environmental teams, performing parties, community communicators, property owners, and production partners a River Mile Evidence Ledger. It is not a sampling plan, engineering deliverable, survey, legal conclusion, health advisory, regulatory filing, remedy approval, or flight authorization. It keeps the view, project area, cleanup phase, visible fact, official status, community-impact commitment, operating authority, allowed claim, and derivative history in one traceable row. The practical rule is simple: coordinates prove where a camera was, not what stage the cleanup reached.

One river frame can cross several regulatory records

The current EPA Portland Harbor site profile describes an in-river and upland Superfund site shaped by decades of industrial use. The City’s Portland Harbor overview defines the site as roughly ten miles of the lower Willamette River between the Broadway Bridge and the southern tip of Sauvie Island. Those descriptions establish the broad geography. They do not turn the entire reach into one project area, owner, remedy, schedule, or production permission.

A useful documentation brief starts with the exact river mile, bank, project-area name, view direction, capture date, and question. “Portland Harbor” is too broad for a claim-bearing image. “Looking north from a verified position toward the River Mile 11 East project area on this date” is a record that an official project owner can evaluate.

Start with river mile and project area

EPA’s current June 2026 project-area and remedial-design fact sheet maps River Mile 2 East, River Mile 3.5 East, Terminal 4, Swan Island Basin, Willamette Cove, Cathedral Park, River Mile 7 West, Willbridge Cove, River Mile 9 West, River Mile 10 East and West, River Mile 11 East, B1a, Gasco, US Moorings, the Navigation Channel, and unassigned areas. Each row has a distinct status, party set, and EPA project contact.

Use that official map to identify the question, not to fabricate a camera boundary. Record the project-area name exactly, then verify the proposed operating point and visible footprint with current assignment sources. A wide oblique frame may show more than one project area, upland property, navigation feature, or unrelated industrial operation. If the story concerns one area, the caption should not silently generalize the whole frame.

The Ledger should also record whether the image is a project-area overview, a bounded visible condition, construction context, access context, community-impact context, or a neutral location reference. Those purposes require different evidence and different approvals.

Separate in-river, riverbank, and upland work

The Oregon Department of Environmental Quality’s current Portland Harbor summary distinguishes EPA’s lead role for contaminated sediment in the riverbed from DEQ’s work with property owners on upland sites along the riverbank. Oregon’s Department of State Lands separately describes its role in authorizing certain sampling, remedial, and restoration activity on state-owned waterways.

That division is crucial for visual claims. An image of a bank can contain the edge of an in-water remedy, a shoreline-design question, an upland source-control site, private property, public infrastructure, and state-owned submerged or submersible land. The view does not reveal which agency owns which decision.

Create separate Ledger columns for:

  1. in-river project area and EPA status owner;
  2. riverbank or shoreline work and its approved design source;
  3. upland property and DEQ source-control status;
  4. state-waterway authorization, if applicable;
  5. property, access, navigation, construction, and publication owners.

If a project uses “cleanup area” as a single label, require a source owner to define what the label includes. Do not ask the pilot, photographer, editor, or map designer to infer the regulatory geography.

Aerial visibility cannot prove cleanup phase

EPA’s June 2026 fact sheet states that all acres designated for active in-water remediation are in remedial design. It then reports different milestones across project areas: some designs are at 30 percent, 60 percent, 90 percent, or under review; other areas are completing sampling, preliminary-design evaluation, sufficiency assessment, or basis-of-design work. Those percentages describe a controlled regulatory and engineering process. They are not percentages of visible cleanup, construction completion, or river recovery.

Design is not remedial action

EPA’s current remedial design and remedial action guidance defines remedial design as the phase when technical specifications for the selected remedy are developed. Remedial action follows as the construction or implementation phase. A design submittal, review, or percentage therefore should not be illustrated with a generic construction image that implies implementation has started.

Design percentages belong to official project records

If the communications piece reports a 30, 60, 90, 95, or 100 percent design milestone, attach the exact official source, project area, document date, reviewing authority, and approved wording. Do not calculate a percentage from photographs. Do not treat a later image date as proof that the design advanced.

The Ledger needs a status as of field and an expiration trigger. EPA’s update shows that statuses can differ by area and change as sampling, reports, design packages, and reviews advance. A graphic generated for one public meeting should not become an undated evergreen status map.

Construction activity needs its own verified phase

A vessel, crane, excavator, truck, boom, floating plant, stockpile, survey boat, or crew may support sampling, investigation, maintenance, ordinary industrial work, navigation, design data collection, or remedial action. The frame alone does not identify the phase.

Before labeling activity as cleanup construction, record the project area, contract or work-plan owner, activity description, schedule, approved public notice, field verification, and responsible communications contact. If those facts are unavailable, describe only the bounded visible activity or use a neutral map. “Equipment was visible” is safer than “cleanup is underway” when the official phase is unresolved.

Different remedies can look similar—or invisible

The City’s current Willamette Cove cleanup page describes a proposed combination of dredging, capping, and riverbank excavation. EPA’s site records also distinguish enhanced natural recovery and monitored natural recovery. Each method has different design, implementation, monitoring, and long-term implications.

An ordinary image cannot prove which remedy is below the surface. Water color does not establish contamination, treatment, turbidity compliance, cap performance, sediment quality, habitat outcome, or safe consumption. A calm reach is not evidence that no work is occurring; a visibly active reach is not evidence that the remedy is complete.

On the Ledger, identify the remedy term only when an official source assigns it to the area. Keep the visual description in a separate field. If the audience needs to understand an underwater cross-section, use an approved diagram or official map rather than forcing an aerial photograph to explain hidden conditions.

Completion requires an official decision record

“Done” can mean design submitted, design approved, field construction mobilized, a construction element installed, remedial action complete, monitoring underway, an institutional control in place, source control completed, or a formal regulatory milestone. Those states are not interchangeable.

Create a completion vocabulary before drafting the headline. For each term, record who can authorize it and which document establishes it. A field team can confirm that planned imagery was captured. It cannot declare that EPA, DEQ, DSL, a property owner, or another authority has accepted an environmental milestone.

Avoid before-and-after layouts that imply outcome solely through appearance. The “after” frame still needs an official status record, matched capture conditions, known processing, and a statement of what the comparison cannot show. If the official milestone is pending, the public asset remains labeled with the verified current phase.

Build the River Mile Evidence Ledger

The Ledger is a structured record for every claim-bearing view. It can live in a database, spreadsheet, or content system, but each row must remain readable by regulators, environmental professionals, community reviewers, property and operations teams, the camera crew, editors, accessibility reviewers, and future archivists.

One master file may need several rows. A project-area status update, community meeting slide, website hero, construction notice, social crop, internal design review, and public archive can use the same pixels while making different claims. The Ledger follows the use, not just the file.

Define the public decision, place, time, and asset class

Begin with the audience decision. Is the reader trying to understand project-area boundaries, current design status, planned field activity, access changes, community-impact controls, public-comment timing, or a completed milestone? The image should serve that decision.

Record:

  • project area, river mile, bank, and visible footprint;
  • exact capture date, time, viewpoint, camera, lens, altitude if applicable, and processing;
  • asset class: cinematic context, repeat photograph, construction record, survey-controlled product, map, owner-supplied record, scientific image, or interpretive graphic;
  • public question, intended claim, intended channel, audience, term, and partners;
  • property, project, regulatory, scientific, community, capture, and publication owners.

If the asset class is unknown, keep it held. A stabilized video frame does not become a survey because it looks precise. A map overlay does not become accurate because it aligns visually with a shoreline.

Attach every claim to an evidence owner

Use four evidence states: verified, not applicable, unresolved, or rejected. “Looks clean,” “appears active,” “probably the project area,” and “client supplied” are not evidence states. They describe impressions or provenance gaps.

Visible facts stay bounded to the frame

A visible-fact row can state that defined equipment, a shoreline feature, a vessel, an access route, a material area, or a water-surface condition was visible from a defined position at a defined time. It should also state limitations: occlusion, distance, vegetation, weather, glare, tide or river stage, traffic, camera resolution, crop, and processing.

Do not derive contaminant presence, concentration, exposure, remedy performance, water quality, sediment condition, habitat health, fish safety, ownership, regulatory compliance, or causation from the image. Those questions require their own official, scientific, engineering, health, or legal sources.

Official status keeps its document and scope

An official-status row records the agency or performing-party source, exact document, project area, section or page, publication date, approved paraphrase, reviewer, and refresh date. It also records what the statement does not mean. “60% design in progress” does not mean 60 percent of construction is complete. “Sampling complete” does not mean every design or remedy decision is final.

When a graphic combines several project areas, preserve each area’s source independently. Do not average design percentages or arrange areas into an invented league table. The status belongs to the official process for that area.

Record access, navigation, people, and exact-location flight review

The lower Willamette is a working river bordered by industrial sites, public areas, neighborhoods, infrastructure, and sensitive locations. The operating brief must identify the exact property, water access, navigation coordination, security, work zone, crew footprint, equipment, people, vehicles, weather, emergency plan, takeoff and landing point, and no-flight substitute.

Use the existing Portland location-control map to route parks, bridges, river, Port property, public right-of-way, property, and aviation questions. Then complete assignment-specific reviews with the responsible owners. The FAA’s current Part 107 airspace authorization guidance handles controlled-airspace authorization routes; it does not grant property access, river-use approval, regulator acceptance, environmental-claim approval, participant releases, or construction control.

For each proposed aerial, record exact coordinates, airspace, altitude, date, time, people, vessels, moving vehicles, structures, cranes, heliports or airports, emergency activity, weather, visibility, lost-link plan, observer plan, and operating authority. If any gate fails, keep the view held and use a ground image, licensed stock, official map, owner-supplied record, or text-led alternative.

Capture community impacts as a separate workstream

The current EPA Community Impacts Mitigation Plan is a living document for remedial design, remedial action, and community understanding. It separates potential impacts and mitigation topics including noise, light, water quality, navigation safety, recreation, resident-fish consumption, jobs, wildlife, cultural and historic resources, riverfront access for housing-insecure community members, traffic, parking, air quality, dust, volatilization, diesel emissions, odor, and ambient air.

That structure is a warning against one “community impact” montage. Each topic needs a defined requirement or recommendation, measurement owner, geography, time window, audience, and communication path. An aerial master can provide spatial context, but it cannot measure most of those impacts.

Plan noise, light, dust, traffic, and navigation separately

A frame can show lights, trucks, vessels, work areas, or traffic. It cannot establish sound level, particulate concentration, emission source, navigation compliance, odor, duration, frequency, threshold exceedance, or mitigation effectiveness. Those need approved monitoring, logs, plans, or agency records.

Build a community-impact companion row for each public claim. Record the applicable plan or work-plan section, requirement or recommendation, monitoring method, unit, location, time window, responsible party, reporting channel, exceedance or complaint process, public contact, and correction owner. Link the visual only when it adds geographic understanding.

Do not present a visually quiet moment as proof that noise controls succeeded, or a clear sky as proof of air quality. Do not present an empty navigation channel as proof of access. The image is context; the monitored record owns the performance statement.

Keep fish, water, habitat, and health language with official owners

The City and Oregon sources identify resident-fish consumption as a primary long-term health concern and link to current public-health advisories. Aerial imagery cannot update, narrow, replace, or contradict those advisories. Water that looks clear is not a health conclusion.

Any page that mentions fish consumption, shellfish, swimming, exposure, habitat, water quality, or human health needs the current responsible public-health or regulatory source, exact retrieval date, approved wording, audience and language review, accessibility, and refresh trigger. Avoid turning a remediation story into unsupported reassurance or alarm.

For habitat or riverbank claims, record whether the statement comes from an approved design, construction-quality record, ecological monitoring result, or general visual description. “A gentler slope is proposed” and “the habitat has recovered” are different claim classes.

Include Tribes, affected communities, workers, and river users

The City’s current records identify the historical, natural, and cultural significance of Portland Harbor to Tribal Nations and diverse communities. They also describe disproportionate impacts involving cultural practices, fish consumption, and housed and unhoused residents near the site. The 2026 CIMP states that its development included input from Tribes, communities, agencies, businesses, and remedial-design parties.

The production should not treat that participation as decorative context. Record which owner can approve cultural or community language, which people may be filmed, how consent and privacy are handled, what areas or practices are sensitive, what accessibility and language needs apply, and how a participant can correct or withdraw an attributed statement.

Workers, residents, anglers, river users, and people experiencing homelessness are not generic scale figures. If identifiable people are not necessary, exclude them or use an approved clean pass. If they are necessary to the story, build an ethical participant plan with the responsible community and project owners.

Portland Harbor work depends on sampling, laboratory analysis, maps, survey, engineering, remedial-design deliverables, approvals, monitoring, construction quality control, and long-term records. A media workflow should preserve those distinctions rather than turning every visual into undifferentiated “drone data.”

Keep sampling and measurement outside ordinary imagery

An ordinary aerial photograph cannot locate subsurface contamination, replace a sediment sample, establish a laboratory result, certify bathymetry, prove cap thickness, measure turbidity, determine river stage, verify a property boundary, or confirm regulatory compliance. If a project uses a measured sensor or survey workflow, record the method, equipment, calibration, control, accuracy, responsible professional, quality plan, and approved purpose.

The Oregon Department of State Lands Portland Harbor page shows why authorization and method matter: it describes state oversight and authorizations for activities such as sediment sampling and remedial or restoration work. A camera assignment does not inherit those permissions.

Give every technical product a product class and lineage. Preserve raw-source identifiers, processing steps, coordinate reference, units, control, quality review, version, responsible professional, access tier, approved use, retention, and replacement relationship. If those records are absent, label the asset as visual context rather than technical evidence.

Build a derivative and correction manifest

Every website image, report figure, presentation crop, social tile, video edit, public-meeting board, press file, archive master, and partner copy needs a manifest row. Record the source asset, project area, claim, caption, alt text, crop, overlay, channel, audience, partner, term, expiration, owner, approval date, and correction route.

A crop can change meaning. Removing the opposite bank may make a project area appear isolated. Tightening around equipment may turn neutral river context into an implied cleanup activity. Adding a label may imply a boundary the image cannot prove. Review the derivative, not only the master.

When EPA, DEQ, DSL, the City, a performing party, property owner, community owner, or health authority updates a source, the manifest identifies every affected derivative. Preserve the historical record when required, but stop serving an expired public status as current.

Publish a narrow, accountable cleanup story

The strongest public update does not promise to explain the entire harbor in one image. It answers one audience question about one project area or site-wide program element, using one current official status and one clearly bounded visual role.

Separate progress, status, activity, and outcome

Use distinct labels:

  • visible activity: what the image shows at a time and place;
  • official status: what a current responsible source says about the phase;
  • process progress: which controlled deliverable or review milestone changed;
  • remedial action: verified construction or implementation under the approved process;
  • outcome: a result supported by the appropriate monitoring, acceptance, or official decision.

Do not move from one label to another because the copy needs a stronger verb. If the official update says a design is in progress, report that. If the image shows a barge but its role is unverified, describe the river context or omit the frame. Accuracy is more useful than artificial momentum.

The existing Portland green-street visual handoff demonstrates how to separate water behavior from crew access, while the Portland repeatable-record specification explains repeatable capture around riverfront and rain-season projects. The Superfund Ledger adds regulatory phase, scientific evidence, community impact, and correction ownership; it does not replace those workflows.

Pilot one project area, one claim, and one version family

Choose one project area and one public question. Complete the Ledger before capture. Verify the project-area source, official phase, property and access, community-impact context, intended claim, exact operating point, aviation path, participants, alternatives, derivatives, expiration, and correction owner.

Then create one master and its planned ratios. Ask the official status owner whether the text matches the current record. Ask the property and operations owners whether the view and activity are correctly identified. Ask the community and accessibility reviewers whether the presentation is accurate and usable. Keep every unresolved version held.

For a scoped Portland assignment, bring the project area, river mile, exact subject and viewpoint, audience question, proposed claim, official status source, property and regulator contacts, community-impact topic, asset class, desired derivatives, operating inputs, and ground or no-flight alternatives to the Portland Drone Footage service overview. The Portland production-budget guide can separate access, crew, weather, locations, approvals, deliverables, and handoff costs. When the River Mile Evidence Ledger is complete, request a Portland project scope without treating that request as regulator approval, property permission, scientific validation, community acceptance, health guidance, remedy acceptance, or flight authorization.