---
title: "Dock + Monday.com: agent-drafted resource plans with attributed PMO sign-off"
excerpt: "Connect Monday.com and Asana to Dock so an agent can draft resource plans from board data, then route each plan to the PMO for attributed sign-off."
author: mei
category: Use Cases
date: "2026-05-30"
---

A project agent that reads a Monday board and proposes who staffs what is useful only if the PMO can see the reasoning and sign off by name. Dock gives the agent a row to write its draft into, a pointer to the originating board, and a reviewer column the PMO fills in. Monday and Asana keep the boards. Dock holds the resource plan and its signature.

Monday.com and Asana stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.

## The Dock surface: Resource Plan Drafts

| Plan ID | Source board | Agent | Proposed staffing | Confidence | PMO reviewer | Decision | Timestamp |
|---|---|---|---|---|---|---|---|
| RP-2041 | monday.com/boards/4471/Q3-launch | planner-agent-v3 | Priya 60%, Marco 40%, contractor 20% | 0.82 | gita@pmo | Approved | 2026-05-28 14:11 |
| RP-2042 | asana.com/0/119/list | planner-agent-v3 | Lin 80%, Sam 20% | 0.71 | gita@pmo | Revise: add QA | 2026-05-29 09:02 |
| RP-2043 | monday.com/boards/4471/migration | planner-agent-v3 | Marco 100% Jun, Priya 50% Jul | 0.68 | hold | pending | 2026-05-29 16:40 |

The Plan ID is Dock's own primary key. Source board is a live link. Every other column is the agent's interpretation, not Monday's data.

## A worked workflow: drafting RP-2041

The planner agent reads board 4471 through the [Monday GraphQL API](https://monday.com/) and pulls open items, owners, due dates, and effort tags. It cross-references the team's current load from Asana via the same fresh-read pattern. It writes a draft into Dock with proposed allocations, a confidence score, and the board snapshot it used.

Gita on the PMO opens RP-2041, sees the agent's reasoning, and approves. Her name and timestamp land in the row. A webhook pushes the approved allocation back to Monday as a status update on the originating items, with a link to the Dock row so anyone clicking the board can see who signed.

If Gita asks for revision, the agent re-reads the board, drafts a new version, and links it as a child row. The original is never overwritten. This is the same shared-context pattern in our [agent collaboration primer](/blog/agent-collaboration-primer).

## Why this matters

Resource planning sits between two failure modes. Plans drafted by humans alone are slow. Plans drafted by agents with no attribution are unauditable. The PMO needs a row it can point to that says: an agent named planner-agent-v3 read this board on this date and proposed this allocation, and Gita approved it at 14:11. That row is what survives an audit, a re-org, or a postmortem.

Monday and Asana are not built to hold that row. They hold tasks. Dock holds the interpretation layer above them, which is the [Cloud 2.0 product story](/blog/cloud-2-0-for-product) in one surface. The agent has its [own identity](/blog/agent-identity), not a borrowed login, so the reviewer column means something.

## Try the planner agent

Spin up Dock, point it at a Monday workspace and an Asana project, and let the planner draft your next resource plan. The [Dock for project management hub](/blog/dock-for-project-management) walks the full setup.

## FAQ

**Does the agent edit Monday boards directly?**
Only after PMO approval and only as a status comment with a backlink to the Dock row. Drafts live in Dock first.

**What if Monday and Asana disagree about who owns a task?**
The agent flags the conflict in the Dock row and refuses to allocate until a human resolves it. Conflict resolution is logged with reviewer identity, the same pattern used in [Dock for people ops](/blog/dock-for-people-ops).

**Can a contractor or PM see only their own rows?**
Yes. Dock row-level permissions filter on reviewer and source board. The PMO sees all plans, an individual contributor sees plans that name them.

**How is the agent itself governed?**
planner-agent-v3 has a Dock-issued identity with scoped read access to Monday and Asana and write access only to its own draft rows, as described in our [agent identity model](/blog/agent-identity). It cannot approve its own plans.