01
Where does the first handoff happen?
Pickup needed, self-drop-off intended, or still unknown.
Open this gate ↗TP / CHOICE GATE / 00
Choose what you need. Keep availability open.
Separate four service-scope requirements before speaking with a provider. Titik Pilih records your intent; it does not recommend a provider, service or transport mode.
Private browser session · No upload · No provider matching
Do not collapse four decisions into one vague request.
02
Who prepares the goods?
Self-pack intended, packing support to confirm, or still unknown.
Open this gate ↗
03
What separation is required?
Shared tolerance, separate-space requirement, or still unknown.
Open this gate ↗
04
Where does the final handoff happen?
Self-collection intended, final delivery to confirm, or still unknown.
Open this gate ↗02 / HONEST STATE
Unknown is a complete answer for now.
Keep an undecided requirement visible instead of replacing it with a guess.
Pickup need and self-drop-off intent are different records.
04 / PREPARATION HINGE
Record responsibility—not packing advice.
State whether self-packing is intended or whether support needs to be discussed. Suitability and method remain for a capable party to confirm.
Open preparation gate ↗
05 / SPACE BOUNDARY
Tolerance for sharing is not proof of available space.
Record whether sharing is acceptable or separation is required. Capacity, equipment and operating arrangement stay unconfirmed.
Open space gate →
Name the intended final handoff.
Self-collection intent and a final-delivery requirement belong in separate states. Neither confirms a service is offered.
Record destination handoff ↗
07 / PRIVATE MATCHER
Assemble a consistent record—without selecting a provider.
- User-recorded requirements
- Choices not yet decided
- Questions for a provider to confirm
“Match” means placing your own requirements in one coherent record. It is not provider matching, a recommendation, an offer or a booking.