A customer may approve the spelling while the shop still needs to check the file, blank and work area. Two approval states make that handoff easier to understand.
A practical check
Use one field for the customer proof version and another for operator readiness. The first can capture text, arrangement and date of approval. The second can identify the selected object, source file and setup check. Do not let a message saying looks good stand in for the operator review.
Keep the decision traceable
If the customer asks for a revision, return the proof to an open state and name the new file version. When the operator checks the job again, the record should point to that same version.
What this establishes
This small distinction helps a shop explain where an order is paused. It does not imply any particular production speed or result from the G1.
Explore related AntBelt preparation notes at /updates/.