About Qualtrics Flow

I think you are on the right track, but can you explain a little more about the content in each End Block in your illustration? Are there questions, or is it limited to messaging? The content the same in each version of the End Block, correct?

Keep in mind that, in the Survey Flow, you can use the “Duplicate” feature to make a single block appear in more than one path. That way any edits you make to the block in the Survey Editor will update all instances of the block in the Survey Flow.

The current plan is to ask a couple of questions in END BLOCK before going to the End of survey . As I am preparing a rather large questionnaires with several exit points and potentially changing these exit points along the way, and the exiting flow is already complex , i was hoping each block can appear only once rather than duplicating at many places . I am not too worried about making changes within the End Block as you have rightly explained that any changes made within the block will be reflected in every occurrence of the block in the flow.

When you said “This is because the end block may need to change to another block as we progress, based on feedback from respondents.” in your original post, what does this mean? That you’ll have to update the Survey Flow in the midst of data collection, or something else?

Yes, that’s correct ,  after pilot run, we may decide to remove some blocks and add new blocks. As such , this end block might be deleted and the exit points to a new end block . As such , having one block in the flow is easier to maintain and to ensure  the flow is correct . The actual flow is much more complicated than depicted in the picture 

The issue with flow is that I cannot permanently position end block at the end . If I branch from a block at the top, eg block 2, if I did not specify skip to end of survey, all other blocks will still appear after end block is triggered after block 2. Which will mess up the flow of entire survey. 

Thanks for the additional details. Rather than deleting the original End Block and swapping in the new one at each exit point, you might keep the End Block and add the new content to it, then use Display Logic to hide the original content that you would have deleted. That would help you to avoid having to make mass updates in the Survey Flow.

Indeed , it’s something I have in mind . It’s hard for me to explain but at times it’s not possible, especially if the exit points to another existing block instead . Do I gather there is no way to have something like the ideal flow but I have to accept that the Qualtrics flow is the best way out ? 

You’ll have to decide whether you want to use Branching in the Survey Flow, or Skip Logic in the Survey Editor. Generally, you should avoid using both in the same survey.  If you go with Branching in the Survey Flow, then as long as you put an EOS object at the end of each branch, the Blocks that follow in the Survey Flow will not appear to respondents that following that branch.

Apologies if I’m not completely grasping this, but you could set up something resembling your Ideal Flow if you used Skip Logic in the Survey Editor and avoided using the Survey Flow feature. I’m presuming you’ve explored the Qualtrics Support pages to understand the Skip Logic and Survey Flow features in depth.

But, whether you use your Ideal Flow or Qualtrics Flow scenario, it seems that the real issue is how can you minimize the changes you have to make to your programming logic when you make updates to the End Block. If the solution I suggested to use Display Logic to hide the old content in the original End Block is not feasible, and you have to create an entirely new End Block, then whether you go with the Ideal Flow or the Qualtrics Flow scenario, you’ll have to swap out the old End Block with the new End Block at each exit point throughout your survey.

I concur that utilizing skip logic consistently would result in a cleaner survey flow. However, I've encountered a hurdle: I require scores and custom piped messages based on response options selected, functionalities that can only be achieved using embedded data. Unfortunately, these two features are not supported by skip logic as they necessitate separating questions into blocks.

this is my understanding, thus far.