Job Application Spreadsheet Template: Build Views for Deadlines and Next Actions

Use one editable application table and three views: employer deadlines due soon, your next actions, and submissions with unresolved receipts. A deadline view shows external dates that need attention. A next-action view shows your own tasks, including work without an employer deadline. A receipt view keeps uncertain submissions visible until you reconcile the evidence.

Start with a role worth reviewing, perhaps from recent jobs on LandOffer. LandOffer publishes this guide. The downloadable files and worked examples use four fictional employers, roles, deadlines, and receipts. Microsoft and Google documentation was reviewed on October 8, 2026. The local workbook was tested with the bundled spreadsheet calculation engine, including changed inputs and a reopened XLSX. Native Excel and Google Sheets recalculation were not tested. The software instructions below describe their documented features separately.

Start with one editable table

Download the Excel workbook or the CSV sample records. The workbook includes formula views; the CSV contains input records only.

The download includes job-application-spreadsheet-template.xlsx and job-application-records.csv. The workbook has an Applications sheet for input and a Views sheet with three completed queues. Its 30 opportunity slots include four examples you can replace. The CSV contains those input records only. It does not preserve formulas, dropdowns, formatting, or the completed views.

Add one row for each distinct opportunity in Applications. Give it a stable ID, such as A001, and record the employer, title, and requisition. Replace the illustrative posting reference with the employer's actual destination when you have one. The sample references deliberately contain no hiring URLs because the employers are fictional.

Keep IDs unique so a change to a status or deadline stays tied to the same opportunity across the views. If the same opening appears on two job boards, compare its employer destination and requisition before adding another record. If the evidence shows one opportunity, retain one row and note the additional source. A second discovery route does not necessarily justify a second application.

Edit the amber input columns A:M. Columns N:T calculate eligibility and queue membership. The Views sheet reads those calculations. Change the underlying record when something happens rather than typing a different status into a displayed queue. This keeps the three views connected to one history.

Keep closed rows in the table. They can answer a later question about an earlier application while staying out of current work. The template excludes Closed and Withdrawn records from all three active views, even if their old deadline is approaching.

Keep employer dates separate from personal plans

An employer deadline and a personal action date mean different things. “Assessment due October 14” comes from an external instruction. “Review the invitation October 12” is your plan. Put the first in Employer deadline and the second in Personal action date. Rescheduling your preparation should not change the employer's requirement.

Preserve the deadline's source in the adjacent note. Record an exact time and time zone only when the listing or invitation supplies them. If the source states only a date, keep it date-only. The sample workbook compares calendar dates. It does not convert time zones or determine whether a deadline later today has already passed.

For a timed assessment, use the original invitation and an appropriate calendar reminder alongside the tracker. A date-only queue can tell you which record to open. It cannot replace an 11:00 a.m. cutoff or resolve an ambiguous time zone. Ask through the available employer route when the instruction itself is unclear.

A blank date means unknown or unscheduled. It must not become zero, today's date, or an invented deadline. Microsoft documents dates as sequential serial numbers, which is why a date-looking format alone does not establish a valid input. The template flags zero and text date inputs for correction rather than classifying them as upcoming dates.

Use status labels with explicit meanings

The workbook offers Saved, Draft, Needs verification, Submitted, Interview, Closed, and Withdrawn. Saved means the role is recorded. Draft means application preparation is underway. Needs verification means a submission outcome remains unclear. Submitted means you have confirmation evidence. Interview, Closed, and Withdrawn should reflect a communication or action you can identify.

The status dropdown is a data-entry aid. It cannot inspect an employer's portal or prove submission. Microsoft's validation guidance explains list and date restrictions. The template also exposes invalid status labels and duplicate IDs in its calculated Record state, because a copied or imported value still needs review.

Write one next action that you can complete. “Check portal and confirmation email” is clearer than “follow up.” Use a personal date when you deliberately plan that task. Leave it blank when you have not scheduled it. The task remains in Next actions with an Unscheduled label, so an empty date does not erase unfinished work.

Work through the four sample records

Open the workbook with its editable as-of date set to October 8, 2026 and window set to seven days. The dates below are fictional calendar dates with no invented times or time zones.

Record	Current evidence	Employer deadline	Personal next action
A001, Juniper Labs, JL-17	Data Engineer application is Draft	October 10	Compare SQL sample with requirements, October 8
A002, Harbor Systems, HS-04	Backend Engineer submission needs verification after an October 7 error	Blank	Check portal and confirmation email, October 8
A003, Cedar Analytics, CA-22	ML Engineer submission confirmed October 6, receipt recorded	Assessment due October 14	Review invitation and complete assessment, October 12
A004, Elm Works, EW-09	Product Analyst record is Closed, earlier receipt retained	October 9	No active action

The table demonstrates why one “Due date” column is insufficient. Cedar has already submitted an application but still has an assessment deadline. Harbor has an immediate verification task without any known employer deadline. Elm has an old date nearby but no longer belongs in the active queue.

The three views return two deadlines, three next actions, and one unresolved receipt. Those are counts of these fictional records. They describe the workbook's selection rules and do not measure application success, interview likelihood, or tool performance.

Build three views that answer different questions

