---
title: "Update Board Card Block: Change Card Status, Assignee, and Info from Forms"
url: "https://help.ontraccr.com/en/article/update-board-card-block-change-card-status-assignee-and-info-from-forms"
language: "en"
last_updated: "2025-05-26T22:03:49.828Z"
---

# Update Board Card Block: Change Card Status, Assignee, and Info from Forms

## 📄 Update Board Card Block: Change Status, Style, and Assignments on Cards from Forms  
 

The **Update Board Card Block** allows you to modify an existing **board card** based on a form submission. This is perfect for updating task status, changing assignees, adding notes, or managing workflows like submittals, issue tracking, or approvals—without manual board edits.

* * *

## 🔁 What Is the Update Board Card Block?

This workflow block lets you:

-   Update a **card that was created from a previous form**
-   Or update a card selected in a **form field**
-   Change its:
    -   Column (status)
    -   Name or description
    -   Color label
    -   Assignee

> ✅ Ideal for workflow-driven task boards, escalation workflows, and status-based handoffs

* * *

## 🛠 How to Configure It

1.  In **Step 3: Workflow**, drag the **Update Board Card Block** into the workflow
2.  Connect it to a relevant prior step (e.g., Submit, Approve, Edit)
3.  Click the block to configure:

* * *

## ⚙️ Configuration Options

### 1\. **Which Card to Update?**

| Source | Description |
| --- | --- |
| **Linked Form Card** | Automatically updates the card that was created by this form’s “Create Board Card” block |
| **Form Field** | User selects a card via dropdown (e.g., “Select Issue Card to Update”) |

✅ Use the linked card option for seamless 1:1 workflows

✅ Use field-based selection for multi-form updates

* * *

### 2\. **Update Actions**

| Setting | Result |
| --- | --- |
| **Move to Column** | Move the card to a new status (e.g., “In Progress”, “Done”) |
| **Update Card Name** | Pull from a form field |
| **Update Description** | Replace or append a card’s description |
| **Change Color** | Visually re-categorize (e.g., red = urgent, green = approved) |
| **Update Assignee** | Assign to role, user, team, or selected field from the form |

> 🧠 Append or override logic supported for description updates

* * *

## 📥 Field Mapping for Card Updates

Use the **mapping panel** to dynamically fill card fields using form input.

| Card Field | Form Field |
| --- | --- |
| Description | “Comments” or “Rejection Notes” |
| Title | “Issue Title” or “Change Order Name” |

* * *

## 🧠 Use Case Examples

| Workflow | What It Does |
| --- | --- |
| FLHA form approved → safety card moves to “Closed” | Moves card to “Closed”, updates color to green |
| Subcontractor form rejected | Card moves back to “In Review”, notes appended |
| PM reviews change request | Description updated with final notes, card reassigned to Accounting |
| Final QA inspection | Card moved to “Complete” and archived with PDF linked |

* * *

## 🔄 Combine With

| Block | Why |
| --- | --- |
| **Create Board Card** | Create card initially, then update as form progresses |
| **Status Update Block** | Update form status to match card movement |
| **Notify In App Block** | Alert users of board/card changes |
| **Approval Block** | Change card status or owner based on approval result |

* * *

## 📌 Best Practices

-   🧩 Use this for “form-driven board workflows”—no need to manually update cards
-   📥 Use field mapping to reduce rework and ensure accurate descriptions
-   🔄 Pair with **shared card logic** in triggered forms for seamless collaboration
-   🧠 Color codes + column movements = visual automation