---
title: "A Six-Order Practice Review: Fix the Entry or Flag the Source?"
url: https://memory.wiki/FK5t7SKb
updated: 2026-11-15T12:26:56.734Z
source: "api"
---
# A Six-Order Practice Review: Fix the Entry or Flag the Source?

Correct a data entry value when the source clearly supports the correction and the assignment permits it. When the source itself is unclear, leave the value unresolved and ask its owner; when the difference is only formatting, check the field rule before changing anything.

This fictional exercise gives a US beginner six nonpersonal order records to review. It focuses on the decision behind each flagged cell: what the source actually says, what the entry says, and whether the reviewer has enough authority and evidence to act.

O*NET OnLine lists comparing entries with source documents, locating and correcting errors or reporting them, and maintaining activity logs among the tasks associated with data entry keyers. The exercise below turns those tasks into a repeatable second pass; it does not assume every employer uses the same procedures.

## What rules apply to this practice batch?

Imagine six order slips labeled S1 through S6 and a separate entry sheet with rows 1 through 6. Each slip has an order ID, item code, quantity, order date, and unit price. The table below shows the one field flagged on each row; assume the other fields have been checked and match their sources.

For this exercise, dates must be entered as YYYY-MM-DD, prices as US dollars with two decimal places, quantities as whole numbers, and item codes exactly as written, including leading zeroes. The reviewer may correct a clear entry mismatch and apply these stated format rules. An unclear source must be referred to the fictional order owner, who can confirm the intended information.

The slip references and row numbers are deliberately paired, so the reviewer can trace each flag to a particular field. In an actual assignment, first establish how documents and records are matched, which version of a source controls, and who can answer questions. A correct-looking value from the wrong order is still a bad correction.

Row and field | Source slip | Entry before review | Finding

1: quantity | S1: 18 | 81 | Clear entry mismatch

2: item code | S2: 0047 | 047 | Clear entry mismatch; zero is part of the code

3: order date | S3: March 4, 2026 | 03/04/2026 | Same date, wrong required format

4: unit price | S4: $7.50 | 7.5 | Same price, wrong required format

5: quantity | S5: handwritten digit could be 3 or 8 | 3 | Source is ambiguous

6: item code | S6: printed A-120; handwritten note says A-129 | A-120 | Source contains conflicting values

## What should the before-and-after log show?

A useful log records the entry as it stood, the exact source location, the decision, and the reason. The following log is the result of the fictional second pass. A held value remains visible for review but is not treated as confirmed or ready for release.

Rows 1 and 2 are transcription corrections because the source is legible and the entered characters differ. Row 1 changes 81 to 18; the reviewer does not need to guess why the digits were reversed. Row 2 restores a leading zero because the exercise expressly treats the item code as text to be copied exactly. Treating it as an ordinary number would discard part of the identifier.

Rows 3 and 4 represent format changes, not changes to the underlying date or price. The written date removes any month-and-day ambiguity in this particular example, and the stated rule tells the reviewer how to render it. Similarly, 7.5 and 7.50 represent the same dollar amount here; the change supplies the required second decimal place.

Rows 5 and 6 stay open. Row 5 happens to contain one possible reading, but that coincidence does not prove it is correct. Row 6 matches the printed code, yet the conflicting note makes it unclear which value controls. Neither a majority vote nor an assumption that handwriting is newer resolves that conflict.

Flag and source | Before | After or status | Reason and next action

Row 1 quantity; S1 quantity | 81 | 18; corrected | Source clearly reads 18 and the assignment permits correction.

Row 2 item code; S2 item code | 047 | 0047; corrected | Source includes two leading zeroes; code must be copied exactly.

Row 3 order date; S3 date | 03/04/2026 | 2026-03-04; reformatted | Source spells out March 4; required date format is YYYY-MM-DD.

Row 4 unit price; S4 price | 7.5 | 7.50; reformatted | Source is $7.50 and the required price format has two decimal places.

