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

# Blocks

> Capacity reservations for client work

Blocks are capacity reservations that help plan and schedule client work for the month ahead. They represent phases of work like Design, Development, and QA, ensuring team capacity is allocated appropriately.

## What are blocks?

Blocks are monthly capacity allocations:

* Reserve team member time for specific work phases
* Organized by client and month
* Track scheduled hours (from tasks) vs logged hours (time entries)
* Appear in team schedules
* Help visualize monthly workload

<Info>
  Blocks are planning tools. They show what capacity is reserved, but actual work is tracked through time entries and subtasks.
</Info>

## Why use blocks?

### Capacity planning

Blocks help ensure:

* Team members aren't over-allocated
* Client work is planned in advance
* Work phases are sequenced correctly
* Realistic delivery timelines

### Schedule visibility

Team members see:

* What client work is coming
* When they're needed
* How much time is allocated
* Their monthly workload

### Client coordination

Blocks help coordinate:

* When design work will happen
* When development can start
* When QA rounds are scheduled
* Deployment timing

## Block components

### Basic information

Every block includes:

* **Client** - Which client the work is for
* **Month/Year** - When the work is planned
* **Block type** - Phase of work (Design, Development, QA, etc.)
* **Round** - For QA blocks, which iteration

### Schedule details

When planned:

* **Assignee** - Team member assigned
* **Start date** - When work should begin
* **End date** - When work should complete
* **Status** - Current state

### Status tracking

| Status                                        | Description                   |
| --------------------------------------------- | ----------------------------- |
| **Not Scheduled**                             | Created but no dates assigned |
| **Scheduled** - Dates assigned, ready to work |                               |
| **In Progress**                               | Work has started              |
| **Completed**                                 | Work finished                 |
| **Late**                                      | Not completed by end date     |

## Block types

### Core blocks

**Design:**

* UI/UX work
* Visual assets
* Creative direction
* Mockups and prototypes
* One per client per month

**Development:**

* Code and features
* Technical implementation
* Integrations
* One per client per month

**Deployment:**

* Production deployment
* Release management
* Go-live coordination
* One per client per month

### QA blocks

**Internal QA Review:**

* Team testing
* Bug identification
* Quality verification
* Can have multiple rounds

**Internal QA Fixes:**

* Bug fixes from internal QA
* Adjustments and corrections
* Can have multiple rounds

**External QA Fixes:**

* Client feedback changes
* Revisions after client review
* Can have multiple rounds

<Note>
  QA blocks support multiple rounds. For example, "Internal QA Review (Round 2)" if testing needs to happen again.
</Note>

## Creating blocks

### Who can create

Users who can manage blocks:

* Project Managers
* CSMs
* Managers
* Admins

### Adding blocks

<Steps>
  <Step title="Navigate to Blocks">
    Go to Blocks page from main navigation
  </Step>

  <Step title="Select month">
    Use month navigation to choose planning month
  </Step>

  <Step title="Find client">
    Click on client row to expand
  </Step>

  <Step title="Add block">
    Click "Add block" button
  </Step>

  <Step title="Choose type">
    Select block type from menu
  </Step>

  <Step title="Block created">
    Block added to client's month
  </Step>
</Steps>

### Block restrictions

**Single instance types:**

* Design, Development, Deployment
* Can only add once per month per client
* Button disabled if already exists

**Multi-round types:**

* All QA blocks
* Can add multiple rounds
* Automatically numbered (Round 1, Round 2, etc.)

## Configuring blocks

### Assigning team members

Assign who will do the work:

* Click block to configure
* Select assignee from team
* Filtered by work type (design/dev/QA)
* Assignee sees block in their schedule

### Scheduling dates

Set when work will happen:

* Start date
* End date
* Block appears in schedule on these dates
* Status changes to "Scheduled" automatically

### Status updates

Track block progress:

* **Not Scheduled** - Initial state
* **Scheduled** - Dates assigned
* **In Progress** - Work started (manual update)
* **Completed** - Work finished (manual update)
* **Late** - Past end date, not complete

<Tip>
  Configure blocks early in the month to help team members plan their time.
</Tip>

## Viewing blocks

### Blocks page

Global view of all clients:

* Navigate by month
* See all active clients
* Expand to view client's blocks
* Click client name to go to client schedule

### Client schedule

Client-specific view:

* Shows blocks for this client
* Alongside tasks and other work
* Integrated timeline
* Color-coded by type

### Team schedule

Individual team member view:

* Shows blocks assigned to them
* Mixed with tasks and other work
* See total capacity for each day
* Plan around commitments

## Hours tracking

### Scheduled hours

Hours from tasks assigned to the block:

* Automatically calculated from task estimates
* Updates as tasks are added or removed
* Shows total planned work for the block

### Logged hours

Actual hours tracked through:

