Short answer: Split a long claims or onboarding form into steps when each step maps to one question about the case, save a draft on the server after every change, and show a field only when an earlier answer makes it relevant. Check Israeli ID and phone numbers in the browser for speed and again on the server for trust.
Key takeaways
- One step per decision: A step ends when one question about the case is answered, such as who is insured.
- Drafts belong in the data model: Autosave needs a draft status, an owner and a last-saved time on the server.
- Israeli formats have rules: A teudat zehut has nine digits including a check digit; a mobile number is 05X plus seven digits, or +972 without the zero.
- Accessibility is a legal duty: Level AA of IS 5568 includes WCAG criterion 3.3.4: checking, confirmation or reversal before a legal or financial submission.
Multi-step flow or a single page
The GOV.UK Design System tells teams to start with one question per page, and notes that internal services, where users repeat tasks, may group questions when research supports it. A policyholder filing a first claim gains from short steps; an underwriter reviewing applications all day wants one dense screen.
Many systems need both views of the same record. Settle this in the specification written before development, because it shapes the API and the data model, as it does when teams move an Excel process into a dedicated system.
Validation, conditional fields and Israeli formats
Run a check when the user leaves a field and put the message beside it. The server repeats every browser check, because anything a browser sends can be altered. Wording matters as much as the rule; see Hebrew microcopy for SaaS products.
| Field | Rule | Frequent mistake |
|---|---|---|
| Teudat zehut | Nine digits including a check digit; pad shorter input with leading zeros | Storing it as a number and dropping the leading zero |
| Israeli mobile | 05X followed by seven digits; +972 in international form | Rejecting numbers typed with dashes or spaces |
| Date | Day before month (6.11.2026) | US-style month first |
| Attachments | An allowlist of file types and a size limit | Trusting the file extension |
Conditional fields need readable rules, such as "if the vehicle was towed, ask who towed it". A hidden field is cleared or left out on submit, or a stale answer reaches the claim file. On phones, inputmode="numeric" opens a digit keypad; it validates nothing.
