If the recipient may be unavailable, do not send the parcel on hope. Before the traveller leaves, the sender, traveller and recipient should agree on one delivery window, one named fallback person or revised meeting, and one clear stop condition. If any of those three answers is missing, the parcel is not ready to move.
A parcel plan can look complete because the sender has packed it and the traveller is going to the right city. Then the recipient stops answering. Now one person is carrying somebody else’s parcel, another person is waiting for an update, and everyone is inventing a new plan while standing on the road.
The recipient is not a final checkbox. They are one-third of the arrangement. In a traveller-carried parcel, the sender prepares the item, the traveller carries it on an existing journey, and the recipient completes the handoff. The plan is only ready when all three people know the same place, time window and fallback.
My practical rule is simple: do not move the parcel until the handoff has a Plan A, a Plan B and a stop point. That sounds slightly boring. It is also much less boring than carrying a box around Bengaluru for three extra hours.
A city match is not a handoff
“The traveller is going to Pune” does not answer who will receive the parcel, where they will meet or how long either person can wait. A city can be fifty kilometres wide in practical travel terms. A recipient who is free at 10:00 AM may be unavailable when the traveller reaches at 2:30 PM.
Start the arrangement on the ParcelPool planning page, but treat the match as the beginning of coordination, not the end. Write the exact neighbourhood, public meeting point, arrival window and maximum waiting time. Do not use “call when you reach” as the entire delivery plan.
The same discipline matters for a same-day parcel plan. Same-day is a compatibility question between an existing journey and two handoffs. It is not a promise that time will bend because the recipient has entered a meeting.
Use the three-person readiness card
Before departure, put the sender, traveller and recipient on one small card. Each person should confirm what they control. The sender controls accurate contents, packing and the first handoff. The traveller controls whether the packed parcel fits the journey and the realistic arrival range. The recipient controls availability, the final meeting point and the backup person or rescheduled handoff.
A green answer is specific and accepted by the people involved. Amber means a detail is missing or only one person has suggested it. Red means the arrangement should not start. One green person cannot compensate for two amber people.
| Person | Must confirm | Green | Stop if |
|---|---|---|---|
| Sender | Contents, packed condition, traveller handoff time and recipient details | The parcel and first handoff are ready | Contents, packaging or recipient changes without reconfirmation |
| Traveller | Available space, route, arrival range, waiting limit and contact method | The parcel fits the existing journey | The parcel creates an unsafe, unclear or impractical detour |
| Recipient | Exact meeting point, availability window, identity check and fallback | The final handoff can actually happen | The recipient cannot confirm or no acceptable fallback exists |
ShipdeHopSet a confirmation clock, not a stream of messages
Agree three moments. First, the recipient confirms before the traveller accepts the parcel. Second, everyone reconfirms near departure. Third, the traveller sends an updated arrival range when it becomes realistic. This avoids twenty vague messages while still catching a genuine change.
Use a window rather than one impossible-to-guarantee minute. For example: “Meet between 4:30 PM and 5:00 PM at the main entrance. The traveller will update the estimate by 3:30 PM. The recipient will reply by 3:45 PM.” The actual times must come from the people and the real journey. Do not copy example times without checking them.
Also agree the waiting limit. Ten minutes, twenty minutes or another period may suit the people and location, but it must be chosen before the traveller arrives. Silence should not create an unlimited obligation.
Build the fallback ladder before anyone leaves
Courier systems have formal exception workflows. Delhivery’s official non-delivery documentation describes attempted but undelivered shipments, reattempts, returns and consignee-detail actions. India Post provides shipment tracking, a helpline and a grievance route. A peer handoff does not automatically inherit any courier company’s reattempt policy, storage network or return process.
That is precisely why the fallback must be explicit. Do not say “we will manage somehow.” Choose the next acceptable action in order. If Plan A fails, move to Plan B only if everyone agreed to it. If Plan B is not possible, stop at Plan C. Nobody should improvise leaving the parcel with a guard, shop, neighbour or stranger.
A fallback person must be named and must consent. They should know what they are receiving and how the parties will confirm the handoff. If the parcel should return with the traveller, say who covers any added travel or coordination. ShipdeHop takes zero commission, now and always, but zero platform commission does not make an unplanned detour free.
| Level | Action | Use only when | Do not assume |
|---|---|---|---|
| Plan A | Meet the named recipient at the agreed public point | Recipient reconfirms inside the agreed window | That a city-level location is enough |
| Plan B | Meet a named, consenting alternate person or use a revised time | All three people accept the change before handoff | That any family member, guard or neighbour may receive it |
| Plan C | Keep the parcel and arrange return or a new handoff | Plan A and Plan B cannot happen safely and clearly | That the traveller can wait indefinitely or store the parcel |
Reference Delhivery One official non-delivery report guidance · India Post official tracking, help and fraud-warning page
Protect the handoff without oversharing
Share only what is needed for the arrangement: the agreed meeting point, a practical contact method, the parcel description and the confirmation rule. Keep account passwords, Aadhaar OTPs, banking details and app verification codes private. India Post’s current official website warns users against fraudulent links and sharing OTP, banking, card or UPI information through unauthorised links.
Use the ShipdeHop safety and handoff guide to prepare the people, place, parcel and record. Identity verification can help establish identity. It does not inspect the contents, guarantee conduct or make an unsuitable meeting point safe.
At handoff, compare the expected person and parcel details. Confirm receipt in the agreed channel. If the person, place, parcel or instruction has materially changed, pause. Convenience is not a reason to hand somebody’s parcel to an unconfirmed person.
Reference India Post official tracking, help and fraud-warning page
Run this stop-or-go check
Use this check before the sender gives the parcel to the traveller. Every essential line should be green. If one essential answer is amber, resolve it first. If it is red, do not begin the handoff.
This is intentionally stricter than “the recipient will probably be home.” Probably is not a delivery window. A compatible parcel arrangement respects the traveller’s existing journey and the recipient’s real availability at the same time.
- GO: contents and packed condition are disclosed and accepted.
- GO: the traveller has confirmed the parcel fits the existing journey.
- GO: the recipient has confirmed the exact meeting point and window.
- GO: everyone knows the maximum waiting time.
- GO: a named fallback or revised-handoff rule is accepted.
- STOP: the recipient is silent before the agreed confirmation deadline.
- STOP: somebody proposes leaving the parcel with an unnamed person.
- STOP: the location, contents, packaging or recipient changes without reconfirmation.
Copy this agreement before the parcel moves
Send this in the shared conversation: “Parcel: [short description]. Sender handoff: [place and window]. Traveller journey: [route and realistic arrival range]. Recipient handoff: [public place and window]. Recipient will reconfirm by [time]. Maximum wait: [agreed time]. If the recipient is unavailable, Plan B is [named person or revised time]. If Plan B fails, the traveller will [keep and return / arrange a new agreed handoff]. Nobody may leave the parcel with another person without confirmation from all three.”
Then ask each person to reply with a clear yes. Do not treat a reaction emoji from yesterday as confirmation of today’s revised plan. If a material detail changes, post the new version and confirm again.
For parcel contents, packing and suitability, check what can be sent before making the arrangement. Restricted, unsafe, illegal or poorly disclosed contents should not move simply because the route matches.
My founder view: the recipient completes the product
People often design parcel flows around the sender and the person carrying the item. The recipient appears as an address at the end. That is the mistake. The recipient contributes time, certainty and a safe completion point. Without that, the traveller is not carrying a parcel to a person. They are carrying a problem into another city.
ShipdeHop should make useful connections between people already moving. It should not turn uncertainty into somebody else’s unpaid waiting time. The better experience is not the one with the most messages. It is the one where three people agree on the same small plan before anyone starts.
If the recipient cannot confirm, wait. A later compatible journey is better than an immediate incompatible handoff.
Use the savings and contribution calculators with your own costs.
Questions, answered
What should happen if a parcel recipient is unavailable?
Use the fallback agreed before departure: a named consenting alternate person, a revised meeting window, or keeping the parcel for return or a new handoff. Do not leave it with an unnamed person.
Can the traveller leave the parcel with a security guard or neighbour?
Only if that exact person or role was accepted by the sender, traveller and recipient, and the handoff can be confirmed. Never assume a guard or neighbour has consented or is authorised.
How long should a traveller wait for the recipient?
There is no universal waiting time. The people involved should agree on a realistic limit before departure. If the recipient misses it, follow the agreed fallback.
Does Aadhaar verification guarantee a safe parcel handoff?
No. Identity verification can help establish identity, but it does not inspect the parcel, guarantee behaviour, confirm availability or replace a clear meeting plan.
Is a traveller-carried parcel the same as a courier delivery?
No. A courier may have formal tracking, reattempt, return and support processes. A peer arrangement needs its own explicit handoff and fallback agreement.
Does ShipdeHop charge commission on ParcelPool?
ShipdeHop takes zero platform commission, now and always. The people involved should still agree on any contribution, detour, return or coordination cost before the parcel moves.
Sources and useful references
External source pages checked on 24 October 2026. The worked amounts are inputs for the decisions explained above.
- Delhivery One official non-delivery report guidanceChecked 24 October 2026
- India Post official tracking, help and fraud-warning pageChecked 24 October 2026
I’m building ShipdeHop around useful connections between people, journeys and pre-loved things. Zero commission. Now and always.
Why I’m building ShipdeHop →