When a manager suggests Thursday for a team dinner, saying that it does not work can feel awkward. People may agree before checking their own plans. The following fictional example shows why a group might prefer to collect availability without displaying names.
Understand what the setting hides
When creating a Pithup event, enable Collect replies with names hidden under Additional settings. Responses are shown with numbered participant labels rather than names. Names are hidden from everyone viewing the event, including the organizer; times and counts remain visible.
This is a scheduling option for reducing named visibility, not a reason to require attendance or explanations for unavailable dates.
Offer several realistic evenings
Open a practical set of evenings over the next two weeks instead of using the manager's first suggestion as the only option. The Evening preset can help set the time range. Check any venue constraints separately.
Explain the setting in the invitation
The event also displays a notice about hidden names. Participants should understand the setting before entering their availability.
Respond without giving a reason for every conflict
Mark the times that work. Use If needed for an option requiring an adjustment, and submit the all-unavailable response if no candidate works. The availability response does not require a written explanation of a personal conflict.
Choose using counts and communicate the result
The decision card shows the suggested date and response counts, with numbered labels rather than names. Compare options using that information and communicate the agreed time yourself. A result based on current responses does not establish agreement from anyone who has not replied.
The same approach can be useful for a department gathering or a club social when named responses would be uncomfortable. Before using it, make sure the group understands both the setting and the expectations around attendance.