Workbook collection and resubmission guide

Collect a workbook consistently: validation, return requests, and row-only resubmission

Set the column contract before distribution, validate returned values, and return only invalid rows. Keep accepted rows out of the resubmission.

Set the four-column contract

record_id and sku are required strings. status is required and must be active or inactive. note is optional. Keep the contract ID, revision, and submission ID distinct.

ColumnRequiredCondition
record_idyesstring
skuyesstring
statusyesactive / inactive
notenostring

Input rules are not validation

Paste operations can introduce an enum value outside the contract. If a large ID has already rounded in Excel, it cannot be reconstructed from the workbook. Confirm the original source. A saved file is not proof of acceptance.

Collect six rows from three people

Receive A01/A02, B01/B02, and C01/C02 with submission IDs. A’s two rows, B01, and C01 are accepted. B02 has an invalid status and C02 has a blank SKU, so both are returned.

RowsConditionResult
A01 / A02validaccepted
B01validaccepted
B02status pendingreturned
C01validaccepted
C02blank SKUreturned

Write the return request

For B02, ask the person to confirm and re-enter active or inactive. For C02, ask them to confirm the missing SKU from the original source. Do not ask AI to guess an unknown value.

Resubmit two rows only

Use the confirmed B02 value inactive and C02 value 0006. The resubmission ID set is B02 and C02 only. Do not mix the four accepted rows into it. Match the original record ID to the new submission ID.

resubmission IDs: B02, C02
B02: inactive
C02: 0006
accepted rows resubmitted: 0

Carry forward only the useful scope

Reuse the template revision, column mapping, and return conditions. All materials are synthetic and contain no personal data, hidden sheets, macros, upload, or fabricated system acceptance.