Design every DocType as a human-facing form, not a flat database table.
Before adding fields, identify:
- the DocType's purpose and primary user
- the real business process or lifecycle it supports
- the relationships, status, reporting, and search needs
- whether it is master data, a transaction, a child table, or a configuration DocType
Field discipline:
- Add only fields that are required for identity, workflow, relationships, decisions, audit, reporting, or search.
- Do not add speculative, vanity, duplicate, or generic fields unless the use case clearly needs them.
- Make required fields truly required, not merely convenient.
- Use child tables only for real one-to-many repeating data.
- Prefer human-readable labels and stable snake_case fieldnames.
Form layout:
- Do not dump all fields into one tab or one section.
- Use
Tab Break for major mental models only when the form has enough fields to justify tabs.
- Use
Section Break for logical groups inside a tab.
- Use
Column Break to create balanced, scan-friendly rows.
- Put the title, status, primary links, and most common required inputs first.
- Put advanced, rare, admin, or integration fields later, and fold them when appropriate.
- Avoid empty tabs, thin sections, and layout breaks that exist only for decoration.
Useful tab patterns include:
- Overview for identity, status, and primary summary fields
- Details for the main business data
- People or Parties for owners, customers, suppliers, employees, or contacts
- Schedule for dates, timelines, reminders, or recurrence
- Finance for amounts, accounts, taxes, or pricing
- Settings for infrequent configuration
- Activity or Audit for comments, references, or system-facing traceability
When proposing or creating a DocType, present the layout grouped by tab and section, and explain why each group exists. If a requested field does not belong, call it out and omit it unless the user confirms the need.
1---2name: frappe-doctype-design3description: Frappe DocType creation and form UX guidance. Use when creating, reviewing, or redesigning DocTypes, including field choice, tabs, sections, columns, required fields, naming, child tables, and form usability.4metadata:5 source: https://skillmd.com/skills/hashgraph-online/frappe-doctype-design6---78Design every DocType as a human-facing form, not a flat database table.910Before adding fields, identify:11- the DocType's purpose and primary user12- the real business process or lifecycle it supports13- the relationships, status, reporting, and search needs14- whether it is master data, a transaction, a child table, or a configuration DocType1516Field discipline:17- Add only fields that are required for identity, workflow, relationships, decisions, audit, reporting, or search.18- Do not add speculative, vanity, duplicate, or generic fields unless the use case clearly needs them.19- Make required fields truly required, not merely convenient.20- Use child tables only for real one-to-many repeating data.21- Prefer human-readable labels and stable snake_case fieldnames.2223Form layout:24- Do not dump all fields into one tab or one section.25- Use `Tab Break` for major mental models only when the form has enough fields to justify tabs.26- Use `Section Break` for logical groups inside a tab.27- Use `Column Break` to create balanced, scan-friendly rows.28- Put the title, status, primary links, and most common required inputs first.29- Put advanced, rare, admin, or integration fields later, and fold them when appropriate.30- Avoid empty tabs, thin sections, and layout breaks that exist only for decoration.3132Useful tab patterns include:33- Overview for identity, status, and primary summary fields34- Details for the main business data35- People or Parties for owners, customers, suppliers, employees, or contacts36- Schedule for dates, timelines, reminders, or recurrence37- Finance for amounts, accounts, taxes, or pricing38- Settings for infrequent configuration39- Activity or Audit for comments, references, or system-facing traceability4041When proposing or creating a DocType, present the layout grouped by tab and section, and explain why each group exists. If a requested field does not belong, call it out and omit it unless the user confirms the need.