The Short-Tenure Job Score, Six Dimensions to List, Compress, or Omit

This is the scoring standard for one recurring call: a job you held for a few months, and whether it goes on your resume as a full entry, shrinks to a single line, or comes off. It is for anyone rewriting a resume with a short stint somewhere in the last ten years. You score the role on six weighted dimensions, read the verdict, then carry it through to your LinkedIn profile, a one-line context note if you need one, and a written rule for every background-check and full-history form you sign after the offer.

What does List, Compress, or Omit actually decide?

The verdict decides how the job appears on your curated documents, meaning your resume and LinkedIn profile. It never decides whether you disclose the job on a form that asks for your employment history. That split is the core of this framework, and most advice on short stints misses it.

The three verdicts:

• List. A full entry: employer, title, month-and-year dates, and two to four bullets, placed in your main experience section.
• Compress. One line, no bullets: employer, title, a short label such as "Contract, 3 months", and dates. It usually sits under an "Additional experience" heading or inside the main section with no detail.
• Omit. The role comes off the resume and the LinkedIn profile. It still goes on every form whose lookback window covers it. A lookback window is the number of years back a form asks you to account for.

One job exists in four records at once. You curate the top two. The bottom two exist whether or not you list the job.

The six dimensions and how to score each

Score each dimension 0, 1, or 2, where 2 is the strongest case for putting the job on the resume. Multiply each score by its weight and add them up, for a maximum of 24. The weights are Refolk's working standard, not the output of a study. If you change them, do it before you score, not after you see the total.

1. Length against your occupation's median tenure

Divide the role's length in years by the median tenure for your age band and occupation. Three months is 0.25 years, so against a 3.0-year median it comes to 8.3%. Score 2 at 25% or more, 1 from 10% to under 25%, and 0 under 10%.

What it proves: whether the stint looks like normal turnover for people like you, or like an outlier.

When it lies: when you score against one universal cutoff or the overall median. In the BLS release this guide uses, overall median tenure was 4.1 years, but the same three months means very different things depending on which group you compare against:

Source: BLS Employee Tenure release and secondary summaries for the medians. The last column is derived by dividing 0.25 years by the median. BLS directly confirms the 4.9-year figure for management, professional and related occupations combined. The single-occupation splits come from secondary summaries.

Some practical notes for this dimension:

• I could not retrieve the 35-44, 45-54, or 65+ age bands from the release this guide was built on. Pull your row from BLS Table 1 yourself.
• Sector matters. The same release-era summaries put public-sector median tenure at 5.6 years against 3.9 for the private sector, and federal at 7.0. If you are targeting government work, score against the longer median.
• Leisure and hospitality sat at 2.4 years, the lowest of the major private industries. Short stints are more ordinary there.
• Medians move between releases. The overall figure went from 3.9 to 4.1 years between the last two, and ages 25-34 went from 2.7 to 3.0. Re-check the current release before you score.

2. Reason it ended

Put the exit in exactly one category, taken from the separation letter rather than from memory. Score 2 for a layoff, role elimination, or contract end. Score 1 for a voluntary quit with a clean exit. Score 0 for a firing, quitting after being told you would be fired, or leaving by mutual agreement.

What it proves: whether listing the job invites a question you can answer with one neutral line.

When it lies: when a walk-out gets recorded in your head as a voluntary quit. That is the documented false negative on investigative forms. The same category also decides which federal questions the job triggers, so a wrong category here causes a wrong answer later.

3. Recency

Score 2 if the role ended less than two years ago, 1 if it ended two to ten years ago, and 0 if it ended more than ten years ago.

What it proves: how visible the stint is. A recent role sits at the top of the resume, and leaving it off makes you look unemployed right now. The payroll database's own report lists every verifier that pulled your data in the past 24 months, which is one reason two years is the first threshold.

When it lies: when an older role is still inside a 10-year form window. Low recency on the resume does not lower exposure on the forms. Dimension 6 catches that.

