Skip to content
Interface language: English
Design / Signal

A form completed over several sessions: returning to work already started

Design saving, return paths and final submission for forms completed over multiple sessions.

Article language: English

In a garden at night, a woman examines an illuminated white petal beside a sleeping cat.
In this article

You know the collection name straight away. Someone in production will check the dimensions tomorrow, and someone else will send the photographs. A form expecting everything in one sitting therefore assumes a working day your company does not happen to have. You can, of course, leave it open until tomorrow. Or you can design it so the browser does not have to serve as a note stuck to the monitor.

In a hypothetical example, a ceramics studio prepares to submit a new collection to a partner's catalogue. It must describe the models, attach materials and name a contact. Some information is ready on Monday, the rest on Tuesday. Preparing is not yet submitting. Saving, returning and the final button should preserve that difference.

Not every long questionnaire needs a separate draft system. First check whether people actually return, gather information or interrupt work because material is missing. If the form requires three simple answers, shortening it may be better. Remove unnecessary questions and dependencies first.

Dividing into parts should help people plan their work

List the information needed to submit the collection and the people it usually comes from. Contact details may be available immediately, dimensions need checking and photos need preparation. That is the basis for division. Splitting one long screen after every five fields produces equal panels but may not correspond to any stage of the customer's work.

Name parts by their contents or task. “Models and dimensions” lets people anticipate what they need. “Step two” only says the first has passed. Before starting, show what will be needed, what can be prepared later and when the collection will be considered submitted. People should be able to decide whether they can finish now.

The GOV.UK Task list component is intended for longer processes in which users need to choose the order of tasks. For a mandatory sequence, the guidance distinguishes that approach from saving and continuing where someone stopped. Length alone does not decide the choice.

Map dependencies for the fictional studio. Photos can be added before all dimensions are established, but describing a particular model requires its name. If parts are independent, let the customer choose the one they have data for. If an answer opens further questions, explain why the order is required. Do not pretend there is freedom by offering links to blocked pages.

A completion percentage can mislead here. Three of four sections checked does not mean a quarter of the work remains. Missing photos may take a day; contact details may take moments. The name of the missing material is more useful to someone planning a return than arithmetic performed on the number of screens.

At Aeneia Design, this layout belongs to content and interaction design. Begin by defining what action the form actually completes and how the system will know it saved a draft. Labels, views and implementation scope follow from those decisions.

“Next”, “save” and “submit” do different work

Moving to the next part does not necessarily mean data has been stored for later. Saving does not necessarily mean completeness, and completeness does not necessarily mean submitting the collection. Set out these meanings separately before naming buttons. Someone who has just entered a model name should know whether they can close the page and where to find the work they started.

If saving is automatic, show a recognisable result. A symbol that briefly disappears does not explain what was preserved. Distinguish editing, waiting for a save and a confirmed state. If the connection fails, the user should also recognise which changes have not yet been confirmed.

If a button initiates saving, place it where someone may actually interrupt work. A form that permits saving only after every field in a part is complete may prevent preserving exactly the work that needs finishing tomorrow. Decide whether an incomplete answer can stay in a draft and how it will be marked on return.

Final submission validation and draft saving have different purposes. A dimension may remain empty in a draft if the user does not know it yet. Submission requires that absence to be resolved. “Section complete” should therefore follow an agreed criterion, not just a page visit. An open screen does not prove a task was done.

In the trial, also save an answer that has begun but is not yet valid. A dimension might be a number followed by “to be checked”, or an unfinished value. Decide whether the draft keeps that text and how it distinguishes it from an approved parameter. Automatically deleting the working note deprives the user of information needed on return. Treating it as a finished dimension, on the other hand, carries uncertainty into the catalogue. That particular answer needs a clear status.

Check the version visible on re-entry. If a customer edits a description and immediately closes the tab, they must be able to judge on return whether they see the last confirmed save. Use a distinctive change in the trial, such as a note about a new model. Do not assess the save only by an earlier message; read the retained content.

In a form like this, attachments have their own states (in Polish) (article in Polish). A saved collection description can coexist with an unfinished photo upload. The draft summary should reveal the difference. On return, the customer needs to know whether to retry the transfer, select the file again or simply move to another part.

Returning begins before the page is closed

People need a route to the same submission. It could be an account, an agreed return link or another method available in the service. The choice should reflect the actual data flow and permissions. Do not promise “finish on any device” if the chosen method keeps material only in one browser.

Before leaving, give the draft a recognisable name. Someone working on several collections needs more than “untitled form”. A collection name, stage and last-save information may be enough to choose the right item. Also let them correct the name if it was provisional.