* Time entries logged to subtasks
* Time entries logged to help desk tickets

### Client total hours

Each client row shows total scheduled hours across all their blocks, helping you see capacity at a glance.

<Note>
  Scheduled hours come from task estimates. Logged hours come from time entries. See [Hours Tracking](/user-guide/blocks/hours-tracking) for details.
</Note>

## Reordering blocks

### Custom order

Change block display order:

* Drag blocks up or down
* Only within same client/month
* Affects display only
* Helps match your workflow

**Default order:**

1. Design
2. Development
3. Internal QA Review
4. Internal QA Fixes
5. External QA Fixes
6. Deployment

### Why reorder?

Custom ordering useful for:

* Showing parallel work phases
* Matching your process
* Highlighting priorities
* Visual clarity

## Deleting blocks

### When to delete

Remove blocks that are:

* No longer needed
* Created by mistake
* Client work cancelled
* Replaced by different plan

### How to delete

<Steps>
  <Step title="Find block">
    Locate block in client's month
  </Step>

  <Step title="Click delete">
    Use delete action
  </Step>

  <Step title="Confirm">
    Confirm deletion
  </Step>

  <Step title="Removed">
    Block deleted, capacity released
  </Step>
</Steps>

<Warning>
  Deleting blocks is permanent. Time entries remain, but the capacity reservation is lost.
</Warning>

## Best practices

<CardGroup cols={2}>
  <Card title="Plan early" icon="calendar-plus">
    Add blocks at start of month for best visibility
  </Card>

  <Card title="Realistic allocation" icon="gauge">
    Don't overallocate - leave buffer time
  </Card>

  <Card title="Assign promptly" icon="user-plus">
    Assign blocks so team can plan ahead
  </Card>

  <Card title="Use QA rounds" icon="rotate-cw">
    Add multiple QA blocks if testing will iterate
  </Card>

  <Card title="Sequence logically" icon="list-ordered">
    Order blocks to match work flow
  </Card>

  <Card title="Update status" icon="refresh-cw">
    Keep status current as work progresses
  </Card>
</CardGroup>

## Common workflows

### Scenario 1: New client project

<Steps>
  <Step title="Create blocks">
    Add Design, Development, Internal QA, Deployment
  </Step>

  <Step title="Assign team">
    Designer, developer, QA tester
  </Step>

  <Step title="Schedule sequence">
    Design (weeks 1-2), Dev (weeks 2-3), QA (week 4), Deploy (week 4)
  </Step>

  <Step title="Add tasks">
    Create subtasks and assign to blocks
  </Step>

  <Step title="Track progress">
    Update statuses as work progresses
  </Step>
</Steps>

### Scenario 2: Ongoing retainer work

<Steps>
  <Step title="Monthly blocks">
    Add Development and Internal QA blocks each month
  </Step>

  <Step title="Assign team">
    Regular team members for this client
  </Step>

  <Step title="Schedule dates">
    Set dates for when work will happen
  </Step>

  <Step title="Add tasks as needed">
    Schedule tasks to blocks as work is defined
  </Step>
</Steps>

### Scenario 3: Multiple QA rounds

<Steps>
  <Step title="Initial QA">
    Add "Internal QA Review" block
  </Step>

  <Step title="Issues found">
    Add "Internal QA Fixes" block
  </Step>

  <Step title="Re-test">
    Add "Internal QA Review (Round 2)" block
  </Step>

  <Step title="More fixes">
    Add "Internal QA Fixes (Round 2)" if needed
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Can't add block - button disabled">
    Core blocks (Design, Development, Deployment) can only be added once per client per month. Check if it already exists.
  </Accordion>

  <Accordion title="Block not showing in schedule">
    Blocks appear in schedules only when assigned and scheduled with dates. Configure the block first.
  </Accordion>

  <Accordion title="Can't find Blocks page">
    Blocks are accessible to PMs, CSMs, and Managers. Check your role permissions.
  </Accordion>

  <Accordion title="Team member says they don't see block">
    Verify block is assigned to them and has scheduled dates. Unassigned or unscheduled blocks don't appear in personal schedules.
  </Accordion>

  <Accordion title="Scheduled hours don't match logged hours">
    Scheduled hours are from task estimates. Logged hours are from time entries. They often differ, which is normal.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Block Types" icon="shapes" href="/user-guide/blocks/block-types">
    Learn about each block type in detail
  </Card>

  <Card title="Hours Tracking" icon="clock" href="/user-guide/blocks/hours-tracking">
    Understand how hours are tracked
  </Card>

  <Card title="Scheduling Blocks" icon="calendar" href="/user-guide/blocks/scheduling-blocks">
    Master block scheduling and assignments
  </Card>

  <Card title="Schedule" icon="calendar-days" href="/user-guide/schedule">
    See how blocks appear in schedules
  </Card>
</CardGroup>