> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spineworkspace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Founder Ops Workflows: Board Prep, Weekly Review, and Follow-Up

> Primary Founder Ops workflows: triggers, steps, handoffs, approvals, and receipts for board prep, weekly review, decisions, and follow-up.

Workflows in Founder Ops are repeatable, governed sequences of capabilities. They connect human decisions with automated execution across source systems.

## Weekly Business Review

**Trigger:** Scheduled weekly cadence based on Calendar and user preference.

**Steps:**

1. Metrics Agent pulls latest KeyMetric values from Salesforce dashboards.
2. Twin assembles open decisions and at-risk commitments from the past week.
3. The weekly review document is drafted in Notion with sections for metrics, decisions, and commitments.
4. A review meeting is scheduled with pre-reads attached automatically.
5. Attendees annotate in context. Decisions and new commitments are recorded during the meeting.

**Receipt:** A meeting receipt captures recorded decisions, updated commitments, and metrics snapshot.

## Board Preparation

**Trigger:** A board meeting is scheduled in Calendar.

**Steps:**

1. Board Prep Agent gathers board deck stubs, previous action items, and decision summaries.
2. Metric snapshots are inserted from Salesforce or board portal sources.
3. Initiative updates and commitment statuses are compiled into structured sections.
4. The review draft is surfaced for executive and chief-of-staff review.
5. Approved drafts are exported or shared to the board portal.

## Decision Log Workflow

**Trigger:** Twin detects a topic discussed in multiple channels without a recorded decision.

**Steps:**

1. Triage flags the topic and assembles related messages and notes.
2. Twin proposes a decision record with options and recommended resolution.
3. The executive reviews and either records the decision or declines.
4. On record, the decision is written to Notion and linked to source conversations.

## Follow-Up Workflow

**Trigger:** Commitment due date approaches or an action item is created in a meeting.

**Steps:**

1. Commitment Agent surfaces the item in the Commitments Tracker.
2. An update is requested from the owner via Slack or email.
3. The owner responds and updates status, which writes back to Notion and Calendar.
4. Twin records the update and reschedules any dependent reviews.

## Related

* [Founder Ops Index](/internal-docs/domains/founder-ops/index)
* [Capabilities](/internal-docs/domains/founder-ops/capabilities)
* [Execution Flow](/internal-docs/domains/founder-ops/execution-flow)
* [AI Workbench](/internal-docs/domains/founder-ops/ai-workbench)
* [Governed Actions](/how-it-works/governed-actions)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.