Create custom pursuit fields
Create workspace-specific pursuit fields so your team can track the capture details that matter to your GovCon workflow.
Custom fields let your workspace add structured pursuit fields beyond GovTribe's standard capture fields. Use them when your team needs to track internal workflow details such as bid decisions, proposal status, review dates, pricing milestones, teaming notes, or customer-specific qualification steps.
What custom fields are for
GovTribe pursuits already include standard capture fields such as owner, pipeline, stage, tags, due date, estimated value, probability of win, estimated award date, and description. Custom fields add the fields your team needs for its own process.
They are useful when your workflow has repeatable details that should stay visible across pursuits, such as:
- Bid or no-bid recommendation
- Capture priority
- Proposal status
- Teaming plan
- Pricing status
- Review date
- Incumbent or competitor notes
- Internal confidence or risk rating
Use custom fields for information your team expects to update and compare across many pursuits. Use the pursuit description for longer narrative notes that do not need their own table column or export column.
Create and manage fields
Open My GovTribe Profile, go to Settings, then choose Manage Custom Fields. Use New Custom Field to open the Create New Custom Field drawer and create a field for pursuits.
Each field definition includes:
| Setting | What it controls |
|---|---|
| Field Type | The kind of value the field stores. |
| Title | The label shown when your team edits or reviews the field. |
| Placeholder Text | Optional help text shown before a value is entered. |
| Fielded Model | The GovTribe item type the field attaches to. Today, customer-facing custom fields are used for pursuits. |
| Make this field required | Whether a value is required when the field is used in a pursuit. |
The drawer also shows a preview of how the field will look when your team enters a value on a pursuit.
You can edit or delete custom fields from the same Manage Custom Fields page. Deleting a custom field removes that field from pursuit workflows and removes its saved values from pursuits.
Choose a field type
Choose the field type that matches how your team expects to enter, review, and export the value.
| Field type | Use it for |
|---|---|
| Text | Short workflow labels, notes, status values, incumbent context, teaming notes, or bid/no-bid rationale. |
| Number | Counts, scores, ratings, quantities, or internal numeric measures that are not dollar amounts. |
| Dollar | Budget, pricing, cost, or revenue values that should be entered and shown as money. |
| Date | Review dates, gate dates, proposal milestones, pricing due dates, or other internal deadlines. |
Keep field titles short and consistent. A title such as Proposal Status or Gate Review Date is easier to scan in a pursuit table and cleaner in a CSV export than a long sentence.
Use required fields carefully
Required custom fields help enforce a consistent workflow when a value is always needed. They work best for fields that every pursuit should have before your team saves or updates the pursuit.
Use required fields sparingly. If a value is only known later in the capture process, leave the field optional so early-stage pursuits can still be created and updated without placeholder values.
Fill in pursuit values
After a custom field is created for pursuits, it appears in the New Pursuit and Edit Pursuit drawers. Use those drawers to add or change the value on an individual pursuit.
Custom field values belong to the pursuit where they are entered. A field can exist for the workspace while a specific pursuit has no value yet. Blank custom fields usually mean no one has entered that value for that pursuit.
Review custom fields on pursuits
Custom fields appear in several pursuit views and outputs:
| View or output | How custom fields appear |
|---|---|
| New Pursuit and Edit Pursuit drawers | Workspace custom fields appear with the other pursuit fields when your workspace has configured them. |
| Pursuit detail page | The Custom Fields tab shows the custom field values saved on the open pursuit. |
| Pursuits table | Custom fields can appear as table columns and can be shown or hidden from Fields. |
| Pursuit export | Custom fields can add extra CSV columns with your workspace's custom field titles. |
Custom fields are workspace-specific. Another workspace may have different field titles, field types, required settings, and saved values.
Related articles
- Pursuits: Track individual opportunities or targets your team is evaluating.
- Create pursuits from records: Start new capture work from a GovTribe record or connect a record to existing pursuit work.
- Pursuit export format: Review the CSV columns included when you export pursuit records.