What is Default Field and Custom Field?
Default fields are standard, pre-configured attributes built directly into the system architecture to manage core business processes. Custom fields are flexible, user-defined inputs configured in settings to capture specialized operational data customized to your organization.
Benefits of Default Field
- Ensures strict data standardization across all users and system dashboards
- Eliminates setup time through pre-built field configurations and pre-population rules
- Drives core platform features, progress tracking, and built-in dashboard analytics

Benefits of Custom Field
-
Customizes forms to capture industry-specific details, compliance requirements, and unique workflows
-
Offers versatile element types including text areas, date-time selectors, dropdowns, checkboxes, and attachments that are tied to specific categories
-
Provides granular control over field enablement, display order, and allocated field limits

How it works in all the different data levels
Both field types work together to manage data across the core hierarchy (Customer → Project → Job) and supporting entities. Default fields handle system-critical tracking, while custom fields capture level-specific operational details.
When to use Default vs Custom?
| Considerations | Default Fields | Custom Fields |
| Primary Purpose | Driving core platform features, dashboard analytics, and standard workflows. | Capturing organization-specific, industry-customized operational data. |
| When to Use | Use for universal data points required for fundamental tracking across all projects/jobs. | Use when capturing unique compliance details, specialized workflows, or customer preferences. |
| Flexibility | Pre-configured and fixed directly within system settings. | Fully adaptable with customizable input types (dropdowns, checkboxes, dates, attachments). |
Help Center