BlockSurvey allows department and job-title questions: employee surveys still need safeguards against small-group identification

BlockSurvey’s anonymity check can block direct identity questions, but HR must still judge whether subgroup reports expose people. It suits collecting overall feedback; detailed results still need human aggregation and editing before release.

Source: help.blocksurvey.io
November 17, 2026
3 min

For HR teams collecting employee feedback with BlockSurvey, the useful safeguard is the identity-question check before publication, not permission to circulate results freely because a survey carries an anonymous seal. It provides a collection-stage defense when the goal is to learn what the company should improve. If managers also want to drill down through departments and job titles to individuals, the reporting approach must change first.

The official help article says that enabling Make it Anonymous in settings triggers a check for questions requesting personally identifiable information. Detection prevents anonymity from being enabled. A passing survey displays an anonymous seal and does not collect IP addresses, browser or device information, or custom URL data. The feature is included in all paid plans. These are documented product behaviors, not findings from an independent security test for this article.

The key boundary appears in the official engineering explanation: the check first blocks certain question types, then evaluates the label and description of each open-ended question. Its examples reject employee-ID questions but allow department and job-title questions. The check happens before responses arrive and does not examine respondents’ answers. Passing it therefore does not establish that every later free-text response or cross-tabulated report is unidentifiable.

Suppose a department has just one senior designer. Department and job-title questions may individually pass the check, yet combining those fields in an internal detail report could let colleagues infer who answered. A specific project or incident volunteered in a comment adds clues. This is risk analysis of a hypothetical scenario, not a finding that BlockSurvey leaked data. HR’s additional work is controlling what it subsequently releases.

Before sending the survey, sketch the final report: which groups are necessary, which combinations leave very few people, and who can see raw comments. Combine very small groups, avoid copying identifiable quotations into management materials, and remind employees before open-text questions not to include names or identifying details. These are organizational rules; do not assume the anonymity switch enforces them automatically. The cost is less granular analysis and difficulty following up on a particular anonymous comment.

If the real task requires contacting a complainant to resolve an individual case, provide a separate contact channel that clearly explains how identity will be used. Do not promise anonymity and then try to recover identity. BlockSurvey is better suited to understanding shared problems without tracking individuals. Before launch, use a test survey to check that identity questions are blocked and the anonymous seal appears, then manually review the planned report. Adoption depends on whether the team will retain that reporting review, not merely on whether it can enable anonymity.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:help.blocksurvey.io