The real problem here isn't the checkbox. It's that we've let a binary control define how we track complex work. This user isn't asking for a fancier button; they're asking for a status system that actually reflects how projects move, through ambiguity, exceptions, and partial completion. And they're right to push back on the default TRUE/FALSE trap. When your team runs 500 projects with multiple sections each, a checkbox that only says "done" or "not done" isn't just limiting, it's misleading.
What stands out is the constraint they've built into their own request: keep the checkbox logic simple so people don't accidentally overwrite data in filtered views. That's not a lack of ambition; that's a deep understanding of how real teams work. They're not asking for a complex dropdown or a custom script that breaks when someone copies a cell. They want a third and fourth state, like "complete with exceptions" or "in progress", but they want it to feel as foolproof as clicking a box. That's the right instinct. The tool should adapt to the user's mental model, not the other way around.
The fact that a script might technically do this is beside the point. Most people in their position won't write a script. They'll search, find nothing, and settle for a workaround that involves color-coding or hidden columns, solutions that silently fail the moment someone sorts or filters. This user is doing something smarter: they're asking for a native, visible way to force transparency about exceptions. That's not a minor feature request. That's a workflow design decision that could prevent a project from looking complete when it isn't.
So what's the takeaway? Stop treating checkboxes as if they're sacred. They're a starting point, not a ceiling. If a spreadsheet tool can't support a simple three- or four-state toggle without requiring a custom script, then it's the tool that's outdated, not the user's needs. Teams deserve status controls that match the nuance of their work, without forcing them to choose between simplicity and accuracy. Build that, and you're not just improving a spreadsheet. You're giving people a reason to trust their data again.