Handling duplicates and new drafts
Scripts come around more than once: a new draft of something you read last year, or the same project pitched by two reps. CoverQueue helps you notice, and links revisions together so the earlier read is never lost.
The "possible prior submission" banner
When you log or confirm a submission, a dedupe check runs in the background. If it finds a likely match (by normalized title and writer-name similarity), a non-blocking banner appears on the submission:
Possible prior submission:
GLASSHOUSE by Marcus Bell, covered Nov 2025, verdict Pass. View coverage →
It never blocks you or slows down logging; the banner just appears when the check finishes, with a link to compare.
Seeing "did we cover this?" answered in seconds is one of the core reasons to keep everything in one log. The banner surfaces the earlier verdict right where you're working.
Version chains for re-sent drafts
When the same script is re-sent (for example a rep forwards a revised PDF), CoverQueue links it into a version chain rather than creating an unrelated duplicate. The submission and the writer both show the chain, so you can move between drafts and see how the read evolved.
Email-in intake helps here too: attachments are hashed, so a re-sent draft links into the chain instead of duplicating.
Common questions
Is it the same file or a new one? A revised draft is a new submission linked to the prior one. A byte-identical re-send is recognized by its hash and won't create a stray copy.
Can I link two submissions myself? The chain is built from the prior-submission link; use the dedupe banner's compare view to confirm a match rather than logging the revision as unrelated.
Does re-covering a new draft touch the old coverage? No. The earlier signed coverage stays on record; see Amending signed coverage for how versions work.