LogoLogo
  • Welcome!
  • Mission Statement
  • Contributing Guidelines
    • Embed CADs in Wiki Articles
  • VEX Worlds Livestream Archive
    • VEX U
    • V5RC High School
    • V5RC Middle School
    • VIQRC Middle School
    • VIQRC Elementary School
    • JROTC
  • ⚙️Hardware
    • Design Fundamentals
      • Gear Ratios
      • Internal Forces (Stress)
      • Torque
      • RPM
      • Center of Mass
    • Introduction to VEX Parts
      • Structure
        • C-Channels and Angles
        • Fasteners
        • Retainers
        • Gussets and Brackets
        • Bearings
        • Plate Metal and Flat Bars
      • Motion
        • High Strength Components
        • Gears and Sprockets
        • Traction Wheels
        • Mecanum Wheels
        • Omnidirectional Wheels
        • Flex Wheels
    • Robot Decorations
      • Part Dyeing
      • Metal Coloring
      • License Plate Holders
    • Lifts
      • Double Reverse Four Bar (DR4B or RD4B)
      • Four Bar
      • Scissor Lift
      • Six Bar
      • Other Lifts
      • Best Practices
    • Shooting Mechanisms
      • Catapult
      • Flywheel
      • Linear Puncher
    • Drivetrains
      • Tank Drive
      • Mecanum Drive
      • Holonomic Drive
      • Designing a Drivetrain
      • Best Practices
    • Pivots & Joints
    • Pneumatics
      • Best Practices - Pneumatics
    • Intakes
    • Flip Out Mechanisms
    • Defensive Mechanisms
    • Misc. Building Techniques
    • VexU
      • Common Manufacturing Techniques
        • 3D Printing
        • Laser Cutting
      • Custom Manufactured Parts Library
      • Commercial Off The Shelf Parts Library
  • 👑Team Administration
    • New Team Resources
      • Creating The Team
      • Gaining Interest for Robotics Teams
      • Attending Competitions
        • Elimination Bracket
    • Team Dynamics
      • Organization Structure and Longevity
      • Member Allocation and Management
      • How *Not* To Run a Team
    • Team Finances
      • One-Year Team Financial Breakdown
      • Funding Your Teams
    • Hosting Competitions
      • Live Streaming
      • Tournament Manager
        • Competition Electronics
        • Creating a Tournament
        • Tools
          • Field Set Control
          • Connecting Mobile Devices
          • Connecting Raspberry Pis
        • Match Control
          • Inputting Match Scores
          • Inputting Skills Scores
          • Inputting Scores on TM Mobile
        • Displays
        • Alliance Selection
      • Additional Event Partner Resources
    • VexU Organization Management
      • Getting Started in VexU
      • Team / Personnel Management
      • Volunteering At Local Events
  • 📚The Judging Process
    • The Engineering Design Process
      • Test and Refine
    • The Engineering Notebook
      • Segments of the Notebook
      • BLRS2 '23-'24 Engineering Notebook
      • Integrating Inventor Models into Documentation
      • Engineering Notebook Rubric Breakdown
    • The Interview
      • Interview Rubric Breakdown
    • Using Notion for an Engineering Notebook
      • How to Setup a Notebook
      • How to Create Entries
      • How to Export a Notebook
      • Purdue SIGBots Notion Template
        • Game Analysis
        • Identify The Problem
        • Brainstorm Solution
        • Select Best Approach & Plan
        • Build Log
        • Programming Log
        • Testing Solution
        • Tournament Recap
        • Innovative Feature
  • 🖥️VEX CAD
    • CAD Programs
      • Inventor
      • Fusion 360
      • Solidworks
      • OnShape
      • Protobot
    • Making a Chassis
      • Inventor Chassis: The Basics
        • Installation
        • User Interface Overview
        • Dark Mode
        • Assemblies
        • Placing Parts
        • Navigating CAD
        • Changing Visual Style
        • Grounding
        • Connecting Two C-Channels
        • Modifying Existing Constraints
        • Toggling Visibility on Existing Parts
        • Completing Half of the Chassis
          • Inner Drive Channel
          • Bearing Flats
          • Motors
          • Wheels
          • Sprockets
          • Spacers, Washers and Standoffs
          • Spacers Cont.
        • Creating Mid-Plane
        • Mirroring
      • Inventor Chassis: Best Practices
        • File Structure
        • Subassemblies
        • Wheel Subassembly
        • Origin Planes
        • Cross Brace
        • Drive Channels
        • Simple Motor iMates
        • Replacing Simple Electronics
        • Completing Half of the Drive
          • Bearing Flats (Best Practice)
          • Wheels
          • Powered Gear
          • Spacer Boxing
          • Spacers, Washers and Standoffs (Best Practice)
        • Model Browser Folders
        • Mirroring (Best Practice)
        • Model Browser Folder (Right)
        • Main Assembly
      • Fusion 360 Chassis
      • Solidworks Chassis, Chain, and Custom Plastic
    • Remembering The Best
      • 62A Skyrise
      • 400X Nothing But Net
      • 2587Z Nothing But Net
      • 365X Starstruck
      • 62A In The Zone
      • 202Z In The Zone
      • 5225A In The Zone
      • 169A Turning Point
      • 929U Turning Point
      • 7K Tower Takeover
      • 5225A Tower Takeover
      • 62A Change Up
    • Scuff Controller
  • 💻Software
    • Odometry
    • Path Planning
    • Robotics Basics
      • Arcade Drive
      • Tank Drive
      • Joystick Deadzones
      • Curvature (Cheesy) Drive
      • Subsystem Toggling
    • Organizing Code
      • Code Style
      • Code Styling Guide
      • Writing Good Comments
      • Version Control
    • Control Algorithms
      • Bang Bang
      • PID Controller
      • Basic Pure Pursuit
      • Flywheel Velocity Control
      • Kalman Filter
      • Take Back Half (TBH) Controller
      • RAMSETE Controller
    • Competition Specific
      • Operator Control
      • Autonomous Control
    • C++ Basics for VEX Robotics
      • Basic Control Flow
      • Enumerations
      • Namespaces (::)
      • Multiple Files (C/C++)
    • VEX Programming Software
      • PROS
        • OkapiLib
      • vexide
      • Robot Mesh Studio (RMS)
      • EasyC
      • RobotC
      • VEXcode
      • Midnight C
    • General
      • Stall Detection
      • Register Programming
      • Sensors and Odometry in Autonomous
      • Embedded Programming Tips
      • Debugging
      • Bit Shift
      • Bit Mask
      • Autoformatting
      • Finite State Machine
      • Data Logging
    • Object Recognition
      • Red Green Buoy
      • AMS
      • OpenCV
      • OpenNI
    • 🤖AI in VRC: Pac-Man Pete
  • ⚡VEX Electronics
    • V5 ESD Protection Board
    • VEX Electronics
      • VEX V5 Brain
        • V5 Electronics Observations and Issues
      • VEX Controller
      • VEXnet and V5 Robot Radio
      • VEX Battery
      • VEX Motors
    • VEX Sensors
      • 3-Pin / ADI Sensors
        • Encoder
        • Potentiometer
        • Limit Switch
        • Bumper Switch
        • Accelerometer
        • Gyroscope
        • Ultrasonic
        • Line Tracker
        • LED Indicator
      • Smart Port Sensors
        • GPS Sensor
        • Rotation Sensor
        • Vision Sensor
        • Optical Sensor
        • Distance Sensor
        • Inertial Sensor (IMU)
        • 3-Wire Expander
    • V5 Brain Wiring Guide
    • Legacy
      • VEX Cortex
      • Power Expander
      • VEX Motor Controller
      • VEX Cortex Wiring Guide
  • General Electronics
    • General Topics
      • External Boards
        • ASUS Tinker Board S
        • Arduino
        • Beagleboard
        • Leaflabs Maple
        • LattePanda
        • Meadow F7 Micro
        • Netduino
        • ODROID-XU4
        • Pandaboard
        • Raspberry Pi
      • Analog-Digital Converter (ADC)
      • Bit-Bang
      • GPIO
      • I2C
      • Jitter
      • Line Noise
      • List of Tools
      • Output Drive
      • Power Consumption
      • Radius Array
      • Resettable Fuse (PTC)
      • SPI
      • Slew Rate
      • Stalling
      • USART
      • UART
      • 5 Volt Tolerant
      • DC Motor Basics
