Who has read an announcement

Every announcement you have posted keeps a list of the judges it went to and which of them have opened it. That is the Read receipts screen, and it is the whole of what FilmScorecard knows about one announcement after it was sent.

It reports reading, not delivery. There is no sent, failed or bounced state anywhere in FilmScorecard, because the delivery is the copy in the judge's inbox and that cannot fail per person. What this screen adds is whether they have opened it. Writing and posting announcements is on Announcements.

Finding the screen

From the Announcements list, on any Sent row: click the subject, or choose Recipients from its three-dot menu.

Its address is:

/org/<organization>/<festival>/<season>/announcements/<id>/recipients

A draft has no receipts screen. Nobody has received it, so the address answers "page not found" — as it does for anyone without the Manage judges and assignments permission on the season, and for every judge. See Who can work here.

Your search and the Read filter live in the address, so a narrowed view survives a reload and can be sent to a colleague.

The header

Under a back link to the announcement list: the subject as the heading, and beside it the audience pill, a green Sent pill, a quiet Archived chip if you have archived it, Sent by whoever posted it, and the announcement's ANN- number.

Two buttons: Export CSV and View as a judge. There is nothing else to press — no resend, no retry, no reminder.

The three counts

All three count the same set of rows, so Read plus Unread always equals Recipients, and the cards can never disagree with the table under them.

Read means opened in FilmScorecard. A judge is marked read when they open the announcement in their judging inbox — nothing else does it. Somebody who read your email and never signed in still shows as Unread, and that is the honest reading: unread here means "has not opened it on FilmScorecard", not "has not seen it".

Two more things the number does not mean:

• Nobody joins the list afterwards. Recipients were settled when you posted; a judge added to the roster the next day is not on it and never will be.
• On sample data the count on the announcements list and the Recipients card can differ. Anything you posted yourself agrees exactly — both numbers come from the same act.

The table

One row per recipient.

Times are in universal time (UTC), not your local time zone, and read Aug 17, 09:12.

Every column heading sorts; click again to reverse. It arrives sorted by recipient name; Read at opens newest first, and recipients who have not read it sort to the end whichever way that column points.

• The search box matches a recipient's name and email address.
• Read is a three-way switch: Any, Read, Unread.
• Clear filters appears whenever either is set.

Nothing here is selectable and no row has a menu — there is no per-recipient action to take.

The line at the foot names what you are looking at — "24 recipients of 24, by recipient ascending". A filter that matches nobody leaves a line inside the table saying so, with Clear filters.

On a very large jury the table loads the newest 1,000 recipients and says so plainly — "Showing 1000 of 1240 recipients … Export CSV includes every recipient." The counts above stay right regardless.

Export CSV

Export CSV is a plain download: press it and the file arrives. Nothing is emailed and nothing runs in the background.

• It matches what you are looking at — the same search and the same Read filter as the table.
• It is never truncated, even past the 1,000 rows the table shows.
• Columns: Recipient, Email, Seat, Read, Read at. Read at carries the full stored timestamp rather than the short form on screen, and is blank for anyone who has not read it.
• A name or address that begins with =, +, - or @ is written with an apostrophe in front of it, so a spreadsheet shows it as text instead of running it as a formula.
• The file is named after the announcement and the day you pressed: ann-1046-recipients-2026-08-19.csv.
• A filter that matches nobody still produces a file with its heading row.

There is nothing in the file about delivery, and no column for the courtesy email — FilmScorecard does not track it.

View as a judge

View as a judge opens the judge's own copy, exactly as it arrives on their side: the festival and season line, the subject, your name and the word Coordinator, the date you posted, the message, and the line telling them how many judges it went to.

• Nothing on it is editable, and nothing is interactive.
• The card is the same for everybody. The Viewing as picker at the top changes only whose name and address is shown above the card — every recipient receives identical words, and no judge's copy names another judge.
• The same preview is on any sent row's menu on the Announcements list.

What this screen does not tell you

• Whether the email arrived. No sent state, no bounce, no failure — and nothing anywhere retries or resends one.
• What a judge did next. Reading is the only per-recipient fact recorded.
• Anything about their scoring. Nothing on this screen touches scorecards.

And there is nothing here that acts on a recipient: no resend, no reminder, no "nudge the unread", and no way to add somebody to an announcement that has already gone out. If a judge needs to be told again, post a new announcement — Duplicate writes the next version from this one.

Related guides

• Announcements — writing, posting, drafts, duplicates and archiving.
• Your inbox — the judge's side: what an announcement looks like when it arrives, and what marks it read.
• Judges — the roster the Seat column reads from.