OINK Tips | How OINK Works

OINK Tips

How OINK fits together, plus short explanations for why it becomes more useful when your training plan, completed activities, goals, PBs, notes, and integrations live in one place.

How OINK Works Where things live in OINK Expand

OINK has a few different surfaces for training, coordination, goals, event signup, and detailed race or mission planning. Start here when you are deciding where something belongs.

Where things live

Use each area for a different running job

Training Planner Plan your training week A classic calendar view for weekly training activities, with integrated AI support and optional synced activity context.

Group Runs Sync up with other runners Coordinate public group runs or private invites, including RSVPs, start details, routes, and who is coming.

Goals Track what you are working toward Capture longer-term aims, milestones, personal bests, target races, and progress notes outside the weekly calendar.

Events Organise and enter events For event organisers and participants: public event pages, signups, entrant management, payments, and race-day information.

Race & Mission Planner Plan a specific race or mission Build detailed pacing, fuel, hydration, electrolyte, gear, route, and safety plans for a race day or mountain mission.

How it links

Training Planner

+----------------------+
| Goals                |
+----------------------+
          |
          | informs AI/context
          v
+----------------------+
| Training Planner     |
+----------------------+

+----------------------+
| Group Runs           |
+----------------------+
          |
          | add to planner
          v
+----------------------+
| Training Planner     |
+----------------------+

+----------------------+
| Training Planner     |
+----------------------+
          |
          | create linked run
          v
+----------------------+
| Group Runs           |
+----------------------+

+----------------------+
| Events               |
+----------------------+
          |
          | add to planner
          v
+----------------------+
| Training Planner     |
+----------------------+

+----------------------+
| Race & Mission       |
| Planner              |
+----------------------+
          |
          | add/update calendar
          v
+----------------------+
| Training Planner     |
+----------------------+

Linked records keep the source of truth clear, so you know where to edit the main details.

Quick rule of thumb

Use Training Planner for your weekly training calendar. Use Group Runs when you need to coordinate with other runners. Use Goals for longer-term outcomes and milestones. Use Events for organised event pages, signup, and participant management. Use Race & Mission Planner for detailed execution plans for a specific race day or mission.

Still not sure?

Use Training Planner as your personal base, then link outward when coordination is needed. A calendar activity can become a linked group run; a group run, event, or race and mission plan can also be added back to your planner.

Open Training Planner Open Group Runs Open Goals Open Events Open Race & Mission Planner

Tip 1

What goes where in OINK?

OINK is most useful when each area has a clear job: planner for the week, goals for direction, group runs for coordination, events for organised signups, and race or mission plans for big days.

Use this when someone asks why OINK has several areas. The short answer is that each area stores a different part of the running workflow, and linked records keep the source of truth clear.

Use Training Planner for the week-to-week calendar.
Use Goals and PBs for longer-term direction and performance context.
Use Group Runs and Events when other runners need a shared place.
Use Race & Mission Planner for detailed execution plans.

+----------------------------+
| Goals + PBs               |
+----------------------------+
              |
              v
+----------------------------+
| Training Planner          |
+----------------------------+
      ^                 ^
      |                 |
      v                 |
+------------+   +-------------+
| Group Runs |   | Events +    |
+------------+   | Race Plans  |
                 +-------------+

Open OINK Tips Share Tip 1

Tip 2

Why OINK AI works better when your context lives here

OINK can give AI a richer training picture because it can bring together planned work, completions, notes, goals, PBs, nutrition, saved AI memory, and optional integrations in one prompt context.

The problem is not any one tool. The problem is jumping between places, rebuilding context by hand, and then asking an AI assistant to make planning decisions from a partial snapshot.

Use the planner as the source of truth for what was planned and what changed.
Mark activities complete and add short notes when the why matters.
Set goals and target races, then mark goals complete when they are done.
Add personal bests and achievements for compact performance benchmarks.
Use integrations where useful, but treat them as inputs rather than the whole story.
Ask AI Chat for decisions once OINK has the context behind the question.

Prompt context example

Generic question

Thin input

Get fitter.

Richer OINK context

Finish a 43 km trail race feeling strong, prioritise climbing endurance, avoid big mileage jumps, race date 20 July.

Before
+-----------+  +-----------+
| Calendar  |  | Activity  |
+-----------+  +-----------+
+-----------+  +-----------+
| Notes     |  | Goals/PBs |
+-----------+  +-----------+
        \ copy + retype /
              v
       Generic AI prompt

With OINK
+----------------------------+
| Planner + completions      |
| Goals + PBs + nutrition    |
| Notes + memory + inputs    |
+----------------------------+
              |
              v
        OINK AI Chat

Open Training Planner Share Tip 2

Tip 3

Use Nutrition Tracker as a simple feedback loop

Nutrition tracking is most useful when it stays simple: set a practical target, log food and water directly, then review the daily and weekly picture before adjusting.

The saved food library is a shortcut, not the starting requirement. Log directly first, save repeat foods when they become obvious, and use the tracker to make nutrition context available beside training.

Set a daily calorie and water target, even if it is a first draft.
Log food directly with a name, serving count, calories, and macros.
Use photo, barcode, or saved foods when they make logging faster.
Track eaten, burned, net calories, water, macros, and week balance.
Ask AI Chat for target help once OINK has training and nutrition context.

Prompt context example

Generic question

I think I need to eat better for training. What should my calories be?

With OINK context

OINK can combine goals, current training load, recent logs, water, macros, burned calories, net calories, and weight trend before suggesting practical targets and tracking habits.

Concrete examples

First target

Thin input

Set a calorie goal.

Richer OINK context

Set a first-draft daily target such as 2400 kcal and 2500 ml water, then review net calories and week balance after a few days.

Direct food log

Thin input

Add banana.

Richer OINK context

Log banana, 1 serving, 105 kcal. Save it to the library only if it becomes a regular item.

Training context

Thin input

Why was today hard?

Richer OINK context

OINK can compare the planned session, completed activity, food intake, water, macros, and recent trend before suggesting what to adjust next.

+----------------------------+
| 1. Set target             |
| Calories + water          |
+----------------------------+
              |
              v
+----------------------------+
| 2. Log food + water       |
| Direct, photo, barcode,   |
| or saved foods            |
+----------------------------+
              |
              v
+----------------------------+
| 3. Track and adjust       |
| Fuel + macros + balance   |
+----------------------------+

Open Nutrition Tracker Share Tip 3