Short answer: Yes - if your submission is rejected during pre-publication review, you will receive a full explanation of the rationale. You will not be left guessing why your project was not approved; the feedback provided is intended to give you enough detail to understand the decision and, where applicable, address the issues before resubmitting.
What "full explanation" means in practice
When a submission does not pass review, Vizno will communicate the specific reason or reasons for the rejection. This means the feedback will go beyond a generic decline notice and identify the aspect(s) of your project that triggered the outcome. The exact delivery mechanism (in-app notification, email, or both) has not yet been finalized - check back here for updates once that detail is confirmed.
What happens after you receive feedback
Once you have reviewed the explanation, you may revise your project to address the identified issues and resubmit for review. The feedback you receive is meant to support that process. If you believe a rejection was made in error, the explanation you receive forms the basis for any appeal you may wish to raise.
What content is checked during review
Pre-publication review evaluates your project against Vizno's content policies. Familiarizing yourself with prohibited content and platform-specific rules before you submit can reduce the likelihood of a rejection.
Why your project might be stuck in pre-publication review
Short answer: Pre-publication review takes a variable amount of time, and a project sitting in review longer than expected usually means it is still in the queue - not that something is wrong.
A few things can cause a project to remain in review longer than you might expect:
- Queue volume. Review is processed in order, and during busy periods the queue can take longer to clear. Your project hasn't been skipped - it's waiting its turn.
- Manual escalation. Some projects require a closer look before a decision can be made. If your submission touches areas that need extra scrutiny under Vizno's content policies, it may take more time than a straightforward case.
- Incomplete submission details. If your project is missing information that reviewers need to assess it properly, it may be held pending clarification. Check whether you have received any communication from Vizno asking for additional context.
Vizno targets a review turnaround within 5 business days of submission, per the Creator Terms. If your project has been in review for more than 5 business days and you haven't heard anything, contact Vizno support and include your project name so the team can look into it.
What you can do while you wait
- Don't resubmit unnecessarily. Withdrawing and resubmitting your project restarts the process and moves you back in the queue.
- Check your notifications. If reviewers have reached out for clarification or additional detail, responding promptly will help move things along.
- Contact support. If your project has been in review for what feels like an unusually long time, reach out at vizno.com/contact and include your project name so the team can look into it.
What happens during pre-publication review
Short answer: Pre-publication review is a check your project goes through before it becomes publicly visible on Vizno. Reviewers assess your submission against Vizno's content policies and platform rules, then either approve it for publication or return it with a rejection rationale.
When you submit a project for publication, it enters a review queue. From there:
- Queue assignment. Your project is placed in line and picked up by reviewers in order. You don't need to do anything at this stage - the process runs on Vizno's side.
- Content assessment. Reviewers examine your project against Vizno's content policies. This includes checking for prohibited content, verifying that the project meets platform-specific rules, and - in some cases - taking a closer look at areas that require extra scrutiny.
- Decision. One of two outcomes is reached:
- Approved - your project is cleared and moves to publication.
- Rejected - your project is returned with a full explanation of the reason(s) it did not pass. You can then revise and resubmit, or raise an appeal if you believe the decision was made in error.
Vizno targets a review turnaround within 5 business days of submission. If your review runs past that target, contact Vizno support.
What to do if your submission is rejected
Short answer: A rejection at pre-publication review is not final. You'll receive a full explanation of why your project didn't pass, and you can revise and resubmit once you've addressed the issues identified.
Here's what the process looks like after a rejection:
- Read the explanation carefully. The feedback you receive will identify the specific reason(s) your project didn't pass - not just a generic decline. Use it as a checklist before you make any changes.
- Revise your project. Make the changes needed to bring your project in line with the feedback. If the rejection relates to content policy, reviewing what content is prohibited on Vizno before you resubmit is a good idea.
- Resubmit for review. Once your revisions are in place, resubmit your project. It will re-enter the review queue and go through the same process as a new submission. Avoid resubmitting without making changes - doing so won't change the outcome and may slow things down.
- Appeal if you believe the decision was an error. If you think your project was rejected incorrectly, the explanation you received forms the basis for an appeal. Contact Vizno support with your project details and your reasoning.
A few things to keep in mind:
- Don't withdraw and resubmit unnecessarily. If your project is still in review, withdrawing it restarts the queue position. Only resubmit after a confirmed rejection and after making genuine revisions.
- One issue at a time. If the feedback lists multiple reasons, address all of them before resubmitting - a partial fix is likely to result in another rejection.
- Still unsure what the feedback means? Reach out at vizno.com/contact and include your project name. Support can help clarify what's needed before you spend time on revisions.
Where to find your review feedback
Short answer: Yes - if your project was rejected during pre-publication review, you will receive feedback explaining why. The exact delivery mechanism (in-app notification, email, or both) is still being finalized, so contact Vizno support if you're unsure where to look for your feedback in a specific situation.
Once a decision is made on your submission, the feedback is sent to you directly - you don't need to go looking for it. In practical terms:
- Rejections come with a full explanation of the reason(s) your project didn't pass. This is delivered to you as part of the rejection notice. If you submitted a project and aren't sure whether you received feedback, check both your in-app notifications and the email address associated with your Vizno account.
- Approvals do not include detailed review notes - if your project passed, it simply moves to publication.
- After publication, review feedback from a prior rejection remains available to you as part of the record of that submission. If you need to reference earlier feedback and can no longer locate it, contact support with your project name and they can help.
If you believe you should have received feedback but haven't seen anything, it's worth checking your spam or junk folder before reaching out. If it's still missing, contact Vizno support.
Related
- What happens during pre-publication review?
- What to do if your submission is rejected?
- What content is prohibited on Vizno?