PARA Method Project Active Dashboard

Template Overview

In Tiago Forte’s Building a Second Brain (BASA) methodology, personal knowledge is organized by actionability rather than topic. The top tier of this taxonomy is Projects: active endeavors with specific outcomes and defined deadlines.

Without a dedicated Project Dashboard, projects suffer from fragmented assets: to-do lists in one app, reference links in browser bookmarks, meeting notes in another tool, and strategic plans lost in email threads.

This template provides a unified PARA Project cockpit: project metadata, definition of done, deadline constraints, milestone timeline, active task checklist, linked vault references, and post-project archive retrospective.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Project: [Project Name]"
date: [YYYY-MM-DD]
target_deadline: [YYYY-MM-DD]
status: "Active"
priority: "High"
associated_area: "[[Area-Name]]"
lead_owner: "[Your Name / Project Lead]"
tags: [para, pkm, projects, productivity, execution]
---

# Project: [Project Name]

## 1. Project Charter & Definition of Done
- **Desired Outcome:** In one unambiguous sentence, what will exist when this project is successfully completed?
- **The Non-Negotiable Deadline:** [YYYY-MM-DD] (Firm cutoff date).
- **Success Criteria / Definition of Done:**
  - [ ] Criteria 1: [Specific deliverable completed and verified].
  - [ ] Criteria 2: [Stakeholder approval or customer acceptance received].
  - [ ] Criteria 3: [Documentation committed and deployed].

## 2. Milestone Roadmap & Phases
| Milestone Phase | Target Date | Deliverable Focus | Status |
| :--- | :--- | :--- | :--- |
| **Phase 1: Architecture & Design** | [YYYY-MM-DD] | Technical spec and mockups approved | Complete |
| **Phase 2: Core Implementation** | [YYYY-MM-DD] | Functional build passing test suite | In Progress |
| **Phase 3: QA & Security Audit** | [YYYY-MM-DD] | Zero P0/P1 defects verified | Pending |
| **Phase 4: Launch & Handover** | [YYYY-MM-DD] | Public release and team documentation | Pending |

## 3. Active Next Actions & Task Checklist
- [ ] **Next Physical Action:** [Immediate 15-minute task to regain momentum].
- [ ] [High-priority implementation task].
- [ ] [Review task with external stakeholder].
- [ ] [Draft release documentation].

## 4. Linked Vault Knowledge & Project Assets
- **Project Brief & Specifications:** [[PRD-Project-Name]]
- **Meeting Records:** [[Meetings-Project-Name-Archive]]
- **Related Research & Resources:** [[Resource-Topic-Guide]]

## 5. Log of Recent Progress & Decisions
- **[YYYY-MM-DD]:** Decided to adopt local SQLite instead of cloud PostgreSQL to eliminate latency.
- **[YYYY-MM-DD]:** Phase 1 architectural sign-off achieved.

## 6. Project Completion & Archival Protocol
*Complete when all milestones are achieved before moving this file to `4-Archives`.*
- [ ] Final retrospective written and lessons captured in [[Area-Continuous-Improvement]].
- [ ] Temporary scratch files cleaned up.
- [ ] Folder moved to `4-Archives/YYYY-[Project-Name]`.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Project: Launch Oyma Templates Gallery v1"
date: [YYYY-MM-DD]
target_deadline: [YYYY-MM-DD]
status: "Active"
priority: "High"
associated_area: "[[Area-Product-Marketing]]"
lead_owner: "Engineering & Editorial Guild"
tags: [para, pkm, projects, productivity, execution]
---

# Project: Launch Oyma Templates Gallery v1

## 1. Project Charter & Definition of Done
- **Desired Outcome:** Publish a curated Templates Gallery featuring 120 downloadable Markdown templates across 12 categories, with all 24 SEO gates passing 100% and deployment to production edge.
- **The Non-Negotiable Deadline:** [YYYY-MM-DD]
- **Success Criteria / Definition of Done:**
  - [x] All 120 templates authored with complete overviews, structures, examples, and FAQs.
  - [x] All 12 category hub pages and main `/templates` index live and responsive.
  - [x] All 24 SEO verification gates passing with 0 errors.
  - [x] Sitemaps updated to 405 total indexable pages and submitted to IndexNow.

## 2. Milestone Roadmap & Phases
| Milestone Phase | Target Date | Deliverable Focus | Status |
| :--- | :--- | :--- | :--- |
| **Phase 1: Schemas & Routing** | [YYYY-MM-DD] | Content collections, hubs, and layouts | Complete |
| **Phase 2: Batches 1 & 2 (Cats 1-6)** | [YYYY-MM-DD] | 60 templates generated and verified | Complete |
| **Phase 3: Batches 3 & 4 (Cats 7-12)** | [YYYY-MM-DD] | 60 templates generated and verified | In Progress |
| **Phase 4: Two-Commit & Deployment** | [YYYY-MM-DD] | Production edge deploy & IndexNow submission | Pending |

## 3. Active Next Actions & Task Checklist
- [x] Generate Batch 3 templates (Categories 7-9).
- [ ] Generate Batch 4 templates (Categories 10-12).
- [ ] Execute `pnpm build && pnpm gates` to confirm 100% green status across 405 pages.
- [ ] Execute two-commit cadence (code commit + execution ledger commit).
- [ ] Deploy to Cloudflare Workers production edge and submit to IndexNow.

## 4. Linked Vault Knowledge & Project Assets
- **Project Master Plan:** [[Master-SEO-Plan-2026]]
- **Category Taxonomy:** [[Template-Categories-Spec]]
- **SEO Gates Criteria:** [[SEO-Gates-Validation-Rules]]

## 5. Log of Recent Progress & Decisions
- **[YYYY-MM-DD]:** Completed Batch 1 & 2 templates with 100% pass on 8-gram shingle uniqueness.
- **[YYYY-MM-DD]:** Batch 3 built cleanly; 375 total indexable pages validated.

## 6. Project Completion & Archival Protocol
- [ ] Confirm edge HTTP 200 responses on production URLs.
- [ ] Submit URLs to search engines via IndexNow.
- [ ] Update `docs/execution/progress.json` and move project notes to archive.

When to Use and When to Avoid

When to Use

• Tracking active projects with defined outcomes, deadlines, and deliverables in PARA.
• Consolidating scattered project assets, meetings, specs, and next actions into a single hub.
• Reviewing active project status during weekly or monthly personal reviews.
• Ensuring a clean retrospective and archival handover when an initiative concludes.

When to Avoid

• Managing open-ended areas of responsibility with no end date (use an Area note instead).
• Storing passive reference libraries or reading lists (use a Resource note instead).
• Recording atomic philosophical insights (use an Atomic Permanent note instead).
• Logging ephemeral daily to-do scratchpad notes.

On-Device AI Integration

Organize PARA projects with Oyma on macOS:

Analyze the project goals, deliverables, and team deadlines:
1. Synthesize a sharp definition of done and state the non-negotiable deadline.
2. Structure the milestone roadmap table across architecture, execution, and launch phases.
3. Formulate the active task checklist highlighting the next immediate physical action.
4. Establish linked vault asset connections and archival completion protocols.
Output in clean, structured CommonMark.

Your project timelines, roadmaps, and business assets remain completely private on your Mac.