---
url: /advisor-guide/28-company-work-map.md
---
# Work Map

The Work Map shows how work moves through the business: which Task Cards hand work to which, where it breaks and where it waits. It does not show who reports to whom. Open **Work Map** in the company sidebar. The page has 4 tabs: **Process map**, **Work flows**, **Task Cards** and **People**. All 4 tabs read the same records as the Company Repo. Nothing is invented to fill a picture.

A Task Card is one person's repeatable job: what arrives, what they do, where it leaves to. A **workflow** is a chain of Task Cards, across people, that carries one **unit of work** (an order, an invoice, a supplier) from start to done. The rule: if the same unit passes through the Task Cards of 2 or more people, it is a workflow.

Business stages are broader than duties. A stage groups work across roles. Edit the stages and their descriptions in Discovery > Edit the profile and stages.

## Process map

The Process map is a grid. The columns are the stages, from left to right. The rows are departments. Each Task Card is a chip in its cell. Long titles take up to 2 lines.

* The **lens bar** counts what the map found: **Breaks**, **Bottlenecks**, **Key-person risk**, **Automation** and **Missing detail**. Pick a lens to mark those cards.
* **Click a Task Card to see how it links.** Lines show where its work **arrives from** and **leaves to**. The page scrolls to **How it links**, **The card** and **Findings** for that card. **Back to map** scrolls back. Esc, a click on empty space or **Deselect** clears it.
* With nothing picked, **What to fix next** under the map lists the findings: the likely constraint first, then the cards waiting behind it, then how often it runs.

A hand-off is **Both sides agree** when each card names the other, **One side said it** when only one does, and **Nobody receives it** when a card sends work to a person with no card for it (a dashed card). A missing "how often" or "how long" reads "not said yet".

On a finding or a card you can choose **Not a problem**, **Mark as the constraint**, **Give it an owner** (a proposal; the Task Card does not change), **Not real work**, **Record: \<name> confirmed it** or **Add to Opportunities**. Each has **Undo**.

**Ask \<name>** sends a question to that person's client app. A question about one Task Card shows on that card under **From your advisor**, and on their Home. The chip reads **Sent to their app**, then **Answered in their app**. If their onboarding has not started, it reads **Saved until their onboarding starts** and is sent when it starts.

When one card names a person and that person's own card does not say so, the person gets a **Mentioned you** check in My work: **Yes**, **Not me** or **Sort of** with a few words. A Yes makes the hand-off **Both sides agree**. Not me and Sort of show beside the hand-off with their words. You can undo a Yes given in the app. A card that changes is asked again.

An old `#graph/stage/…` link opens the Process map.

## Work flows

**Work flows** shows one workflow as swim lanes, one lane per person. The list has **Confirmed**, **Suggested** and **Not workflows** (with **Hide** and **Bring back**). The tab shows how many are suggested, for example "4 suggested". **What counts as a workflow?** gives the rule.

DutyGraph suggests a workflow by following the recorded hand-offs between Task Cards. It keeps a chain only when 2 or more people do its cards, and leaves out a chain a confirmed workflow covers. **How DutyGraph found it** names the first and last card and the hand-offs it followed. The unit of work is suggested only when a word from the first card is on 2 or more people's cards; otherwise pick or type one. **Where does it break?** lists each hand-off on the chain that does not hold, with **Ask** and **Edit steps**.

The **Is this a workflow?** panel has 4 choices: **Confirm workflow**, **Edit steps**, **Split here** (pick the card where part 2 starts) and **Not a workflow** (with a reason). Each has **Undo**; a workflow confirmed from a suggestion keeps **Take back confirm** until it is reviewed. A confirmed workflow is documentation only until it has an owner; use **Edit unit** to change its unit of work. The Company Repo writes the unit in the workflow's file.

## DutyGraph Agent on the Work Map

DutyGraph Agent beside the map sees every Task Card, hand-off, workflow and finding on it. Its starters follow what you picked: **Where is the biggest constraint?**, **Where does the chain break?**, **Who should own this?**, **Why did you suggest this?**. It answers as an operations analyst with the theory of constraints: find the constraint and tell it apart from its symptoms, check for a policy constraint (a rule or an approval) first, then exploit, subordinate and elevate. Each answer names cards by their exact title, gives the counted evidence and ends with a **Test it** step. The cards it names ring green on the map; **Clear highlight** removes the marks. It needs the company's AI connection.

**Fix it.** When an answer names a Task Card nobody owns, a **Fix it** box shows under it (and **Fix this** on the card): **Let the people involved decide**, **Assign an owner now** or **Test it first**. The fix is drafted under the map with the cards it changes numbered on the map, who it goes to, the rule that locks it in, and each person's card as their app shows it. Nothing is sent until **Send**. People pick a way and say why (talk or type) in their app and see what the others picked; the decider confirms; the new owner accepts the step onto their Task Cards and the people on each side accept the hand-off. The pane under the map follows each step. **Take it back** undoes what it wrote.

On a laptop the map's columns narrow so 6 stages show with the Agent open.

## People

People shows who holds which work. It has 2 views:

1. **By stage** (the default) is a matrix. The rows are people, grouped by department. The columns are the stages. A filled dot means that the person owns work in the stage. An open dot means that the person does the work of a Task Card there. On a phone, each department is a list.
2. **Reporting lines** shows the reporting chart of the Company Repo (the same chart as the Repo's Team layer). It is the only reporting chart in DutyGraph.

Select a person to open their panel: "Reports to", the duties and Task Cards they own, the Task Cards they do, and their open asks. The address changes to `#graph/people/<person>`. Owners and performers describe accountability and work. Neither role is an approval.

## Task Cards

**Task Cards** shows the cards with their filters. A card is **Locked in** when all three parts (arrives, I do, leaves) have words, and **Ready** when it also hands on to a named person. Open the Client Brief on **Reports** to discuss priorities and prepare a report.

PostgreSQL is authoritative. Neo4j is a derived projection. The Cobalt sample has a saved, fictional business profile, stage assignments and 2 workflows. You can edit them.
