Receiving a handover is two decisions, not one. First: is this complete enough to accept? Then, separately: do I confirm I have taken on the documents and the responsibility that come with it? Keeping them apart is what makes the second one mean something.
Accepting needs accept_handover, sending it back needs reject_handover, and confirming needs acknowledge_handover.
Reviewing what arrived
The review shows the checklist as the sender left it, with anything required and missing called out. Accepting a short handover makes its gaps yours.
Accept when what is missing is genuinely not needed yet.
Return it for corrections with a reason naming the document, not "incomplete".
A returned handover goes back to the sender with your reason attached to it.
Acknowledging
Acknowledgement is the receiving department confirming, in its own words, that it now carries the after-sales responsibility - warranty claims, maintenance scheduling, the customer's next call.
Acceptance moves the job; acknowledgement is the receiving side signing for it. A handover accepted but never acknowledged is one the register still counts as open business - and it is, because nobody has said out loud that they have it.