---
id: DFMOD-C2-POS-001
title: "Save scope follows the Save button location, not where edits were made"
product: web
module: digital-form
type: functional
priority: P0
risk: critical
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C2
  tsdScenario: C2.1
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C2.1; 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
  - save-scope
  - client-portal
  - pk141
  - staging
---
## Objective
Verify which steps are committed depends on the Save button used, not where edits occurred.

## Preconditions
- See [[PRE-DF-cp-editing-form]]
- And the user has changed data across several steps

## Steps
1. Click Save in Step 1
2. In a separate run, click Save in Step 4
3. In a separate run, click Save in Step 5

## Expected Result
- Then Save in Step 1 persists only Step 1 data; Step 2 and Step 3 changes are not persisted
- And Save in Step 4 commits Step 1, Step 2, and Step 3 changes
- And Save in Step 5 commits all changes from Step 1 to Step 5

## Source Traceability
- TSD: PK141
- Section: C2 - Save Scope
- Scenario: C2.1 - Save scope follows Save button location
- Acceptance Criteria: PRD C.5 Scenario 1-4, C.6 Scenario 1-5, C.7 Scenario 0-5

## Evidence Required
- Backend diff per Save location.

## Notes / Gaps
- Mixed/invalid-step behavior is covered by DFMOD-C2-EDGE-002. Testing Concern TC-01 (High): Step 4 vs Step 5 save contract for mixed edits not fully finalized.