Skip across the chapter
Quota Playbook

Airtable percent fields: 3 checks before a win rate report

Quota Playbook Editorial Team · Published · 12 min read

To check an Airtable win rate, confirm the stored value, the field type and what a blank means. A rep has a number, the number is formatted as a percent, and that percent ends up on the coaching agenda. The trouble is that a percent field can look right on screen while the number underneath means something else. A rate that is off by a factor of 100, a rate whose field was converted to a different type, or a blank that quietly reads as zero can send a 1:1 in the wrong direction. Before you tell someone their win rate is down, run three quick checks on the field itself.

None of these checks takes long. Each one asks you to confirm something specific: what the field stores, what kind of field it is, and what an empty cell means. This post walks through the three checks in order, links to Airtable's own help pages wherever a rule applies, works through a small example, and includes a checklist you can keep beside your coaching notes. It is written for managers who pull rates from Airtable into a 1:1 themselves, so the steps avoid anything that needs a formula or a script.

Key takeaways

  • Check three or four records against their inputs, including a high, a low and a middling rate.
  • Read the field type from the settings, not from the display.
  • Note when the base was created, and check the default-value setting if it predates January 31, 2024.
  • Write down what a blank means, and apply that rule everywhere.
  • Show the closed-deal count and the period beside every rate.

Why the display can hide the number

A percent field is partly a display choice. Airtable's help center explains that the values in a percent field are shown as fractions of 100 with the percent symbol. Number-based fields in Airtable The same page gives a concrete example: .75 in a percent field is represented as 75%. That one example holds the whole first check. The cell shows 75%, but the value behind it is .75. Whenever you copy that number into another calculation, sort by it, or compare it with a figure you typed by hand, you need to know which of the two values you have in hand.

This matters in coaching because managers rarely look at the raw value. They look at the rendered percent and form a judgment from it. A rep showing 75% and a rep showing a rate a tenth of that size are far apart, and that gap is easy to miss when a column has been filled in by several people over several months. You do not need to be a spreadsheet expert to protect yourself from this. You need a habit of checking a few records before you trust a whole column, and a team rule for which format rates get entered in.

There is also a quieter risk. Rates tend to get copied into slide decks, weekly notes, and chat messages. Each copy strips a little context. By the time a figure reaches the 1:1, nobody remembers whether it was a fraction, what period it covered, or how many deals sat behind it. The checks below are meant to catch the problem at the source, in the base, before the number leaves it.

Comparing reps over time raises the stakes. A rate from this month is only comparable with a rate from last month if both were stored the same way and cover the same period. If the format of the column changed between those two months, the difference you see may be a change in how the number is written rather than a change in how the rep sold. Treat any trend line built from a rate field as suspect until you have confirmed the format held steady.

Check 1: Confirm the stored number matches the display

The first check takes a few minutes. Pick three or four records from the rep table: one with a high rate, one with a low rate, and one in the middle. For each, write down what the cell shows, then find the raw inputs that produced it. If the rate is meant to be wins divided by closed deals, divide those two numbers yourself and compare the result with the percent on screen. If the two agree, the field is doing what you think it is doing for those rows.

Do not stop after one record. A column can be correct in most rows and still have a few entries in a different format. One mismatched row can distort a team comparison, and you will not see it unless you check values you have no particular reason to suspect. If the sample agrees, check a few more before you move on, especially rows that were entered by hand rather than calculated from other fields.

When a value disagrees with its inputs, resist the urge to correct it on the spot. Trace it back to the record and to the process that wrote it. A rate that looks like it was entered in a different format is a clue, not a fix. Find out whether the number was entered as a fraction or as a whole number, confirm which one the rest of the column uses, and only then decide what the right value is. Write the decision down, so the next person who opens the base can see it. For a related way to record reasons, see timestamped call notes.

This check also covers a related problem. Suppose every rate in the column looks reasonable, but the inputs behind them are stale. A rate can be formatted perfectly and still be out of date. Confirm the date range for the inputs too. If a rate reflects last quarter, label it as last quarter in your notes, even if the field name does not say so.

Check 2: Confirm the field type and the base's history

The second check is about the field itself, not the individual values. Open the field's settings and read the type that Airtable reports. Do not rely on the look of the column, because the look is only a display. Two columns can show identical percent symbols and still behave differently in a calculation, so the type is what you need to confirm.

Age matters here. Airtable's help center indicates that percent fields created before May 2019 have since been converted to number fields. Number-based fields in Airtable If your rep table was built before that date, the column you think of as a percent field may now be a number field, and the way you read its values should change to match.

Why does this matter for a rate? If you read a converted column as though it were a percent field, you may have assumed a fraction when the stored value was a whole number, or the reverse. You will not find that mistake by looking at the display. You find it by comparing the stored values with the inputs, which is why the first check and the second check go together.

Next, ask who built the base and when. A base that is a few years old may have gone through several rounds of edits, imports, and field changes. If the person who set it up is still around, ask them what format they intended for the rate field. If they are gone, write down only what you can confirm from the field settings and the first few records, and leave the open question open rather than assuming an answer. A note that says "stored as a fraction, verified on four records" is far more useful to the next manager than a clean-looking percent sign.

