TrawpieEach term has a small picture of where you’ll see it, what it is, and an example with made-up people.
AI agent
An app like Claude or Cursor that works in Trawpie for you through a personal token. Its changes say “via AI agent” in the history.
Example: Sam asks an agent to add five tasks to next week; they appear in Sam’s row.
See also: Role
Backlog
A column for ideas that aren’t planned into a week yet. Backlog tasks have no dates, so they never carry over.
Example: “Dark mode” waits in the Backlog until the team has a free week.
Board
The main screen of a workspace: people down the side, weeks across the top, tasks where they meet.
Example: Sam’s “Order bearings” sits in Sam’s row, in Week 1.
Carry-over
An unfinished task copied into the next week, joined to the original by a solid blue arrow. Ticked sub-tasks come with it.
Example: “Draft the report” isn’t done on Friday, so it appears again in Week 2. You can undo it for a few days.
See also: Workflow and stage, Sprint
Category
A row under one person that groups their tasks. Each person can have several.
Example: Sam has Hardware, Report and Admin. A new task goes in the one you pick in the New task form.
See also: Board, Slim names
Decision matrix (MCDA)
Compare options by scoring each against criteria that matter more or less. The weighted total shows the leader.
Example: Three poster ideas scored on cost and clarity; clarity counts more, so Idea B wins.
Dissertation planner
A workspace planned back from a hand-in date, with chapters, word counts, a writing log and supervisor feedback.
Example: Priya needs 60 words a day to finish by 1 May.
See also: SelfTrack, Weekly metric
Gantt
A timeline: each task is a bar from its start to its deadline, with arrows for what waits on what.
Example: Dragging “Build frame” a week later moves “Paint frame”, which waits on it.
See also: Waits on, Phase and milestone
GitHub link
Every task has a reference like TT-7Q2K. Put it in a branch or pull request and it links itself; a merge can finish the task.
Example: Alex’s branch fix/TT-7Q2K-login-loop shows its pull request on the card.
See also: Version and branch
Helper
Someone who helps with a task without owning it. A task can have two.
Example: Jo adds Sam and Alex as helpers on “Test the sensor”.
See also: Supporting task
Kanban
A view with one column per stage. Drag a card between columns to change its stage.
Example: In the last week before the open day, the team works from the Kanban: To do, Doing, Done.
See also: Workflow and stage, Board
Organisation
Everyone at a university or company, found by email domain, who can see shared workspaces and invite each other by name.
Example: After uni.ac.uk is verified, new students join automatically when they sign in.
Overview
One page per workspace: what it’s about, a status set by hand, progress, stages, timeline and what’s late.
Example: The tutor opens the Overview and sees “At risk: survey closes late”.
See also: Phase and milestone, Decision matrix (MCDA)
Phase and milestone
A phase is a stretch of the project with dates; a milestone is the moment it should end with.
Example: “Design” runs three weeks and ends with a design review; tasks in it show a Design tag.
Role
What someone can do in a workspace: Owner, Admin, Member, Viewer, Guest, or your own.
Example: The treasurer has a custom “Treasurer” role that can see and approve money.
SelfTrack
Your private space: your own days, habits, skills and projects, with the tasks your teams give you.
Example: Alex tracks “Read 20 minutes” daily and a personal project “Learn Python”.
See also: Dissertation planner
Sign-off
A stage that needs someone’s approval before work moves on. The server enforces it.
Example: Sam’s design can’t move to Build until Jo, the lead, approves it.
See also: Workflow and stage, Role
Slim names
A switch that narrows the person and category columns, to fit more weeks on screen.
Example: On a small laptop, Sam turns on Slim names and sees four weeks instead of three.
See also: Category
Sprint
A short run of weeks with one goal, drawn as a band above them, with a burndown in Analytics.
Example: Weeks 5 and 6 become “Sprint 3: first test run”; whatever is left at the end carries into Sprint 4.
See also: Carry-over, Phase and milestone
Sub-task
A step inside a task, ticked as you go. Ticking them moves the task’s progress bar.
Example: “Draft the report” has four sub-tasks: Outline, Methods, Results, Proof-read.
See also: Task
Supporting task
A task you help with but don’t own. It shows in your Supporting row too, joined by an orange dotted line.
Example: Jo owns “Test the sensor”; Sam is added as a helper, so it also appears under Sam.
Task
A card on the board: one piece of work with an owner, a week, and optionally a deadline, priority, sub-tasks, helpers and files.
Example: “Draft the report”, Jo’s, Week 4, due Friday, 2 of 4 sub-tasks done.
Version and branch
For software teams: a release (v1.2) sits on a line under the weeks, and the branches being worked on curve off it.
Example: Three tasks on feature/search ship in v1.2; click the branch and just those cards light up.
See also: GitHub link, Sprint
Waits on
A link saying one task can’t finish until another does. The Gantt draws it as an arrow.
Example: Priya’s “Write results” waits on Sam’s “Run the tests”.
Weekly metric
A small badge on each week for the one number that matters that week. Click it to type.
Example: A dissertation shows “Words: 2,400”; an event shows “Tickets sold: 85”.
See also: Board
Workflow and stage
The path a task takes, as stages like Design → Review → Build. Stages show on cards and as Kanban columns.
Example: A content team uses Idea → Draft → Review → Published.
Workload
Hours planned for each person, by week or day, against what they have. Red means too much.
Example: Jo’s exam week is red, so Sam takes one of Jo’s tasks.
Workspace
One project or team: its board, people, roles and settings. You can be in many.
Example: Jo is in three: Robotics, Open day and a dissertation.
See also: Role, Organisation