Best Practices for Campus DEVCON Events

I. Underpromise and overdeliver

• Assume risks by default. Plan as if the internet will fail, a speaker will be late, and power will fluctuate.
• Build strategic buffers of 10–15 minutes so you never cut a speaker’s slot.
• Commit conservatively. Never promise a partner an attendance number unless you’re sure you can hit 120% of it.
• Keep a safe space. Follow the HQ Safe Space Guidelines and the Code of Conduct.

II. Creative fundraising and partnerships

DEVCON is a 17-year-old brand. Use that credibility.

• Plan 3–6 months ahead. The biggest costs are raffle items, speaker tokens, and organizer meals.
• Target budget cycles: partner with local DOST, DICT, or school IT organizations during peak cycles like IT Week.
• Start with a proposal: find official emails of local representatives and send a professional collaboration proposal.
• Prioritize in-kind sponsorships over cash, due to tax and legal risk. Look for win-win “X-deals”.

III. Content strategy and slides

• Diverse topics: quantum computing, generative AI, web3 and blockchain, robotics, cybersecurity, DevOps, and tech leadership.
• One master slide file to avoid flash-drive and permission issues.
• Decks due 3–4 days before, with a calendar reminder to speakers.
• Collaborate in Canva or Google Slides so the tech team can check content and aspect ratios early.

IV. Program management

• Play the DEVCON loop during registration and breaks (see the Community Playbook).
• Arrive 3–4 hours early (4–6 for large summits) for rehearsals and safety checks.
• Tech-check every speaker: audio, clicker, transitions.
• Energetic, rehearsed hosts who manage transitions smoothly.

V. Speaker and sponsor relations

• Professional impression: your speaker might be your future employer.
• Speaker integrity is non-negotiable: never drop a speaker on the day. Shorten breaks or Q&A instead.
• Logistics 14 days prior: a calendar invite with a map pin, gate number, building, and parking.
• A dedicated liaison for every guest, from entrance to holding area.
• Quality appreciation: professionally printed certificates and quality tokens, never flimsy bond paper.

VI. Safety and emergencies

• Open with a 60-second safety brief: nearest exits and medical station.
• Technical redundancy: backup laptop, spare clicker, and a secondary internet source.
• Contingency protocols for speaker no-shows, power outages, and medical emergencies.

VII. Final readiness checklist

2–6 months before

• Local DOST, DICT, and school reps contacted
• Venue confirmed, electrical and A/V capacity verified
• Promotions live for at least 3 weeks
• Partner and co-presenter roles defined
• In-kind deals for meals, raffle, and tokens secured
• Volunteer briefing 2–4 days before
• E-certificates designed and delivery tested

Speakers and content

• All decks submitted 3–4 days before
• Final logistics invite sent (map, call time, parking)
• Liaisons briefed on all VIPs
• Looping videos downloaded

Technical and risk

• All presentations in one master file
• Projector and sound tested (16:9 / 4:3, mic batteries)
• Mobile hotspot ready as Plan B
• Fire exits clear, safety officer assigned
• All volunteers briefed on Safe Space policies