Handover is its own slice

Release is not delivery. Handover begins when you can say who may take the item, at what temperature, and from which moment the responsibility is theirs. Write that fork before anyone arms the aircraft.

Not the last second of the flight

Handover is not the last second of flight. It is the next slice, with its own custodian and its own clock. The aircraft can release, lower, or land. It cannot decide that the right person has the right item, at the right temperature, under a rule you can defend later. Until that decision exists, the mission has relocated risk. It has not delivered. A van's procedure at a door fails here for a physical reason. The aircraft cannot climb stairs, cannot wait cheaply, and is dangerous to approach while the rotors turn. Write handover as a procedure that starts before release and ends at a recorded acceptance, a recorded rejection, or a recorded abort.

The clock often starts earlier than the landing. A chilled product leaves controlled storage, sits through a weather hold, flies, and then waits again for a person. Everyone quotes the flight time. The two waits are what usually break the specification. Identity has the same shape. A code, a face, or a professional role is checked inside the energy you kept for loiter, or the check happens after shutdown, with the parcel in a locker or in someone's hands. Choose which, and do not discover it on the first live drop. Remote identification of the aircraft, where rules require it, tells a third party who is flying. It does not name the person who received the goods.

Five ways to receive

Unattended placement leaves the parcel on open or private ground with nobody there. Theft, rain, animals, and the wrong garden are ordinary. A photograph from the aircraft shows a position at a time. It is not a chain of custody, and the camera is also a privacy problem over a yard. Someone must own the land you use. Injury to a person who approaches a machine that has not finished shutting down sits with the operation, not with the photograph. A locker moves identity from a face to a code and gives the parcel a box. The locker can still be hot, full, or misaligned with the landing. A passive metal box in the sun is not a cold chain. Where the lockers are, and how many slots they have, is a capacity question like the pad itself.

A window is not a general mode. Wind around a facade, the right to use the building, and the risk of a falling object make it a special geometry with a person already inside. It belongs in a demonstration or a purpose-built opening, not in a default promise to consumers. Hand-to-hand means a person must be present. If they are late, loiter spends the reserve, or the sortie aborts and flies home heavy. The identity check spends that same clock. Taking a parcel from a hovering aircraft near faces and hands is a bad procedure. Land and shut down, or use a mechanism that keeps people out of the rotor plane, and treat the extra minute as part of the design rather than as a surprise.

Handover to a health worker is a protocol, not a consumer experience. The receiver is a role: a nurse, a pharmacist, a laboratory technician. The hospital is not a receiver. Blood or a named medicine needs a lot or a batch, a temperature history, a time out of storage, and an acceptance in a system or on a signature. The person who should accept it may be in a procedure and cannot come to the roof. The elevator is then its own slice, and if nobody owns it the chain of custody ends in a corridor. Rejection has to be designed. A product that has gone warm is not a success with a note. It is a failed delivery, and the aircraft may have to carry it back.

Identity, temperature, liability

Three questions fork, and they do not share an answer. Who may receive this item? A snack, a contract, and a controlled medicine are not one rule. How warm or cold may it be, for how long, measured from which moment, and who may reject it? When do risk and responsibility pass: at release, at rest in a locker, at a person's acknowledgment, or only when a professional accepts inside the specification? Mix these and every argument after an incident will pick the definition that suits the speaker. Write the three answers onto the shipment before anyone arms the aircraft. The answers change the procedure, the hardware, and the energy reserve. They are not a paragraph of terms that nobody at the pad has read.

The branches are practical. If identity fails, the parcel goes back or to a defined exception site, and the energy plan includes that heavy return. If temperature fails, the receiver rejects, and the shipper's rule, not the pilot's optimism, decides whether the item can still be used. If a person is injured, or a camera records a home, the site owner and the operator are in a liability conversation that remote identification of the drone does not close. Under level-4 flight, third parties are the environment, not a rare intruder. A casual drop in that environment is an unstated claim that injury, loss, and privacy have all been accepted. Do not leave the claim implicit. Put it in the procedure, then fly.