Start a review round
Create the round
Open Reviews, give the round a clear name such as “Client sign-off”, and choose how reviewers collaborate.
Prepare the preview
Add test data when the survey uses conditional paths, so reviewers can reach the cases that matter.
Invite reviewers
Add their email addresses. Each person receives a private invitation to the review preview.
“Create a private review round called Client sign-off and invite anna@example.com and joan@example.com.”
Choose how reviewers see each other
Collaborative
Reviewers see each other's comments and can build on the same discussion. This usually works best for an internal team.
Private
Each reviewer sees only their own comments, while the survey owner sees everything. Use this for independent opinions or mixed client and internal reviews.
What reviewers experience
Reviewers walk through the same questions and flow as a respondent, but their test answers do not create real responses. They can comment on the whole survey, a block, a question or a specific option, then mark their review as complete.
Comments stay attached to the survey version the reviewer actually saw. If you publish a newer version later, the original discussion still makes sense and remains part of the audit trail.
Make conditional paths reviewable
If the survey branches on contact data, URL parameters or variables, set representative test values before inviting anyone. Otherwise reviewers may only see the default path or reach the end without seeing any questions.
Use more than one deliberate test case when a survey has important edge paths. This lets the same round cover, for example, a new customer, a returning customer and someone who is not eligible.
“Which test values does this review need to exercise every conditional path?”
“Prepare one test case for a contact under 40 and another for a contact over 40.”
Work through the feedback
Replies stay threaded with the original comment, so the discussion does not scatter. When you have considered a comment, record what happened:
- Applied means you made the requested change.
- Rejected means you deliberately decided not to make it.
- Resolved means it was handled another way or is no longer relevant.
If an applied change creates a new survey version, Dayalogs records where that change landed. Your AI assistant can summarize and suggest decisions, but applying or rejecting feedback always requires your explicit confirmation.
“Summarize the open review comments and suggest how to resolve each one.”
“Show me the wording change Anna suggested on the satisfaction question and ask before applying it.”
Choose when the round closes
“Has everyone finished reviewing? If they have, close the round.”