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.
Choose the survey and review languages
The survey content language controls the questionnaire itself. Reviewers can switch between the translations supported by that survey.
The review language controls the review panel, its buttons and messages, and the invitation email. One language applies to the whole round, independently from the survey content language. New rounds default to English.
Changing your Dayalogs profile language or the survey's source language later does not silently change an existing round. Create separate rounds when different reviewer groups need different interface and email languages.
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.
Every invited participant may comment while their own review and the round remain open. Decision permissions are separate: they control who can approve or reject feedback, not who can contribute comments.
Completing a review is irreversible. Dayalogs asks for explicit confirmation first. After confirmation, that participant's link becomes read-only; other participants can continue until they finish or the round closes.
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.
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.