Row 5 quantity; S5 quantity | 3 | 3 retained; held | Source could read 3 or 8. Ask the order owner which quantity was intended.

Row 6 item code; S6 printed code and note | A-120 | A-120 retained; held | Printed code and note conflict. Ask the order owner which code controls.

## How do you perform a traceable second pass?

Start by matching each entry row to its source using the assignment's designated identifier. Compare one field at a time, including leading zeroes, punctuation, units, and decimal places. Record the source location as well as the apparent difference; a note such as “row 2, item code, S2 item-code field” is more useful than “code looks wrong.”

Next, classify the difference before touching the entry. A legible source and a different entry point to a possible transcription error. A legible source that agrees in meaning but uses a different permitted representation points to a format question. An unreadable mark, missing information, or conflicting source statements point to a source problem. If a rule is missing, ask for it rather than deciding on a format by habit.

Make only the changes supported by the source and the stated rules. Record the old and new values, the reason, and the status. Then reread the corrected cell against the same source field: a second comparison can catch a correction typed into the wrong row or a new digit introduced during editing.

For an unresolved cell, preserve the original entry and follow the assignment's hold or escalation process. Send a specific question with the source reference and alternatives, without presenting either as the answer. For row 5, ask, “Does S5 specify quantity 3 or 8?” For row 6, ask, “Should the printed A-120 or the handwritten A-129 be used?” Record the response and its source before applying an authorized resolution.

If a real system cannot mark an individual cell as held, ask how the affected record should be handled. Do not quietly submit an uncertain value as verified, and do not erase the original entry merely to make the sheet look complete. The fictional log preserves it so another reviewer can see what was entered before the question was raised.

## Why not apply a blanket correction?

A blanket approach might make every flagged field look uniform quickly, but it treats different problems as though they have the same answer. Reformatting all dates and prices can be useful when a clear rule applies and the underlying values are known. It cannot tell a reviewer whether an unclear digit is 3 or 8, or which of two conflicting item codes the order owner intended.

The traceable second pass takes more attention because each change needs a source and reason. Its advantage is that another person can distinguish a corrected typo from a formatting change and can find the two questions that still need answers. The log also makes it possible to revisit a decision if the source or rule was misunderstood.

For a broader introduction to the work, the [Peaklivo data entry guide](https://peaklivo.com/guides/data-entry-jobs-from-home/) is a related next step after practicing the review. Keep this six-record exercise as a reusable template: establish the rules, compare each field to its source, correct only what the evidence supports, and leave a clear trail for the remaining questions.

## Sources

- [O*NET OnLine: Data Entry Keyers](https://www.onetonline.org/link/details/43-9021.00)

- [Source for: Treating an identifier such as 0047 as an ordinary number can discard its leading zeroes.](https://support.microsoft.com/en-us/excel/keeping-leading-zeros-and-large-numbers)


---

## Summary
Reviewers should correct data entry errors only when the source is clear and the assignment rules permit the change. If the source is ambiguous or contains conflicting information, the value must remain unresolved and be referred to the order owner for clarification.

## Themes
- data entry verification
- traceable review processes
- source document reconciliation
- error classification

## Key takeaways
- Corrections should only be applied when the source is clear and the assignment rules permit the change.
- Formatting changes are distinct from transcription corrections and require adherence to specific field rules.
- Unresolved source conflicts or ambiguous data must be referred to the order owner rather than guessed.
- A traceable second pass requires logging the original entry, the source location, the decision, and the reasoning for each action.

## Insights
- A correct value placed in the wrong row is still considered a bad correction.
- The presence of a majority vote or assumptions about handwriting age are insufficient methods for resolving conflicting source data.
- Retaining original entries for held items is necessary to maintain a transparent audit trail for future reviewers.

## Open questions / gaps
- How should a reviewer handle records when the order owner is unavailable or unresponsive?
- What specific system-level mechanisms should be used to flag records if the software lacks a hold status?

