Documentation · Structure
Org chart
Declare every role once, then draw the reporting lines. Levels, spacing and the bus routing are worked out for you.
When to use it
Describe reporting relationships, roles, people and advisory ties in an organization.
Keep the role and the person's name separate. Reporting lines use a shared rail beneath a parent so its children remain easy to read.
Working example
Copy this complete example into the Source tab, then press Generate. Change its labels or values to make your first version.
org "FACULTY OF PSYCHOLOGY ORGANISATIONAL CHART" {
role DEAN "DEAN" "Dr. Marion Hale"
role SENATE "FACULTY SENATE"
role VD1 "VICE DEAN I" "Priya Raman, Ph.D"
role VD2 "VICE DEAN II" "Dr. Elena Sorbo, M.Ed"
role VD3 "VICE DEAN III" "Tomas Weller, Ph.D"
role LABS "HEAD OF LABORATORIES" {
unit "Psychodiagnostics Lab" "Ines Fabri, M.Sc"
unit "Computing Lab" "Karel Sandvik, M.Sc"
unit "Experimental and Media Lab" "Ada Moreau, M.Sc"
}
role UG "HEAD OF UNDERGRADUATE PROGRAMME" "Nadia Brenner, M.Sc"
role PG "HEAD OF MASTER PROGRAMME" "Dr. Owen Castellan"
role QA "QUALITY ASSURANCE CHAIR" "Sofia Lindqvist, M.Sc"
role SERVICES "SERVICES COORDINATOR" "Rafael Duarte, M.A"
role QA1 "QA TEAM, UNDERGRADUATE" "Hana Oyelaan, M.Sc"
role QA2 "QA TEAM, MASTER" "Iris Kovak, M.Sc"
DEAN -> VD1
DEAN -> VD2
DEAN -> VD3
DEAN -> LABS
DEAN -> UG
DEAN -> PG
DEAN -> QA
UG -> SERVICES
QA -> QA1
QA -> QA2
DEAN -.-> SENATE
}Syntax reference
The same reference used by the editor and AI briefing. Syntax is notation-specific; use the keywords listed here.
Chart
| Syntax | Meaning |
|---|---|
org "Title" { | open an org chart |
Boxes
| Syntax | Meaning |
|---|---|
role ID "Role" "Name" | role band over a name |
role ID "Role" | role band on its own |
role ID "Role" { | role band over sub-roles |
unit "Sub-role" "Name" | one sub-role, inside a role block |
Lines
| Syntax | Meaning |
|---|---|
A -> B | B reports to A |
A -> B -> C | chain of reporting lines |
A -.-> B | advisory tie (dashed) |
# comment | line comment (also //) |
Language rules
- The file is one org "Title" { ... } block.
- A box is role ID "ROLE" "Name". Drop the second caption for a role with no name attached.
- A box that lists sub-roles opens a block: role ID "ROLE" { unit "Sub-role" "Name" ... }. unit is only legal inside such a block.
- A -> B means B reports to A. Use it once per reporting line.
- A -.-> B is an advisory tie, drawn dashed and left out of the reporting bus.
Edit on the canvas
- Move or rename roles on the sheet and add reporting lines using the connector rail.
- Use dashed advisory ties for relationships that are not the main reporting hierarchy.
Generate replaces the drawing from source. Save before generating again if you want to preserve manual finishing touches.
Read Saving & exportingWrite it with an assistant
Tingraph AI already knows this notation. For another assistant, copy the tutorial below, describe your diagram under MY DIAGRAM, then paste the returned source into the editor. This prompt includes every syntax row, rule and working example above.
Read the complete prompt
You are writing Tingraph source. Tingraph is a small text language that draws a organisational chart. Answer with Tingraph source only.
SYNTAX
Chart
org "Title" { open an org chart
Boxes
role ID "Role" "Name" role band over a name
role ID "Role" role band on its own
role ID "Role" { role band over sub-roles
unit "Sub-role" "Name" one sub-role, inside a role block
Lines
A -> B B reports to A
A -> B -> C chain of reporting lines
A -.-> B advisory tie (dashed)
# comment line comment (also //)
RULES
- The file is one `org "Title" { ... }` block.
- A box is `role ID "ROLE" "Name"`. Drop the second caption for a role with no name attached.
- A box that lists sub-roles opens a block: `role ID "ROLE" { unit "Sub-role" "Name" ... }`. `unit` is only legal inside such a block.
- `A -> B` means B reports to A. Use it once per reporting line.
- `A -.-> B` is an advisory tie, drawn dashed and left out of the reporting bus.
WORKED EXAMPLE
org "FACULTY OF PSYCHOLOGY ORGANISATIONAL CHART" {
role DEAN "DEAN" "Dr. Marion Hale"
role SENATE "FACULTY SENATE"
role VD1 "VICE DEAN I" "Priya Raman, Ph.D"
role VD2 "VICE DEAN II" "Dr. Elena Sorbo, M.Ed"
role VD3 "VICE DEAN III" "Tomas Weller, Ph.D"
role LABS "HEAD OF LABORATORIES" {
unit "Psychodiagnostics Lab" "Ines Fabri, M.Sc"
unit "Computing Lab" "Karel Sandvik, M.Sc"
unit "Experimental and Media Lab" "Ada Moreau, M.Sc"
}
role UG "HEAD OF UNDERGRADUATE PROGRAMME" "Nadia Brenner, M.Sc"
role PG "HEAD OF MASTER PROGRAMME" "Dr. Owen Castellan"
role QA "QUALITY ASSURANCE CHAIR" "Sofia Lindqvist, M.Sc"
role SERVICES "SERVICES COORDINATOR" "Rafael Duarte, M.A"
role QA1 "QA TEAM, UNDERGRADUATE" "Hana Oyelaan, M.Sc"
role QA2 "QA TEAM, MASTER" "Iris Kovak, M.Sc"
DEAN -> VD1
DEAN -> VD2
DEAN -> VD3
DEAN -> LABS
DEAN -> UG
DEAN -> PG
DEAN -> QA
UG -> SERVICES
QA -> QA1
QA -> QA2
DEAN -.-> SENATE
}
OUTPUT
- Reply with one fenced code block and nothing else.
- The block starts with `org "…" {` and ends with `}`.
- Do not invent keywords: use only the ones listed above.
- Keep labels short enough to read inside a box, and keep every ID unique.
MY DIAGRAM
Describe what you want here, then send this message.Something unclear? Contact support or read the Privacy Policy.