Finally, watch for copies. Teams sometimes duplicate a rate field to add a filter or a calculation. Confirm the copy has the same type as the original and the same meaning. A new field that looks identical but has a different type can break a comparison between this quarter and last quarter without anyone noticing. If you find a copy, record which field is the source of truth and which ones are derived from it.

Check 3: Decide what a blank means

The third check is about empty cells, and it is the one most managers skip. A rep with no closed deals in a period does not have a meaningful win rate. The cell might be blank, it might hold a zero, or it might hold a default value that a setting filled in. These are three different situations, and a coaching conversation should treat them differently. A zero says the rep closed deals and won none of them, which is information. A blank says there is no data. A default says a setting wrote a value into a field that nobody filled in.

Airtable's help center notes that single line text, number, currency, and percent fields in bases created before January 31, 2024 offer an option to toggle on or off "Apply default value for all actions." Number-based fields in Airtable Whether that option is on for your rate field is a setting you can check, so check it rather than assume. If your base predates that date and the option is on, check whether it wrote a default value into any blank rate, since a rep with no closed deals could then appear to have a real figure.

The fix is a rule, not a formula. Decide what a blank means for your team and write it down. Many teams use blank for no data and show no rate at all for that rep. Others prefer a dash or the words "no closed deals." The rule that matters is that a zero should appear only when deals were closed and none were won. Anything else is not a win rate, and it should not be presented as one in the 1:1.

Blank handling also affects averages. If you average rates across reps, a rep with no data should usually be left out of that average rather than counted as zero. Counting it as zero pulls the team figure down for a reason that has nothing to do with selling. Say how you handled it, so that anyone who recalculates the number gets the same result.

Illustrative example: checking three records

One row shows a rate far too small for its closed-deal count. When you work back from the wins and the closed deals, the displayed rate does not match its inputs.

The next record is blank. The rep had no closed deals in the period, so under the rule you wrote down, the team average should leave this rep out. This base predates January 31, 2024, so check the "Apply default value for all actions." setting next.

The third record has a middling rate on only a few closed deals. One more win or loss would move it a lot, so the 1:1 should focus on those deals rather than the percentage alone.

Last, the field type. If the rate field was created before May 2019, it may have been converted from a percent field to a number field.

Bring the count, not just the rate

A win rate on its own is a weak basis for coaching. Two reps at the same percentage can be in very different positions. One may have a handful of closed deals, and the other may have many. The rate looks identical on a slide, but the first rep's number could move a lot with one more deal, while the second rep's number is much steadier. Bring the count of closed deals alongside the rate every time, and say what period both cover.

This is not about making a number look better or worse. It is about making the conversation fair. A rep with a low rate over a small sample needs a different conversation than a rep with the same low rate over a long track record. Without the count, you may spend the 1:1 debating the number instead of looking at the deals that produced it.

A simple order for the meeting works well. Start by stating what the figure measures and the period it covers. Then give the count of closed deals behind it. Next, walk through two or three of those deals together, looking at what happened rather than only the outcome. Ask the rep what they think happened before you offer a view. Opening with the bare percentage tends to make the meeting about the percentage, and the rep will spend the time defending it. For a fuller meeting example, see the Sales One-on-One Agenda for Coaching Software Sellers. For turning the talk into actions, see coaching follow-up tasks.

Keep the rate in your notes too, in the same form each time. If the format changes from one week to the next, the trend you show will not be a trend. Store the rate as the same type, use the same period, and record the count, so that next month's figure can be compared directly with this month's.

What a ready figure looks like

Before a rate goes into a 1:1 document, it should pass a short set of tests. The stored value matches its inputs for the records you checked. The field type is confirmed rather than assumed. A blank has a written meaning, and that meaning is applied the same way across the team. The rate comes with its count of closed deals and the period it covers. If any of those is missing, the figure is not ready, and it is better to say so than to present it with confidence it has not earned.

None of this requires a data team. It takes a short block of time the first time you do it, and a few minutes each cycle after that. The payoff is that when a rep asks why their number is what it is, you can answer with the inputs rather than with a shrug. That answer builds trust, and it makes the rest of the coaching conversation easier.

Closing thought

Three checks, each a few minutes long, will catch most of the errors that make a rep's win rate misleading. Confirm what the field stores, confirm what type it is, and decide what a blank means. Bring the count and the period with the rate. Do that before the 1:1, and the conversation can start with the deals rather than with a number nobody can explain.

Your next step today: open the settings for your rate field, note the field type Airtable reports, and write that type beside the rate in your notes.

Frequently asked questions

Do I need the closed-deal count if I already have the rate?

Yes, bring the count, because a rate on a small sample can change a lot with one more deal.

How do I find the field type?

Open the field's settings and read the type Airtable reports, rather than judging from how the column looks.

Sources

  1. Schedule send for coaching recaps: 4 tools to use
  2. Role-play coaching: 3 numbers to check before 1:1s
  3. Quote math: 6 checks for rounding and payment reviews

More plays