Practice a limited crew-readiness check

First step

Build a fictional three-role roster using labels only: issued apprentice license, pending application, and unverified status. This is a readiness exercise, not hiring or employment-law guidance. Fictional example: add a first-hire readiness table with license-status evidence reference, proposed supervisor, task or site-assignment question, training owner, work-record owner, unresolved hiring obligation, and next verification date. Leave any assignment pending when authorization or supervision is unverified; this is not an employment-law checklist. Changed-condition retry (fictional): the issued-apprentice row's license status is now confirmed against a dated placeholder evidence reference, but that row's supervision arrangement is still unstated; the pending and unverified rows are unchanged. Update the roster and state exactly which cells change.

The roster distinguishes actual issued authorization from an application and from a status not yet checked. Issued, pending, and unverified licenses lead to different assignment statuses; every proposed supervisor and training task has an owner. Retry result: only the issued row's license-status cell becomes confirmed, with its placeholder evidence reference and check date; that row's assignment stays pending because supervision is unstated, and the pending and unverified rows stay not ready with their owners and next verification dates.

All three role labels are assigned the same ready status because they appear on the roster. First retry error: one confirmed license check marks the row ready, or its check date is treated as closing the supervision question; correct it by closing only the license-status cell and keeping supervision and assignment open.