Organize the packet first, interpret it second
A clean information packet is not the same thing as an operating decision. One is recordkeeping. The other belongs with current official sources, onboard judgment, navigation rules, and, when needed, professional instruction.
For a Pacific Northwest owner-operator, fog prep often gets tangled because people mix product types, compare screenshots with no labels, or rely on memory of what a page “said earlier.” That is avoidable. Before anyone talks about timing, comfort, or workload, assemble the official records you are actually looking at and label them so another person can identify them without guessing.
That matters during weather-window planning, but also for ordinary passage prep. A compact, well-labeled packet helps when several people are involved, when an older download is still sitting in the same folder as a current page, or when questions come up during a longer planning day that also includes navigation and communications redundancy, provisioning, and checks of pilothouse windshield wipers, washers, and demisters. The goal here is simple: know what each record is, where it came from, when it was displayed, what area it says it covers, and what is still unclear.
Forecasts, observations, and notices are different records
Do not treat forecasts, observations, and notices as interchangeable. They answer different questions and are created as different kinds of records.
Forecasts
A forecast is a forward-looking official product. It is an agency statement about expected conditions for the source’s own stated coverage area and time frame. When you save one, keep the exact official product name and the displayed issue time exactly as shown on the source page or document.
Observations
An observation is a report of measured or reported conditions associated with the observation source at the displayed observation time. It is not a forecast, and it should not be labeled as one in your packet. Save the page or record with the observation time exactly as displayed and the source’s own stated coverage or station description as presented.
Notices
A notice is neither a forecast nor an observation. It is an official notice record. Treat it as its own category, save it under its official product name, and keep the displayed time or publication identifier that the source provides. Do not summarize it into a weather note or tuck it into a forecast folder just because it was gathered during the same planning session.
That separation sounds basic, but it prevents a lot of confusion. A page titled one way, captured at one time, and covering one stated area should keep that identity all the way through your prep notes.
U.S. official source families to gather
For the U.S. side of a Pacific Northwest passage packet, the main official families are straightforward: NOAA/National Weather Service marine forecasts, NOAA/NDBC observation pages, and U.S. Coast Guard Local Notices to Mariners. You do not need to force them into one format. You do need to label each record consistently.
NOAA/National Weather Service marine forecasts
Use the official NOAA/National Weather Service marine forecast products relevant to your planning area. When you save one, capture five things without paraphrasing them away:
- Exact official product name
- Displayed issue time
- Source’s own stated coverage description
- Your retrieval time
- A note if any needed displayed field is absent or unclear
That last item matters more than people think. If the page does not clearly show a field you expected to see, write that down instead of filling the gap from memory.
Practical example: if you save a screenshot or PDF, the file itself may not preserve the source header cleanly. In that case, your source log should carry the exact product name and displayed issue time so the saved copy still has context.
NOAA/NDBC observation pages
NOAA/NDBC observation pages belong in a separate observations section of the packet. Their job in your file is not to “confirm” a forecast. Their job is to preserve what official observation record you actually reviewed, at what displayed observation time, from what stated source description.
Keep the observation page with:
– The exact page or product name as shown
– The displayed observation time
– The source’s own stated coverage or source description
– Your retrieval time
– An unresolved-gap note if something you expected on the page is absent or not clearly labeled
Many packet errors happen when an observation screenshot gets renamed to something generic like “current marine weather.” That title throws away the distinction between record types. Keep the official identity visible.
U.S. Coast Guard Local Notices to Mariners
Local Notices to Mariners are their own record family. Save them separately from weather material and log them the same disciplined way:
– Exact official product name
– Displayed issue or publication time, or equivalent identifying display if shown
– Source’s own stated coverage description
– Your retrieval time
– An unresolved-gap note if a needed displayed field is missing or unclear
The point is not to interpret the notice in your packet. The point is to preserve what official notice record was actually gathered and how it identified itself at the time you pulled it.
Canadian official source families to gather
For passages that involve Canadian official products in your prep, the source families to gather are Environment and Climate Change Canada marine forecasts and warnings, and Canadian Coast Guard Navigational Warnings. Keep them in their own sections and label them the same way you label U.S. products.
Environment and Climate Change Canada marine forecasts and warnings
Environment and Climate Change Canada marine forecasts and warnings are forecast-family records. Save the exact official product name as shown, the displayed issue time, the source’s own stated coverage description, your retrieval time, and an unresolved-gap note if a needed displayed field is absent or unclear.
Do not rename the product into your own shorthand if that shorthand drops the official title. Your shorthand can live in a separate note, but the saved record and source log should preserve the official identity.
If you are collecting more than one Canadian forecast-family product in the same prep session, consistent naming matters. The value is not in making the packet pretty. The value is in letting the responsible operator tell, at a glance, which official product was gathered, when it said it was issued, and what area it said it covered.
Canadian Coast Guard Navigational Warnings
Canadian Coast Guard Navigational Warnings belong in the notices section of the packet. Treat them as official notice records, not as “extra weather info” and not as an appendix nobody opens.
Log them with the same six data points used across the whole packet:
– Source or product name
– Displayed time
– Stated coverage
– Retrieval time
– Saved-file identity
– Unresolved-gap note
That uniformity is what makes a mixed U.S./Canada packet usable, especially if planning extends into evening prep, handoff between crew, or a later review before night running.
A compact source log that works under real prep conditions
Keep the source log short enough that you will actually maintain it. One line per saved record is enough.
Use only these fields:
| Field | What to record |
|---|---|
| Source/product name | The exact official name shown on the page or document |
| Displayed time | The issue time, observation time, or displayed publication time exactly as shown |
| Stated coverage | The source’s own wording for the area or source description |
| Retrieval time | When you pulled or saved the record |
| Saved-file identity | The filename, screenshot label, print name, or folder reference you used |
| Unresolved-gap note | A brief note when a needed displayed field was absent, ambiguous, or not clearly visible |
That is enough structure to answer basic packet questions later:
– What official record is this?
– When did the source say it was issued or observed?
– What did the source say it covered?
– When did we retrieve it?
– Which saved file matches the log entry?
– What was unclear at the time?
Keep the wording literal
Copy titles and displayed times exactly as shown. Avoid “cleaning up” the wording into your own version. Literal entries reduce argument and memory drift.
Make saved-file identity obvious
Your saved-file identity can be simple. It just needs to tie the record to the log line without guesswork. A filename like NWS-marine-forecast_2026-09-07-0815-saved.pdf is fine if it is consistent inside your own folder system. The exact format matters less than the ability to match file and log entry quickly.
Write unresolved gaps down immediately
If a field is absent or unclear, note that when you save the record. Do not wait. “Coverage wording not visible on saved image” or “displayed time not clear on print copy” is useful. Silence is not.
If the question matters to your prep and you cannot resolve it from the source display you have, carry that forward as an open item for the responsible operator or the appropriate official authority.
Separate current records from older screenshots and downloads
Current material and archive copies should never sit in one unlabeled pile. Separate them physically or digitally.
A simple folder structure works:
– Current official packet
– Older saved records
– Questions to resolve
If you prefer paper, use the same separation with clips or tabs. The method is not the point. The distinction is.
Mark older material as older material
An older screenshot can still be useful for comparison or recordkeeping, but it should never masquerade as current. Add a visible label such as “saved earlier” or “older record retained for reference” in the filename, cover sheet, or packet index.
Preserve uncertainty instead of editing it away
Do not patch an incomplete saved record by guessing what it must have shown. If the displayed time is cut off in the screenshot, your log should say so. If the source’s coverage wording is not visible on a printout, note that. A packet with clearly labeled uncertainty is more useful than a neat packet that quietly invents certainty.
Avoid mixed bundles
One common failure point is a single PDF bundle or photo album containing current forecast pages, old observation screenshots, and notices captured on different days, all without a log. That format looks efficient until someone tries to determine what is current and what is not. Keep current records together and older records clearly separate.
Assemble the packet, then surface the open questions
The practical task is straightforward. Gather the official-source packet from the record families you actually need: NOAA/National Weather Service marine forecasts, NOAA/NDBC observation pages, U.S. Coast Guard Local Notices to Mariners, Environment and Climate Change Canada marine forecasts and warnings, and Canadian Coast Guard Navigational Warnings. Save each record with its exact official name, displayed time, stated coverage description, retrieval time, saved-file identity, and any unresolved-gap note.
Then stop and look for blanks. If a field is absent, unclear, or inconsistent in your saved material, label that uncertainty and bring the question to the responsible operator or the appropriate official authority. That handoff is part of good preparation.
This article does not replace current official sources, onboard judgment, navigation rules, or professional instruction. What it can do is help you build a packet that is organized, traceable, and usable when preparation gets busy.
Sources
- NOAA National Weather Service marine information
- NOAA National Data Buoy Center
- U.S. Coast Guard Local Notices to Mariners
- Environment and Climate Change Canada marine forecasts
- Canadian Coast Guard Navigational Warnings
Cruising plans
Explore North Pacific Yachts
Browse our current models online. When you are ready, get in touch with us to talk through your cruising ideas.