How to Track Vendor Questions That Are Waiting on a Client Answer (So Nothing Stalls for Weeks)
7 September 2026 · 6 min read
Not every vendor message needs a task with a due date. Sometimes a florist asks whether the arch should be white or ivory, a caterer asks if there's a vegetarian headcount yet, a stationer asks for a final wording change on the welcome sign, and the honest answer is: it depends on what the couple decides. That message doesn't disappear once it's read. It sits there, half a task, waiting on someone outside the studio to make a call, and it's exactly the kind of item a deadline-focused tracker was never built to hold.
Why a stalled question is a different kind of task
Most of what a studio tracks has a deadline: pay this by Friday, confirm this headcount by Tuesday. A question waiting on a client answer doesn't have that shape. There's no date attached to when the couple will decide on the arch color, just a vague sense that it needs to happen before the florist can finalize the order. It isn't urgent the way a deposit is urgent, and it isn't optional either, it just sits in a kind of limbo most tracking systems aren't built to represent.
It doesn't look urgent, until it is
The danger with a stalled question isn't that it gets forgotten immediately, it's that it gets forgotten quietly, over weeks, because nothing about it ever demanded attention on any particular day. Then the florist follows up two weeks later asking if there's an answer yet, or worse, doesn't follow up at all and simply orders based on a guess, and the studio finds out on delivery day that the arch is the wrong color because the question meant to prevent that never got answered.
Why a deadline tracker misses this
A tracker built around dates handles "pay the deposit by the 15th" well, since there's a clear date to sort by and a clear moment when it's overdue. "Waiting on the couple to pick a font for the menu cards" doesn't sort the same way. There's no date to flag it red, so it sits at the bottom of the list indefinitely, technically present but functionally invisible, right up until the vendor needs the answer immediately with no visible pressure having built toward that moment at all.
A worked example
Say a caterer emails: "Quick question, do you know yet if we need a vegetarian plate count, or are we going with a blanket vegetarian option for the whole table? Would help to know before we finalize the kitchen order." That's not a deadline exactly, it's a decision the couple needs to make, which then needs to get back to the caterer. Logged as a stalled item rather than filed away as answered, it stays visible on the shared board with the couple's name attached, not urgent today but not disappearing either, until someone actually gets the answer and closes it out.
Common mistakes
Answering a vendor's question with a guess just to keep the conversation moving, rather than actually checking with the client, which can lock in a decision nobody actually made. Marking a message as handled the moment it's forwarded to the client, when handled should really mean the client responded and the vendor got word back. Letting these questions live only in email threads with no shared visibility, so the one planner who happened to read the original message is the only one who knows it's still open.
Where to start
The fix isn't a stricter deadline on every open question, some genuinely don't have one. It's giving stalled items their own visible category on the shared board, separate from dated tasks, so a question waiting on a client answer doesn't quietly disappear just because it never had a due date to begin with. Forward the vendor's question the moment it arrives, and it stays visible until someone actually closes the loop, not until someone happens to remember it exists.
Frequently asked questions
How is a stalled question different from a regular task with no assigned date?
A regular task is something the studio still needs to do. A stalled question is something the studio is waiting on someone outside the studio, usually the couple, to answer before the vendor can move forward. Treating the two the same hides the fact that the next move belongs to the client, not the team.
What if the couple takes weeks to respond?
That's exactly why the question needs to stay visible rather than sit in an old email thread. A stalled item on a shared board is easy to bring back up in a check-in call or a follow-up message, since it's still sitting there unanswered instead of buried in a conversation from three weeks ago.
Should every small vendor question get tracked this way?
Not every one, a quick preference that doesn't affect the vendor's planning probably doesn't need its own entry. It's worth tracking anything where a vendor is genuinely waiting on the answer before finalizing an order, a headcount, or a design choice, since that's where a missed answer actually costs something.
Can a vendor's question get answered without the couple, if the studio already knows their preferences?
Sometimes, if the planner has clear prior direction from the couple on that exact choice. It's worth being cautious here though, since answering on the couple's behalf without checking is exactly the kind of guess that can lock in something nobody actually decided.
Get your studio address, free
Get your studio address
