Record which submitted part needs correction
The synthetic submission SUB-B has three sections. The receiving operator accepts sections A and C but identifies a missing source note in B. The project’s internal task rule uses submitted, correction-needed and complete states; submission alone is not completion. This is not a contract acceptance decision.
| Section | Observation | Next state |
|---|---|---|
| A | Accepted as submitted | Retain completed part |
| B | Source note missing | Correction COR-B |
| C | Accepted as submitted | Retain completed part |
Recheck the correction and retain the original submission
- Record received SUB-B
- Identify B correction
- Return exact scope to author
- Submit corrected B linked to SUB-B
- Receiver checks B before closing task
A newly requested section D is a separate change request, not a correction of the missing B note under this record.
Two of three sections remain accepted while B is corrected. Keep SUB-B as the original event and COR-B as the unfinished action so activity history remains understandable.
After B is returned, how many accepted sections must be redone under the supplied scope?
Show the worked answer
Zero. Only B needs the source note; A and C retain their accepted state unless another specific issue is found.