WEEKEND READ

Build a weekend-read packet

3 min read · Updated Jul 2026 · Applies to all plans

The weekend read is the Friday ritual: gather the week's most promising material into one thing to hand an exec. In CoverQueue you flag as you go, curate the list, and build a packet, for reading in-app or for sending out as a watermarked link.

Flag as you go

In the submission log, flag any row to the weekend read: press w on a selected row, or use the flag icon. Flagged items collect into a queue you can review before you send. Flagging throughout the week beats scrambling on Friday.

Curate the queue

The Weekend Read screen shows your flagged items as reorderable cards: title, writer, format, and a verdict chip if coverage is in. Drag to set the reading order, and drop anything that no longer belongs before you build.

Tip

Order matters for the exec's experience: put the strongest or most time-sensitive scripts first so they're read even if Friday runs short.

Build the packet

Click Build packet and choose how it goes out:

  • Internal: a full-screen reading queue for the exec: step through scripts or coverage in order, with a quick note per item. Mobile-friendly for reading on the couch.
  • External share link: pick contents (scripts, coverage, or both), a recipient label, and an expiry (default 7 days). This creates a tokenized link, and every included item is watermarked per recipient.
Build packet
  Contents    Scripts + coverage
  Deliver     ○ Internal (reading queue)   ● External link
  Recipient   Daniel Cho
  Expires     in 7 days

Packet creation takes under a minute, and external items are pre-stamped so the recipient's first click is instant.

Heads up

An external packet is delivered like any share link: watermarked and logged. See How watermarking works and Create and revoke share links.

Common questions

How do I remove something from the queue? Unflag it from the card or the log row; it drops out of the packet.

Does the exec need an account? Internal reading uses their CoverQueue account; an external link needs no login at all.

Can I send to more than one exec? Build a packet per recipient so each gets its own watermarked, separately revocable link.

Was this helpful?