How to read a notice of readiness when the vessel is still at anchor
A notice of readiness lands in the inbox the moment the master wants it to. The vessel might still be five miles out, swinging at anchor behind forty other hulls, waiting on a berth that hasn't existed in a week. What a charterer needs to know is whether the NOR was valid when it was tendered, and whether the clock started running from an anchorage that was never going to see a pilot that day.
What makes a NOR valid at anchorage
Most charter parties allow NOR to be tendered "whether in berth or not" (WIBON) or "whether in port or not" (WIPON), and a lot of voyage charters go further with "whether in free pratique or not" and "whether customs cleared or not." Those clauses exist because owners know congestion happens, and they want laytime running even if the vessel sits at anchor for days before a berth opens up.
Valid tender still carries conditions, though. The vessel has to be physically ready in all respects, holds clean, gear tested, documents in order, and it has to be within whatever limits the charter party defines as "the port," not loitering outside a designated anchorage that falls outside those limits. A NOR tendered from a safe-waters anchorage the charter party doesn't recognize as part of the port isn't a valid NOR, no matter what the agent's telex says. This is the fight that shows up in laytime disputes more than almost anything else: was the ship inside the port when it said it was ready.
Timing against the laycan matters too. A NOR tendered before the layday window opens, even from a valid anchorage, typically doesn't start the clock until the layday begins, unless the charter party says otherwise.
Reading the NOR against the actual queue
This is where the paperwork and the anchorage stop matching. An agent's telex reports the master's statement. It doesn't report how many vessels are ahead in the queue, how long the berth has been occupied, or whether the port is running three days behind on pilotage because of weather or a labor slowdown. A charterer reading a NOR in isolation sees a timestamp and a position. What that charterer needs to know is where the vessel sits in a queue that's been building for a week, because that's what decides whether the owner's demurrage claim holds up, and whether the congested-port clause in the charter party, if there is one, even gets triggered.
A congested-port or "time lost waiting for berth" clause typically counts laytime, or time on demurrage, from a valid NOR regardless of whether the vessel is at berth, provided the delay is due to port congestion rather than something within the owner's control. Proving that requires knowing the anchorage picture on the day the NOR was tendered, not just the agent's version of it. Port Congestion Watch builds a daily congestion series for the anchorage from repeat high-res passes, so the number of vessels waiting on any given day is a matter of record instead of a matter of whose telex you trust.
Before accepting or disputing a NOR, a charterer wants to check three things: was the vessel within the charter party's defined port limits, was it genuinely ready in all respects, and did the anchorage queue on that date actually support the owner's story about congestion. The first two come from the charter party wording and the ship's documents. The third comes from watching the anchorage itself over time, not from a single snapshot the agent happened to send.
If the queue count on the date of tender doesn't match what the telex implies, that gap is worth chasing before the laytime statement gets finalized, not after demurrage has already been paid out on it. Run your anchorage through a congestion series before the next NOR hits your desk.