Action Log

For leaders who report status upward

Your board scorecard, current before you open it

Action Log syncs status and owners from Jira, Azure DevOps, and Basecamp, and your AI assistant fills in the rest from email, comments, and meetings. You review one view by workstream and send the update upward.

Get started free

Free plan available. Works with Claude through MCP. No credit card.

Most of the status meeting is reading rows that did not change.

If you lead several teams and report to a board or leadership team, your week probably includes:

  • A status meeting spent going row by row through a spreadsheet where almost nothing moved.
  • Updates scattered across Jira, DevOps, Basecamp, email, and chat, with no single current picture.
  • A board scorecard you rebuild by hand every week from all of the above.

You need the current picture, and the hour back.

How it works

  1. Connect your tools. Link Jira, Azure DevOps, or Basecamp. Status and owners sync automatically as your teams work.
  2. Let Claude add the context. Connect Claude with one URL. Ask it to read your email and meeting notes, and it updates the right actions for you.
  3. See the plan by workstream. Actions roll up into a few areas, each with a health status and its blockers. Open one only when it needs you.
  4. Report from the scorecard. Each area on one row with its owner, RAG, what changed, and the next step, ready for your board pack.

See the whole plan, not hundreds of actions

A long action list is hard work to read. Workstreams group actions by area of the plan, so a handful of cards tell you where things stand. Open a card only when it needs you.

  • Health at a glance: Each workstream rolls its actions up into On track, At risk, Quiet, or Blocked, with the reason in one line.
  • Problems surface on their own: Blocked dependencies and quiet areas show on the card, so you stop scanning rows to find them.
  • Drill in only when needed: Click a card to see just that area’s actions. Tag rules file new work into the right workstream.

Status and owners sync from the tools your teams already use

Link actions to Jira issues, Azure DevOps work items, and Basecamp to-dos. When the status or assignee changes there, Action Log updates on its own, and mismatches are flagged for review.

Available now: Jira, Basecamp, Azure DevOps. Coming soon: GitHub, Monday.

Your AI assistant does the reading

Connect Claude to Action Log with a single URL and your usual login. Ask it to review Basecamp threads, email, and DevOps comments, and it updates actions and workstreams for you. Your tools sync status and owners on their own; Claude adds the context in between.

In Claude Code, run this once and sign in with your Action Log account when prompted. No API keys to copy.

claude mcp add --transport http actionlog https://www.actionlog.app/mcp

Claude Desktop, GitHub Copilot, Cursor, and other MCP clients connect with the same URL. https://www.actionlog.app/mcp

Ask Claude:

  • Review this week’s Basecamp threads and my email, and update Action Log.
  • Which workstreams went quiet, and what changed since last week?
  • Draft this week’s scorecard by workstream, with a line on what changed for each.

Area owners keep their own status current

Each workstream has a named owner, the same way your board scorecard does. Owners update their items through a personal magic link, with no account to create and no paid seat.

  • Magic links: One click from an email to their own items. Nothing to install.
  • Daily digests: Owners see what is due soon and overdue before you have to ask.
  • Quiet-work alerts: Workstreams with no recent movement surface on their own, before the board asks.

A scorecard your board recognizes

Each area on one row: its owner, RAG status with the reason, what changed this week, the next step, and where help is needed. Copy the table or export it into your board pack.

Turn meeting transcripts into tracked actions

Paste a transcript from Zoom, Teams, Meet, or your AI notetaker. Action Log proposes actions, owners, and due dates, and you choose what lands in each workstream.

Why Action Log exists

As a CTO and VP, I sat through the same status meeting every week: open the spreadsheet, go row by row, and learn that most of it hadn't changed. I built Action Log to fix that. Then I connected Claude, let it read our Basecamp, email, and DevOps, and it became where I check every workstream and prepare my board scorecard each week.

Glen Conway, Founder, Action Log

Pricing that matches the way you actually work

Start free on one project, then upgrade when you track several programs or bring in more editors.

Free: $0 no credit card

Track one project end to end, including Claude and transcripts

  • Projects you own: 1
  • Editors: Up to 3 (People who can change actions and projects)
  • Transcript-to-actions: Included
  • AI credits per month: 50 (About 2 half-hour meeting transcripts)
  • Stakeholder magic links and digests: Included
  • Integrations: 1 connection per tool

Pro: $10 per editor / month

For people who run several teams or workstreams

  • Projects you own: Unlimited
  • Editors: Unlimited (Buy and assign editor seats from billing)
  • Transcript-to-actions: Included
  • AI credits per month: 500 (About 20 half-hour meeting transcripts)
  • Stakeholder magic links and digests: Included
  • Integrations: 1 connection per tool

Business: $20 per editor / month

Several project leads on one company subscription

  • Projects you own: Unlimited
  • Editors: Unlimited (Team billing for departments and shared budgets)
  • Transcript-to-actions: Included
  • AI credits per month: 2,000 (About 80 half-hour meeting transcripts)
  • Stakeholder magic links and digests: Included
  • Integrations: Multiple per tool (Connect several Jira sites, DevOps orgs, or Basecamp accounts)

Stakeholders are always free. You pay only for editors. People who view or update their own items through a magic link never need a seat.

Frequently asked questions

What does Action Log sync automatically?

Status and assignees sync from linked Jira issues, Azure DevOps work items, and Basecamp to-dos, and Action Log flags any item where the two disagree. Comments and discussion stay in those tools; connect Claude through MCP to bring that context into Action Log.

How do I connect Claude?

In Claude Code, run "claude mcp add --transport http actionlog https://www.actionlog.app/mcp" and sign in with your Action Log account when prompted. There are no API keys to copy. Claude Desktop, GitHub Copilot in VS Code, Cursor, and other MCP clients connect with the same URL.

Can it produce the scorecard I send to my board?

Mark the workstreams that belong on your scorecard, give each an owner, and Action Log shows status, health, and an AI-drafted note on what changed since last week. Review it, adjust anything, and carry it into your board pack or reporting system.

What is a workstream?

A workstream is one area of your plan, such as hiring, platform reliability, or a product launch. It groups the related actions and shows their combined health, so you read a few cards instead of every action. Each workstream can have an owner and can appear as a row on your scorecard.

How is this different from project management software?

Action Log sits above your project tools. Teams keep working in Jira, DevOps, or Basecamp; Action Log reads their status and rolls it up by workstream for leadership. It has no sprints, backlogs, or Gantt charts.

I already use an AI notetaker. Do I still need Action Log?

Keep your notetaker. Paste its transcript or notes into Action Log and the actions join the same workstream view as everything synced from your tools, with owners and reminders until they are done.

Do area owners need to log in to update their items?

No. Owners receive a personalized magic link and can view and update their own items without creating an account. People who only update their own items are always free.

Where is my data stored, and is it used to train AI?

Action Log runs on Microsoft Azure in the United States. AI processing uses Azure OpenAI Service on our own Azure resource, and your data is never used to train AI models. Transcripts stay with your project so you can see where each action came from, and they are deleted when you delete the project or your account.

Can I get my data out?

Yes. Export your full project to Excel or JSON at any time. You are never locked in to Action Log.

See every workstream before your next board update

Connect a tool, connect Claude, and let the scorecard fill in. Free to start, and your teams keep working where they already do.

Get started free

Free plan available. No credit card.