---
title: Subtask Workflow for Bulk Pages
type: article
created: '2025-11-03'
updated: '2025-11-03'
source_docs:
- raw/2025-11-03-design-team-sync-98639555.md
tags:
- project-management
- workflow
- client-feedback
- clickup
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Subtask Workflow for Bulk Pages

## Overview

When a project requires creating a large number of similar pages (e.g., state-specific landing pages, location variants, templated content pages), batching the work into small subtask groups of 4–5 pages at a time reduces the risk of compounding errors and keeps client feedback manageable.

This pattern emerged during the [[wiki/clients/bluepoint/_index|Bluepoint]] state services page project, where a single ClickUp card covering all pages at once was identified as a likely source of confusion and quality drift.

## The Problem with Doing All Pages at Once

When bulk page work is tracked as a single task:

- Client feedback arrives in large, hard-to-triage batches
- Errors introduced early propagate across all remaining pages before they're caught
- It becomes difficult to track which pages have been reviewed and approved
- Designers and developers lose a clear sense of progress and priority

## Recommended Approach

### 1. Create a Parent Task in ClickUp

Set up a single parent card for the overall deliverable (e.g., "Bluepoint State Pages"). Write a clear description covering the repeatable changes required per page.

### 2. Add Subtasks in Batches of 4–5

Rather than listing every page as a separate top-level task, add subtasks to the parent card in groups of 4–5. Work through one batch, get client sign-off, then proceed to the next.

> "I think we do like four or five at a time… I'm worried that if we do all of these on one card, the client, there's going to be feedback, and we're going to start getting sloppy."
> — Melissa Cusumano, Design Team Sync 2025-11-03

Andrzej's suggestion to use subtasks rather than separate tasks was adopted specifically to avoid cluttering the task board while still maintaining granular tracking.

### 3. Define Repeatable Changes per Page

Document the standard changes required for each page in the parent task description so the designer doesn't need to re-reference source materials for every subtask. For Bluepoint, these were:

- Update hero image background for the specific state
- Update state-specific copy
- Replace phone number (use a placeholder if the real number isn't available yet)
- Remove any region-specific logos (e.g., Colorado logos)

### 4. Use Placeholders for Missing Content

If content (such as phone numbers or region-specific assets) isn't available yet, insert clearly labeled placeholders rather than blocking progress. This keeps the batch moving and makes the gaps visible for review.

### 5. Prioritize and Sort Subtasks

With subtasks, it's easy to assign priority order — complete higher-priority states or regions first, and sort accordingly within the parent card.

## Benefits

| Approach | Risk |
|---|---|
| Single task, all pages | Feedback overwhelm, error propagation, unclear progress |
| Separate top-level tasks per page | Task board clutter, hard to see the big picture |
| **Parent task + batched subtasks (4–5)** | **Manageable feedback cycles, clear progress, contained errors** |

## When to Use This Pattern

Apply this workflow whenever:

- A project involves **5 or more structurally similar pages**
- The client will be reviewing and providing feedback on the output
- The work involves **templated changes** (swap image, update copy, change phone number, etc.)
- A single designer or developer is executing the work sequentially

## Related

- [[wiki/clients/bluepoint/_index|Bluepoint]] — first project to use this workflow
- [[wiki/knowledge/project-management/clickup-task-hygiene|ClickUp Task Hygiene]] — general task management conventions