Batch intake

An operator receives a file for an organization and creates a batch with a number, name, import date, owner and validation definition. The source hash identifies the submitted material and the revision identifies the version under review. Keep those identities together before any row is checked. If another file arrives with the same business purpose, decide whether it is a new batch or a successor revision before staff begin review.

• Batch identity. Record the number, import date, organization and owner before adding results.
• Source version. Keep the hash and revision together so a corrected submission is identifiable.
• Supporting material. Attach the sender document to the batch when the team needs to verify its origin.

The Import Operator uses the same batch number when discussing a submission with the Validation Steward. The owner reference identifies the person responsible for resolving source questions; the organization identifies whose data is being received. A replacement file changes the source hash and revision, while the earlier submission remains available for review. The validation definition is selected before parsing so every row result can be tied back to the rule set used for that revision.

The owner checks the row count against the submission and attaches a source document when the sender supplied one. The organization and definition should already be active and agreed with the validation steward. A batch marked Uploaded is ready for parsing; its accepted and error counts belong to the resulting review, not to a guess made at intake.

Agree how the sender identifies its submissions and how staff decide whether a replacement is a new batch or a successor revision. Name the Import Operator who records the batch and the Validation Steward who confirms its definition. An incoming row needs a source record identifier that can be matched to a later validation result. Keep the sender document with the batch if it is needed to verify the source.

Suppose an organization sends a corrected file after an operator recorded an initial import. The team compares the source hash and revision, preserves the earlier batch evidence and places the replacement under the right owner. The reviewer then has a clear subject for the decision.

In the rehearsal, compare the original and corrected source hashes, revision numbers and documents. Open the row results for each version and show the Independent Reviewer which revision is ready for a decision. If the new material cannot be tied to its sender, keep it at intake until the owner establishes that identity.

• Incoming Batches — See uploaded and parsed submissions with their organization, owner and selected definition.
• Batch Board — Compare open batch statuses before assigning the next intake task.

See the related process and the data model to rehearse this handoff with a real submission.