Powered by GitBook
LogoLogo

This work is licensed under a Attribution-ShareAlike 2.0 Generic License

On this page
  • Club Organization
  • Bylaws
  • Officer Board
  • Communication & Organization Platforms
  • Organization Platforms
  • Communication Platforms
  • Club Management
  • Resource Management
  • Personnel Management

Was this helpful?

Edit on GitHub
Export as PDF
  1. Team Administration
  2. VexU Organization Management

Team / Personnel Management

PreviousGetting Started in VexUNextVolunteering At Local Events

Last updated 1 year ago

Was this helpful?

Club Organization

When founding a VexU team, it is important to setup processes and procedures that will be followed each year in order to develop stability within the club.

Bylaws

Bylaws are a written set of rules & processes that are followed by an organization in order to clarify any questions about how an organization works. This may or may not be required by the university that a team is a part of, but is nonetheless a good practice to set up expectations within a club.

Bylaws should include any status that a person can hold in a club (recruit, member, officer, etc.) as well as the expectations & responsibilities that come with that status. They should also outline processes such as onboarding, disciplinary action, and officer elections. It is important that bylaws are agreed upon and specific so that there are less disagreements.

Officer Board

An Officer Board is an elected group of students to hold key roles in a club/team. This board should include (at minimum) a President, Vice President, and a Treasurer while additional officers can be added as seen fit. It is up to an organization to find specific requirements, expectations, and election processes to follow.