Aeneia conceptual photography

Test returning with two tabs open. An older tab may still show the old description although the customer added a model in the other. On resuming, the current saved version must be recognised before another edit replaces it. If an editing conflict (in Polish) occurs, offer a deliberate resolution (article in Polish). Silently retaining whichever version was clicked last does not explain whether the intended content survived. Also test what happens when the older tab is refreshed.

Returning after a session expires (in Polish) requires distinguishing loss of access from loss of data (article in Polish). Customers should not have to guess whether signing in again will delete their work. After access is restored, show the draft state and a clear next step. Do not send them through the entire form if returning to one missing section is enough.

Creating an account does not solve every problem either. In checkout without an account (in Polish) (article in Polish), the goal of the action is separated from additional registration. For a draft, likewise establish why identity is needed. It may support later access and protect work already started. Explain that connection instead of adding a requirement without a reason.

At our studio, the person gathering materials may need a colleague's answer, but that need not mean shared editing of one draft. Establish who owns it, who may open it and how missing information is passed on. If sharing is part of the agreed solution, show whose change was saved. If it is not, prepare clear instructions for the person assembling the submission.

Returning should also work when a user immediately chooses a section completed earlier. Do not treat it as closed forever. A customer may find a typo or receive newer material. Status should help plan the work, not turn the form into an exam in which the first question can never be revisited.

Tuesday's data may differ from Monday's

Suppose the partner changes the required way to describe a collection after the draft is saved. Some old data is still useful, but a new question appears. On return, explain what needs completing and why. Preserve earlier answers where they still matter. Deleting the whole draft because one condition changed transfers the cost of the update to the customer.

If submissions have a deadline, separately decide what happens to earlier drafts. Saved work does not reserve the ability to submit. After applications close, customers should see whether they can still read the material, download it or contact the partner. Do not leave an active button that leads only to a generic error. Show the deadline before they leave: people plan their return using the information they have just received.

Also test a changed answer within the form. The user initially selects the whole collection for submission in the form, then changes the choice to only two models. Photos and descriptions of the others must not quietly return to the sent package. Decide what has been excluded, what remains as draft work and what will need to be chosen again. The summary must reflect the current decision.

The GOV.UK Check answers pattern recommends retaining earlier answers during a correction and returning to the summary without revisiting the whole journey. If a change triggers new questions, ask them before that return. This specific condition helps plan correction in a branching form.

In the collection example, a newly required question might concern shared packaging for two models. Take the user there without deleting contact details or already selected photos. Then show the updated set. People should be able to check the effect where they will make the final decision, rather than merely trust that new questions were somehow accounted for.

Aeneia Design

Let us organise a form that takes several sessions. We will design its parts, saving, return route and final confirmation so customers can recognise their own work and the missing materials. Plan saving and resuming a submission

A finished draft still awaits a decision to submit

In the summary, show the answers needed to assess the whole, including an absence in an optional field. The user should understand whether they deliberately left something out or saving failed. Allow a specific part to be corrected and a return to the summary. Do not require the entire route to be repeated because one dimension changed.

The final button should name the effect. “Submit the collection for review” says more than another “Next”. After the action, distinguish an accepted submission, an uncertain outcome and the available next step. A saved draft may help recover material, but should not pass itself off as a new version of an already submitted case without explanation.

Decide what happens to the draft after submission. Does it become an available view of the submission, disappear from the list of started work, or provide a basis for another collection? These options need different names and behaviour. If a later correction is meant for the existing case, people should know how it will be linked to it.

Work waiting for a customer's materials (in Polish) (article in Polish) is not always a task accepted for execution. A draft remains preparation until the agreed handover occurs. Show that boundary to the team too. Otherwise the customer may think they are still collecting data while the partner starts awaiting a response in a case nobody decided to submit.

If a customer needs help preparing, offer a separate contact route about the draft. They can give a recognisable number and ask which photos to attach. The employee should then know they are helping before submission. Do not force an incomplete collection to be submitted just to get an explanation. Separate the help request from the action that actually transfers material for review; each needs its own confirmation.

Test returning with your own distinctive set of data. Interrupt work halfway, close the tab, return, correct an earlier choice and finish. Then compare the accepted submission with the last summary. Such a form test (in Polish) (article in Polish) shows whether saving really helps complete the task. A “save for later” button alone does not prove it.

A well-prepared return does not require a person to remember the form's state from Monday. On Tuesday they see their own data, understand what is missing and know what will happen after the last click. They can attend to the collection. Making sure a draft has not accidentally become a submission remains the design's job.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear