---
id: DFMOD-C1-POS-003
title: "Edited state stays active even after a value is reverted to its original"
product: web
module: digital-form
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C1
  tsdScenario: C1.2
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C1.2; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-DF-cp-editing-form
tags:
  - web
  - digital-form
  - form-modification
  - edit-state
  - revert
  - client-portal
  - pk141
  - staging
---
## Objective
Verify the form remains in an "edited" state and Save stays enabled even after a changed value is reverted to its original.

## Preconditions
- See [[PRE-DF-cp-editing-form]]

## Steps
1. Change a field, then change it back to its original value
2. Navigate to another step

## Expected Result
- Then the system still treats the form as edited
- And the Save button stays enabled on steps that allow save

## Source Traceability
- TSD: PK141
- Section: C1 - Edited State
- Scenario: C1.2 - Edited state stays active after revert
- Acceptance Criteria: PRD C.1 Scenario 7-10

## Evidence Required
- Screen recording of revert + Save still enabled.

## Notes / Gaps
- A structural-field revert before save must still be distinguished from a no-change final state at version evaluation (see DFMOD-C2-EDGE-004).
