Supplier Delivery Schedule: Coordinate Jobsite Receiving Windows

1. Define an arrival window, not just a dispatch date

“Tuesday” may not be enough for the site receiver. State whether the date means supplier dispatch, gate arrival or a receiving window coordinated with the site. Record the date, times and local time zone with the exact destination and PO reference. The material need-by time is another planning input, not a substitute for the arrival window.

Oracle describes a PO schedule through quantity, destination and required date, separating different destinations and dates. For jobsite coordination, add the receiver and verified receiving conditions to the worksheet. This is a proposed team worksheet, not a reproduction of Oracle screens or a promise of automated scheduling in Novapro.

Further reading: Oracle Procurement: quantity, destination and schedule date

2. Check receiving conditions across suppliers

Bring the relevant shipments for one site and day into a shared list. Each row should retain the supplier, PO and line, item and unit, quantity, destination, requested window, vendor response, receiver and coordination owner. Mark unconfirmed details as pending. An empty cell in a planner is not evidence that a vendor or the site is available.

Ask the responsible site coordinator to verify receiving hours, access coordination, receiver availability, material space and prerequisites. When deliveries share a receiving team or area, review them together. Window durations and coordination gaps depend on the actual shipments and local process; one fixed duration does not fit every jobsite.

3. Example: correct quantities, conflicting windows

This fictional example involves three different POs and shipments not yet received. For the example only, the site has planned one receiving team that can handle one delivery per window. Vendor A is planned for ⁦09:00–10:00⁩, B for ⁦09:30–10:30⁩ and C for ⁦11:00–12:00⁩. Each proposes the requested quantity, but A and B overlap for 30 minutes.

Moving B alone to ⁦10:30–11:30⁩ creates a new conflict with C. If the example’s team assumes a 30-minute coordination gap, it can review a proposed sequence: A ⁦09:00–10:00⁩, B ⁦10:30–11:30⁩ and C ⁦12:00–13:00⁩. This is an option for review, not an approved schedule. Both B and C and the site receiver must confirm suitability; real durations and gaps require project-specific verification.

4. Share a coordinated revision and distinguish proposals

After a proposed change, recheck every affected window, destination and need-by requirement. Record the schedule version, update time, proposer, approver and outstanding responses. A change affecting PO terms also follows the existing PO approval process. Sending a new window does not establish that it was accepted.

Suggested handoff record: “Schedule ___ revision ___, site and time zone ___. PO and line ___; quantity and unit ___. Previous window ___; proposed window ___. Vendor and receiver to confirm by ___. Unverified receiving condition ___; owner ___; review time ___.” Until confirmation, label the option pending and retain the current accepted source.

5. Record actual receipt without turning a plan into a fact

On delivery day, keep the coordinated window, reported arrival time, receiver’s check and receiving document distinct. When a new arrival time is reported, check the effect on other deliveries. For a partial receipt, link the received quantity to the PO and retain the remainder for follow-up coordination. A dispatch message alone does not make the entire schedule delivered.

Microsoft describes splitting an ordered quantity into delivery lines and recording receipt afterward. That implementation belongs to Dynamics; this worksheet is a manual coordination aid. Novapro brings orders, suppliers and documents into project context. Explore your order-to-receipt trail in a demo without assuming automatic truck booking, window approval or update messages.

Further reading: Microsoft Learn: purchase-order delivery schedules and later receipt

Frequently asked questions