TrawpieDocs Guide Open Trawpie
Use cases

A student engineering team

A society building something for a competition: sub-teams, parts and budget, design reviews with sign-offs, and a weekly meeting.

Updated 11 Nov 2026 · 1 min read

Think of a 20-person team building a robot, a drone or a race car for a competition, with a budget from sponsors and a design review before anything gets built.

Set this upHow
Sub-teamsMechanical, Electronics and Software, each with a lead (Settings ▸ Sub-teams)
WorkflowEngineering build: Design → Review (lead signs off) → Build → Test
MoneyFinance and Parts on; purchases over £100 need the treasurer
Weekly meetingMeetings on; actions become tasks
Weekly metric“Hours logged” or “Budget left” on each week
A design can’t move to Build until the sub-team lead signs it off.
Example
Sam (Mechanical) finishes “Bracket v2” and moves it on. Jo, the Mechanical lead, gets the sign-off on Home, checks “Load calculations attached”, and approves. Sam then orders the aluminium; it’s £140, so Priya the treasurer approves that too.
Open the drone or Formula Student sample in the demo to see all of this set up.