Written by DROPS.ST.
Write the unresolved task, checked facts and next action first. Name the receiver and confirm they accepted it. A transcript alone leaves the next shift to decide what matters and who is responsible.
DROPS keeps order items linked to the customer, with website and connected Telegram orders using the same shop system. The next person can start from the relevant record instead of rebuilding the story from messages.
Start with the job still needed
“Check whether the requested quantity change can be made” gives the receiver a task. “Customer called about their order” gives them an event to investigate.
Use a permitted reference within the approved workflow. Avoid copying customer identifiers into unrelated groups or documents.
Keep one note focused on one task. If a product correction and order question need different owners, separate them and identify their relationship.
Use a compact handover card
This is a writing template for your approved staff tool, not a native DROPS handover-form claim.
| Field | Record | Purpose |
|---|---|---|
| Task | Unresolved decision or action | Clear starting point |
| Reference | Relevant order, product or case | Locates the evidence |
| Checked facts | What was verified and when | Avoids repeated work |
| Open question | Missing information | Defines the uncertainty |
| Next action | Concrete permitted step | Makes the note actionable |
| Receiver | Named person accepting it | Transfers responsibility |
| Timing | Deadline or review point | Sets action or escalation |
“Customer reports payment” and “payment verified” are different facts. Do not collapse them to shorten the note.
Record progress, not the whole conversation
Include facts that change the next decision. Identify the checked stock source or an update promised but not yet sent.
Keep unrelated personal background out. Describe the operational request, not symptoms, buying motivations or judgments about the customer.
“Requested availability confirmation” is more useful than “difficult customer.” Where history matters, reference the approved record and explain its implication.
Longer notes will not fix an unclear source or missing decision owner.
Make ownership a two-person exchange
The outgoing person proposes the receiver. The receiver confirms understanding and ability to act within their responsibility.
If access or authority is missing, find an appropriate owner before declaring the handover complete. Forwarding to someone who cannot act does not settle responsibility.
If nobody can accept, escalate to the shift manager and record the review point. “Team to check” leaves ownership unresolved.
A short read-back can help: the receiver states the task, next action and timing, then the written note preserves that agreement.
Hypothetical example: a quantity request
A fictional customer asks to change TRAINING-ORDER-A. Staff checked the item reference but not whether the change is possible.
Task: Review the quantity request. Checked: Item reference matches. Open: Current order position. Next: Inspect the record and follow the approved change process before confirming. Owner: Receiving shift lead, acceptance confirmed. Timing: Start of the fictional next shift; escalate if further authority is needed.
The note makes no promise that the change happened. If the receiver cannot decide it, they record the authorised next owner and step.
It is a fictional writing example, not automatic assignment or a customer record.
Use the same card when a request exceeds staff authority or a customer contact changes at departure. Preserve unresolved promises and name the accepting receiver. Coordinate access removal through the offboarding checklist.
Check usability and close the task
Read the note at phone size. Put the task and receiver near the top. Use a date and time instead of “tomorrow” where that would become ambiguous.
Confirm the receiver can open the record with their own access. Arrange an authorised review rather than sharing a login. The permissions guide explains the broader role scope.
When the decision is made, record the outcome and assign any remaining follow-up. Forwarding a message is not evidence that the agreed action happened.
For product corrections, the descriptions guide helps identify the approved record. Review recurring gaps at their source rather than writing longer handovers.
Keep continuity with DROPS
Choose DROPS when the next shift needs connected customer, item and order context. The handover note adds the unresolved decision and responsible person to those working records.
Explore DROPS and view demo shops. Bring a fictional unresolved question, locate its record and write the next action. Confirm who accepts it before adding another handover tool.