An organization chart shows reporting relationships. Supply roles, teams and managers rather than asking the agent to infer authority from job titles. Two people with similar titles can belong to different parts of an organization, and a project lead is not necessarily a line manager.
Choose people, positions or teams
Decide what each box represents. A role-based chart is useful for planning a future structure; a people-based chart represents current appointments. Avoid mixing vacant positions with named departments unless the visual key makes the distinction clear.
Use only the personal information required for the task. A name and title may be enough; employee identifiers, contact details and private performance information usually do not belong in a public-facing chart.
Explain multiple relationships
Name the primary reporting line and any secondary relationship. A dotted line should have a defined meaning, such as project coordination. Do not let a second connection imply a second formal manager unless that is the intended model.
Ask “Group the application engineers under their lead and preserve the design reporting lines.” Review both the changed group and the relationships that should remain intact.
Review before sharing
Confirm current titles, reporting lines and vacancies with the appropriate source. The agent does not synchronize an HR system or verify organizational authority. A chart is a snapshot of the information you provide.
For ownership within a process, use a swimlane diagram. For when people need to deliver work, use a Gantt chart.
Make it about your work
Edit this starting prompt, then send it when you are ready.