diff --git a/checklist.md b/checklist.md
index 17ba8dd..e76d46d 100644
--- a/checklist.md
+++ b/checklist.md
@@ -166,7 +166,9 @@ The steps for deleting, adding, and replacing test cases, changing bounds, etc,
 ## Appeals
 
 There is little time between the end of the competition and the start of appeals. You should rehearse what will happen in this time:
+- Local submissions must be retrieved and added to CMS.
 - Judging needs to complete. Perhaps a re-judge to ensure stability of results (border-line timeout cases are inevitably going to change the results, so don't worry if they do but stick with the results shown to the students the first time!)
+- During the contest, for several reasons, the connection between ProxyService and Ranking instances may experience data losses. In this case, some or all instances might miss a submission. To ensure rankings are all up to date, restart ProxyService once the judging is finished. ProxyService sends a fresh copy of the latest data at start time. Make sure that this transfer succeeds on all instances. Double check the data on ranking instances with the ranking from admin to make sure they match.
 - The state of the contest database should be dumped for posterity.
 - Test data must be made available to students, along with a mechanism to allow students to run their solutions on the provided test data. CMS now provides an "analysis mode" to support this.
 - Students should be able to download their submissions (on day 2, you may want to provide access to both day 1 and day 2 submissions)