Reporting Lines
How delegation works between workforce members through visual reporting line connections.
How Delegation Works
Reporting lines in a workforce define the delegation paths between members. Each visual edge on the canvas represents a parent-child relationship where the parent can delegate tasks to the child.
Parent-Child Relationship
Each reporting line edge means "the parent may delegate to the child via agent-as-tool."
- Parent agents can invoke child agents as callable tools
- The child's capabilities become available to the parent
- Results flow back up to the parent for further processing
Runtime Behavior
At runtime, the parent's system prompt exposes children as callable tools.
- Children appear as functions in the parent's tool list
- Parent decides when to delegate based on the task
- Child executes with full access to their own tools and knowledge
Delegation Direction
Downward Only
Delegation is downward only. Children cannot invoke their parents. This ensures a clear chain of command and prevents infinite delegation loops.
CEO Agent
Can delegate to managers
Sales Manager
Can delegate to SDRs
SDR Agent
Executes tasks, cannot delegate up
Example: Delegation Call
Here's how a CEO Agent might delegate a research task to a specialized Research Agent:
// CEO Agent's system prompt includes Research_Agent as a tool
// When CEO receives: "Find competitor pricing data"
// CEO decides to delegate and calls:
delegate_to(Research_Agent, {
task: "Research and compile competitor pricing data for Q1 2024",
context: "Focus on direct competitors in the SaaS space",
format: "Structured comparison table"
})
// Research_Agent executes with its own tools (web search, scholar)
// Returns results back to CEO for synthesisThe parent agent decides what to delegate and provides context. The child agent decides how to accomplish the task using its own capabilities.
Creating Reporting Lines
In the Canvas
- Hover over a member node to see connection handles
- Drag from a handle to create a new edge
- Drop on another member to establish the reporting line
- The edge direction shows delegation flow (parent → child)
Via AI Bar
- Use natural language to describe reporting structure
- "Make Sarah report to John"
- "Have the SDRs report to the Sales Manager"
- The AI will update the canvas accordingly
Circular Dependencies Rejected
Circular reporting lines are rejected at save time. If Agent A reports to Agent B, Agent B cannot report to Agent A (directly or indirectly). The system validates the graph structure before saving.
Multi-Level Delegation
For complex workforces, delegation can flow through multiple levels:
CEOreceives: "Plan the product launch campaign"
delegates strategy toMarketing Director
delegates content toContent Writer
delegates design toGraphic Designer
delegates distribution toSocial Media Manager
Each level focuses on their specialty while the parent coordinates and synthesizes results.
Best Practices
Do
- Keep hierarchies shallow (2-3 levels max)
- Give managers clear scope over their reports
- Match delegation to natural task breakdown
- Use descriptive role names that clarify purpose
- Test delegation paths before deploying
Avoid
- Deep hierarchies (4+ levels add latency)
- Overlapping responsibilities between siblings
- Managers with too many direct reports (5+ gets complex)
- Delegation for simple tasks (adds overhead)
- Circular or ambiguous reporting structures