4. Gap it would leave

Measure in months, not years, how long the hole in your history would be if the role disappeared. Score 2 if omitting it leaves a gap of six months or more, 1 for three to six months, and 0 under three months or where another role overlaps it.

What it proves: whether Omit trades a short stint for a longer gap you cannot explain. In most cases a three-month job is easier to explain than a seven-month blank.

When it lies: when year-only dates on the neighbouring roles hide the gap on paper. Verifiers and full-history forms work in months, so score in months.

5. Relevance or brand value to the target

Score 2 if the work directly matches the target role or the employer is one your target readers will recognise and respect. Score 1 for adjacent skills and 0 for unrelated work.

What it proves: whether the stint adds evidence to the application you are sending.

When it lies: when you score on the employer's name rather than what you did there. A famous name on a six-week entry can draw more "why so short" attention than an unknown one, so only count brand value if a recruiter would see it as a plus.

This is the only dimension that changes from one posting to the next, so one role can come out as List for one application and Compress for another. Refolk builds each tailored resume from your own history and scores how well you fit each posting, which makes that per-posting variation cheap. The disclosure rule does not vary between applications.

6. Disclosure exposure

Score 2 if the role falls inside the window of a form you will sign that asks for every employer, such as SF-86 Section 13A. Score 1 if it appears in your payroll records, or if it ended in a firing, push-out, or mutual agreement inside a reason-based window (OF-306 Q12 or SF-85P). Score 0 if neither applies.

Source: OPM, FELTG and the payroll database's own documentation.

What it proves: whether the job will show up on a record you must sign or that a verifier can read, whatever the resume says.

When it lies: in both directions. Lookback periods on typical private background-check intake forms are not publicly established, so read the actual form you receive. I could not verify FINRA Form U4 requirements either. If you work in a regulated industry, read that form's instructions before scoring. A job missing from your payroll report can still belong in your work history, so a low score here is not a licence to leave it off a form.

How to read the total: List, Compress, or Omit

Add the weighted scores and read the band, then apply the two overrides. The bands are 15 to 24 for List, 8 to 14 for Compress, and 0 to 7 for Omit.

Overrides, applied after the total:

1. Federal full-history floor. If you will sign an SF-86 and the role is within the last 10 years, the worst verdict you can get is Compress. A DOJ instruction says SF-86 employment needs to match the OF-612 or the resume for the past 10 years, so leaving the job off the resume creates a mismatch, and a mismatch can be read as a false statement.
2. Current employer floor. If you still work there, the worst verdict is Compress. You will be asked where you work now, and the payroll record shows the job as active.

A worked example: a three-month contract for someone aged 25 to 34, ended last year, adjacent to the target, with a four-month gap if omitted and no federal forms ahead.

• Length: 8.3% of median, 0 x2 = 0
• Reason: contract end, 2 x1 = 2
• Recency: under two years, 2 x1 = 2
• Gap: four months, 1 x3 = 3
• Relevance: adjacent, 1 x3 = 3
• Disclosure: payroll record only, 1 x2 = 2

The total is 12, so the verdict is Compress: one line labelled as a contract, no bullets. Change the target to one where that contract was directly relevant and relevance becomes 6, the total becomes 15, and the verdict flips to List for that application only.

The two heaviest dimensions, gap and relevance, carry half the maximum score between them. The matrix below shows how they interact before the smaller dimensions shift the result.

How much does a short stint cost you with hiring managers?

Less than the headline percentages suggest. The surveys measure reactions to patterns of frequent job changes, not to one short stint among normal tenures, and none of them measures a rejection rate.

What the surveys say, and how far each can be trusted:

