Onboarding

Onboarding & Workshops

[x] Match the teammates through random generator
[x] Send a blast message in the platform for Figma verification and Discord announcements
[x] Discord Channels created
[x] Send a welcome email to all the participants
[x] Full Team kickoff and onboarding (Morgan Denner)
[x] Get everyone in Shipathon Discord channel (Automated through the platform)
[x] Get everyone in Figma Workspace (Julia Debari)
[ ] Provide teams with Claude Code seat (Morgan Denner)
[ ] Connect teammates to the Mentor’s (Shipathon Organizers)

Workshops

[x] Agile and Service Leadership (Neha Agarwal)
[x] Team RACI chart (Dominic Bradley)
[ ] Discovery backlog for individual teams (Morgan Denner)

Code of Conduct

Teams must follow Tech Fleet policies and our community agreement when they participate in the shipathon. The language from the code of conduct is below. Important links to additional information on our website include

Code of Conduct

All Tech Fleet community members are expected to adhere to the following conduct standards:

Treat others with dignity and respect at all times.
Foster teamwork and participation. Seek out and encourage participation and insights from members with different experiences, perspectives and backgrounds.
Support flexible work arrangements for co-workers with different needs, abilities and/or obligations. Be respectful of time zones. Embrace habits that are inclusive and productive for team members wherever they are, using asynchronous communication tools and pay attention to time zones when scheduling meetings.
Be generous in both giving and accepting feedback. Good feedback is kind, respectful, clear, and constructive and focused on goals and values.
Be open-minded and listen when given constructive feedback regarding others’ perception of your conduct. Understand and act upon the fact that what may be acceptable to one person may not be to another.
Commit to self-improvement. If you’re approached as having acted in a way that has offended another, listen with an open mind and do better.
Avoid behavior or language that is or may be perceived to be offensive and exclusionary or that may offend, intimidate, degrade, insult or humiliate others. This includes jokes, banter, ridicule or taunts as well incivility, bullying and physical aggression, microaggressions, foul or suggestive language, sexual images, innuendo or actions, slang or derogatory language, or inappropriate personal remarks.
Address and report inappropriate behavior and language that are in breach of this Code of Conduct.

Rules

Teams must follow Tech Fleet’s Code of Conduct
1. If there is a conduct concern that needs attention, please email us at [email protected] and _______ will get back to you within 48 hours.
Teams must clearly document their design judgment in their usage of AI
Teams must have a launched application url hosted on Vercel at the end of the shipathon along with requested deliverables to be eligible for judging
Teams have broad discretion in how they conceive of and execute their work. However, teams may be disqualified if they:
1. Pursue a project topic that does not meet Tech Fleet criteria
2. Fail to create a unique engineering, logic, or infrastructure
3. Fake a working project
4. Violate data privacy, safety, and open-source compliance

Judgement Criteria

Rubric

Rubric item	Criteria	Score
How impactful is the solution to the problems being solved?	Impactful products:
• Solve meaningful problems
• Are driven by more than just money
• Serve underserved and underrepresented audiences
• Do not extract from customers
• Addresses root causes of problems
• Are based on actual lived experiences of problems that people face, not just theory
• Sustainability - how environment friendly is the product and its efficiency.	1 - 10
How realistic is this product to scale in the real world?	• Feasibility - the product is simple, testable, valuable, easy to build and maintain
• Viability - the product is more likely to succeed in the market with a realistic and sound business model and environmental impact.
• Usability - the product is easy to use and accessible to as many audiences as possible
1 - 10
The team’s storytelling during the presentation	• The team’s reasoning that they communicate
• Presentation order and structure
• Storytelling capabilities
• How captive you hold audiences during the presentation	1 - 10

Mentors

Coming Soon

Judges

Coming Soon

Resources

Judging Rubric

Catalyst Cup FigJam folder

FigJam Workshop Templates

Tech Fleet Onboarding Courses (requires login)

Fleety the Helper Bot (requires login)

Recordings

Meeting Recordings Space

Pitch Submissions

Submit your presentation