ICDE Workflow
Use this as the project-management skill for an ICDE research submission. Replace every date
with the current edition's official timetable and plan backward from the round you target.
ICDE is a conference, not a journal-of-the-conference: it has no standing editor-in-chief and
no article-processing charge. Leadership rotates per edition (General and Program Chairs named
on each icdeYYYY.github.io site), the cost model is registration, and accepted papers publish
in IEEE Xplore — not in a PACMMOD- or PVLDB-style venue journal. Re-check the current
organization page rather than carrying a name forward.
The two-round unit
Unlike SIGMOD's four quarterly PACMMOD rounds or PVLDB's twelve monthly deadlines, ICDE gives
you two shots per edition and no more. ICDE 2027's Round 1 paper deadline was June 11,
2026; Round 2 is November 11, 2026 with notification February 10, 2027. Because a Round 1
reject cannot re-enter Round 2, the round choice is a real commitment, not a convenience.
Milestones
- Venue and round fit: confirm the contribution is a data-management primitive and that the
chosen round is reachable without rushing the evaluation.
- Evidence lock: freeze the mechanism, workloads, baselines, scale grid, and the claims map.
- Paper deadline (CMT): upload the IEEE-format PDF plus supplemental material; file all
co-author conflicts.
- Review release: triage correctness, novelty, evaluation soundness, and reproducibility.
- Revision window (if invited): ICDE 2026 granted invited revisions a 4-week window
with a re-review before the final decision; budget for it or forfeit it (revision status for
the current edition is 待核实 — confirm).
- Decision: archive reviews, the revision, and the submitted versions.
- Camera-ready + Xplore: IEEE eCF/PDF-eXpress checks, copyright form, final artifact
release, registration, and in-person presentation.
Backward plan from the round paper deadline
| Weeks out (heuristic) |
Systems-paper milestone |
| 10+ |
System implemented; workloads and baselines chosen |
| 8 |
Scale grid running; measurement harness logging seeds and variance |
| 6 |
All main-result runs complete; crossover/cost analysis drafted |
| 4 |
Full draft sitting in IEEE two-column format |
| 3 |
Internal mock review by a builder who did not write the system |
| 2 |
Supplement assembled: run_all.sh, run_small.sh, README, generators |
| 1 |
CMT profiles + conflicts filed; page count and format sweep |
| 0 |
PDF and supplement in CMT before the round cutoff |
These offsets are planning heuristics — anchor each to the current important-dates page, never
to a past edition's calendar.
Revision-bandwidth reasoning
- If your target round can return a Revise & Resubmit, the honest question at submission time
is whether the team has four weeks of free bandwidth in the revision window; a revision
you cannot execute is a reject in slow motion.
- The two-round structure means a missed Round 1 pushes you to Round 2 of the same edition
(five months later) but a Round 1 reject pushes you a whole edition back — price both
outcomes before choosing.
Failure modes by stage
- Treating the two rounds as interchangeable and burning Round 1 on an unfinished evaluation,
losing the whole edition.
- Leaving IEEE format conversion to the final week, when two-column overflow surfaces late.
- Skipping the builder mock review — the one chance to hear "your baseline is untuned" from a
colleague instead of a reviewer.
- Assuming a revision window exists for the current edition without confirming it.
Output format
[Current stage] idea / building / measuring / writing / submission / revision / accepted
[Target round] Round 1 or Round 2 (edition), with next official deadline + source
[Critical path] <three tasks that determine readiness>
[Revision reserve] <weeks of bandwidth available if R&R returns>
[Risk register] <round-choice / format / evaluation / reproducibility / presentation>
[Owner map] <task -> person or role>
Source: brycewang-stanford/Awesome-Journal-Skills → ICDE-Skills/skills/icde-workflow/SKILL.md
1---2name: icde-workflow3description: "Use when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication."4category: research-and-academic5source_repo: brycewang-stanford/Awesome-Journal-Skills6source_path: "ICDE-Skills/skills/icde-workflow/SKILL.md"7source_url: https://github.com/brycewang-stanford/Awesome-Journal-Skills/blob/HEAD/ICDE-Skills/skills/icde-workflow/SKILL.md8metadata:9 source: https://skillmd.com/skills/thedixitjain/icde-workflow10---111213# ICDE Workflow1415Use this as the project-management skill for an ICDE research submission. Replace every date16with the current edition's official timetable and plan backward from the round you target.1718ICDE is a conference, not a journal-of-the-conference: it has no standing editor-in-chief and19no article-processing charge. Leadership rotates per edition (General and Program Chairs named20on each `icdeYYYY.github.io` site), the cost model is registration, and accepted papers publish21in **IEEE Xplore** — not in a PACMMOD- or PVLDB-style venue journal. Re-check the current22organization page rather than carrying a name forward.2324## The two-round unit2526Unlike SIGMOD's four quarterly PACMMOD rounds or PVLDB's twelve monthly deadlines, ICDE gives27you **two shots per edition** and no more. ICDE 2027's Round 1 paper deadline was June 11,282026; Round 2 is November 11, 2026 with notification February 10, 2027. Because a Round 129reject cannot re-enter Round 2, the round choice is a real commitment, not a convenience.3031## Milestones3233- **Venue and round fit:** confirm the contribution is a data-management primitive and that the34 chosen round is reachable without rushing the evaluation.35- **Evidence lock:** freeze the mechanism, workloads, baselines, scale grid, and the claims map.36- **Paper deadline (CMT):** upload the IEEE-format PDF plus supplemental material; file all37 co-author conflicts.38- **Review release:** triage correctness, novelty, evaluation soundness, and reproducibility.39- **Revision window (if invited):** ICDE 2026 granted invited revisions a **4-week** window40 with a re-review before the final decision; budget for it or forfeit it (revision status for41 the current edition is 待核实 — confirm).42- **Decision:** archive reviews, the revision, and the submitted versions.43- **Camera-ready + Xplore:** IEEE eCF/PDF-eXpress checks, copyright form, final artifact44 release, registration, and in-person presentation.4546## Backward plan from the round paper deadline4748| Weeks out (heuristic) | Systems-paper milestone |49|---|---|50| 10+ | System implemented; workloads and baselines chosen |51| 8 | Scale grid running; measurement harness logging seeds and variance |52| 6 | All main-result runs complete; crossover/cost analysis drafted |53| 4 | Full draft sitting in IEEE two-column format |54| 3 | Internal mock review by a builder who did not write the system |55| 2 | Supplement assembled: run_all.sh, run_small.sh, README, generators |56| 1 | CMT profiles + conflicts filed; page count and format sweep |57| 0 | PDF and supplement in CMT before the round cutoff |5859These offsets are planning heuristics — anchor each to the current important-dates page, never60to a past edition's calendar.6162## Revision-bandwidth reasoning6364- If your target round can return a Revise & Resubmit, the honest question at submission time65 is whether the team has **four weeks of free bandwidth** in the revision window; a revision66 you cannot execute is a reject in slow motion.67- The two-round structure means a missed Round 1 pushes you to Round 2 of the **same** edition68 (five months later) but a Round 1 *reject* pushes you a whole **edition** back — price both69 outcomes before choosing.7071## Failure modes by stage7273- Treating the two rounds as interchangeable and burning Round 1 on an unfinished evaluation,74 losing the whole edition.75- Leaving IEEE format conversion to the final week, when two-column overflow surfaces late.76- Skipping the builder mock review — the one chance to hear "your baseline is untuned" from a77 colleague instead of a reviewer.78- Assuming a revision window exists for the current edition without confirming it.7980## Output format8182```text83[Current stage] idea / building / measuring / writing / submission / revision / accepted84[Target round] Round 1 or Round 2 (edition), with next official deadline + source85[Critical path] <three tasks that determine readiness>86[Revision reserve] <weeks of bandwidth available if R&R returns>87[Risk register] <round-choice / format / evaluation / reproducibility / presentation>88[Owner map] <task -> person or role>89```9091---9293**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `ICDE-Skills/skills/icde-workflow/SKILL.md`