Overview of Checkpoints

Checkpoints are points in an interview where it can be saved, resumed and reviewed from. A checkpoint works by saving the progress of the interview, enabling interview users to easily resume an interview that they or someone else left partially completed. Checkpoints also allow completed interviews to be reviewed at any time.

For example, a user could resume an interview after they were interrupted or where they needed more time to gather additional data, or to seek help. Using checkpoints, assessments can be continued on-site that were started in the office, or vice versa, so that answers can be reviewed or updated before final submission. To see an example of how checkpoints would work in an interview, refer to Example: Checkpoints In Use.

The data collected from the interview is not saved to the connected application when a checkpoint is reached, it is packaged up with the state of the interview. A checkpoint can occur after any screen which the policy modeler has put a checkpoint on. This can occur before or after a Submit screen. If the user has already passed a Submit screen then their data has already been submitted and saved to the connected application, so this type of checkpoint would allow the user to review the submitted data, as well as see the state of the interview after this point. Note that unsuccessfully submitted screens or skipped screens do not result in checkpoints.

For the steps required to set up checkpoints in an interview, see Enable an Interview to Be Resumed Using Checkpoints.