In This Guide
1 Academic Events Have Unique Constraints
University events operate under procurement rules, faculty committee approvals, academic calendar restrictions, and shared venue scheduling. A 200-attendee research symposium involves 60–90 tasks across 4–6 months: call for papers, peer review, speaker travel, venue booking, catering RFPs, AV setup, registration systems, and program printing.
Most campus event teams track this in shared Google Sheets that become unwieldy by month two.
Tip
University procurement cycles add 2–4 weeks to vendor selection. Build this into your timeline from day one — it’s the most common cause of academic event delays.
2 Canvas Structure for a Conference
Build zones around event phases:
• Pre-Planning (6–4 months out) — budget approval, venue RFP, call for papers, committee formation
• Production (4–2 months out) — speaker confirmations, travel booking, catering selection, AV requirements, program design
• Final Prep (2 weeks–day of) — signage, registration setup, volunteer assignments, tech rehearsal
• Day-Of Operations — check-in desk, session management, speaker green room, emergency contacts
• Post-Event — attendee surveys, expense reconciliation, proceedings publication
Color-code cards by responsible group: blue for facilities, purple for academic committee, green for admin staff.
1
6 months out
Budget approval, venue RFP, call for papers announced, program committee formed.
2
4 months out
Venue confirmed, peer review begins, keynote speakers invited.
3
2 months out
Paper acceptances sent, travel booked, catering finalized, program printed.
4
2 weeks out
Signage ordered, volunteer training, tech rehearsal, registration system tested.
5
Event day
Registration desk, session management, A/V support, emergency coordination.
6
2 weeks after
Surveys sent, expenses reconciled, proceedings published, thank-you notes.
3 Managing the Peer Review Pipeline
For research conferences, the call-for-papers process generates its own workstream. Create a sub-zone with stages:
Submission Open → Under Review → Accepted → Rejected → Notification Sent → Presenter Confirmed
Each submission is a card. Assign reviewer cards with depends-on connectors to the notification milestone. This makes it easy to see if 30 submissions are still "Under Review" with the notification deadline 2 weeks away.
Peer Review Pipeline Status (Sample Conference)
Submissions received87
Under review34
Accepted28
Rejected19
Awaiting notification6
At T-8 weeks, 34 submissions still under review with a 2-week notification deadline ahead
4 Vendor Coordination
University procurement often requires three quotes for anything over a threshold (commonly $5,000). Create vendor comparison cards with notes fields for each quote.
Draw connectors from vendor selection cards to the downstream tasks they unlock — you can't finalize the catering menu until the vendor is selected, and you can't print table cards until the menu is finalized.
Run Dependency Detection to identify these chains automatically.
Vendor Coordination Checklist
Key Takeaways
- Structure the canvas in 5 phases from pre-planning through post-event
- Track the peer review pipeline as a sub-zone with submission cards and reviewer assignments
- Build university procurement lead times (2–4 weeks) into the timeline from the start
- Use connectors to show procurement dependencies and approval chains
- Color-code by responsible group for instant accountability