Mark as complete button is not intuitively placed

[mvl22]

In making amendments to almost-ready application, I found myself using the "Mark as complete" button quite a bit.

However, the intuitive action is to press the significantly more dominant "Save and return to application overview" button instead, which reverts the question state from complete back to to incomplete, which is unlikely to be the user's intention. Furthermore, "Mark as complete" does not clearly imply that saving and returning the to application overview is incorporated.

Although the two buttons could be side-by-side:

[[Save and return to application overview]] or [[Mark as complete]]

However, I think this gives rise to other usability issues, namely that still the save & return action is not clearly incorporated.

A better solution might be to use a checkbox to allow the user to set the state, which has memory from its previous state (i.e. editing having marked as complete retains the checkbox, unless the word length overflows). The checkbox is essentially an attribute as an adjunct to the primary action, which is to save the page. At present, the primary action that the user performs thus moves inconsistently from one button to the other based on whether the text is complete or not. Thus perhaps this could be reworked along the lines of:

[ ] Mark as complete

[[Save and return to application overview]]

A further problem with the current UI is that, when a form includes a document upload, Mark as complete comes before that (i.e. between the richtext and the document upload) rather than after both, and that Mark as complete is very strongly visually associated with the richtext form (e.g. its close placement and background highlighting), whereas it actually sets the status in respect of the presence of a document also.

Again, this lends itself to an approach of using a status-setting checkbox just before the submission button.