Add / Edit Consistency Checklist
Add and Edit for the same entity must be identical in behavior, validation, layout, and error handling. A user should not be able to do something in Edit that Add prevents, or vice versa.
Back to Frontend Checklist
0/0 completed
Core Rule
The Consistency Rule
A teammate comparing Add and Edit must see the same fields, same validation rules, same error messages, same layout, and same loading and success behavior.
| Difference | Allowed | Why |
|---|---|---|
| Page or modal title | Yes | Context label only |
| Submit button label | Yes | Action wording only |
| Pre-filled values in Edit | Yes | Existing data is loaded |
| Some fields disabled in Edit | Only if intentional | Documented business rule required |
| Additional Edit-only fields | Only if they do not exist at creation time | Examples: created_at, post-creation status |
Live Add / Edit Example
Add Project
Edit Project
| Behavior | Add | Edit |
|---|---|---|
| Fields | Name, Status, Description | Name, Status, Description |
| Validation schema | Shared | Shared |
| Field order | Same order | Same order |
| Spacing and layout | Shared component | Shared component |
| Button wording | Create Project | Save Changes |
Field Consistency
Validation Consistency
UI and Layout Consistency
Pre-Fill Behavior (Edit Only)
Good Edit Loading State