Application completion rate

Define a start and a successful submission

Application completion rate is usually calculated as completed submissions divided by started applications. If 40 candidates begin and 28 submit successfully, the illustrative completion rate is 70%.

If no starts were recorded in the period, report the count rather than a completion rate. The denominator is zero, so no percentage is defined.

That simple fraction only holds if its events are stable. A page view is not necessarily a start; reopening a saved form may or may not count as a new attempt; a form with validation errors is not a successful submission. Write down those choices alongside the metric, especially when a tracking change makes a month-to-month comparison tempting.

Look for a barrier, not a verdict

A fall in completion is a signal to inspect the path. It does not, on its own, prove that the form is too long or that candidates lost interest. Check device type, error messages, required fields, and whether the job ad still matches the application’s request for information.

The W3C’s guidance on form notifications makes the practical point: people need to know whether a submission succeeded and how to correct an error. That applies to recruitment forms as much as any other online form. A required document can be relevant for one role and needless friction for another; Join’s job-creation guidance documents that application documents can be configured for a job.

Decide what to test next

Change one plausible obstacle, then compare like-for-like cohorts long enough to see whether submissions recover. For example, test whether a required cover letter is doing useful screening work before retaining it. Keep the application form separate from the wider hiring funnel: someone who submits has only entered the process, not converted into a hire.