Dev.to WebDev 🛠 Dev 👁 0 📖 5 min read

Save Points for Law Firm Intake Forms: A Game Design Lesson

Anyone who played games before autosave remembers losing an hour of progress to a power cut or a missed save point. Modern game design treats that kind of loss as the game's fault. Progress is saved quietly at sensible m

Anyone who played games before autosave remembers losing an hour of progress to a power cut or a missed save point. Modern game design treats that kind of loss as the game's fault. Progress is saved quietly at sensible moments, and a crash costs a few seconds at most.

Law firm intake forms rarely get the same care. A person filling out a criminal defense contact form is often stressed, on a phone, and interrupted. A call comes in, the browser reloads, the screen locks, and everything they typed about the arrest is gone. Some will start again. Many will not. If you build sites for defense firms, a save point in the intake form is a small piece of work with a real payoff, as long as you handle the privacy side carefully.

What games get right about saving

Good save systems share a few habits. They save without asking, so the player never has to think about it. They save at natural checkpoints, such as entering a new area, rather than every frame. They tell the player when a save happened with a small, unobtrusive icon. And they make it easy to start fresh when the player wants to.

Each of those maps onto a form. Save quietly as the user types, at the moment a field loses focus. Show a short "Saved on this device" note. Offer a clear way to wipe the saved data. Restore it automatically if the page reloads.

The privacy problem games do not have

A saved game holds a character's inventory. A saved intake form can hold a description of an arrest, a charge, a court date and a phone number. That changes the design.

The device may be shared. A person might fill out the form on a family computer, a work laptop or a friend's phone. Anything stored in the browser can be seen by the next person who opens it. For that reason, persistent storage that survives closing the browser is a poor fit for defense intake. Session-scoped storage is a better default: in current browsers, sessionStorage data survives a reload but is cleared when the tab is closed, and it is not shared with other tabs.

It also helps to be selective about what gets saved at all. Contact details and simple choices, such as the type of charge from a dropdown, are the fields people most hate retyping. The long free-text description of what happened is the most sensitive. A reasonable compromise is to save the structured fields and leave the free-text box out, or to save it only if the firm decides the trade-off is worth it after discussing it with the lawyers.

A minimal implementation

Here is a small sketch using sessionStorage. It saves listed fields when they lose focus, restores them on load, and clears everything on submit or when the user asks.

const KEY = "intake-draft";
const form = document.querySelector("#intake");
const SAVED = ["name", "phone", "email", "charge_type", "county"];

function save() {
  const data = {};
  SAVED.forEach(n => { data[n] = form.elements[n]?.value || ""; });
  try { sessionStorage.setItem(KEY, JSON.stringify(data)); } catch (e) {}
}

function restore() {
  try {
    const data = JSON.parse(sessionStorage.getItem(KEY) || "{}");
    SAVED.forEach(n => { if (data[n] && form.elements[n]) form.elements[n].value = data[n]; });
  } catch (e) {}
}

function clearDraft() {
  try { sessionStorage.removeItem(KEY); } catch (e) {}
}

form.addEventListener("focusout", save);
form.addEventListener("submit", clearDraft);
document.querySelector("#clear-draft").addEventListener("click", () => { clearDraft(); form.reset(); });
restore();

The try blocks matter. Storage can throw in private browsing modes or when the browser blocks site data, and the form has to keep working either way. Clearing on submit should happen after you confirm the submission succeeded if the form posts by script, so a network error does not wipe the draft.

Telling the user what happened

Games show a spinning icon in the corner. A form can show a line of small text under the submit button that changes to "Saved on this device until you close this tab" after the first save. That one sentence tells the person their work is safe and tells them how long it stays. Next to it, a "Clear this form" link gives them control on a shared device.

Keep the message honest. Do not say "saved" in a way that suggests the firm has received anything. Only the submit button sends the information.

Making the form shorter matters more

A save point helps people who get interrupted. It does nothing for people who give up because the form asks too much. Before building any of this, look at which fields the firm actually uses at the first call. Some intake forms ask for date of birth, case number and a long narrative that the lawyer will cover by phone anyway. A guide to designing an intake form a frightened caller will finish goes through trimming the form itself.

Track the effect with your existing form analytics. Compare form starts with completed submissions for a few weeks before and after adding the save feature. Small sites will need longer to see a pattern.

Questions about saving intake form progress

Should the form use localStorage so drafts survive closing the browser?

For criminal defense intake, that is risky on shared devices. Session-scoped storage is the safer default unless the firm has a clear reason and tells users plainly.

Does saving in the browser send anything to the firm?

No. Data in sessionStorage stays on the device until the user submits the form.

Does the firm need to mention this in its privacy policy?

Ask the firm to review its privacy policy with whoever maintains it. Describing local draft saving in plain words is good practice.

SBD Marketing works only with criminal defense firms, one firm per city, and helps them with website design, SEO for the charges they defend, visibility in AI search tools and SEO audits. Its notes on UX lessons from video game design cover more ideas from games that apply to law firm sites.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.