Creating and organizing Tracks
Learn when to create a Track, where it should live, and how to keep long-running work organized in Giga.
Create a Track when the work will continue over time and the history around it will matter later.
Good Track candidates include a client account, product launch, research effort, hiring process, ongoing function, or any other body of work where people will return to the same subject across multiple Chats.
Before you create a Track
A Track should have a clear subject and a reason to persist.
Use one when:
- the work will span more than one Chat
- files, decisions, or research should stay attached to the same subject
- several people may need the same background
- Giga should be able to understand what has already happened
- the work will keep changing over time
For a quick one-off question with no need for continuity, a normal Chat is usually enough.
A useful Track is specific enough to stay coherent
“Q4 product launch” is easier to maintain than a catch-all Track containing every piece of company work.
Choose the right Group
Every Track lives inside a Group, which determines the access scope around it.
| If the work is… | Put the Track in… |
|---|---|
| Personal or private to you | Your existing private Group |
| Shared with a team | The relevant shared Group |
| Part of an existing department or workstream | The Group that already contains that work |
You generally do not need a new Group just to make a Track private. Each member already has a private Group for personal work.
Create a Track
You can ask Giga to create a Track from a Chat.
Name the work
Use a name that will still make sense several weeks from now, such as Customer onboarding, Website redesign, or Acme account.
Choose where it belongs
Tell Giga which Group should contain the Track. If the work is private, use your existing private Group.
Add a short description
Explain what belongs in the Track so teammates can understand its purpose when they encounter it later.
Start adding useful context
Add Context Notes, relevant files, and the Chats that belong to the work.
Giga may use internal metadata to understand the type of work behind the scenes. You should not need to classify the Track yourself.
Avoid duplicate Tracks
Before creating a new Track, Giga should check the Tracks you can already access for an obvious match.
If something similar already exists, it is usually better to continue there rather than split the same work across several Tracks.
One subject, one clear home
Duplicate Tracks make context harder to retrieve and increase the chance that decisions or files end up in different places.
Give the Track enough context
A freshly created Track becomes more useful once it has a small amount of durable background.
A good starting point is:
- a short description of what the Track covers
- a Context Note with important background or instructions
- the first relevant Chat
- any files that people will need repeatedly
- an owner, target date, or check-in cadence when those are useful for the work
You do not need to document everything up front. Add context when it will help Giga or your teammates work more effectively.
Keep work product and memory separate
A Track can hold authored files, but files are only one part of its state.
| What you are storing | Where it belongs |
|---|---|
| Standing background or instructions | Context Notes |
| Decisions, changes, progress, and learned context | Memory |
| Reports, drafts, code, and other supported outputs | Files in Tracks |
| Structured data that grows over time | A database rather than a narrative file |
This separation helps Giga retrieve the right information without treating every file as memory.
Keep the Track list clean
As work changes, keep Tracks aligned with reality.
- Keep active work easy to find.
- Pause work that is temporarily inactive instead of creating a replacement.
- Archive work that is finished but still worth keeping for reference.
- Reuse an existing Track when the same subject becomes active again.
A Track can also have an owner, target date, and check-in settings when the work benefits from them.
Avoid deleting a Track just because work has paused
Deleting a Track also removes its files and is irreversible. Pausing or archiving is safer when the history may still matter.
A simple example
Imagine your team is preparing a new website.
Website redesign
The Track holds the ongoing body of work.
Context Note
Brand goals, audience, constraints, and standing instructions.
Chats
Research, copy reviews, design discussions, and implementation tasks.
Files
Briefs, screenshots, copy drafts, design exports, and code.
The result is one place where the subject can accumulate useful context instead of being scattered across unrelated Chats and folders.
Image placeholder
Screenshot showing the Track creation flow and Group placement in Giga.