Sync & A&R workflow.

You have a catalog. A supervisor asks for "indie-leaning, cinematic, mid-tempo." You build a reel, send it, watch the listens roll in, follow up on the tracks they played twice. Cue maps to that shape:

• ·Library — your catalog of record (every upload, every metadata field).
• ·Collection — the reel you build for one supervisor / pitch.
• ·Presentation — the public, branded page they actually open.
• ·Share link OR public /p/<slug> — the URL you paste into the email.
• ·Events — Cue records each play, each share visit, with timestamps.

Open /collections. Name the new one for the specific brief ("Brief — Sundance trailer cut, Apr '26" beats "untitled-3" every time). Add tracks via the inline picker — search by title, ISRC, BPM, or any custom field you've defined.

Reorder until the front of the reel is your strongest + most-on-brief. Supervisors triage with the first 30 seconds; lead with that.

Click into /presentations → "new". Title it for the brief. Drop the audio in the tracks panel; the page inherits its own collection automatically. Cover image (a still from the spec the brief referenced is a nice touch). Paragraph of context — one or two sentences, not three. Publish.

The URL is now a real page, not a Drive folder. Paste it into the email.

Cue logs share.viewed + share.play events as they happen. The activity feed in the workspace shows them in real time. If your supervisor played track 3 three times, that's the one you follow up on.

A presentation visit is also pre-attributed: visits while a guest session cookie is set carry a name + email; otherwise they're anonymous-by-IP-hash so you can still cluster "person played this five times across the week."

Supervisor wrote back interested in two cuts? Make a new round on those two tracks (or on the original collection — Cue doesn't care). Send the supervisor or the sync coordinator the Collab link. Now they can leave timed notes on a specific 8-bar lift, and you can run the engineer feedback on the same surface.

That's the Cue advantage — the pitch and the review-after-interest happen in one workspace, not two.

Per-recipient share tokens carry the recipient's name + email and can be revoked individually. The deal closes; you revoke the supervisor's token. Their URL 404s without invalidating anyone else's.