Which Papers Have No Registered Author?

Every conference has the same rule: at least one author of each accepted paper must register, or the paper drops from the program. Answering the simple question — which papers don't have a registered author yet? — may take hours of manual cross-referencing, and the answer is still wrong.

Problem 1: Authors and Registrants Often Live in Different Systems

The author list comes out of the submission system. The registrant list comes out of the payment platform. They're filled out months apart, by the same people in different moods, and they don't auto-sync.

Problem 2: Cross-Referencing by Hand is Tedious and Error-Prone

Take a 300-paper conference with 800 registrants. That's roughly 900 author rows to scan against an 800-row registrant list — hours of focused work. And even when a chair is paying attention, the same person shows up looking like a different person:

The failure modes are bad either way: chase someone who already paid (trust erodes), or skip someone who didn't (paper drops from the program).

PaperFox solves both problems.

Solution 1: One System

Two ways to bring registration data into PaperFox alongside your submissions.

(a) Run registration on PaperFox. Configure registration types, point attendees at the registration page, and PaperFox handles Stripe payments, badges, and confirmations end-to-end. The registrant list and the author list share a database — no second system, no reconciliation. Simple workflow, simple transparent and competitive pricing.

(b) Import data from your existing registration platform. If registration runs through another system — Eventbrite, your university's registration system, a custom form, anything that can export a CSV — bulk-import it into PaperFox. The smart importer dedupes by email, so you can keep re-uploading as new registrations come in. Those rows land as External Registrants alongside native ones.

Solution 2: Auto-Match

Three layers, in order:

1. Exact email match. Author's email matches a registrant email → paper is covered. Handles the easy 70–80% with no chair input.
2. Fuzzy match. For everyone else, PaperFox compares the author's name and identity hints against every registrant. Name similarity is Jaro-Winkler on tokenized names (so "Tony Lin" matches "Jianhui (Tony) Lin"); identity hints are institutional email domain (nyu.edu ↔ stern.nyu.edu counts as a partial match because they share the nyu base), ROR id, or distinctive affiliation tokens after stripping stopwords ("Nova" matches between "NOVA School of Business" and "Nova SBE"). Consumer domains like gmail and outlook are denylisted — sharing those means nothing. The matcher tunes toward false positives because dismissing a wrong suggestion is one click; missing a real registration sends a needless reminder.
3. Chair confirms. Every fuzzy suggestion appears inline on the Author Registration Coverage report with two buttons — Confirm match or Not a match. Every decision is reversible from a dedicated Matching Decisions page.

Under this system, the four cases above resolve as:

All four surface as "potential match" for one-click chair confirmation.

Before and After

---

Related Docs

• Author Registration Coverage — How to use the report end-to-end
• Import External Registrants — Pulling in registrants from outside PaperFox
• Fixing the Affiliation Data Mess — Companion piece on cleaning up the source data