10 min read
Six finished contracts in eighteen months isn't a red flag by itself. It's a formatting problem when each stint gets half a line, no end date, and a title that doesn't match what you actually did on site. Corporate screeners expect Experience rows they can map to a req. Gig-heavy files often fail that test before anyone reads bullet two, and you can't fix that with a prettier template.
Run your export through check your resume for free before you touch layout again. You're checking whether dates and employer names survived as rows, not chasing a decorative score. If the plain-text pass looks scrambled, don't add keywords until the rows are stable.
Tonight you'll sort pay types, pick rollup versus split lines, write tight bullets, and trim side income that doesn't belong on this apply. Same work history, clearer tenure story, and you won't need to apologize for short gigs when the dates are closed.
Quick wins
- Close every contract with an end month, even when the next gig started the same week.
- Match four stack terms from the posting before you choose which clients stay on page one.
- Label W2 agency roles with the client first, not the staffing shop alone.
Rollups versus separate lines on page one
A rollup puts several paid gigs under one employer line, usually your LLC name or Independent Consultant, with a date span that covers the whole consulting period. Separate lines give each end client its own title, Contract tag, and Month Year range. Neither is cheating. The wrong pick is the one that hides a gap or makes a named client impossible to find in a six-second skim.
Parsers read dates first. Workday and Greenhouse build tenure from start and end fields on each Experience row. Four three-month jobs import as four rows when headers stay plain. One rollup imports as one row. Both can pass import. Humans then ask whether the story matches the posting lane.
Roll up when buyers were mid-market clients in the same function, you invoiced through one entity, and bullets can name outcomes without breaking NDAs. Split when the req lists a client you supported, titles shifted from analyst to lead, or a W2 stretch sits between gigs and must not disappear inside Consulting.
Before: Nine client names, no end dates, every line still says Present.
After: Either one consulting header with dated sub-bullets per buyer, or four client rows with closed months and Contract in the title.
Agency payroll adds a fork. When the check came from a staffing firm but you sat on site at the buyer, the buyer belongs on the employer line with Contract in the title. For deeper before/after blocks on that pattern, see how to list contract work so recruiters don't get confused . This page focuses on when to bundle versus split once dates are honest.
Gig platforms sit at the edge. If you drove most of your income through one marketplace for a year, treat it like an employer with Contract in the title and describe buyer work in bullets. Scattered one-off tasks don't earn page one on a corporate upload unless they're your only proof for a required skill.
Decision table for tonight's file:
| Pattern | Layout |
|---|---|
| Same-lane clients, one LLC | Consulting rollup + client bullets |
| Posting names a client you staffed | Separate row, client as employer |
| W2 job between contracts | Own row, no rollup over it |
| Mixed stacks across gigs | Split rows, trim off-lane clients |
If your lane jumps (support, then data, then PM), organize the story before you compress dates. How to organize a resume when you did many different things helps you pick which contract leads page one for this req.
Write short-term contract experience step by step
Run these five steps against one posting you'll submit tonight. Stop when plain text shows closed Month Year ranges and your top rows repeat vocabulary from the job text.
Step 1: Sort engagements by client and pay type
Open a scratch doc. List every paid engagement from the last five years: client or platform, functional title, W2 versus 1099, agency name if any, and true start and end months. Mark overlaps you can explain and gaps you won't fake.
Tag each line with two tools from the posting highlight pass. Clients that share fewer than two must-haves move to the master file for this apply, even if the work was real and paid well.
Step 2: Choose rollup or separate Experience rows
Apply the table from the prior section. When you rollup, set the employer line to your consulting entity or Independent Consultant, span Month Year to Month Year across the cluster, and nest client names inside bullets. When you split, each buyer gets employer, Contract title, and its own date range in reverse chronological order.
Never rollup across a full-time W2 row. Never leave a finished contract on Present because the next gig feels related. End dates are how parsers compute stable tenure.
Step 3: Write two bullets per contract line
Bullet one names audience, scope, and stack in the first eight words. Bullet two carries one illustrative metric inside the sample line, such as cutting ticket backlog 18% in a ninety-day renewal. Swap in your real tools and counts.
Under a rollup, prefix bullet one with the client when NDAs allow: Northwind Bank: rebuilt Service Cloud routing rules for tier-two queue. Under split rows, keep the client on the employer line and let bullets stay outcome-focused.
Step 4: Align headers and contract labels
Type Experience as a plain header. Repeat Contract, Freelance, or Independent contractor in the title line, not five different synonyms. Single-column DOCX beats two-column templates when dates must sit beside titles.
When imports scramble order, read resume formatting errors that break ATS parsing before you add more keywords to a broken file.
Step 5: Parse-check the upload file
Save the file type the portal accepts. Paste into plain text and confirm each contract row shows employer, title, start, end, and bullets in order. Re-export after any header rename.
In Greenhouse previews, scan whether short gigs imported as separate rows or merged into orphan text. If dates vanished, fix the source layout instead of typing dates only in the web form.
Copy-paste into your notes app:
Posting stack: [4 terms from JD]
Pay type: W2 agency / 1099 / client W2
Layout: rollup / split row
Employer line: [client or LLC]
Dates: [Mon YYYY – Mon YYYY]
Bullet 1 (scope + stack): [line]
Bullet 2 (illustrative metric): [line]
Plain-text row check: pass / fail
I've screened Workday imports where six active Present tags stacked on one page while the candidate hadn't worked anywhere in four months. The bullets were strong. The open dates made tenure look unstable before a human reached bullet one.
Before: Consulting header with no months and a list of logos.
After: Closed dates, two bullets per client or a dated rollup with stack terms the req repeats.
Contract layouts that break the second scan
- Merging unrelated buyers into one Freelance line with no Month Year span.
- Listing the staffing agency alone when the req expects the end client name.
- Using creative headers like Client Engagements that importers drop into the body.
- Deleting a short gig to hide hopper optics and creating a real calendar gap.
- Repeating Contract in Skills without showing the same tool in a dated bullet.
Before: "I'll list every logo so they see I'm busy."
After: "I'll show three dated rows that match this posting's lane and stack."
Gaps between honest contracts happen. One dated line for caregiving, training, or job search beats stretching a rollup across empty months. Why career gaps are not always bad covers how to label non-client months without stuffing the summary.
Confirm dates before you add keywords
Keyword stuffing under a vague Consulting header still fails import when dates don't map. Scan after you close end months, not before.
Run a free ATS scan on the company-specific export. You're confirming Experience rows and tenure survived, not chasing a decorative score.
Build your resume in a single-column template if plain text still drops contract dates after manual fixes.
Close the dates, then tailor
How to write a resume with short-term contracts is mostly a layout call plus honest months. Pick rollup or split rows for this req, write two bullets per line, and keep Experience headers boring so parsers attach stack terms to dated work.
Save a company-named file before you submit on Workday or Lever. The next posting may need different clients on page one, not a different work history.
Mirror your lead contract outcome in a short letter with Generate a cover letter so the attachment repeats the same stack language as bullet one.
Read more
Frequently asked questions
Group when you served similar buyers through your own LLC or sole proprietorship, the work shares one lane, and dates can span the whole period without hiding a six-month gap. Split into separate client rows when the posting names a Fortune client you staffed, when titles or stacks differ sharply, or when a rollup would blur W2 employment that belongs on its own line.
Short tenure is normal in contract markets. Each client gets Month Year start and end, two outcome bullets, and a Contract tag in the title line. A one-line summary above Experience can say you deliver through fixed-term engagements. Do not delete finished gigs to stretch dates; parsers compare rows and gaps you cannot see in the PDF view.
Keep marketplace gigs off the corporate file unless the posting asks for that proof. If one platform supplied most of your income for a year, list it as the employer with Contract in the title and name the end client inside bullet one when NDAs allow. Random weekend tasks belong in a master file, not page one of a Workday upload.
Rollups fail when bullets stay vague. Under one header, nest client sub-lines or lead each bullet with the tool the job text repeats. Parsers attach keywords to Experience rows with dates. A rollup with three stack-heavy bullets beats six empty client names. After export, paste plain text and confirm tools sit under dated Experience, not floating above Skills.