Advertisement
A booking handover needs a clear next action, the person taking it and the latest client decision. Keep those beside the booking record so a colleague can continue the work without reconstructing it from messages. A list of dates alone leaves the important decisions unexplained.
Consider a fictional printing shop with one client ordering signs for two events. The client’s name belongs in one client record; the two jobs need separate booking records. Each job can then keep its own collection date and agreed wording without losing the connection to the same customer.
Give each booking a definite status
Use status names the team can apply consistently. “Awaiting artwork” identifies a dependency, while “Confirmed” should mean the client has agreed the details your business requires. Write down that rule. Otherwise, two colleagues can use the same label for different stages of a job.
Put the next action in a sentence, such as “Confirm collection after revised artwork arrives.” Assign a colleague to that action and record the date they need to act. When a client changes the instructions, add a dated note explaining the change so the next person can distinguish it from the earlier agreement.
Teams adopting Notion can use NotionSolutions’ client-work guides to separate client information from the work booked against it. Start with those two record types. Add a separate task database only once the team has a reason to maintain it and someone responsible for keeping it current.
Connect the client before adding a total
In Notion, a relation links a booking to an existing client page. Typing the client’s name into an ordinary text field does not create that connection. The walkthrough for connecting client and project records explains the relation setup; the same structure can use Bookings as the name of the work database.
If each booking has one client, choose the relation’s “1 page” limit on the booking side. Enable the corresponding relation in Clients if colleagues need to see the bookings from there too. Open a client page and inspect the linked booking names before adding calculations.
A rollup can summarise a property of those linked bookings. A count based on the booking title can help check the number attached to a client. Keep the meaning of any financial total explicit: agreed job values are not payments received. Likewise, an earliest date across linked bookings can include a finished job; hiding that job in a view does not remove its relation.
Try the handover with a fictional booking
- Ask a colleague to find the next action without opening the message history.
- Check that the client page leads to the intended booking, including any similarly named jobs.
- Change the example booking’s client link and inspect the corresponding client records again.
- Compare a summary with the actual linked records before relying on its result.
Give the colleague an ordinary booking first, then one awaiting a client reply. If they cannot tell who acts next, revise the note or status rule before adding more fields. Keep the agreed handover instructions beside the records, and name the person who will update them when the workflow changes.
