Where a Google Calendar schedule stops holding up
None of these matter with four people and fixed hours. They start costing you somewhere around a dozen staff, a second location, or a lot of shift swapping.
Nothing stops a double booking
How you'll know: Someone is on two shifts at once, or on shift during their time off, and nobody notices until they don't turn up.
Fix: Calendar can show a guest as busy when you can see their calendar, but it never blocks the booking. Scan the week in a per-person view before you publish it, or have something check for overlaps automatically.
Swaps happen in a group chat
How you'll know: Two staff agree a swap by text, the calendar still shows the old names, and the manager finds out on the day.
Fix: Make one rule: a swap isn't real until the shift event is changed. If swaps are weekly, this is the point a scheduling app with swap requests pays for itself.
No hours total
How you'll know: Payroll needs hours per person, and someone is adding up event lengths by hand, or overtime gets missed.
Fix: Calendar doesn't total shift hours per employee. Keep the spreadsheet you imported from as the record of hours, or export the calendar and total it, but don't treat Calendar as your timesheet.
Availability lives in people's heads
How you'll know: Shifts get booked on days people already said they can't work.
Fix: Ask staff to put unavailable days on the Shifts calendar as their own events, or keep an availability tab next to the sheet you build the week in.