Dock Scheduling: Appointments, Resources and Capacity
Match loading and unloading appointments to usable bay time, compatible equipment and shared teams, then manage changes without confusing booking with physical execution.

On this page · 11 sections
- 1What dock scheduling means—and where it stops
- 2Calculate capacity from time, compatibility and shared resources
- 3US dock-safety requirements and their scheduling implications
- 4Run the appointment lifecycle from request to closeout
- 5Design appointment records, resource calendars and event history
- 6Worked cases: usable time, shared labor and disrupted arrivals
- 7Connect systems and recover from late arrivals or outages
- 8Measure waiting, service reliability and constrained capacity
- 9Control booking errors and misleading schedule status
- 10Adapt the schedule to the load and manufacturing context
- 11Implement, test and review the scheduling process
How does Dock Appointment Scheduling apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What dock scheduling means—and where it stops
Dock scheduling is the planning and booking of loading or unloading appointments against available time, compatible bays and shared resources.
The practical decision is which load can be serviced during which window, with which resource commitments and prerequisites. A booking might reserve unloading capacity, a handling crew and suitable equipment, conditional on paperwork being ready. This is constraint-based scheduling, not simply an entry on a carrier calendar.
| Term | Main decision or event | Typical output | Boundary |
|---|---|---|---|
| Dock scheduling | When can the load be serviced? | Appointment and resource reservation | Plans capacity; does not move trailers |
| Door assignment | Which specific door will serve the load? | Load-to-door allocation | Selects a location, not the booking window |
| Gate check-in | Has the carrier arrived? | Arrival timestamp and identity record | Records arrival, not service start |
| Yard execution | Where should the trailer move or wait? | Move instruction and movement status | Coordinates physical positioning |
| Receiving or shipping execution | What goods were handled? | Receipt or shipment confirmation | Performs and records material handling |
An appointment can reserve capacity within a compatible bay group before the final door is selected. The group identifies acceptable bays; door assignment later chooses a specific member. Trailer positioning then belongs to yard management, rather than appointment booking.
- Carrier arrival window: the agreed period for presenting at the designated check-in point.
- Planned service interval: the scheduled start-to-finish period for loading or unloading.
- Bay occupancy interval: the period during which the bay is unavailable to another load, including positioning, setup and clearance where applicable.
These are distinct planning terms: arrival can precede service, and bay occupancy can extend beyond handling time. An appointment therefore does not, by itself, confirm arrival, door availability or completed work.
02Calculate capacity from time, compatibility and shared resources
Dock capacity is the set of appointments that can fit both bay time and the resources needed to serve them. As an operational planning practice, finite-capacity scheduling tests those constraints together; counting doors alone does not establish bookable capacity.
Build usable time, not just opening hours
Start each bay calendar with operating periods, then remove maintenance closures and breaks that actually prevent service. Account for preparation and turnover either as calendar blocks or within job occupancy, without deducting the same time twice. Keep the resulting contiguous available windows separate.
Planned occupancy runs from the first activity that blocks the bay until it becomes available again. Include preparation, vehicle positioning, handling and clearance where applicable. Overlapping activities contribute their combined elapsed interval, not the sum of their individual durations. Unloading can stop while a trailer, uncleared pallets or unfinished clearance still makes the bay unavailable.
Time-only capacity = sum, across usable bay windows, of floor(contiguous available minutes / planned occupancy minutes).
This assumes identical jobs with positive occupancy durations that cannot cross blocked intervals. Floor means rounding down within each window before summing. The result is an upper bound before compatibility and shared-resource checks—not a booking commitment.
Filter by compatibility
Use a compatibility matrix relating load and vehicle profiles to eligible bays. Cover vehicle interface, load-handling method, equipment suitability, temperature needs and site-defined segregation restrictions. Treat unsuitable interfaces, unavailable handling capability and safety exclusions as hard constraints. Treat shorter travel distance or a preferred receiving team as preferences only where alternatives remain acceptable. Constraint-based scheduling separates eligibility from ranking eligible choices.
Check concurrent demand and downstream readiness
Model labor by skill and equipment by suitable type over the intervals when each is needed. For every overlap, compare combined demand with available supply. Sufficient staff-minutes across a shift do not establish sufficient simultaneous staffing; several jobs may need the same qualified team at once. A shared resource, such as a forklift serving several bays, can constrain otherwise empty doors.
Include staging space and downstream receiving readiness when either can delay bay clearance. Base locally selected recovery capacity on observed duration variability and the consequences of overruns. Leave recoverable time or resources where disruption is likely to propagate, rather than prescribing a universal buffer or filling every theoretical slot.
03US dock-safety requirements and their scheduling implications
Dock scheduling translates physical operating limits into booking decisions. The table separates binding US workplace-safety requirements from site-selected planning responses. Its scope is workplace loading safety, not product quality or destination-market compliance; check applicable product and market rules separately.
| Jurisdiction and workplace scope | Binding provision | Operational constraint | Scheduling response |
|---|---|---|---|
| US general-industry manufacturing workplaces handling pharmaceuticals, supplements, food, medical devices or chemicals; mechanical handling equipment in use. | 29 CFR 1910.176(a) requires sufficient safe clearances, including at loading docks. | Concurrent activity cannot consume the space needed for safe passage and turns. | Site practice: reduce overlapping appointments or available capacity where loads share constrained approaches or staging space. |
| US general-industry manufacturing workplaces handling pharmaceuticals, supplements, food, medical devices or chemicals; powered industrial truck handling. | 29 CFR 1910.178(o)(2) requires handled loads to remain within the truck’s rated capacity. | An available truck is not necessarily suitable for the booked load. | Site practice: match load information to suitable equipment availability before confirming the handling window. |
| US general-industry manufacturing workplaces handling pharmaceuticals, supplements, food, medical devices or chemicals; dockboard use. | 29 CFR 1910.26(d) requires measures to prevent the supporting transport vehicle from moving while employees are on the dockboard. | Vehicle-movement prevention is a condition of dockboard work. | Site practice: include preparation time and a safe-work readiness hold before handling begins. |
Keep planning responses separate from legal duties
Capacity reductions, equipment matching and readiness holds are local operating responses—not statutory appointment procedures or official recommendations. Incorporate them into finite-capacity scheduling, with handling decisions coordinated through the site’s forklift safety process.
Treat appointment-software selection as an operating decision, not a compliance conclusion. A confirmed appointment is a planning commitment, not permission to bypass a safety hold. If safe working conditions reduce usable capacity, the practical response is to revise the booking plan rather than compress preparation or clearance allowances to protect the original slot.
04Run the appointment lifecycle from request to closeout
A practical operating model gives the scheduler control of booking commitments and the dock supervisor control of service readiness. The following workflow is operating practice, not a prescribed regulatory sequence.
- Request and classify. The carrier or supplier proposes an arrival window and supplies the shipment reference, contact, inbound or outbound movement, vehicle type, load quantity and units, handling method, and special handling needs. Classify the work before estimating duration; a part-load delivery may involve different handling from a full-trailer movement.
- Estimate and test. The scheduler estimates handling service time separately from total bay occupancy, adding bay-blocking preparation and clearance to occupancy, then checks usable time, compatible bays, shared labor, equipment and staging availability. Treat these as the minimum feasibility inputs. Keep the request provisional when unresolved details could change duration or compatibility; identify the missing information and who will provide it.
- Confirm and control changes. The scheduler confirms the window and compatible resource reservation. Carriers or suppliers may propose changes or request cancellation; the scheduler authorizes and records booking changes and cancellations after checking affected capacity. The dock supervisor can flag operational unavailability. Communicate revised commitments to the carrier, gate and dock team rather than silently overwriting the booking.
- Update arrival separately. Gate staff record actual check-in and report discrepancies or revised arrival information; they do not implicitly reconfirm a missed slot. Keep booking states such as requested, confirmed and cancelled separate from execution states such as checked in, ready, service started and departed. Use the opening definitions for the booking/arrival distinction.
- Hand off to service. The dock supervisor converts the compatible resource reservation into a door assignment and coordinates physical readiness checks against the safety constraints above. Gate staff relay routing instructions; authorized site personnel direct physical movement. Record ready and service-start events when they occur, not when the appointment window begins.
- Close with evidence. Capture actual service-end and departure events in the process event log, plus a completion or exception reason and an owner for unresolved follow-up. If an event is missing, flag it for reconciliation rather than inventing a timestamp. Administrative closure does not establish physical departure.
- Describe the LoadCapture handling needs and references.
- Estimate OccupancyInclude bay-blocking service and clearance.
- Check feasibilityMatch calendars, compatibility and shared resources.
- Confirm the bookingCommunicate the window and prerequisites.
- Reassess changesResolve arrival updates and conflicting commitments.
- Hand off ExecutionRecord readiness, assignment and service events.
- Reconcile closeoutPreserve actuals, revisions and exception ownership.
05Design appointment records, resource calendars and event history
A practical dock-scheduling data model separates bookings, resources and events. Assign stable appointment_id, load_id, carrier_id, resource_id and event_id values; keep external references separately. Link shipment documents through an appointment-document association so several delivery notes or shipment references can belong to the same booking without creating duplicate appointments. This follows a relational traceability data model.
Keep planned arrival, planned service start and planned service end separate from current estimates and actual event times. Store the site time zone and timestamp offsets. For each event, distinguish occurred_at from received_at: a delayed arrival message should not make the vehicle appear to have arrived later.
Vendor-neutral entity diagram: arrows below show links, not process sequence.
| Entity link | Relationship key |
|---|---|
| Appointment → loads, document associations, events, revisions | appointment_id connects each record to its booking |
| Appointment → carrier | carrier_id identifies the booked carrier |
| Appointment → resource commitments → resource | appointment_id and resource_id connect demand to capacity |
| Resource → capabilities, availability calendar | resource_id connects suitability and available intervals |
Represent bay capabilities, such as trailer compatibility and handling equipment, separately from availability calendars. For shared labor and equipment, record available quantities and commitments with quantity, unit, interval start and interval end. A door number alone cannot describe simultaneous demand on a shared crew or forklift pool.
For each schedule revision, retain the previous value, revised value, reason, decision owner and decision time. Preserve the confirmed baseline used for performance measurement rather than replacing it with the latest estimate; link subsequent confirmations to their corresponding revisions.
Keep operational evidence attached to the booking: confirmation, arrival event, readiness-hold start and end with reason, service timestamps, and replan decision. A linked process event log helps reviewers reconstruct what was planned, changed and performed without treating the current status field as the complete history.
Appointment
The planned service commitment.
- appointment_id
- load_id
- planned_start_at
- planned_end_at
- status
Bay Capability
Physical matching criteria.
- bay_id
- capability_code
- availability_state
Shared Resource
Labor or equipment pool.
- resource_id
- resource_type
- resource_pool_id
Resource Window
Time-bounded supply and commitments.
- resource_id
- window_start_at
- window_end_at
- available_units
- committed_units
Execution Event
Actual occurrence and message timing.
- event_id
- appointment_id
- event_type
- occurred_at
- received_at
Replan Decision
Owned changes with reasons.
- decision_id
- appointment_id
- previous_start_at
- revised_start_at
- reason_code
- approved_by
06Worked cases: usable time, shared labor and disrupted arrivals
These hypothetical cases illustrate finite-capacity scheduling. All times, staffing levels and durations are scenario assumptions; calculated results are not external limits or benchmarks. Assume equipment suitability and safety checks permit the planned work; unresolved checks would block service.
Time capacity: fragmented minutes cannot be pooled
Assume one bay operates 08:00–11:40, with a blocked interval of 09:40–10:00. Each appointment uses sequential, non-overlapping activities: 10 minutes of bay-blocking preparation, 40 minutes of service and 10 minutes of bay clearance. Occupancy = 10 + 40 + 10 = 60 minutes. Appointments cannot cross the blocked interval.
| Contiguous window | Usable minutes | Whole appointments | Unused minutes |
|---|---|---|---|
| 08:00–09:40 | 100 | floor(100 ÷ 60) = 1 | 40 |
| 10:00–11:40 | 100 | floor(100 ÷ 60) = 1 | 40 |
A feasible occupancy plan is 08:00–09:00 and 10:00–11:00. Total free time is 200 minutes, but floor(200 ÷ 60) = 3 overstates capacity: only 2 whole appointments fit. The 80 unused minutes are split into unusable 40-minute fragments.
Compatibility and labor: an empty door is not a team
Assume bay A supports temperature-controlled and ambient loads; bay B supports ambient loads only. Load C needs temperature control; load D is ambient. Both are ready at 08:00. Eliminate C–B; retain C–A, D–A and D–B. Preparation is complete. Each unloading task takes 40 minutes with 2 staff, followed by 10 minutes of clearance needing no unloading staff. Only one 2-person team is available.
| Load and bay | Service interval | Clearance interval |
|---|---|---|
| C at A | 08:00–08:40 | 08:40–08:50 |
| D at B | 08:40–09:20 | 09:20–09:30 |
Each task consumes 2 × 40 = 80 staff-minutes; total demand is 160 staff-minutes. Concurrent unloading would need 4 staff, exceeding the 2 available. Sequential service uses exactly 2 staff throughout 80 minutes. Bay B is physically unused until 08:40, but the shared resource prevents an earlier start.
Disrupted arrivals: revise commitments, preserve history
Assume a separate schedule has one compatible bay and team, both free from 13:00. Service takes 40 minutes; clearance takes 10. Original starts are L at 13:00, N at 13:50 and confirmed load Q at 14:40. Preparation is included in arrival readiness, not service.
L arrives at 13:45 and is ready at 14:00. N remains absent at 14:00, meeting an assumed local no-show review threshold of 10 minutes after booking. At review, the dock supervisor confirms readiness; the scheduler approves releasing N’s reservation pending rebooking and serving L.
L’s earliest service start = max(readiness 14:00, bay availability 13:00, team availability 13:00) = 14:00. Completion is 14:40; clearance ends 14:50. Assuming Q is ready by 14:40, its revised start is 14:50 and completion is 15:30, rather than 15:20. The scheduler approves Q’s changed commitment and notifies its carrier. Apply the design section’s history controls to this replan.
07Connect systems and recover from late arrivals or outages
Treat these as vendor-neutral operating practices. Assign an authoritative owner to each fact; other systems consume it or request corrections rather than silently overwriting it.
- Order planning supplies order references, load requirements and required dates to establish booking scope; the dock scheduler owns appointment confirmation.
- Transport planning exchanges carrier references, estimated arrival and confirmed windows to coordinate dispatch; the transport planner owns the arrival estimate, using carrier updates.
- Warehouse execution exchanges readiness, service progress and receipt status to coordinate unloading; warehouse operations owns service events, while inventory control owns inventory receipt in the warehouse system.
- Gate or yard operations exchanges arrival and location status to coordinate access and positioning; gate staff owns check-in, and the dock supervisor owns door assignment, while the yard controller coordinates physical positioning.
Match external references using partner identity and appointment identifiers; route ambiguous matches for review. Deduplicate message identifiers so retries cannot create bookings. Preserve source event time, receipt time and revision sequence in the process event log. Interpret timestamps using explicit site time zones and offsets, including daylight-saving transitions. Reconcile delayed updates against authoritative records; an older message should not replace a newer commitment.
Use locally agreed review triggers for lateness and no-shows, not a universal grace period. Before revising a commitment, reassess compatible bay time, shared labor, equipment and safety constraints, as in the worked disruption case. Record cancellation acknowledgement, notify the carrier of changed commitments, and escalate affected downstream promises to transport and order-planning owners.
During an outage, designate the shift scheduling lead as decision owner and use a controlled fallback schedule with a timestamped baseline and change log. Suspend competing booking channels to prevent duplicate commitments. Before normal booking resumes, reconcile fallback changes, queued messages, cancellations and actual arrivals; resolve conflicts and communicate the authoritative schedule.
08Measure waiting, service reliability and constrained capacity
Use these operational definitions, not regulatory targets. Define the cohort as confirmed bookings whose original windows end within the reporting period. Use the design section’s confirmed baseline. Compare planned and actual handling durations at service-start/service-end boundaries; compare planned occupancy against actual bay-blocking and bay-clear events.
| Measure | Calculation or event boundary | Denominator or exclusions | Decision supported. |
|---|---|---|---|
| Arrival-window adherence | Gate check-in within original confirmed window | Arrived cohort bookings with timestamps | Arrival exception rules |
| Gate-to-service waiting | service_start_at − gate_check_in_at | Started visits with both events | Staffing |
| Turnaround | departure_at − gate_check_in_at | Departed visits with both events | Calendar allowances |
| Service duration | service_end_at − service_start_at | Completed services | Duration assumptions |
| Bay occupancy | Occupied bay-minutes / available bay-minutes | Compatible-bay calendar; includes non-service occupation | Bay calendars |
| Shared-team utilization | Busy team-minutes / available team-minutes | Same team calendar; exclude double-counted overlaps | Shared staffing |
| Cancellation rate | Cancelled bookings / cohort | Include advance cancellations; classify against a declared cutoff | Cancellation rules |
| No-show rate | Confirmed no-shows / resolved, noncancelled cohort bookings | Exclude advance cancellations and unresolved bookings | No-show rules |
| Replan rate | Bookings revised after confirmation / cohort | Count each booking once; retain cancelled and unresolved bookings | Calendar stability |
Report unresolved counts separately; mark rates provisional until closure. Never treat missing events as zero waits. Segment by load type, service method, arrival pattern and binding resource constraint. Show medians, upper-tail waits and sample counts—not one average. Set local decisions rather than universal utilization targets or promised savings; align service commitments and labor assumptions.
09Control booking errors and misleading schedule status
These practice-based controls address common booking failures; they are process-design options, not regulatory mandates.
| Failure mode | Operational consequence | Control | Owner |
|---|---|---|---|
| Separate shipment references create duplicate appointments | Capacity reserved twice | Link references to one visit; review suspected duplicates before confirmation. | Booking coordinator |
| Silent cancellation | Carrier travels against a withdrawn booking | Record cancellation; notify carrier and dock team; track acknowledgement. | Booking coordinator |
| Stale arrival estimate | Sequence reflects obsolete information | Show estimate age; reconfirm before replanning. | Transport coordinator |
| Unacknowledged appointment change | Parties follow different schedules | Keep change pending until acknowledgement; escalate unanswered changes. | Booking coordinator |
| Planned timestamps overwritten | Original commitment disappears | Apply the design section’s baseline control; audit reports for mixed planned/actual timestamps. | Scheduling lead |
| Premature completion status | Unfinished work disappears from review | Define completion events; review unresolved events before closeout. | Dock supervisor |
| Unowned replanning | Conflicting recovery decisions | Name the shift decision owner; record reasons and notify affected parties. | Scheduling lead |
| Informal priority override | Queue changes without accountability | Route preference exceptions through the named owner; record reasons and notify displaced carriers and teams. | Shift decision owner |
Use contemporaneous recording for actual events rather than reconstructing them from the plan. A planning preference can be reconsidered; a safety constraint is not a priority override. See the regulatory mapping for safety boundaries, and the capacity section for compatibility and shared-resource errors.
10Adapt the schedule to the load and manufacturing context
These illustrative practices translate load characteristics into booking inputs, not universal requirements for a product category. Applicability depends on the material, facility and handling process.
| Load | Site-defined constraint | Appointment field | Replanning trigger |
|---|---|---|---|
| Chilled food | Reserve temperature-suitable receiving space before unloading. | Handling temperature band and receiving-space reservation. | Cooling failure or occupied chilled staging space prompts reassessment of the slot. |
| Pharmaceutical or device materials | Schedule receipt when staff can review the site's specified receiving documents. | Document-readiness status and review owner. | Missing or mismatched documents prompt review of the booking before arrival. |
| Packaged chemicals | Reserve handling equipment suited to the declared package, load and local operating conditions. | Package format, load characteristics and suitable equipment class. | Changed packaging or equipment unavailability prompts a compatibility check and revised booking. |
Feed these inputs into finite-capacity scheduling. For chemical loads, coordinate the booking with local spillage and cross-contamination controls rather than treating every packaged load as interchangeable.
11Implement, test and review the scheduling process
Use this practical checklist to test readiness locally, whether bookings use a shared calendar or dedicated software.
- Process definition: Check appointment start and end boundaries, service-duration assumptions, required booking information and confirmation authority against the lifecycle described above.
- Calendar and compatibility setup: Check bay/load compatibility, resource calendars, equipment availability and shared-team availability. Confirm that breaks, maintenance and safety constraints reduce bookable time rather than remaining informal notes.
- Ownership: Name the owner who resolves conflicting commitments. Confirm that carriers, receiving or shipping teams, gate staff and resource owners receive relevant changes and acknowledge revised commitments.
- Exception tests: Use the disruption and recovery cases above to test late arrivals, no-shows, equipment unavailability, incompatible loads, duplicate updates and outage reconciliation. Check that each test leaves a coherent process event history, without duplicate bookings or silently overwritten commitments.
- Performance review: Examine observed duration distributions by load type, queue patterns and recurring exception reasons before changing capacity assumptions. Compare process changes, staffing, shift coordination and software support against the measured bottleneck. Record revised assumptions through change control and check subsequent performance; do not assume any option is universally cheapest or delivers a predetermined return.
Frequently asked questions
Q.Can a carrier reserve an appointment before the final trailer and shipment details are known?+
Yes—as a scheduling practice, use a provisional reservation with an owner and a deadline for completing missing details. Capture enough information to estimate service duration, compatible bay type, handling equipment and crew demand. Unknown trailer identity may be manageable; unknown temperature-control needs or unloading method can change feasibility. Keep provisional bookings visible in finite-capacity planning, and confirm the receiving dock requirements before converting the reservation into a firm service commitment.
Q.When should a late arrival keep its place rather than move to another service window?+
Keep the appointment only when the remaining work fits the available service window without displacing a protected commitment or exceeding shared resources. Recalculate from the expected service start, not the original arrival time, including setup and clearance. For a partially handled load, account for the remaining work rather than reusing the original full-load estimate. Use constraint-based scheduling to test the revised fit. Otherwise offer another window; for a no-show, release reserved capacity according to the site's agreed cutoff and notification process.
Q.How should drop-trailer appointments differ from live loading or unloading?+
For a drop-trailer appointment, distinguish the carrier's handoff window, the trailer's service window and its collection readiness. Reserve parking capacity and movement resources as well as dock time; a dropped trailer still consumes space while waiting. For live loading or unloading, plan around the tractor and driver remaining with the load. Track handoff, service completion and departure separately so a quick carrier visit does not conceal a growing backlog of unworked trailers.
Q.What should happen when a truck checks in on time but cannot safely begin service?+
Record arrival as on time, but mark service blocked and assign someone to resolve the unsafe condition. At US manufacturing workplaces using powered industrial trucks, 29 CFR 1910.178(q)(1) requires removal from service of a truck not in safe operating condition. Operationally, keep that equipment unavailable in the plan and reassess the appointment using safe alternatives. Retain separate arrival and service-start timestamps, communicate the delay, and avoid treating appointment punctuality as permission to bypass forklift safety controls.
Q.Can a small manufacturing site coordinate dock appointments without dedicated scheduling software?+
Yes. A shared calendar or controlled spreadsheet can support a modest appointment workload if someone owns updates and checks conflicts before confirming bookings. Include service duration, compatible bays, crew and equipment demand, staging space, status and carrier contact details. Coordinate the calendar with warehouse shift planning, with an agreed update cutoff and a visible common-resource calendar. Reconsider the tool when concurrent edits or frequent replanning make commitments difficult to control.
Q.Which appointment changes need an owner’s approval, and what history is useful to retain?+
A practical approval rule distinguishes clerical edits from changes that affect commitments. Route changes to service duration, load characteristics, equipment needs, priority, cancellation or an already confirmed window to the responsible scheduling owner. Carrier contact corrections can usually follow a simpler process. Use the design section’s appointment change history, adding notification outcome for the affected carrier. This supports reconstruction of decisions without treating every scheduling adjustment as a formal quality-system change.
Q.How should customer pickups and inbound deliveries compete for the same dock team?+
Use an explicit priority rule rather than automatically favoring either traffic direction. Consider material shortages, shipment readiness, agreed collection commitments, handling compatibility and the consequences of delay. Resolve conflicts against the combined inbound/outbound queue, not two independent priority lists. Apply allocation arbitration when commitments conflict, with a named owner for exceptions. Check staging-area capacity before bringing forward another load, and communicate which commitment moved and why rather than quietly double-booking the team.
Q.Does a confirmed dock appointment authorize material receipt, inventory availability or product release?+
No. In a practical workflow, booking confirmation and receiving acceptance are separate records; receipt checks and authorized disposition remain with their respective owners. Keep appointment, receipt, inventory and quality statuses separate, with responsibility for each transition defined locally. For example, unloading may be complete while material remains unavailable under an electronic hold. Appointment completion should not trigger product release; authorized people retain approval and release decisions under the applicable site procedures.
Primary sources
Want to see how Dock Appointment Scheduling could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
