CCS Workflow
Use this as the project-management skill for a CCS submission. CCS is a conference, not a
journal: it has no editor-in-chief and no article-processing charge. The rotating leadership
is the per-edition General Chairs and Program Co-Chairs (CCS 2026 Program Co-Chairs: Véronique
Cortier and Zhiqiang Lin, reported 2026-07-08; verify against the organizing-committee page).
Replace every date below with the current cycle's HotCRP deadlines and work backward.
The dual-deadline cycle
CCS runs two review cycles per year into one conference. A paper enters one cycle only; work
rejected in the first cycle may not be resubmitted (even revised) to the second cycle of the
same year. Pick the cycle from readiness, not hope — a thin first-cycle submission burns the
year at this venue.
- CCS 2026 (The Hague, Netherlands, Nov 15-19, 2026) Cycle A: abstract registration Jan 7,
full paper Jan 14, rebuttal Mar 17-20, notification Apr 9, 2026 (verify).
- CCS 2026 Cycle B: abstract registration Apr 22, full paper Apr 29, rebuttal Jun 29-Jul 1,
notification Jul 17, 2026 (verify). Camera-ready reported Aug 21, 2026.
- Both 2026 deadlines have passed as of 2026-07-08; treat them as a template and read the
CCS 2027 CFP when posted (CCS 2027 host city was still under steering-committee selection).
Milestones
- Venue fit: confirm the contribution is a broad security result for the SIGSAC PC.
- Evidence lock: freeze threat model, attack/defense implementation, adaptive evaluation,
measurement validation, and the ethics/disclosure posture.
- Abstract registration: mandatory title, authors, abstract, and topics in HotCRP before the
registration deadline; no paper without a registered abstract.
- Full-paper deadline: upload the anonymized 12-page ACM sigconf PDF plus appendices.
- Rebuttal window: respond to reviews in the short author-response period.
- Notification: accept, minor revision (revise within the cycle), or reject.
- Artifact evaluation: submit artifacts after acceptance for ACM badges if you opt in.
- Camera-ready and registration: ACM proceedings version, then in-person presentation.
Backward plan from the full-paper deadline
| Weeks out (heuristic) |
Attack-plus-defense milestone |
| 10+ |
Threat model frozen, attack primitive working end to end |
| 8 |
Defense implemented; adaptive attacker designed against it |
| 6 |
Measurement or evaluation runs complete, environment logged |
| 4 |
Ethics and responsible-disclosure section drafted, disclosure initiated |
| 3 |
Full draft in ACM sigconf two-column format |
| 2 |
Internal red-team read by an adversarial-minded colleague |
| 1 |
Anonymity sweep, artifact-availability statement, appendix assembly |
| 0 |
Abstract registered, then full paper in HotCRP |
Anchor every offset to the current cycle, never to a past calendar.
Big-four deadline-hopping
CCS, IEEE S&P, USENIX Security, and NDSS run rolling multi-cycle deadlines, so a paper
rejected in one can often be reworked into the next open venue within weeks. Keep a live map:
a CCS Cycle A reject in April can target USENIX Security or the next NDSS cycle rather than
waiting a year. Never resubmit unchanged — reviewers rotate across all four venues.
Coordination notes
- Assign one owner for the ethics/disclosure section and another for the anonymity sweep;
shared ownership is how both slip.
- Archive the exact submitted PDF and appendices, since rebuttal replies must quote them.
Output format
[Current stage] idea / building / writing / abstract / submission / rebuttal / accepted / artifact
[Cycle] A / B and next official deadline (date + source, or unknown)
[Critical path] <three tasks that determine readiness>
[Risk register] <threat-model / anonymity / ethics / evidence / artifact / presentation>
[Owner map] <task -> person or role>
Source: brycewang-stanford/Awesome-Journal-Skills → ACM-CCS-Skills/skills/ccs-workflow/SKILL.md
1---2name: ccs-workflow3description: Use when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification, revision, artifact evaluation, ACM camera-ready, and in-person presentation, with backward-planning offsets and the security big-four deadline-hopping calendar.4---567# CCS Workflow89Use this as the project-management skill for a CCS submission. CCS is a conference, not a10journal: it has no editor-in-chief and no article-processing charge. The rotating leadership11is the per-edition General Chairs and Program Co-Chairs (CCS 2026 Program Co-Chairs: Véronique12Cortier and Zhiqiang Lin, reported 2026-07-08; verify against the organizing-committee page).13Replace every date below with the current cycle's HotCRP deadlines and work backward.1415## The dual-deadline cycle1617CCS runs two review cycles per year into one conference. A paper enters one cycle only; work18rejected in the first cycle may not be resubmitted (even revised) to the second cycle of the19same year. Pick the cycle from readiness, not hope — a thin first-cycle submission burns the20year at this venue.2122- CCS 2026 (The Hague, Netherlands, Nov 15-19, 2026) Cycle A: abstract registration Jan 7,23 full paper Jan 14, rebuttal Mar 17-20, notification Apr 9, 2026 (verify).24- CCS 2026 Cycle B: abstract registration Apr 22, full paper Apr 29, rebuttal Jun 29-Jul 1,25 notification Jul 17, 2026 (verify). Camera-ready reported Aug 21, 2026.26- Both 2026 deadlines have passed as of 2026-07-08; treat them as a template and read the27 CCS 2027 CFP when posted (CCS 2027 host city was still under steering-committee selection).2829## Milestones3031- Venue fit: confirm the contribution is a broad security result for the SIGSAC PC.32- Evidence lock: freeze threat model, attack/defense implementation, adaptive evaluation,33 measurement validation, and the ethics/disclosure posture.34- Abstract registration: mandatory title, authors, abstract, and topics in HotCRP before the35 registration deadline; no paper without a registered abstract.36- Full-paper deadline: upload the anonymized 12-page ACM sigconf PDF plus appendices.37- Rebuttal window: respond to reviews in the short author-response period.38- Notification: accept, minor revision (revise within the cycle), or reject.39- Artifact evaluation: submit artifacts after acceptance for ACM badges if you opt in.40- Camera-ready and registration: ACM proceedings version, then in-person presentation.4142## Backward plan from the full-paper deadline4344| Weeks out (heuristic) | Attack-plus-defense milestone |45|---|---|46| 10+ | Threat model frozen, attack primitive working end to end |47| 8 | Defense implemented; adaptive attacker designed against it |48| 6 | Measurement or evaluation runs complete, environment logged |49| 4 | Ethics and responsible-disclosure section drafted, disclosure initiated |50| 3 | Full draft in ACM sigconf two-column format |51| 2 | Internal red-team read by an adversarial-minded colleague |52| 1 | Anonymity sweep, artifact-availability statement, appendix assembly |53| 0 | Abstract registered, then full paper in HotCRP |5455Anchor every offset to the current cycle, never to a past calendar.5657## Big-four deadline-hopping5859CCS, IEEE S&P, USENIX Security, and NDSS run rolling multi-cycle deadlines, so a paper60rejected in one can often be reworked into the next open venue within weeks. Keep a live map:61a CCS Cycle A reject in April can target USENIX Security or the next NDSS cycle rather than62waiting a year. Never resubmit unchanged — reviewers rotate across all four venues.6364## Coordination notes6566- Assign one owner for the ethics/disclosure section and another for the anonymity sweep;67 shared ownership is how both slip.68- Archive the exact submitted PDF and appendices, since rebuttal replies must quote them.6970## Output format7172```text73[Current stage] idea / building / writing / abstract / submission / rebuttal / accepted / artifact74[Cycle] A / B and next official deadline (date + source, or unknown)75[Critical path] <three tasks that determine readiness>76[Risk register] <threat-model / anonymity / ethics / evidence / artifact / presentation>77[Owner map] <task -> person or role>78```7980---8182**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `ACM-CCS-Skills/skills/ccs-workflow/SKILL.md`
thedixitjain