> ## 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.

# Requirement Blocks

> Building and estimating quote requirements

Requirement blocks define the scope and time estimates for each work type in a quote. Each block captures detailed information and provides a t-shirt size estimate.

## What are requirement blocks?

Requirements are separate scopes for each type of work:

* One block per work type
* Independent scope and estimates
* Team members assigned per requirement
* Tracked separately through completion

<Info>
  A quote can have multiple requirement blocks - for example, both Design and Development blocks for a new feature.
</Info>

## Requirement types

### Design

For visual and UX work:

* UI/UX design
* Visual assets
* Brand identity
* Marketing materials
* Prototypes

**Key fields:**

* Design goal
* Design types (can select multiple)
* Target audience
* Reference links
* Brand guidelines availability
* Timeline

### Development

For code and functionality:

* New features
* Enhancements
* Bug fixes
* Integrations
* Performance optimization

**Key fields:**

* Development goal
* Work type
* Current behavior (for fixes/enhancements)
* Expected outcome
* Relevant links
* Technical constraints
* Timeline

## Completing requirements

### Step 1: Review the brief

Assigned team members review:

* Client's goal and description
* Requirement-specific details
* Any attachments or references
* Timeline expectations

### Step 2: Add detailed scope

Click **Edit Scope** to provide:

* Detailed breakdown of work
* Technical approach (for development)
* Design direction (for design)
* Deliverables list
* Any assumptions or dependencies

**Scope editor features:**

* Rich text formatting
* AI generation assistance ("Generate with Alan")
* AI scope review ("Check with Alan") for manually-written scope
* Save as draft
* Preview before completing

<Tip>
  Use "Generate with Alan" for a starting point, or write your own scope and use "Check with Alan" to get feedback on clarity, completeness, and brief alignment before finalising.
</Tip>

### Step 3: Choose t-shirt size

Select appropriate size based on effort:

| Size             | Duration   | Use For                                   |
| ---------------- | ---------- | ----------------------------------------- |
| **XS**           | 15-30 min  | Tiny fixes, copy changes, config updates  |
| **S**            | 1-2 hours  | Small bug fixes, minor enhancements       |
| **M**            | 3-6 hours  | Medium features, moderate complexity      |
| **L**            | 1-2 days   | Large features, significant work          |
| **XL**           | 3-5 days   | Very large features, complex integrations |
| **XXL**          | 1-3+ weeks | Project-level work, major builds          |
| **Not Required** | N/A        | Work not needed for this requirement      |

**Time ranges for each size:**

<Accordion title="XS - Very Small">
  * **Minimum**: 15 minutes
  * **Average**: 22.5 minutes
  * **Maximum**: 30 minutes
  * **Example**: Update button color, fix typo
</Accordion>

<Accordion title="S - Small">
  * **Minimum**: 60 minutes
  * **Average**: 90 minutes
  * **Maximum**: 120 minutes
  * **Example**: Fix validation bug, add new button
</Accordion>

<Accordion title="M - Medium">
  * **Minimum**: 180 minutes (3 hours)
  * **Average**: 270 minutes (4.5 hours)
  * **Maximum**: 360 minutes (6 hours)
  * **Example**: New form with validation, product filter feature
</Accordion>

<Accordion title="L - Large">
  * **Minimum**: 480 minutes (8 hours)
  * **Average**: 720 minutes (12 hours)
  * **Maximum**: 960 minutes (16 hours)
  * **Example**: Complex checkout flow, multi-step wizard
</Accordion>

<Accordion title="XL - Very Large">
  * **Minimum**: 1440 minutes (24 hours)
  * **Average**: 1920 minutes (32 hours)
  * **Maximum**: 2400 minutes (40 hours)
  * **Example**: Custom integration, complex dashboard
</Accordion>

<Accordion title="XXL - Extra Large">
  * **Minimum**: 2400 minutes (40 hours)
  * **Average**: 4800 minutes (80 hours)
  * **Maximum**: 7200 minutes (120 hours)
  * **Example**: Full platform build, major redesign
</Accordion>

<Warning>
  T-shirt sizes are estimates based on complexity, not firm commitments. Actual time may vary based on unknowns discovered during work.
</Warning>

### Step 4: Confirm accuracy

Before marking complete:

* Review scope is clear and complete
* T-shirt size is appropriate
* All details are accurate
* Click **Confirm** to acknowledge

### Step 5: Mark complete

Once confirmed:

* Requirement marked complete
* Auto-moves to next requirement (if any)
* When all complete → quote goes to "quoted"

## The 80/20 split

### How it works

Each estimate is split:

* **80%** - Core work (initial subtask)
* **20%** - Feedback budget (for fixes)

**Example - M size Development (270 minutes average):**

* Feedback budget: 60 minutes (20% = 54 min, rounded up to 1 hour)
* Development subtask: 210 minutes (3.5 hours)

### Exception: XS tasks

XS tasks have no split:

* All time goes to core work
* No feedback budget reserved
* Assumed too small for meaningful QA

<Note>
  The feedback budget doesn't create a subtask initially. It's used when QA fails to estimate fix subtasks.
</Note>

### Using the feedback budget

The 20% budget is used when:

* Design needs client feedback changes
* Internal QA finds issues
* External QA requests changes

Fix subtasks are estimated using this budget:

* "Client Design Feedback" subtask
* "Internal QA Fixes" subtask
* "External QA Fixes" subtask

<Note>
  The feedback budget doesn't create subtasks initially - it's only used when reviews request changes.
</Note>

## Requirement status

Requirements progress through completion:

* Start as incomplete when quote is created
* Marked complete when scope and estimate provided
* Can be edited anytime (marks incomplete again)

When all requirements are complete, the quote moves to awaiting CSM review status.

## Needs more info

Sometimes the team needs additional clarification before providing an accurate estimate.

### Flagging a requirement

Team members can mark a requirement as "Needs More Info" when:

* The brief is unclear or ambiguous
* Technical details are missing
* Reference materials are needed
* Scope boundaries need clarification

### How it works

When a requirement is flagged:

* An amber **"Needs Info"** badge appears next to the quote title in the quotes list
* CSMs can quickly identify quotes requiring attention
* The flag can be cleared once the information is provided

<Info>
  The "Needs Info" badge helps CSMs prioritize their work by immediately surfacing quotes that are blocked on missing information.
</Info>

### Resolving the flag

To clear the flag:

1. Review the requirement to understand what's needed
2. Gather the missing information from the client or internally
3. Update the requirement details or brief
4. Uncheck the "Needs More Info" option
5. Team can then proceed with scoping and estimation

## Editing requirements

### Before completion

Full editing available:

* Scope content
* T-shirt size
* Brief details

### After completion

Can still edit, but:

* Marks requirement as incomplete
* Quote returns to "in\_progress"
* Must re-complete to progress
* CSM/client review reset

<Warning>
  Editing a completed requirement after CSM approval will reset the approval workflow.
</Warning>

## Best practices

### Sizing guidelines

<CardGroup cols={2}>
  <Card title="Include buffer" icon="shield">
    Size for complexity and unknowns, not just happy path
  </Card>

  <Card title="Consider dependencies" icon="link">
    Account for integrations and external factors
  </Card>

  <Card title="Break down large work" icon="scissors">
    XXL should be rare - consider splitting into multiple quotes
  </Card>

  <Card title="Document assumptions" icon="file-text">
    List what's included and excluded in scope
  </Card>
</CardGroup>

### Scope writing

<CardGroup cols={2}>
  <Card title="Be specific" icon="crosshairs">
    Vague scope leads to scope creep
  </Card>

  <Card title="List deliverables" icon="list-check">
    Enumerate what will be delivered
  </Card>

  <Card title="Technical approach" icon="code">
    Briefly explain how you'll build it
  </Card>

  <Card title="Edge cases" icon="diamond-exclamation">
    Mention what you're accounting for
  </Card>
</CardGroup>

## Common sizing mistakes

### Undersizing

**Mistake:** Selecting S for work that's actually M

**Impact:**

* Insufficient time allocated
* Work goes over budget
* Profitability suffers

**Solution:** Size for realistic effort, not ideal scenario

### Oversizing

**Mistake:** Selecting XL for work that's actually L

**Impact:**

* Quote appears expensive
* Client may reject
* Leaves budget unused

**Solution:** Be honest about effort - padding creates other problems

### Not considering iterations

**Mistake:** Sizing only for initial build, forgetting feedback loops

**Impact:**

* Budget consumed by fixes
* No time for revisions

**Solution:** The 80/20 split handles this - size the full work

## Multiple requirements

### When to use multiple

Use multiple requirement blocks when:

* Work requires multiple work types (design + development)
* Separating phases (design first, then development)
* Different team members estimate different parts

### How they work together

Each requirement:

* Estimated independently
* Can be completed in any order
* All must complete before quote approval
* Convert to separate task requirements

**Example: New feature quote**

* **Design requirement**: L size (12 hours) - UI/UX for new feature
* **Development requirement**: XL size (32 hours) - Build the feature
* **Total**: 44 hours estimated

## Next steps

<CardGroup cols={2}>
  <Card title="Approval Workflow" icon="check-circle" href="/user-guide/quotes/approval-workflow">
    Learn how quotes are approved
  </Card>

  <Card title="Converting to Tasks" icon="arrow-right" href="/user-guide/quotes/converting-to-tasks">
    See how requirements become subtasks
  </Card>

  <Card title="T-shirt Sizing" icon="ruler" href="/concepts/estimation/t-shirt-sizing">
    Deep dive into estimation methodology
  </Card>

  <Card title="Tasks" icon="check-square" href="/user-guide/tasks">
    Understand task requirements and subtasks
  </Card>
</CardGroup>