• LinkedIn, 1,024 hiring managers: 37% said frequent job changes might stop them pursuing a candidate. "Might" is a hedge, so this is not a rejection rate.
• Resume Genius, 625 US hiring managers: a job-hopping pattern made 50% hesitant to move forward. The key word is pattern.
• Jobera, 200 recruiters: only 52% call job hopping out, but 84% admit it has cost a candidate the role. This comes from a secondary source, and I have not verified the primary.
• Amply's 77% figure: no published sample size. Treat it as unverified.

Each survey worded the question differently ("might prevent", "hesitant", "flag"), so you cannot compare the numbers or average them. The fair reading is this: two or three short stints in a row is a pattern some screeners hold against you, while one stint inside an otherwise normal history mostly is not.

The base rate supports that reading.

Market norms matter too. Where contract and interim titles are common, a short stint labelled as contract work explains itself.

Source: Refolk's index of professional profiles. Ratios and shares are derived. The Germany count is likely too low because German-language titles were not matched, and a sample of 25 is too small to read the freelance shares as anything more than a hint.

What to do with this: if the stint really was a fixed-term or contract engagement, say so in the title or label. That one word turns an unexplained short tenure into a role that ended on schedule. Do not add the label to a permanent role that ended early.

Step-by-step: scoring one short-tenure role

Work through the steps in order, and pull your records first. Most resume guides skip the records pull entirely, but it is the only way to know what a verifier can already see before you decide what to leave out.

Why the records pull comes first: payroll data reaches the verification database directly from employers and payroll providers, not from you. The largest such database reports more than 823 million employee records from nearly 5 million employers. Not every employer participates, which is why the IRS transcript is the second half of the pull. Whether a verifier flags an employer that appears in payroll data but not on your application as an omission is not publicly established. Plan as if it could be flagged.

Use one scorecard per role. If you have two short stints, score them separately, because the gap dimension for one depends on whether the other stays on the resume.

ROLE = employer, title, start month and year, end month and year
TARGET SEGMENT = the kind of posting this version is for
MEDIAN USED = BLS row (age band or occupation) and value in years

1. Length vs median (x2)   months / 12 / median = ____%   25%+ = 2, 10-25% = 1, under 10% = 0   score ___ x2 = ___
2. Reason it ended (x1)    category from separation letter ________   layoff or contract end = 2, voluntary quit = 1, fired, pushed, or mutual = 0   score ___ x1 = ___
3. Recency (x1)            ended ___ years ago   under 2 = 2, 2-10 = 1, over 10 = 0   score ___ x1 = ___
4. Gap if omitted (x3)     ___ months   6+ = 2, 3-6 = 1, under 3 or overlapped = 0   score ___ x3 = ___
5. Relevance or brand (x3) direct = 2, adjacent = 1, unrelated = 0   score ___ x3 = ___
6. Disclosure exposure (x2) full-history form in window = 2, payroll record or event window = 1, neither = 0   score ___ x2 = ___

TOTAL ___ / 24
OVERRIDES   SF-86 within 10 years? Y / N   Current employer? Y / N   (either Y = no Omit)
VERDICT     List (15-24)   Compress (8-14)   Omit (0-7)
FORMS IN WINDOW   OF-306 Q12 Y / N   SF-85P Y / N   SF-86 13A Y / N   Payroll record Y / N

LinkedIn and the context note for each verdict

LinkedIn should carry the same verdict as the resume, with identical dates and titles. Turn off "Share profile updates with your network" before you make any edit. A context note is a short parenthetical that explains why a role was short. Use one only when the reason is neutral.

On LinkedIn's sharing behaviour, documented and not:

• LinkedIn says job updates may take up to two hours to be shared.
• It also says editing or deleting the update after adding it may affect notification generation. Adding a role and deleting it straight away is not a safe way to undo a post.
• LinkedIn does not document whether removing a position notifies anyone. Assume it might, turn the toggle off first, and check Recent Activity afterwards.

Context notes work when they state a fact a verifier would confirm. Never write a note for a firing, a push-out, or a mutual-agreement exit. Those belong in your interview answer and on the forms that ask, not on the resume.

