I've had to deal with some similar situations like this before (e.g. skipping from survey 1 to survey 2 but having a delay of 2 days between survey 1 and survey 2).
I found the SystemTime function to be very handy for these type of dilemmas.
Hopefully this idea helps.
You can possibly keep this all in one survey and split into the 5 sections.
The order may look something like this ...
*Complete section 1.
*Record the system time.
*Thank the respondent for completing section 1 and inform them when section 2 is ready to commence.
*Suspend at the section 2 introduction.
*Check the current system time and the Wednesday start time has been passed.
*Complete section 2.
*Record the system time.
*Thank the respondent for completing section 2 and inform them when section 3 is ready to commence.
*Suspend at the section 3 introduction.
*Check the current system time and the Friday start time has been passed.
*Complete section 3.
*Record the system time.
*Thank the respondent for completing section 3 and inform them when section 4 is ready to commence.
*Suspend at the section 4 introduction.
*Check the current system time and the Saturday start time has been passed.
*Complete section 4.
*Record the system time.
*Thank the respondent for completing section 4 and inform them when section 5 is ready to commence.
*Suspend at the section 5 introduction.
*Check the current system time and the Sunday start time has been passed.
*Complete section 5.
*Thank the respondent for completing section 5.
*File the survey away as a completed status.
After each section is completed, record the system time (as per the steps mentioned above). An example of how to do this at section 1 is to create a pass-in field and call it "Section1Time".
Use this script at the end of section 1 by placing it in the footer of the section 1 thank you page ...
[%SetValue(Section1Time,SystemTime())%]
When Wednesday arrives, each respondent who has completed section 1 should be suspended at the introduction page for section 2. Use a skip which controls them going forward or not. The logic can be something like these examples ...
Not(SystemTime()>(Section1Time+172800)) [2 day delay from when section 1 was completed]
*Note SystemTime is captured in seconds. The 172800 refers to 2 days.
Not(SystemTime()>(???) [where ??? is the system time in seconds for the Wednesday start time]
You would repeat this process at the beginning of sections 3-4-5.
You need to decide on whether you want an exact 2 day delay to be reached or a simple start time on each day. I mentioned both skip types above.
The downside to the single survey approach is the respondent will only be filed as a completed survey once all 5 sections have been completed.
If you decide to go with a 5 survey approach, you can pass all relevant fields from survey 1 to survey 2, survey 2 to survey 3, and so on ...
This would include passing a system time variable for each survey and checking the system time at the beginning of survey 2-3-4-5 before proceeding. If you are needing to pass a lot of variables from one survey to the next, it may be easier to keep it in one survey.
*Note: When you pass a numeric variable from one survey to another, the maximum number allowed within Sawtooth is 999,999,999. I worked a way around this issue.
If you need to see .ssi examples of the survey 1 / delay of 2 days / survey 2, I'm happy to pass them on to you as this may trigger some ideas of your own.
In summary, look to the SystemTime function for assistance. It's a beauty!
I hope this information points you in the right direction.
