ATDNSHINC and Laytime: Calendar-Day Service Windows for Procurement

ATDNSHINC Is a Clock Assumption, Not a Complete Clause

The SSDER glossary expands ATDNSHINC as Any Time, Daytime, Night, Sundays and Holidays Included. In procurement, that phrase signals a broad calendar-day treatment, but it does not answer when the clock starts, what notice makes time count, or which events suspend it. Those details must be written into the service or charter agreement.

A buyer should record the port, berth, cargo, operation, local time zone and governing contract before comparing bids. A carrier that prices all calendar days may still exclude weather, authority delay, shifting, strike or a failure to tender a valid notice. The commercial risk sits in the definitions around the acronym.

Define the Laytime Event and Notice Evidence

A usable clause identifies the event that starts the clock: notice of readiness, truck arrival, all-fast at berth, cargo availability, document acceptance or another agreed milestone. It also defines the notice channel, recipient, timestamp, acceptance and what happens if the notice is sent outside working hours.

Require a notice register with the booking, vessel or equipment identifier, berth, date, time zone, sender, recipient, readiness evidence and acknowledgement. A spreadsheet that contains only a start and end date cannot distinguish a valid laytime event from an informal forecast.

Separate Included Time from Exclusions

BIMCO contract structures show why time, off-hire, delay and indemnity language must be read together. Procurement should list included calendar periods and excluded causes separately, then state the priority if two clauses conflict. Sunday or holiday inclusion is not the same as accepting time caused by a port closure or an unsafe berth.

Ask bidders to price the same scenarios: ready before the window, late cargo, weekend handling, weather interruption, equipment failure, customs hold and terminal congestion. The comparison should show base freight, time allowance, waiting rate, demurrage or detention, overtime and any cap.

Measure Clock Accuracy and Commercial Impact

Track first-notice acceptance, laytime variance, waiting hours, disputed hours, approved hours, demurrage value, weekend share and root cause by carrier, terminal, lane and supplier. A low dispute rate can mean a good process, or it can mean that the buyer is accepting unverified invoices.

Review exceptions with logistics, procurement, finance and the terminal or carrier. If a supplier regularly misses the cargo-ready milestone, changing the laytime clause will not solve the cause; the sourcing plan, packing schedule or booking lead time needs attention.

Worked Example: Holiday Hours Misread

A buyer accepts a quotation marked ATDNSHINC for a Saturday vessel operation. The purchase order does not specify whether the terminal is open on the holiday Monday, and the carrier later invoices waiting time from the original notice through the next available shift. Operations disputes the invoice, but there is no shared event record.

The corrected award defines the local holiday calendar, terminal operating window, readiness evidence, notice recipient, included time, excluded closure and rate. The buyer prices the expected weekend and holiday scenarios before award and requires a signed time sheet for each exception.

Metrics and Governance

For ATDNSHINC laytime procurement controls, measure both service and evidence quality. Useful indicators include first-pass acceptance, exception rate, response time, unplanned cost, document completeness, damage or discrepancy rate, and the percentage of shipments that follow the approved process. A dashboard should distinguish a supplier failure from a carrier, terminal, broker or internal master-data failure.

Review the metric trend with procurement, logistics, finance, quality and the responsible specialist. Use a monthly exception sample to test whether the control worked in a real transaction, not just whether a field was filled. Repeated exceptions should change the sourcing strategy, contract, lane design or supplier development plan.

Keep the control proportionate to risk. High-value, regulated, time-critical or safety-sensitive cargo needs stronger evidence and faster escalation than a routine shipment. Record the decision owner, approval date, source documents and follow-up action so the next buyer can understand the operating history.

Supplier and Carrier Questions

• Which ATDNSHINC or related glossary condition is assumed in your quotation, procedure or service description?
• Which party owns each data field, physical handoff, inspection, document and exception?
• What evidence will be available before release, loading, movement, receipt, invoice approval or claim?
• What changes require advance notice, requalification, a revised price or a new risk decision?
• How will the supplier report incidents, delays, mismatches and corrective actions, and within what response time?

Implementation Sequence

Implement the control in a small, representative lane first. Capture the baseline process, test the required data and evidence, run a real transaction, and review every exception with the people who performed the work. Do not declare the control effective only because a supplier signed a procedure.

After the first three shipments or operating cycles, update the purchase-order clause, work instruction, scorecard and training. Scale the control to other suppliers only when the evidence is repeatable and the owner can explain what happens when the normal path fails.

Common Mistakes to Avoid

• Treating ATDNSHINC as a self-executing legal rule.
• Using a date without a time zone, port, notice event or readiness condition.
• Counting weekends or holidays without checking terminal and supplier operating capability.
• Approving waiting or demurrage without gate, berth, notice and release evidence.
• Comparing freight bids without modelling the same delay and calendar scenarios.

Procurement Implementation Checklist

• Define ATDNSHINC, laytime, notice of readiness and the relevant port clock.
• State included periods, exclusions, free time, rates, caps and dispute deadlines.
• Link booking, berth, gate, cargo-ready and terminal records to one shipment ID.
• Price weekend, holiday, weather, congestion and document-delay scenarios.
• Require signed or system-generated time evidence before invoice approval.
• Review recurring exceptions in the carrier, terminal and supplier scorecards.

Frequently Asked Questions

Related Kurums Guides

• Freight Contracts and Parties
• Shipping Documents for Procurement
• Customs EDI and Entry Data
• Freight Network Design for Procurement
• Cargo Abandonment and Acquittance
• Advanced Charges and Pass-Through Freight

Standards and Authoritative Sources

• BIMCO — Contracts and charter-party resources
• BIMCO — Standard clauses
• FMC — Detention and demurrage billing practices
• FMC — Detention and demurrage overview

Glossary terms covered: ATDNSHINC, laytime, calendar days, notice, waiting time, demurrage, berth terms