COMPRESS LINE
[Employer] - [Title] (Contract, 3 months) - [Mon YYYY] to [Mon YYYY]

NEUTRAL CONTEXT NOTES, use only if the letter says so
(Contract role, fixed term)
(Role eliminated in reorganization)
(Team laid off)
(Fixed-term cover)

NO NOTE
Fired, quit after being told you would be fired, or mutual agreement

DISCLOSURE RULE
Every form that asks for my employment history lists every employer inside that form's lookback, with the same dates and titles as my records pull, whatever my resume shows. On OF-306 Q12 and SF-85P, I answer the event questions using the reason-ended category from the separation letter.

How this goes wrong

Most failures come from treating the resume decision and the form decision as one decision, or from scoring on a guess where a record exists. These are the documented failure modes, each with the check that catches it.

1. Length scored against one universal cutoff. Three months is about 17% of the median for ages 20-24 but about 3% for ages 55-64. A "drop anything under six months" rule gets both of those wrong. Check: score against the BLS row for your own age band and occupation.
2. Reason for leaving misclassified. Calling a walk-out a voluntary quit is the documented false negative on investigative forms. It lowers your exposure score and gives you the wrong answer on OF-306 Q12. Check: read the separation letter and use its wording.
3. Resume and SF-86 don't match. A DOJ instruction requires the employment history on the two to agree for the past 10 years. An omitted role inside that window shows up as a discrepancy. Check: put the two side by side and compare them line by line before you submit the form.
4. Assuming an omitted employer is invisible. Payroll records exist whether or not you list the job. Leaving it off the resume removes it from one document and nowhere else. Check: the EDR and the IRS transcript.
5. Assuming an employer missing from the EDR is safe to omit. Not every employer reports to the payroll database, and a job can be absent from the report and still belong in your work history. Check: the IRS transcript, your own records, and the form's lookback, never the database alone.
6. LinkedIn surprise post. Deleting a role right after adding it may still trigger a notification. Check: turn off the sharing toggle first and review Recent Activity afterwards.
7. Reading survey percentages as a rejection rate. The 37% figure means "might prevent", which is not the same as rejection. If you take it as a one-in-three rejection risk, you will omit roles that would have helped. Check: read each survey's actual wording before letting it influence a score.

The consequences when a form and the record disagree are on the record:

• In a federal case before the MSPB (Baker), OPM found "material and false statements regarding employment history" after the applicant answered "No" to OF-306 Q12.
• A Border Patrol trainee was debarred for three years due to deception or fraud.
• In private employment, McKennon v. Nashville Banner (513 U.S. 352) cut off back pay at the date the employer discovered the evidence. An omission found later limits damages but does not erase an otherwise valid discrimination claim.
• In Colorado contract claims, resume fraud is a complete defense only if the concealment "undermined the very basis upon which he or she was hired."

I did not retrieve the wording of private application attestation clauses, so I cannot tell you what a given employer's signature line commits you to. Read yours before you sign. None of this is legal advice. If you are already facing a discrepancy, take it to an employment lawyer.

Keeping the resume, profile, and forms consistent after the call

Write the disclosure rule down, keep it with your records pull, and re-score whenever your target or your forms change. The resume is meant to vary between applications. The dates, titles, and form answers must not.

Re-score the role when any of these happens:

• You switch target segment. Relevance carries a weight of 3, so a new target can flip the verdict.
• A federal application appears. The SF-86 floor applies to any role in the last 10 years.
• The stint ages past a window. Crossing 2, 5, 7, or 10 years changes recency or exposure.
• A new BLS Employee Tenure release comes out. Medians move, and so does your length ratio.

Version drift is the quiet risk. Five tailored resumes edited by hand tend to end up with five slightly different end dates for the same short role. Refolk writes every tailored version from one underlying history, so the dates and titles stay identical even when the Compress line appears in one version and a full entry in another.