Would not think that stretching time using forced delay or captcha is a very effective technique here - the user would probably start wondering why does captcha exist on earth at all, i think what you really want is to try and enforce the user to double check their entry before submitting an application form.

##Overview Before Submit

This is a similar pattern - with some utility differences - that is used in an e-commerce checkout, once the users have inputted their data, navigate them to a mediator page/view that provides them an overview where you ask them to double check their entries before the final submit.

And if you want to take it to the next level, you can add a dialog box on checkout that asks "Are you sure you have checked your entry" but that will most likely freak them out.

Hope this helps :)

Would not think that stretching time using forced delay or captcha is a very effective technique here - the user would probably start wondering why does captcha exist on earth at all, i think what you really want is to try and enforce the user to double check their entry before submitting an application form.

Overview Before Submit

This is a similar pattern - with some utility differences - that is used in an e-commerce checkout, once the users have inputted their data, navigate them to a mediator page/view that provides them an overview where you ask them to double check their entries before the final submit.

And if you want to take it to the next level, you can add a dialog box on checkout that asks "Are you sure you have checked your entry" but that will most likely freak them out.

Hope this helps :)