Say what to hand in and by when. Teams get a receipt for every submission, every version is kept, and each round has one inbox where you accept or reject what arrived.
sendkan.com/nb4k7x2q/submit
Due in
00d05h42m00s18 Mar · 23:59 GMT+7
On time · v3- Solution deckmango-final-deck.pdf · 14 pages
- Executive summarysummary.pdf · 1 page
- Financial modelOptional Submit
1Step 1 of 4Collect
Participants
A checklist, a countdown, one Submit button and a receipt.
Organizers
One inbox per round: what's in, what's missing, what needs checking.
Reviewers
The exact version that was accepted, with every earlier one on record.
What it does.
- 01Requirements that check themselvesFiles, links or short answers. Each one sets its formats, size, PDF page limit or word count, checked on upload.
- 02Deadlines to the minuteEach round opens and closes in your event's timezone. The server enforces it; late work is labeled, never lost.
- 03A receipt for every submissionEach Submit creates a version with a receipt code and a server timestamp. Nothing is overwritten.
- 04Accept or reject, with a reasonCheck each submission against the requirements. Rejections carry a reason the team reads, and you choose whether they can resubmit.
- 05Fair exceptionsExtend one team, close early or reopen for late work, with a note participants can see.
- 06Get everything outDownload a round as one ZIP, or export the inbox to Excel or CSV.
- 07As many rounds as you needPreliminary, semi-final, final: each round on its own schedule, open only to the teams you select. On every plan.
Received, checked, and on the record
Received isn't accepted, and accepted isn't qualified. The inbox keeps those apart, and every check, extension and window change lands in the activity log.
- Needs checking, Accepted, Rejected
- On time or late, as its own filter
- Searchable activity log
sendkan/host · Round 1 · Mango Sticky Strategists
mango-final-deck.pdf · v314 pages
Check
Accepted RejectReceipt SK-7Q2M-K4PD · on time · v3Free plan. No credit card.