# Fictional process notes: weekly content queue review
Process owner: Priya. Backup: Leo.
Trigger: the coordinator starts a weekly queue review; no automation is configured.
Input: content-queue.csv with item_id, owner, status, source_link, reviewer, approval_date.
Allowed statuses: Draft, In review, Approved, Blocked.

[P1] Preserve the received queue and work on a dated copy.
[P2] Check every item has an ID and owner. Missing values go to the issue list.
[P3] An Approved item must have a reviewer and approval_date. Otherwise change its status in the draft review to Blocked and explain why.
[P4] Check source_link is present. Do not open private links without the required access.
[P5] Priya reviews the proposed changes. If Priya is away, Leo reviews them.
[P6] Save the reviewed queue and issue list. Queue review does not authorize publication.
[P7] If the source file cannot be read, stop and request a readable copy; do not overwrite it.

Test case: Q-17 has owner Mina, status Approved, source_link internal-note-17, reviewer blank, approval_date blank. Priya is available.