Deadlines due soon selects active records with valid employer dates from the as-of date through the as-of date plus the window. Here, that means October 8 through October 15, inclusive. Past dates are counted separately as expired. Juniper's October 10 application deadline and Cedar's October 14 assessment deadline qualify. Harbor's blank deadline does not. Elm's closed status excludes it despite its October 9 date.

The view displays the employer date, source note, and requisition so you can open the right instruction. It preserves input order rather than sorting by urgency. Review the actual dates before choosing what to work on first. A record appearing above another record does not establish that its deadline is earlier.

Next actions selects active rows that contain a task, whether the personal date is overdue, today, planned, or unscheduled. Juniper and Harbor are labeled Today. Cedar is Planned for October 12. A future task stays visible because you may need to reserve preparation time before it becomes urgent.

Removing a personal date changes the task to Unscheduled and leaves it in the queue. Removing the task itself exposes Missing action in the input calculation and raises the correction count. This distinction helps you see whether you lack a schedule or lack a defined next step.

Unresolved receipt selects Needs verification rows, plus Submitted or Interview rows with no receipt reference. It returns Harbor alone in the sample. Juniper is still Draft and has no claimed submission to reconcile. Cedar has a receipt, while Elm is closed. The view therefore does not treat every empty confirmation cell as a failed application.

The workbook also displays an expired-deadline count and a correction count. An active employer date before the as-of date becomes Expired and leaves the upcoming view. Read that record and its original instruction to decide what remains possible. Moving the date forward to keep it visible would hide the missed date rather than resolve it.

Reconcile Harbor's missing receipt

An unclear outcome needs a decision based on evidence. Harbor's record says the fictional October 7 attempt ended in an error. Its confirmed submission date and receipt are blank, and its status remains Needs verification. The immediate task is to inspect the available portal and confirmation email, not to assume another submission is required.

After an error screen, it is easy to feel unfinished and click again. First check the same record: another attempt can leave you with two uncertain events to reconcile. Match any confirmation to the employer, requisition HS-04, and application destination. An unrelated email or a saved draft does not resolve this row. If nothing establishes receipt, keep the uncertainty and record the next appropriate check.

Suppose a matching confirmation establishes that HS-04 was submitted on October 7. Record that date and its receipt reference, then change the status to Submitted. Replace the completed verification task with “Review the employer's stated timeline,” choosing a personal review date that fits that communication. Do not derive a universal recruiter follow-up interval from this template.

Harbor leaves Unresolved receipt, changing that count from one to zero after both the matching receipt and Submitted status are recorded. Deadlines due soon stays at two because Harbor still has no employer deadline. Next actions remains at three if you replace its completed task with the new review task. This is a reconciliation of one existing opportunity, not an extra application or an extra opportunity row.

Use Excel filters or Google Sheets views deliberately

The workbook's three queues are formula outputs, not saved native filter views. To inspect the input table in Excel, use its column filters. Microsoft documents additive filters: filtering another column further narrows the visible records. Clear all filters before concluding that an opportunity is absent or adding a possible duplicate.

If you build your own Google Sheet, Google's filter-view guidance describes saved, named views that apply to your view of the spreadsheet. A regular filter is visible to other people with access. That difference matters when a mentor wants to inspect interview records while you work on deadlines.

For a native Sheet, create a headered table, define controlled statuses, and save the same three selection rules. Google also documents dropdown validation. Recreate and check the date conditions in that environment. Importing a CSV supplies records, not the workbook's formulas or saved views. Importing an XLSX also warrants checking controls and calculated outcomes rather than assuming identical behavior.

Check the template before adding your full search

Make a working copy and replace one sample row first. Confirm its ID is unique, its status means what the evidence supports, and its employer and personal dates occupy the correct columns. Compare its view membership to the rules above before importing a larger list.

Change the as-of date when you review the queue. The default is fixed at October 8 for a reproducible example. It will not silently advance tomorrow. Change the seven-day window when a shorter or longer planning horizon suits your search, while keeping employer deadlines unchanged.

If an expected record is missing, inspect its Record state, Deadline state, Action state, and Receipt review. Check blank dates, pasted text dates, duplicate IDs, closed statuses, and missing tasks. These fields explain eligibility. Increasing the window cannot fix an invalid date or a duplicate identifier.

Use the 30 prepared slots before extending the template. Adding a row beyond them requires extending the formulas, input controls, and bounded view ranges together. Copying values below the existing table does not establish that the queues include them. Keep the untouched download available so you can compare a later customization with the original.

End each review with a small set of actions you can perform: open the relevant instruction, complete the planned preparation, or verify the unresolved receipt. Keep the original history when an opportunity closes. The value of the tracker is a clear decision about the next step.

Make one working copy of the template, then choose a role from LandOffer's recent jobs. Replace one fictional record with its actual destination, preserve any supplied deadline, and check the resulting views before adding the rest of your search. The files organize records you enter; they do not submit applications.

Sources and Further Reading

• Microsoft: Filter data in a range or table in Excel: filtering behavior, combined filters, and reapplying filters after changes.
• Microsoft: Apply data validation to cells: list, date, and other input restrictions.
• Microsoft: DATE function: date construction and serial-number representation.
• Google Sheets: Sort and filter your data: regular filters and named filter views.
• Google Sheets: Create an in-cell dropdown list: controlled choices and validation settings.