The symptom is specific: editors receive drafts without sources. Start with the affected item and identify the decision or input that could produce this behavior.
Find the likely cause
Generation and evidence collection are treated as separate work.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Attach the source packet and unresolved claim list to the draft.
A reliable handoff tells the next person what is complete, what remains uncertain, and what action is required.
Check that the repair worked
The editor should be able to verify important facts immediately.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: aI drafts are marked ready despite open questions. Define what must be true before each stage transition.
Monitor the useful outcome
Track returned handoffs, waiting time, and missing information discovered downstream.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.