When a booking spreadsheet starts fighting back, it is usually a sign that the tool has been pushed past its natural limits. The user here has built a thoughtful system: a master input sheet tracking children across five sessions per day, five days a week, with a monthly sheet that pulls that data forward. It is exactly the kind of practical, homegrown solution that thousands of administrators rely on every day. But the formula breaks when a session has only one child. Instead of pulling that single name into one cell, it duplicates the child across multiple cells. That is not a user error. It is the spreadsheet itself telling you that the logic you are using was designed for a different kind of problem.
The core issue is that traditional spreadsheet formulas treat data as a grid of static references, not as a dynamic set of records. When the input sheet has two or more entries in a session column, the formula can safely assume it is working with a range. With a single entry, the formula interprets that cell as a scalar value and applies it differently. This is a structural limitation, not a missing semicolon. The user has already built the right architecture for their workflow, an input sheet, a monthly pull sheet, and conditional formatting. What they need is a smarter way to move data between those sheets, one that treats each booking as an individual record regardless of how many children share a time slot.
What this means in practice is that the user is spending time fighting the formula instead of managing bookings. Every session with a single child becomes a manual check. Over a month, with five sessions per day and five days per week, that adds up to real friction. The solution is not to patch the formula with more nested conditions. It is to step back and ask whether the tool itself should be handling this differently. An AI-native spreadsheet would recognize that a session with one child is still a valid data point. It would not treat a single record as an edge case. It would pull that name into the monthly sheet exactly once, the same way it handles twelve names in a full session.
Our opinion is plain: if your spreadsheet is making you work harder, not smarter, it is time to explore a different approach. The user has already done the hard part, designing a clear, logical booking system. They should not have to fight a formula to make it work. A modern, AI-driven spreadsheet would handle this variability naturally, freeing the user to focus on the children and sessions that matter. Stop debugging the past. Start exploring tools that treat your data the way you actually use it.