USENIX Security Workflow

USENIX Security runs two independent submission cycles per year, so "when do we submit?" is a real strategic choice, not a fixed date. This skill turns a target cycle into a dated backward plan and assigns owners to the venue-specific risks. Dates below are the '26/'27 cycle values read on 2026-07-08 (via search renderings; usenix.org direct fetch 403'd) — reconfirm against the live CFP.

Step 1: pick the cycle

*Subject to the cycle's resubmission-restriction text — the '26 CFP delegated Cycle-2 reject restrictions to the '27 chairs, so verify before assuming a reject can re-enter (see usenixsec-review-process).

Reference calendar (verify per cycle):

Step 2: backward-plan from the registration date

Registration, not submission, is the first hard wall (it freezes title, abstract, authors, conflicts a week early). Plan backward from it:

T-12 wk  Topic/venue fit locked (usenixsec-topic-selection); threat model drafted
T-10 wk  Core experiments running; artifact repo scaffolded from day one
T-8  wk  Related-work sweep of all Big-Four cycles closed since last pass
T-6  wk  Adaptive-attacker / base-rate experiments (the ones that get demanded)
T-4  wk  Full draft; Ethical Considerations + Open Science appendices written
T-3  wk  Internal review + cold-reader pass on intro/threat model
T-2  wk  Anonymization sweep; artifact anonymous mirror live and tested
T-1  wk  REGISTRATION: freeze metadata; final polish only after this
T-0      Submit; re-download from HotCRP and read cold

The two moves teams most often leave too late: the adaptive-attacker experiment (defenses) and the ethics/disclosure timeline (live-system work). Both must start weeks before the deadline — a disclosure clock especially cannot be compressed, since vendors set the pace.

Step 3: assign the venue-specific risks

Step 4: run the post-submission and post-decision phases

• Waiting: expect the early-reject gate first (a survivable-but-quiet signal), then full notification. Do not start the next paper assuming acceptance, but do keep the artifact repo warm — acceptance starts the Phase-1 clock immediately.
• Shepherd approval: scope the change list within 48 hours; it fits a two-week window and no more (see usenixsec-author-response).
• Accept: run camera-ready and Phase-1 artifact availability in parallel — they share a deadline (see usenixsec-camera-ready).
• Reject: mine the reviews, check the resubmission restriction, decide between the next USENIX cycle and a sibling venue with an open deadline.

Coordinating across the Big-Four calendar

Because USENIX Security, CCS, S&P, and NDSS each run multiple deadlines, a lab can keep a paper in motion nearly year-round — but a paper may sit under review at only one archival venue at a time. Maintain a shared deadline board and a one-in-one-out rule per paper; the dual-submission bar is real and enforced.

Reverify each cycle

• All dates in the table above ('27 review/notification/finals are 待核实).
• Symposium location and dates for your target year.
• Resubmission restrictions gating cycle-to-cycle and year-to-year moves.

Output format

[Cycle chosen] which cycle + why (readiness / lead time / clash / runway)
[Backward plan] dated milestones from registration wall
[Risk owners] the five venue risks assigned + early mitigations underway
[Post-decision] branch plan for accept / shepherd / reject