Why the person leaving accepts or passes on a DropIn match
Understand why DropIn asks the departing person to approve a nearby parking request before sharing the bay, plate and precise location.
The algorithm cannot see everything
GPS can estimate who is nearby, but it cannot reliably see a queue, a blocked lane, a person already waiting beside the bay or a child who still needs to be secured in the car.
The giver can assess those details before committing to the handover.
What the giver reviews
Accepting means the giver intends to wait for that member if it remains safe and legal to do so.
- The requesting member’s display name and community profile.
- The approximate distance and expected arrival.
- Whether that arrival fits the selected departure time.
- Whether an existing driver is already clearly waiting for the space.
- Whether the handover can occur without blocking traffic or creating conflict.
What Pass means
Passing is not a negative rating and does not publish private information. It simply tells DropIn that this proposal is not suitable.
The system may consider another eligible nearby member, while preventing the same stale proposal from being treated as an active match.
Why this supports privacy
Before acceptance, the requester does not see the exact bay or the giver’s plate. After acceptance, both people receive the minimum practical details needed to recognise each other and coordinate the active handover.
Questions about this guide
Can a giver reject someone?
Yes. A giver may pass on any proposal. DropIn is a voluntary community handover, not a compulsory assignment.
Does passing hurt the finder’s rating?
No. A pre-acceptance pass is not a failed handover and should not be treated as misconduct.
What happens after acceptance?
Both members see the selected vehicles, plates, live handover location and arrival estimate for the active journey.