The Field Management page
Open the web app, go to Settings, and pick Field Management — the third item in the settings navigation, after Profile and Team, at/app/settings/field-management.
The page is a single table of every field Tempo knows about, one row per field:
A field name can appear more than once — once per category.
Account ID, for example, exists separately as a contact field, an opportunity field, and an account field. Check the Category column before you edit, or you’ll configure the wrong one.
Categories and types
Category is the CRM object the field hangs off:opportunity, account, or contact.
Type is the field’s data type. The types you’ll see in the table include reference, text, money, longtext, date, and boolean. The full set Tempo reports across a field catalog also includes number, datetime, select, percentage, multiselect, email, url, and phone.
Fields carry your CRM’s own naming, so what you see depends on which CRM you’ve connected. In Salesforce a MEDDPICC champion field appears as Champion__c and system fields like CreatedDate and IsClosed sync as read-only. In HubSpot you’ll see property names like dealtype and lifecyclestage.
Finding a field
Two controls narrow the table:- Find a field — a search box at the top of the page.
- Filters — opens a panel that filters on Field Name (contains), Category (contains), Type (contains), Scope (checkboxes for Private and Team), Owner (contains), Managed By (checkboxes for CRM and Tempo), CRM synced (checkbox), Visible (checkbox), Update Behavior (contains), and Frequency.
Automatic shows you every field Tempo writes without review — the single most useful view on this page before a security or governance conversation.
Editing a field
1
Click the field name
The Edit field panel opens for that field.
2
Change the controls you need
The panel shows, in order: Field Name, Scope, Visible, CRM synced, Update Behavior, Frequency, Write Mode, Instructions, Description, Owner, Category, and Type.
Scope
Scope is eitherPrivate or Team.
- Private fields apply only to your opportunities. Any seller can create one.
- Team fields apply across the organization. Only an organization admin can create one.
Team by default, with an Owner of Team.
Managed By
Managed By says where the field came from:CRM for fields synced from Salesforce or HubSpot, Tempo for fields Tempo holds itself.
Tempo-managed fields do not sync to your CRM. Their values remain in Tempo, including after you approve a suggested value.
Create a Tempo-managed opportunity field
Create a field when you want Tempo to calculate information that does not belong in your CRM schema. You can define the field yourself or ask Tempo to draft an editable definition.1
Open the Fields panel
Go to All Opportunities and click Fields.
2
Start a new field
Click Create New Field.
3
Choose a creation method
Select Draft with AI to describe what you want to track, or select Create manually to start with a blank definition.
4
Complete the definition
Review the Title, Type, Scope, Description, optional Instructions, and Updates behavior. Add labels and descriptions when you choose Select or Multiselect.
5
Choose when to generate values
Select Generate now to calculate the field for matching existing opportunities. Select Start going forward to wait for new evidence. With Generate now, use Add filter to narrow the matching opportunities.
6
Create the field
Click Create field. Tempo confirms whether the field is ready or values are being generated.
Visible
Visible is a toggle in the Edit field panel and a filter on the table. Tempo-managed deal-state dimensions start hidden. An organization admin can expose individual dimensions without changing how Tempo generates them.1
Find Tempo-managed fields
Filter Managed By to Tempo.
2
Choose a dimension
Open the deal-state dimension you want to expose.
3
Show the dimension
Turn on Visible.
CRM synced
CRM synced is a toggle in the Edit field panel and a filter on the table. Fields managed by your CRM have it on by default. Tempo-managed fields are not CRM synced. Applying or approving a value changes the field in Tempo without writing to your CRM.Update Behavior
Update Behavior decides whether Tempo generates a value and whether a person reviews it first. There are exactly three options:
In practice, identifier and system-ish fields sit on Manual —
Account ID and Closed were both Manual on the fields observed — while substantive judgement fields like Amount, Champion, and Close Date sit on Suggest.
Frequency
Frequency sets how often Tempo updates a field. Each option is one of two kinds, and the difference is the part worth getting right:- Since last update measures from the moment the field itself last changed. A field that changed on Wednesday is next eligible a day, week, or month after Wednesday. The window is relative to the field.
- A named reset — start of day, a specific weekday, start of month — is a calendar boundary. Everything resets at the same moment for every field on that setting, regardless of when each field last changed.
CRM-synced fields default to Every change.
Write Mode
Write Mode decides what happens to the value already in the field when Tempo writes to it. There are exactly three options:
Overwrite is the default on every field observed. Append and Prepend suit long-text fields where the history matters more than the latest state — a running champion log rather than a single current champion.
Instructions
Instructions is a free-text control in the Edit field panel. When you create a Tempo-managed field, it is optional. Use Description to explain what the field means and how to interpret its value. Use Instructions to tell Tempo how to calculate the field. Instructions can identify evidence, decision rules, exceptions, and value mappings.Description
Description is a free-text control in the Edit field panel, and a column on the table. It’s the field’s semantic guidance — what belongs in the field.Field descriptions do real work
A field’s description isn’t documentation — it’s instruction. It tells Tempo what belongs in the field and, just as importantly, what doesn’t. A weak description produces noisy proposals. A strong one is specific about inclusion and exclusion:Stores the identity and specific internal influence actions of a single customer-side individual who actively advocates for the solution. Entries must document the individual’s name and role alongside concrete evidence of how they exert political capital. Excludes individuals who solely perform administrative functions like vendor onboarding or procurement processing without clear demonstration of proactive internal sponsorship.That exclusion clause is what stops every procurement contact getting logged as a champion.
How field updates work
Every proposal Tempo generates cites the artifact it came from, whatever the update behavior. You can trace a value back to the transcript, email, or saved chat that produced it. For a CRM-synced field, an automatic or approved value can write to your CRM. A Tempo-managed field always remains in Tempo.What happens on a Suggest field
1
Tempo observes something
A meeting transcript, email, or saved chat contains information relevant to a tracked field.
2
It proposes an update with citations
The proposal links back to the source artifact, so you can see exactly what it’s based on.
3
You approve or reject
The proposal waits in the Updates queue. When you approve it, Tempo applies the value. It writes to your CRM only when the field is CRM synced.
Only CRM fields marked updateable can be written to your CRM. Read-only and system fields are never written.
Changing a field’s update behavior
You set Update Behavior per field, so different fields on the same opportunity can behave differently. Changing it on a team field is an administrative action, not something every user can do.Manage fields from chat
From an MCP-connected AI platform, you can read the field catalog and manage Tempo-managed opportunity fields. Start by listing fields instead of guessing their keys:
Don’t hardcode field keys — list them and read what’s actually there.
To see the full rules on a field, including value constraints and update policy:
Create and configure a field
Ask Tempo to draft a definition before creating it when you want to review the title, type, description, instructions, and update behavior:Generate values for existing opportunities
You can start generation for existing opportunities when you create a field, or start it later with an optional opportunity filter:Improving proposal quality
If proposals are noisy or missing, the field description is almost always the lever:- Too many proposals → the description isn’t excluding enough. Add what doesn’t belong.
- Wrong values → the description isn’t specific about format or source of truth.
- No proposals → the field may be set to Manual, its Frequency may not have come round yet, it may not be updateable, or nothing in your context speaks to it.