--- title: 'How to Use Airtable for Task Management (With Subtasks, Dependencies, and Recurring Tasks)' description: 'Build a full Airtable task management system with subtasks, dependencies, recurring tasks, and multiple views. Yes, Airtable is a real project management tool.' canonical_url: 'https://www.business-automated.com/tutorials/airtable-task-management-with-subtasks' md_url: 'https://www.business-automated.com/tutorials/airtable-task-management-with-subtasks.md' last_updated: 2026-05-03 --- "Is Airtable a project management tool?" is a question we answer almost every week, and the answer is always the same: **yes, and after the first serious build it's usually better than the dedicated PM tools.** Airtable's flexibility means you can model any process — not just the generic "project → task → subtask" hierarchy baked into tools like Asana or Monday, but the specific shape your team actually needs. The catch is that "flexible" means "you have to build it." This guide walks through building a complete [Airtable](/airtable-consultant) task management system from scratch: subtasks, dependencies, recurring tasks, the right set of views, and the automations that make the whole thing feel like a real PM tool. By the end you'll have a system that can run a single team's task board, a multi-project consultancy, or a company-wide operations tracker — all on the same foundation. ## The Core Schema Every Airtable task management system needs at minimum these tables: **1. Tasks** (the main table). Fields: - Name (Primary field, Single Line Text) - Status (Single Select: Not Started, In Progress, Blocked, Done, Cancelled) - Assignee (Collaborator) - Due Date (Date) - Priority (Single Select: P1, P2, P3, P4) - Description (Long Text) - Project (Linked Record → Projects) - Parent Task (Linked Record → Tasks, self-link) - Blocked By (Linked Record → Tasks, self-link) - Estimated Hours (Number) - Actual Hours (Number) - Created At (Created Time) - Last Modified (Last Modified Time) **2. Projects** (optional but recommended). Fields: - Name (Primary) - Client (Linked Record → Clients, if multi-client) - Owner (Collaborator) - Start Date, End Date (Date fields) - Status (Single Select) - Budget (Currency) - Tasks (Linked Record → Tasks, inverse of the Tasks.Project link) **3. Clients** (if the work is for external clients). That's the foundation. Most of the rest of this guide is about what you layer on top of it. ## Subtasks: The Self-Link Pattern The single most important pattern in Airtable task management is the **self-linked record**. Instead of having a separate "Subtasks" table, you add a linked-record field on the Tasks table that points back to the Tasks table itself. **How to set it up:** 1. In the Tasks table, add a new Linked Record field. 2. Set the target table to... Tasks (the same table). 3. Name it `Parent Task` and allow only one link. 4. Airtable automatically creates the inverse field `Subtasks` (allowing multiple links). Now any task can reference a parent task, and any task can have multiple subtasks. You get unlimited nesting — a subtask can have its own subtasks, which can have theirs, and so on. **Viewing the hierarchy:** - **Grid view with grouping.** Group by Parent Task to see tasks nested under their parents. - **Filter to top-level only.** Add a view filter where Parent Task is empty to see just the top-level tasks. - **Drill into a task.** Click any task to see its expanded view, including a Subtasks section listing all its children. **Rolling up subtask progress to parents:** Add a Rollup field on Tasks called `Subtask Progress`. Configure it to roll up the Status field of linked Subtasks, using a formula like: ```airtable-formula COUNTALL(values) > 0 ? ROUND(COUNT(values) / COUNTALL(values) * 100) & '%' : '' ``` Adjust the formula based on how you want to measure completion. Common variants: percentage of subtasks marked Done, count of open subtasks, earliest due date across subtasks. ## Dependencies: The "Blocked By" Self-Link A task that can't start until another task is done is a **dependency**, and you model it the same way as subtasks — with a self-link. But this one is `Blocked By` / `Blocks`. **How to set it up:** 1. Add another Linked Record field on Tasks, targeting Tasks. 2. Allow multiple links (a task can be blocked by several others). 3. Name it `Blocked By`. Airtable creates the inverse `Blocks`. **Enforcing dependencies with a formula:** Add a formula field called `Can Start` that checks whether all blockers are done: ```airtable-formula IF( {Blocked By}, IF( {Blockers Not Done}, '🔴 Blocked', '🟢 Ready' ), '🟢 Ready' ) ``` To compute `Blockers Not Done`, add a rollup field that counts how many blocker tasks are in a status other than Done. If it's greater than zero, the task isn't ready to start. **Visualizing dependencies:** Airtable's Gantt view (on supported plans) draws dependency arrows between task bars when you configure the view with a dependencies linked-record field. Timeline view can show tasks stacked with their dependency relationships. **Automating dependency notifications:** Build an automation: "When a task's status changes to Done, find all tasks where Blocked By contains this task, and notify the assignees that their blockers are cleared." This turns dependency tracking from a passive visualization into an active workflow. ## Recurring Tasks: The Scheduled Automation Pattern Recurring tasks are surprisingly tricky because Airtable doesn't have a native "recurrence" concept. The cleanest pattern is a scheduled automation that generates instances. **Fields to add to Tasks:** - `Recurrence` (Single Select: Daily, Weekly, Biweekly, Monthly, Quarterly, None) - `Recurrence Owner` (Collaborator — who should be assigned to new instances) - `Next Due` (Date) - `Is Template` (Checkbox — marks the task as the recurring template, not an actual instance) **The template pattern:** Mark a task as `Is Template` and set its Recurrence. This task is never "done" — it's the blueprint for future instances. Real work happens on the instances. **The scheduled automation:** 1. **Trigger:** At scheduled time (daily at 6 AM). 2. **Find records:** All templates where `Next Due` is today or earlier. 3. **For each:** Create a new Task record with the template's fields copied over, set Status to Not Started, set Due Date to `Next Due`, set Assignee to `Recurrence Owner`, and clear `Is Template`. 4. **Update the template's `Next Due`** based on the Recurrence type (`DATEADD({Next Due}, 1, 'weeks')` for Weekly, and so on — see our [date formulas guide](/tutorials/airtable-date-formulas)). Every morning, the automation generates the tasks that are due that day. Past instances stay in the base as a history. **Variations:** - **Business-day-only recurrence.** Use WORKDAY instead of DATEADD for "next weekday." - **Monthly on specific day.** Compute the next instance with date math that handles month-end edge cases. - **Conditional recurrence.** Only generate a new instance if the previous one was marked Done (useful for checklist-style recurring work). ## The Essential Views A task management base needs a specific set of views for different audiences. At minimum: **View 1: My Tasks (personal).** - Filter: Assignee = current user, Status ≠ Done AND Status ≠ Cancelled - Group by: Due Date (Today, This Week, Next Week, Later) - Sort: Priority ascending, Due Date ascending - Purpose: "What am I working on right now?" **View 2: Team Kanban.** - Layout: Kanban - Group by: Status - Filter: Status ≠ Done (or show Done only for the last 7 days) - Purpose: "Where is the team's work?" **View 3: Calendar.** - Layout: Calendar - Date field: Due Date - Color by: Assignee or Project - Purpose: "What's happening when?" **View 4: Timeline / Gantt.** - Layout: Timeline or Gantt - Date fields: Start Date, Due Date - Group by: Project - Purpose: "How do these tasks fit together over time?" **View 5: Blocked Tasks (special alert view).** - Filter: Status = Blocked, or formula-based `Can Start` = Blocked - Sort: By days blocked descending - Purpose: "What needs attention because something is stuck?" **View 6: Overdue (management oversight).** - Filter: Due Date < TODAY() AND Status ≠ Done - Group by: Assignee - Purpose: "Who has past-due items?" These six views cover the "where is everything?" question from every angle — individual, team, calendar, dependency, exception, and oversight. You'll add more specific to your use case, but these are the foundation. ## Recurring Tasks Meets Subtasks: Template Checklists One of the most powerful combinations is recurring tasks with pre-populated subtasks — think monthly accounting close checklists or weekly content publishing workflows. **The pattern:** 1. Create a parent Task marked `Is Template` with Recurrence = Monthly. 2. Create child Tasks also marked `Is Template`, linked as subtasks to the parent. 3. The scheduled automation that generates monthly instances is modified: when it creates the parent instance, it also creates copies of all the subtask templates and links them to the new parent. The team gets a fresh parent task every month with all the subtasks already laid out. They work through the checklist, check off each subtask, and the monthly close is complete. ## Automations That Make Everything Feel Alive Beyond the recurring task generator, these are the automations we recommend on almost every task management base: **1. Overdue notifications.** Daily at 9 AM, find all tasks where Due Date < today AND Status ≠ Done, and send the assignee a summary email or Slack message. **2. Status change notifications.** When a task's Assignee changes, notify the new assignee with a link to the task. **3. Blocker cleared notifications.** When a task enters Done, find all tasks that list it as a blocker and notify their assignees. **4. New subtask notifications.** When a subtask is added to a parent, notify the parent's assignee so they're aware of the scope expansion. **5. Stale task warnings.** When a task has been in In Progress for more than N days without status change, alert the assignee and their manager. Each automation is a small thing. Together, they turn a static task list into an active workflow that nudges people when nudging is useful. ## Pair With Interfaces for a Real PM Tool Once the base is built, Interface Designer turns it into something that looks and feels like a dedicated PM tool. Build: - **A personal dashboard** with "My Tasks," "Overdue," and "Upcoming" sections. - **A team overview** with Kanban boards for each active project. - **A project detail page** with the project info, its timeline, its tasks, and its team. - **A manager view** with utilization, overdue counts, and blocker alerts. Each interface is scoped to its audience. The personal dashboard filters to the logged-in user; the team overview shows everything; the manager view layers aggregate metrics on top. See our [guide to building Airtable interfaces with Omni](/tutorials/build-interfaces-with-airtable-omni) for how to scaffold these quickly. ## When Airtable Isn't the Right Tool Airtable is excellent for most task management use cases, but it's not universal. Skip Airtable and use a dedicated PM tool when: - **You need the absolute simplest setup with zero customization.** Trello or Asana give you a usable task board in five minutes. - **Your team needs advanced specialist features** like native Gantt dependencies with critical path analysis, built-in time tracking with timer interfaces, or resource management with capacity forecasting. These exist in Airtable but typically need custom builds or add-ons. - **The rest of your tooling is already deeply integrated with a specific PM tool.** Don't migrate to Airtable just for the sake of it. For everything else — and especially when your task data needs to connect to other business data (clients, projects, finances, deliverables) — Airtable is a better long-term choice than any dedicated tool because it adapts to your needs instead of forcing you to adapt to its. ## The Bigger Picture A properly-built Airtable task management system is one of the highest-leverage things a team can have. It's the central nervous system that connects work to outcomes, assignees to accountability, and deadlines to action. Done well, it replaces three or four separate tools (tasks, calendar, dependency tracker, reporting) with a single base that everyone understands. The investment is in the build. Once it's running, it costs almost nothing to maintain and saves hours of coordination overhead every week. If you're also managing approvals, client reporting, or recurring operations inside the same base, pair this guide with our tutorials on [building an Airtable approval workflow](/tutorials/airtable-approval-workflow) and [client reporting dashboards](/tutorials/airtable-client-reporting-dashboards). All three systems can share the same underlying base and reinforce each other. ## Let Us Build It At [Business Automated](/airtable-consultant), we've built Airtable task management systems for agencies, consultancies, in-house ops teams, and small businesses. We know which patterns hold up at scale and which ones look clever but fall apart after six months. If your team is tired of the dedicated PM tool they're currently using — too rigid, too limited, too disconnected from everything else — let us build you the version that fits. [Get in touch](/airtable-consultant) and we'll scope a task management system that actually fits your process. ## Sitemap See the full [sitemap](/sitemap.md) for all pages.