VexU teams are on average larger than VRC teams. This makes it so much more important that members of the team are communicating clearly and working together.

This article is written primarily based on the experience of The Purdue SIGBots. As an organization with 14 years of experience competing in VexU, we have made many mistakes and want to share what we have learned, but this is not the End-All / Be-All solution.

Communication & Organization Platforms

There are 2 structures that need to be setup for a VexU team to be successful. Firstly is a communication platform. This is where members can discuss plans for a season, potential meeting times, and the status of tasks. Second is an organization platform where progress is documented, and overarching club organization can take place. These can be one shared platform, but it is often times better to find 2+ platforms that better suit each need.

Organization Platforms

This should be a highly organized place for documenting what is most important to the organization as a whole, and likely where a team's can be written & stored. The Purdue SIGBots has had success with using a combination of Google Drive & Notion.

Notion is a great way to organize information in series of databases, and nested pages. This allows for an organization to host living documents that need to be both edited & read (e.g. club bylaws & weekly meeting notes) alongside many other features that help with team organization, onboarding, and sharing resources.

Google Drive is a more general purpose file storage system. Google Drive has the capability to do what Notion does, but also allows for large file storage (e.g. shared CAD libraries, etc.) and a connection to the Google Work Suite with Google Docs, Sheets, & Slides for general purpose use.

Communication Platforms

This should be used for daily communication for members of the team. It is a best practice to keep this as open as possible as to not limit communication between members. Never create communication pathways that are needlessly restricted from certain members as this can quickly lead to a toxic working environment.

Discord is a common communication platform used in the Vex community. The benefits of Discord is its cross platform capabilities as well as how is can split one organization's server into many categories & channels for specific topics. Discord also allows for fast sharing of files and the ability to do audio/video calls within a server. Discord is also free.

Slack & Microsoft Teams both act similar to Discord but are used more widely in professional atmospheres. They both offer several plans for specific needs, but a university might also provide licenses for students.

Club Management

Resource Management

The process that is used to track resources will vary based on the scale and preference of a club however it is vital to reduce waste, harm, and expenses.

Firstly, ensure that all equipment that is owned by the club has a place. The easiest way to keep a space clean, is to give everything a place that it should be stored and used. Small bins & tape for labels is a very inexpensive way to help organize a space.

After organizing, catalog all equipment. This doesn't have to be a count of every screw, but a list of all tools & equipment paired with a rough estimate of building materials goes a long way. This will ensure that when packing for competitions, equipment can be tracked and over a season, nothing is lost or stollen.

When ordering more parts & tools, it is a good practice to share an order sheet with the entire club so that expenses can be tracked easily & everyone can receive the parts that they need.

Personnel Management

When dealing with large groups, it is important to keep track of all members in an organized way. It is a good practice to share a form with the team to document key information about them. From an organizational standpoint, having a name attached to a phone number, email, and similar information is helpful for emergencies. Having information on members' age, major, and experience is very helpful when dealing with the university as well has when talking to potential sponsors.

👑
Engineering Notebook