A short trip can still be difficult to plan when the origin, destination, timing, and waiting expectations are unclear. ArcDev’s live Rates page lists Local Driving as a point-to-point mileage service and provides a local-drive calculator. That makes it different from a grocery pickup, restaurant delivery, shopping request, or multi-stop errand route.
This guide explains how to prepare a point-to-point request without assuming that every transportation need is automatically available. Send the details to ARC Driving & Delivery and let ARC confirm whether the request fits the current service.
Start with one origin and one destination
A point-to-point request should name the complete starting location and complete destination. Do not rely on a business nickname, property name, or general neighborhood.
Provide:
- Origin name and full address
- Destination name and full address
- Requested date and time
- Contact name and phone number
- Any fixed arrival deadline
- Parking, entrance, gate, or meeting notes
- What needs to happen at the destination
The first question is simple: what needs to move, from where, to where, and by when? ARC can then review the distance, timing, and service fit.
Explain timing in practical terms
“Morning” or “later today” leaves too much open. Share the earliest available time, the requested departure or pickup time, and any fixed deadline at the destination.
If timing depends on a store, office, business, property manager, or another party, confirm that person’s availability first. A point-to-point route cannot be planned accurately around a destination that may be closed or a contact who may not be present.
The public site does not promise guaranteed availability. A requested time remains a request until ARC confirms it.
Tell ARC about waiting before the route begins
Waiting can change a straightforward route. Explain whether the request includes an appointment window, a pickup that may not be ready, a recipient who must arrive, or another delay at the origin or destination.
Do not assume unlimited waiting is included. Give the best available estimate and ask ARC how the request should be handled if the other party is late.
The same applies to a return trip. A point-to-point request should not quietly become a wait-and-return route after it begins. If a return, later pickup, or second leg may be needed, include that in the first message so ARC can review the complete request.
Separate an extra stop from a true point-to-point trip
One origin and one destination are easy to understand. An added store, pharmacy, office, restaurant, or second delivery address turns the request into a different route.
List every proposed stop and its purpose. If several stops are required, use the Ocean Shores errand route guide instead of treating each addition as a small change.
For an item pickup followed by delivery, the broader Ocean Shores delivery and errand guide may be the better starting point.
Do not blur local driving and specialized delivery
Some requests belong in another service category:
- A ready grocery or pharmacy order needs pickup authorization and item handoff details.
- A restaurant order needs the restaurant’s ready time and order name.
- An Aberdeen or Hoquiam store run needs longer-route and retailer information.
- Heavy or oversized materials need dimensions, loading, and destination access planning.
- A shopping request needs an item list and substitution rules.
Choosing the right request type helps ARC review the route and point the customer to the correct current rate.
Use the local-drive calculator as a starting point
The live ArcDev Rates page includes a local-drive calculator. Use the current page rather than copying an old price into a message or relying on a screenshot.
The calculator helps with mileage planning, but it does not confirm availability or approve a request. Waiting, extra stops, unusual timing, access conditions, or a request outside the listed service may need direct review.
For questions about service fit, use the ArcDev FAQs and Contact page.
Questions to answer before contacting ARC
The retired local-driving questions post included a useful principle: clear questions make local help easier to schedule. For a point-to-point request, answer these before sending it:
- What is the exact origin?
- What is the exact destination?
- What date and time are requested?
- Is there a fixed arrival deadline?
- Is any waiting expected?
- Is a return trip or later second leg needed?
- Are there additional stops?
- Who is the active contact?
- Are parking, gate, entrance, or meeting notes required?
- Does the request actually belong under delivery, shopping, or a store run instead?
Copy-and-paste local driving request
Point-to-point request:
Origin name and full address:
Destination name and full address:
Requested date and time:
Fixed arrival deadline, if any:
Expected waiting:
Return trip or second leg requested:
Additional stops:
Contact name and phone number:
Parking, access, and meeting notes:
Other timing limits:Point-to-point local driving works best when the route stays clear. Accurate addresses, real timing, and advance notice about waiting or extra stops give ARC enough information to confirm whether the request fits.
Related Ocean Shores delivery guides
- Questions before scheduling delivery or errand help
- How Ocean Shores delivery and errand rates work
- Plan a multi-stop errand route
Helpful ArcDev planning links
Compare common service questions, rate details, delivery notes, and ways to contact ARC before scheduling an Ocean Shores delivery or errand run.
Delivery notes Delivery FAQs Rates Contact ARC Investor roadmap