This page is the parent hub for 30 practical 3RK guides covering editorial operations, meetings, handoffs, documentation, and AI workflow governance. If you know the operational problem you are solving, this page should help you find the right guide faster than browsing individual posts one by one.
Direct Answer
A small team usually needs fewer systems than it thinks, but those systems need clearer formats. Use this library when the real question is not “what tool should I try?” but “what structure should I use for this recurring job?”
If the work needs a reusable starting shell, start with a template. If the work needs a final pre-publish or pre-send review, use a checklist. If the work has stages and handoffs, use a workflow. If the work depends on routing or approval rules, use a matrix. This hub organizes the 30 guides around that logic.
Evaluation Criteria
- The page helps readers choose the right format before they choose more tools.
- Each cluster is organized by operational job, not by generic productivity language.
- High-risk handoffs and AI-assisted steps still show a human review point.
- The best next page is obvious for each type of problem.
- The hub stays useful even if a reader ignores the AI-specific pages.
Library Overview
| Cluster | Best for | Main formats | Best first page |
|---|---|---|---|
| Editorial Operations | Briefs, QA, updates, internal links, and content reuse | Checklists, templates, workflows | Editorial Workflow for Small Teams |
| Meetings and Accountability | Notes, action items, decisions, owners, and follow-up | Templates, checklists, workflows | Action Log Template |
| Requests, Handoffs, and Documentation | Intake, launch prep, stakeholder updates, and knowledge systems | Templates, checklists | Project Intake Form Template |
| AI Workflow Governance | Approval rules, prompt review, workflow intake, and adoption | Matrices, checklists, templates | AI Workflow Intake Template |
Format Selection Matrix
| If the problem is… | Start with… | Why it fits | Human review gate |
|---|---|---|---|
| A recurring document or request that needs the same structure every time | Template | Templates reduce blank-page friction and improve consistency. | Check that the template still matches the current process. |
| A final quality pass before publishing, sending, or handing off | Checklist | Checklists reduce avoidable mistakes in time-sensitive work. | Confirm who owns the final yes or no. |
| A sequence with several stages and handoffs | Workflow | Workflows make transitions visible and keep the team aligned. | Review who approves stage changes or exceptions. |
| A routing, approval, or escalation decision with different branches | Matrix | Matrices make ownership and review rules easy to scan. | Keep a named human owner for high-risk branches. |
Where to Start by Problem
| If your problem is… | Start here | Then read | Why |
|---|---|---|---|
| Weak briefs and inconsistent articles | Content Brief Template | Editorial QA Checklist | Fix the article plan first, then tighten review quality. |
| Meetings that create notes but not movement | Action Log Template | Post-Meeting Follow-Up Workflow | Track ownership first, then standardize the follow-up sequence. |
| Too many vague incoming requests | Project Intake Form Template | Marketing Request Template | Clarify the intake path before work enters the queue. |
| Unclear AI approval and review boundaries | Approval Matrix Template | AI Workflow Intake Template | Make review rules explicit before broader automation design. |
| Older content drifting out of date | Blog Post Update Checklist | Post-Publish Content QA Checklist | Refresh the page first, then improve the live quality pass. |
Editorial Operations Library
This cluster is for content systems: planning, briefing, reviewing, updating, linking, and repurposing. If your editorial work feels messy before it feels difficult, start here.
- Content Brief Template: Template for article angle, intent, sources, and internal links.
- SEO Content Brief Checklist: Checklist for search intent, source rules, and internal links before drafting.
- Editorial QA Checklist: Review checklist for claims, links, sources, and CTA alignment.
- Post-Publish Content QA Checklist: Live-page QA pass for links, formatting, tracking, and internal navigation.
- Blog Post Update Checklist: Evergreen maintenance checklist for facts, dates, examples, and CTA fit.
- Source Verification Checklist: Citation-quality checklist for AI and workflow articles.
- Internal Linking Workflow: Workflow for adding related guides without clutter or stuffing.
- Content Calendar Template: Template for planning newsletters, social posts, and lead magnets.
- Content Repurposing Checklist: Checklist for turning one source asset into multiple channel-specific outputs.
- Editorial Workflow for Small Teams: Hub workflow for brief, draft, review, publish, and update stages.
Meetings and Accountability Library
This cluster is for work that breaks down between discussion and execution. It is most useful when meetings generate notes, but not clear ownership, action items, or follow-up.
- Action Log Template: Template for tasks, owners, deadlines, blockers, and status.
- Meeting Agenda Template: Agenda format for decisions, blockers, owners, and next steps.
- Recurring Meeting Notes Template: Recurring notes format for agenda, decisions, and action items.
- One-on-One Meeting Template: Template for updates, blockers, feedback, and next steps.
- Post-Meeting Follow-Up Workflow: Workflow for turning discussion into owned tasks and review dates.
- Action Item Tracking Checklist: Checklist for converting notes into accountable work.
- Meeting Notes to Task Handoff Template: Template for moving decisions and tasks into the source-of-truth system.
- Decision Log Template: Template for recording choices, rationale, risks, and owners.
Requests, Handoffs, and Documentation Library
This cluster is for intake, cross-team coordination, launch prep, stakeholder communication, and shared team memory. Use these pages when work gets delayed because context, scope, or ownership is unclear.
- Project Intake Form Template: Intake structure for goals, scope, inputs, deadlines, and dependencies.
- Marketing Request Template: Request structure for goals, assets, due dates, and approvals.
- Campaign Handoff Template: Template for briefs, assets, links, launch readiness, and reporting.
- Launch Readiness Checklist: Checklist for content, QA, approvals, and follow-up before go-live.
- Stakeholder Update Template: Template for progress, risks, decisions, and next steps.
- Knowledge Base Audit Checklist: Checklist for outdated docs, gaps, ownership, and cleanup priorities.
AI Workflow Governance Library
This cluster is for teams that already know the operational job, but need clearer review boundaries before AI becomes part of the workflow. It is less about hype and more about where humans still need to approve, check, or stop the system.
- Approval Matrix Template: Matrix for who reviews what and when approval is required.
- AI Prompt Review Checklist: Checklist for prompt scope, inputs, constraints, and approval.
- Human Review Matrix: Matrix for where AI help stops and human review must stay.
- AI Workflow Intake Template: Template for goal, inputs, outputs, risks, and review gates.
- AI Tool Adoption Checklist: Checklist for rollout scope, training, owner, and risk review.
- AI Workflow Pilot Template: Template for test window, success criteria, and review plan.
How to Use This Parent Hub
If you are building from scratch, do not try to adopt every page at once. Start with one recurring pain point, choose the format that fits it, and adopt one guide as the team’s working standard. Once that works, add the next format that solves the next recurring problem.
Most small teams can grow this library in a practical order: one intake or brief template, one review checklist, one workflow for repeated handoffs, and one matrix for routing or approval logic. Optional AI support can help with summaries, first drafts, or clustering repetitive work, but the library only becomes trustworthy when human ownership stays explicit.
Review Checklist
- The selected guide matches the operational job, not just the keyword.
- The chosen format is clear before the team adds more tooling around it.
- Approval points and high-risk handoffs still have a human owner.
- The cluster path from one guide to the next is easy to follow.
- The hub stays useful for non-AI and AI-adjacent readers alike.
FAQ
What is the difference between this hub and the Small Team Workflow Library?
The Small Team Workflow Library is the broader format-first hub. This page is the parent hub for the 30 competitor-inspired operational resources that now sit under that broader system.
Should I start with a template or a workflow?
Start with a template when the structure should repeat. Start with a workflow when the work moves through several stages or handoffs.
When should I use the AI workflow pages?
Use them when the operational job is already clear, but the team still needs explicit review gates, scope rules, or adoption boundaries before AI becomes part of the process.
Does every team need all 30 pages?
No. The point of the hub is to help teams adopt the few pages that match their real recurring jobs instead of trying to implement every format at once.
Can AI help build or run this library?
Yes, especially for first-pass summaries, clustering, and draft structures, but the library should still function with human ownership, review, and maintenance.
Bottom Line
A useful operations template library is not a pile of documents. It is a navigable system of templates, checklists, workflows, and matrices that match recurring jobs across content, meetings, handoffs, documentation, and AI review. Once the format fits the problem, the team can move faster with fewer repeated mistakes.
Verified External Sources
- Google helpful content guide
- Google crawlable links guidance
- Asana templates
- Notion templates
- OpenAI safety best practices
- Microsoft generative AI architecture overview