This is a real problem people run into often enough that it shows up regularly in the Cvent Community forum: a question is set to required, registrants clearly had to answer it to complete registration, and yet when the report is exported, some rows have an answer and others are blank. It looks like a bug. Most of the time, it isn’t — it’s one of a handful of setup or report-building issues that are easy to miss.
Here’s what’s actually going on, and how to check each cause.
Cause 1: The question was added after some people already registered
“Mandatory” only applies going forward from the moment a question is added and published to the registration form. If you added or edited a question after registration had already been open for a while, everyone who registered before that change simply never saw it — so there’s nothing for them to have answered. Their blank answer isn’t a report error; it reflects the registration form they actually filled out.
How to check: Compare the registration timestamps of the blank rows against the date you added or last edited the question. If the blanks cluster before that date, this is your cause.
Cause 2: The question is required only for certain registration types or categories
A question can be marked mandatory overall but only actually required for specific attendee categories — this shows as a “partial” requirement in the question settings rather than a flat “required for everyone.” If a registrant’s category wasn’t included in that requirement, they were never forced to answer it, even though the question looked mandatory when you were viewing it as an admin.
How to check: Open the question’s settings and check whether the “Required” status is set per category rather than globally. Cross-reference the blank rows against which registration type or category those registrants belong to.
Cause 3: The question has conditional (branching) logic
If the question only displays based on an earlier answer — for example, “What size booth do you need?” only shown to people who answered “Exhibitor” to a prior question — then anyone who didn’t trigger that condition never saw the question at all. It wasn’t skipped; it was never shown, and that’s expected behavior, not a data loss issue.
How to check: Look at the question’s display logic settings and trace which earlier answer(s) trigger it. Then check whether the blank rows share a common answer to that earlier question that doesn’t trigger the branch.
Cause 4: The report doesn't include that question as a column
This is the most common cause, and it’s a report-building issue rather than a registration issue. If you’re using a standard or previously-saved report template, it may not automatically pull in a question added later, or it may be scoped to a specific set of fields that don’t include this one. The registrant did answer it — the data exists — the report just isn’t showing that field.
How to check: Build a fresh custom report (rather than reusing an old saved one) and explicitly add the question as a field/column. If the answers appear now, this was the cause.
Cause 5: The question was deleted or deactivated after the deadline passed
If a question was deleted (not just deactivated) after registration closed, its answers may no longer appear in the standard question summary report, even though people did answer it while it was live. This is a known point of confusion — deleting a question to “clean up” a form after a deadline can quietly remove it from reporting as well.
How to check: Look in your Inactive Questions or Question Library (rather than the active question list) — if the question still exists there but was deactivated rather than deleted, its historical answers are usually still reportable. If it was fully deleted, you may need to pull an older saved report generated before the deletion, or check with support about whether the raw response data is still retrievable.
Cause 6: The registrant was added manually, not through the registration form
Registrants added directly by an admin (walk-ins, manual entries, imports) don’t always go through the same form flow as someone self-registering online — which means they can be added without ever being prompted for that question, mandatory or not.
How to check: Cross-reference the blank rows against your registration source/method field, if your report includes one. Manual or imported registrations are the likely source.
Prevention checklist for future events
- Finalize your required questions before opening registration — adding mandatory questions mid-registration-period is the single biggest cause of this issue.
- When a question only needs to apply to certain attendee types, use category-specific requirements deliberately, and document which categories they apply to somewhere your team can reference later.
- Build reports fresh (or update saved templates) whenever you add a new question, rather than assuming older templates will pick it up automatically.
- Deactivate questions instead of deleting them once a deadline passes, if you may need to report on the answers later.
- If you’re adding registrants manually, use a process that walks through the same required fields as the public form, rather than a bare-bones admin entry.
The takeaway
A blank answer for a “mandatory” question in a Cvent report is almost always explainable once you check the timing of the question, whether it was required for that specific registrant’s category, whether conditional logic kept it hidden, and — most often — whether the report itself was actually pulling that field in the first place. Work through these in order and the pattern in your blank rows will usually point straight to the cause.