Get the Most | Submittable Next · Issue 1 · June 2026

How to use Calculated Value Fields to know where to start — before you read a single word

When your application window closes and 200 submissions land in your queue, someone has to figure out which ones deserve an in-depth look. Without any signal to go on, that means opening everything. And anyone who's been through a busy cycle knows: reading your way to a shortlist is exhausting, slow, and if you're honest — inconsistent. The ones you open when you're fresh get a different level of attention than the ones you open on a Friday afternoon.

Calculated Value Fields solve for that. You assign point values to specific questions on your intake form, and Submittable tallies a score for each application the moment it comes in. By the time you open your submissions view, every application already has a number attached. Sort by score, and you know where to start.

It's not a replacement for your judgment. It's a way to apply your judgment in the right order.

VIDEO: Coming Soon

Video title: Scoring with Calculated Value Fields 

What makes a good scored question?

Not every question on your intake form needs a value — and trying to score everything tends to produce a number that doesn't mean much. The questions worth scoring are the ones where the answer genuinely changes how you feel about an application.

Think about your last cycle. Which answers made you immediately more interested? Which ones gave you pause? Those are your scored fields.

In practice, this usually means multiple-choice questions where certain responses clearly align better with your program's focus — organization type, geographic area, population served, funding request range, years in operation. Likert scales work well too if you're asking applicants to self-assess something that matters to your criteria, such as urgency or potential impact of funding. Number fields are useful for things like budget totals, where you want to flag requests that fall outside your typical range.

One thing worth doing before you build: give each scored field an alias — a short name that makes it easy to identify when you're assembling the formula. Keep aliases simple to work with: lowercase, one word if you can manage it — readiness, budget, geography. You'll thank yourself when you have six fields in the calculator and they're not all showing up as "SingleSelect1, Single Select2, etc."

Building the formula: simple or weighted?

Before you build anything, write your formula out on paper. Something like geography + (2 × population served) takes thirty seconds to sketch and saves you from rebuilding it halfway through.

Then decide how much formula you need. Formulas miss in two directions: too simple, and every application scores within a few points of every other; too complex, and you get a number nobody on the team can interpret. A straight sum of your scored questions is often enough — the point values you assigned already do the weighting. Reach for a weighted formula when some criteria clearly outweigh others, or when a plain total doesn't separate applications the way your judgment would.

Simple Caculation Example	Weighted Calculation Example
Simple version — add it up. Sum the scored questions together. Importance is already built in through the points themselves: the answers that matter most carry the most points.	Weighted version — emphasize, then normalize.  Multiply your most important criteria by 3 (project type) and your next by 2 (geography), divide by the maximum possible points (32.5), and multiply by 100 to land on a 0–100 scale.
What you get. A raw point total	What you get. A score on a familiar 0-100 scale
When to use. A handful of fields, roughly equal in importance	When to use. Some criteria matter much more than others, or you want scores your whole team can understand at a glance,

One form can carry more than one calculation

You're not limited to a single formula per form. You might build one calculation that scores the strength of the proposed project, and a separate one that scores risk — say, whether the applicant has ever run a grant program before. Keep the scores side by side, or add them together for a total. Each calculation becomes its own sortable column in your views.

Calculated Value Fields also aren't limited to intake — the same mechanics work on Recommendation, Profile Forms and Custom Feedback Forms anywhere a scored answer would help.

Test it before you publish

Run a few sample submissions and look at the score each one lands on. Does it make sense? Does it separate the applications you'd want at the top from the ones you wouldn't? A quick pass/fail check: if your strongest sample application doesn't rank first, adjust the points or the weights before real applicants arrive.

Catching a broken formula before launch takes five minutes. Catching it mid-cycle does not.

The payoff: your view when applications come in

Once your scored fields and formula are set up, every application that comes in gets a total score automatically. You don't have to do anything.

The useful part is what happens next. In your Intake view, you can add your calculated score as a column, then sort from highest to lowest. In about ten seconds, your entire applicant pool is ranked — and you can start at the top.

You can also filter by score range — useful if you want to pull everything above a certain threshold for a first-pass read, or flag anything below a cutoff for a faster decision. Save that view, and it's there every time you open the round.

This is the part that actually changes how you spend your time. A scoring rubric built into the intake form means your team isn't relying on gut feel alone — and it means the 5 applications that should get your full attention aren't buried under 45 that shouldn't.

Help Article: Sort & Filter Applications →

A few things worth knowing before you build

You can hide the score from applicants — and from reviewers. These are two separate settings. To hide it from applicants, toggle "Hide Field" on in the calculated value field settings. To hide it from reviewers, do it while setting up your review round in the Workflow Builder. Use both and you've got an internal, admin-only ranking — useful when you don't want the score to color how reviewers read each application. If you're running a simple completion score, you might leave it visible. If you're using it as an internal ranking tool, keep it hidden.

Give your calculated field its own alias too. This matters if you plan to use multiple calculations in your form or average scoring in your Workflow Builder. The alias is what shows up there, and "Calculated Value Field 1" won't be easy to work with.

Quick Reference: Do This, Not That

Wrapping Up

The goal isn't to read everything — it's to know what to read.  Scored intake forms are one of the most practical ways to get there, and the programs that use them consistently tend to move through review faster and with more confidence in the shortlist they're building.

Set it up before your next cycle opens. By the time the application window closes, the work of sorting your pile will already be done.

Related Resources

Calculated Value Fields →

Sort & Filter Applications →