CAPA Dependency Map

The Dependency Map provides a visual representation of CAPA actions and their sequential relationships. This page covers how to access and read the dependency map.

Open the dependency map

1. On the left sidebar, select CAPA.
2. Expand a CAPA row in the list.
3. The Dependency Map appears in the expanded view, showing all actions for that CAPA.

Read the dependency flow

The map reads left to right:

1. The first action appears on the left — this is the starting point of the CAPA action sequence.
2. Arrows point from each action to the next, showing the dependency chain.
3. The last action appears on the right — when this action is completed, the sequence is finished.

Understand action nodes

Each action is represented as a rectangular node containing:

Element	Description
Action ID	The unique identifier (for example, “Action #42”).
Description	Truncated description of the action (first 25 characters).
Assignee	Name of the person responsible, or “Unassigned” if not yet assigned.
Status	Current status displayed in uppercase, color-coded to match the node border.

Identify status by color

Status	Node Border	Node Background	Text Color
Completed	Green	Light green	Green
In Progress	Amber	Light amber	Amber
Open / Pending	Grey	Light grey	Grey

Below the map, a legend displays the three status colors for reference.

Tip

Use the dependency map during team meetings to quickly review CAPA progress. The visual format makes it easy to identify which actions are blocking the completion of the CAPA.

Scroll through actions

When a CAPA has many actions, the map extends horizontally. The container supports horizontal scrolling so you can view all actions.

Note

The dependency map shows a linear sequence. Each action depends on the previous one. For complex CAPAs with parallel work streams, coordinate through the action management page where individual action statuses can be updated independently.

Relationship to CAPA workflow

The dependency map works alongside:

• Action list — detailed view of each action with edit and status update controls.
• Bulk assignment — assign multiple actions to a user from the expanded view.
• Effectiveness review — available when the map shows all actions as completed (green).

When all nodes in the map are green (completed), the CAPA is ready for the effectiveness review phase.

Practical example: reading a dependency map for an equipment qualification CAPA

Scenario: After a deviation involving a failed IQ/OQ for a new lyophilizer, a CAPA was created with four sequential actions. You open the CAPA expanded view to check progress during a weekly quality review meeting.

What you see on the map

The dependency map displays four nodes connected by arrows, left to right:

1. Action #1 — “Vendor audit of lyophilizer shelf temperature uniformity” — Assignee: validation.engineer@company.com — Status: COMPLETED (green border, light green background).
2. Action #2 — “Repeat IQ protocol with revised acceptance criteria” — Assignee: validation.engineer@company.com — Status: COMPLETED (green border).
3. Action #3 — “Execute OQ with updated thermocouple mapping” — Assignee: validation.lead@company.com — Status: IN PROGRESS (amber border, light amber background).
4. Action #4 — “Update equipment qualification SOP-EQ-019” — Assignee: qa.specialist@company.com — Status: PENDING (grey border, light grey background).

How to interpret this

• Actions #1 and #2 are done (green). The vendor audit findings informed the revised IQ protocol.
• Action #3 is the current bottleneck (amber). The OQ execution is underway and must complete before Action #4 can begin.
• Action #4 (grey) is waiting. The SOP update depends on the finalized OQ results.
• The CAPA is not ready for effectiveness review because two actions are not yet completed.

During the meeting, you can scroll horizontally if the map extends beyond the visible area and reference the color legend below the map to confirm status meanings.