Which statement is true about the Unassigned Variation table usage?

• A. It must be checked daily for new unassigned variations and must be assigned before the EFD.
• B. It updates only weekly.
• C. It never changes.
• D. It is used only during audits.

Answer: (A)

Managing unassigned variations hinges on timely ownership and a clear deadline-driven workflow. The statement is true because the table should be reviewed every day for new unassigned variations and those variations must be assigned before the EFD deadline. Daily checks keep new issues from piling up, ensure accountability by showing who is responsible for each variation, and help keep the work moving smoothly rather than letting items linger unaddressed. Assigning before the EFD ensures there is an owner in place and that the variation can be resolved in time, avoiding last‑minute scrambling or missed targets. The table is a live, continually updated record: new entries appear as they are reported, and once assigned they exit the unassigned view. If it were updated only weekly, or never changed, or only used during audits, it wouldn’t provide timely visibility or ownership, leading to delays and confusion.