A complete walkthrough of every part of OrgTP, written for someone using it for the first time. No prior EOS or "operating system" knowledge assumed.
No sections match.
Try a different word, or raise a ticket and a human will help.
OrgTP is two things in one place:
You can use just the first half (run your team) and grow into the second half (coordinate your agents) whenever you're ready.
The five things you'll touch every week:
| Thing | Plain meaning |
|---|---|
| Rock (a.k.a. Quarterly Priority) | A big goal you commit to finishing in the next ~90 days. |
| KPI / Scorecard | The handful of numbers that tell you the business is healthy, reviewed weekly. |
| To-Do | A small action item, due within ~7 days, owned by one person. |
| Issue (IDS) | Anything that needs to be worked through as a team: Identify it, Discuss it, Solve it. |
| Headline | A short piece of customer or employee news (good or bad) shared in the meeting. |
OrgTP uses Google sign-in (and email/password). Go to orgtp.com, click Sign In, and choose Continue with Google or enter your email and password.
The first time you create an organization, OrgTP walks you through seven quick steps. Every step after the first has a "Skip for now" link and a "Skip → take me in" escape to the dashboard, so you can do the bare minimum and fill the rest in later. You can always return to any of these later from inside the app.
Name your company (company name, industry, team size) and claim your own seat (your name and your role). Submitting this step is what brings your organization into existence.
Add coworkers by name, role (Team member / Manager / Admin / Observer), and email. Each one gets an email invitation and shows up on your chart marked "Invite sent."
Add the one or two big outcomes the company is driving toward. Give each a title, a timeframe (This year / This quarter), and an owner. These become your Rocks.
Define the numbers that each seat watches. For each KPI: a title, an optional target, an owner, and a cadence (Weekly / Monthly). This is the start of your Scorecard.
Give your AI tools real seats. For each agent: a name, what it does, its runtime (Claude / ChatGPT / Zapier / Make / Other), and an owner. This is what makes OrgTP different from a plain EOS tool.
Group seats into teams (e.g. "Leadership," "Web Team"). Each team gets its own meeting and scoreboard. Name the team and tap the members who belong on it.
A recap of everything you set up, plus a preview of your weekly meeting (defaults to "[Company] Leadership Team," Mondays, 30 min) and its four-step agenda. Click "Start your first meeting" or "Explore your chart first" to enter the app.
Where: /dashboard — the screen you land on after signing in.
This is your personal cockpit. It greets you by name and stacks everything you need for the day into panels:
Controls: switch between organizations or teams (top of the page), toggle "show only mine," and open any meeting or to-do directly.
This is where the whole system pays off: one timed screen your team runs its weekly meeting from, so meetings start and end on time and nothing falls through.
Where: /l8 (the old /l10 address redirects here).
Lists your past and upcoming meetings, each with a status badge (scheduled / in progress / completed). Use the New Meeting form to create one (title, date/time, type, recurrence, team), then Create + Open. If you're on more than one team, a team filter appears. Click the "?" for an explainer of the meeting types (Weekly Leadership, Departmental, Quarterly, Annual, One-on-One).
Where: /l8/meeting/[id] — opens when you click a meeting or create one.
Everything for the meeting lives on one page: the title and time, Start / End controls, an "Add to calendar" panel, a "Driving toward" strip (your longer-term targets), the attendee list, an optional Agent Reports panel (a summary from your AI seats), and a sticky agenda bar with a per-section timer.
Tip: Click Start meeting at the top. This freezes a snapshot of your scorecard and Rocks so the meeting becomes the official record of where things stood. A completed meeting is read-only.
The agenda runs in seven sections, in this order:
Where: /me/todos — your personal action queue, separate from the dashboard.
Sections you'll see: a create box at top, "⚠ Verify these happened" (items you delegated that are awaiting your sign-off), your open queue, "Waiting on others" (things you delegated out), an L10 section (to-dos tied to a meeting), and "Closed last 24h."
What you can do: create a to-do (title, optional description, priority P1–P4, due date, assign to one or more people, recurrence, optionally attach it to a meeting); mark Done; "→ L10" to promote it into the leadership meeting; Edit; Delete; and Verify or Reopen delegated items. On mobile there's a sticky quick-add bar and swipe-to-complete.
Where: /dashboard/kpis — the full company scoreboard.
Every measurable number in the company, organized by the seat that owns it. A tab strip switches between Trends / Weekly / Monthly / Quarterly / Annual views; a filter row lets you scope by team, owner type (All / Human / Agent), and date range. KPIs appear in tables showing Title, Owner, Goal, and either editable per-period value cells (green = met, red = missed) or a latest value with a sparkline trend.
What you can do: type actual values straight into the period cells to record results each week, assign a KPI to a person with a goal, and jump to the org chart to add new KPIs.
OrgTP doesn't have a separate "Rocks page." Your Rocks show up in three places:
So to manage Rocks day-to-day, open your weekly meeting or your dashboard panel.
Where: /dashboard/ids — a cross-team master list of every open issue (visible to owners/admins/managers).
Filter by team and by IDS status (open / identified / discussed / solved). Each row shows the issue, its status, owner, team, and date. You can reassign an issue to a different team. Most issue work happens inside the meeting (§5b, section 6); this page is the bird's-eye view for leaders managing several teams.
Where: /dashboard/team — a visual, editable chart of your humans and AI agents and who reports to whom.
Filter by All / Agents / Humans. Click a tile to edit a seat or see its meetings and accountability. Add a human or agent, invite by email, or import people via CSV. Edits save to a draft until you click Publish — publishing turns the chart into an OOS (see §11).
Where: /dashboard/members — invite people and control what each can see and do.
Shows active members and pending invites. Invite by email with a role, team assignment, and fine-grained Feature / Data / Agent access toggles. Edit, resend, or revoke. Roles range from Owner and Admin down to Observer and Free — the dropdown explains each.
Where: /dashboard/teams — create sub-teams so meetings, issues, and KPIs can be scoped to a group instead of the whole company.
Create a team (name, short slug, description), then add or remove members.
Where: /team/[seat-id] — open by clicking a name anywhere.
Shows what that seat owns: Quarterly Priorities, Responsibilities, Seat Fit (the "right person, right seat" rating: Gets it / Wants it / Capacity), open To-Dos, open and solved Issues, and their meeting history.
Where: /team/review — rate your direct reports on seat fit and your company's core values (the EOS "People Analyzer").
A grid: one row per person, columns for Understands / Wants / Capacity plus each core value, and a computed verdict (Solid / Needs conversation / Wrong seat). Click a cell to cycle its rating.
This is the part that turns your operating data into reusable intelligence for your AI agents and even across organizations.
Key idea — the OOS (Organizational Operating System): a structured file of your company's coordination rules and knowledge — who owns what, how decisions get made, what's failed before, and the lessons learned. Each rule in an OOS is a Claim, tagged with how confident and how evidence-backed it is. Agents read your OOS so they start informed instead of from scratch.
Where: /dashboard/oos-operating-plan — a guided business-planning workspace (vision, traction, strengths/weaknesses) that turns your strategy into a 90-day execution list and into OOS claims. Create a plan, fill in the tabs, generate a 90-day plan, and (for admins) push it to your OOS.
Where: /dashboard/ceo (owners/visionaries only) — the whole company on one screen: long-term direction, scoreboard health, this quarter's execution, the team, and what needs attention. Driven entirely by the Operating Plan above.
Where: /claims — a public, browse-by-topic index of coordination knowledge published across every organization on the platform. Click a section to read its claims (each with confidence, evidence, and a rule / why / failure-mode).
Where: /graph — an interactive map of how organizations connect through shared patterns and best practices. Switch modes (Intelligence / Infrastructure / Best Practices), click nodes for detail, and in Best Practices mode you can ingest a practice into your own org as a claim. (The graph data requires sign-in.)
Where: /dashboard/source-documents — upload your own raw docs (a playbook, SOPs, a CLAUDE.md) and OrgTP extracts coordination intelligence into OOS files. Upload/paste, click Process, then open the generated OOS.
Switching from another EOS tool? OrgTP imports your data.
Where: /import/ninety (for Ninety.io) or /import/bloom (for Bloom Growth). Both work identically.
Reach these from the settings menu. All but one are fully functional.
| Page | Where | What it's for |
|---|---|---|
| Profile | /settings/profile | Your personal info for this org: pronouns, title, bio, work-style metrics (MBTI, Kolbe, CliftonStrengths), extra emails/phones, LinkedIn. |
| Account | /settings/account | Your login identity — email, password, two-factor, connected accounts (handled by Clerk, the sign-in provider). |
| Billing | /settings/billing | What your AI-agent team costs. Humans are free; each active AI agent is billable. Shows a monthly estimate. (Self-serve checkout is currently turned off — you aren't charged automatically.) |
| Integrations | /settings/integrations | Connect outside tools. API & MCP is live today; Slack, Google Workspace, and Microsoft 365 are marked "coming soon." |
| Notifications | /settings/notifications | A grid of which events (assignments, comments, mentions, headlines) notify you, and on which channel (email / web / mobile). |
| Preferences | /settings/preferences | Theme, date format, default team, timezone. |
| Coaches | /settings/coaches | See and revoke/restore which outside EOS coaches can view your workspace. |
| API Keys | /settings/api | Create and revoke keys that let your AI agents connect (see §14). |
| Configuration | /settings/configuration | Company-level info: name, website, description, and whether to list the org publicly. (Admins only can edit.) |
This is how an agent (e.g. Claude Code, ChatGPT) actually reads and writes your OrgTP data.
Where: /settings/api
Read-only tools work without a key; publishing to your OOS requires one. MCP (Model Context Protocol) is the standard that lets an AI agent talk to OrgTP's server safely.
Want the fast path? The Connect Your Agent page has a copy-paste AI prompt that generates your first OOS in about 60 seconds, plus a one-line install that gives Claude Code the OTP MCP server and slash commands.