Tenant Screening for Travel Nurses and Contract Workers: Why Good Renters Get Rejected
Key takeaways
- Standard tenant screening scores people on how long they have stayed put. Contract workers score badly on that by definition, not because they are risky.
- A travel nurse on a 13-week hospital contract will show 30 days at her employer, a stipend instead of a salary, and a two-week last tenancy. All three are red flags on a standard report and all three are just the job.
- The underlying data is not wrong. The credit check, eviction search and criminal check all work fine. What fails is the layer that decides which facts count as stability.
- A court has already ruled that a screening company cannot avoid responsibility for its score by saying the landlord made the final call.
- Declining these applicants never shows up as a loss on any report, which is why it goes on for years.
A travel nurse starts a 13-week contract at a hospital in Houston on July 1. On August 1 she applies for a furnished two-bedroom near the medical center. Her screening report comes back with four problems:
- Employment: 30 days at current employer
- Income: per-diem stipend, not salary
- Rental history: last tenancy, 14 days
- References: HR coordinators at a staffing agency
Every one of those is a red flag on a standard tenant screening report.
Every one of them is also a condition of the job she was hired to do.
She is not an unstable applicant. She is a perfectly normal mid-term applicant, being read by a system built to judge someone signing up for twelve months.
What is tenant screening, and what is a mid-term renter?
Tenant screening is the background check a landlord runs before approving an applicant. It usually combines a credit check, an eviction records search, a criminal records check, income verification and employment verification. Many services roll all of that into a single score, a number between roughly 300 and 850, and hand it to the landlord as a recommendation.
A mid-term renter is someone taking a furnished property for roughly 30 days to 12 months. In practice this means travel healthcare workers, contract engineers, consultants on fixed assignments, families between homes and people relocating for a new job.
A per-diem stipend is a daily allowance paid to cover housing and living costs on assignment. It is real, contracted money, but it is not structured like a salary, so income verification tools often cannot read it.
The key point is that nothing is broken in the data. The credit file is the credit file. The eviction search runs the same query it always did. The criminal check is unchanged.
What breaks is the interpretation layer sitting on top: the part that decides which facts mean "stable".
Why "stability" is measured wrongly here
Traditional screening treats length of tenure as the master signal, and it has a good reason for that.
On a twelve-month lease, staying in the same job and the same home does correlate with paying rent for twelve months. Long tenure is not valued for its own sake. It is a stand-in for a prediction: this person will probably still be doing the same thing next year.
Mid-term flips that relationship without weakening it.
A travel nurse's rent is not backed by tenure. It is backed by a signed clinical assignment with a defined end date, a contracted weekly rate, and a staffing agency legally obliged to pay it.
That is arguably clearer evidence than a salaried applicant's employment letter, which in most US states can end with two weeks' notice and no reason given.
But no field on a standard report holds any of it. So it gets typed into a free-text box, or left out entirely, and the score falls back on what it can actually measure: thirty days.
The same thing happens all the way down the list:
| What the applicant actually has | How a standard report reads it |
|---|---|
| Signed 13-week contract with a defined rate and end date | 30 days at current employer |
| Per-diem housing stipend from a staffing agency | No verifiable salary |
| Verified contractor income through Stripe or Deel | Self-employed, unverified |
| Relocation offer letter from a corporate mobility team | Not yet employed at stated address |
| 14-day prior stay with a five-star host rating | Rental history: 14 days |
Every item in the left column is evidence. Several are better evidence than the fields being scored. None of them has a slot.
The same mistake shows up everywhere else
Once you notice this pattern, you see it wherever a system quietly assumes twelve months.
Pets. Pet screening and pet rent are written for annual tenancies, then applied unchanged to a 30-day stay, with a full annual deposit and a policy calibrated to a year of wear.
Roommates. Two nurses sharing a two-bedroom get recorded as one lease. Two screenings, two signatures, two payment methods and one shared maintenance thread do not fit a system built around a single named tenant. Almost no third-party platform supports a lease per bedroom.
Renewals. Renewal reminders fire 90, 60 and 30 days before the lease ends. On a 30-day stay, the first one arrives after the tenant has already gone.
Individually these look like small settings problems. Together they describe a whole category running on assumptions imported from long-term residential renting, without anyone ever deciding to import them.
Screening scores are not neutral, legally
There is a comfortable assumption that the score is just infrastructure. The vendor supplies a number, the landlord makes the decision, and responsibility sits with the landlord.
A federal court has already rejected that argument.
In November 2024, a judge in the District of Massachusetts approved a settlement of roughly $2.3 million in Louis v. SafeRent, a class action alleging that an algorithmic tenant score disproportionately harmed people using housing vouchers. Earlier in the case, the court refused to dismiss the claim on the theory that the vendor could not be liable because landlords made the final accept-or-deny decision.
One of the criticisms of the product is directly relevant here: the score drew on data designed to predict credit repayment and used it to predict rent payment. Under the settlement, the company agreed to stop showing scores for voucher applicants and to have any replacement score independently validated.
That case is about housing vouchers and protected classes, not about travel nurses, and the distinction matters legally. But the structural lesson carries over cleanly. A scoring model built on inputs that do not measure the thing you are trying to predict is a liability, and the company supplying it does not get to stand outside the decision.
An operator declining qualified mid-term applicants because an old scoring model misreads contract work is not in the same legal position. They are in the commercial version of it: turning away good tenants, slowly, at scale, and filing it under caution.
Why this costs money you never see
The failure is invisible by design, which is exactly why it survives.
A declined applicant does not appear on any report as a loss. There is no line item for the unit that sat empty eleven extra days because the person who would have filled it scored 580 on a model that could not read her contract. You see a decline, then a vacancy, then a later booking, and nothing connects them.
Meanwhile the applicants being misread are the most valuable pool in the category. Travel healthcare workers, contract engineers on factory and data centre projects, corporate relocations and consultants on fixed assignments are precisely the people who:
- Pay above market rate for a furnished unit
- Stay for a defined, predictable period
- Rotate back through the same cities on their next contract
- Have an employer or agency standing behind the payment
They are also, without exception, short on tenure and rich in contracts.
Screening on tenure filters hardest against exactly the demand this category exists to serve.
What would actually fix it
Not more data. The market already collects plenty. Several vendors have launched conversational screening tools that gather documents and produce a recommendation in a single session, though the performance figures they publish are their own and should be read that way.
The missing piece is narrower and much less exciting. It is a scoring model that reads:
- A contract assignment as employment, with the end date and counterparty recorded
- A per-diem stipend as income, verified against the agency
- A rated 14-day prior stay as rental history, weighted by the rating rather than the length
Same inputs. Correct weights.
It also needs a report that shows why an applicant fits, rather than handing over a number and leaving you to argue with it. An operator who can see that rent is covered 3.4 times over by a contracted weekly rate running through a known end date has enough to decide. An operator who sees "580" does not, and will decline by default.
As of today, no property management system ships this. The data is fine. The reading is wrong.
RentOS is built for the 30-day-plus category, with applicant records that treat contract assignments, stipend income and short prior stays as real evidence rather than free-text exceptions. Book a demo at rrentos.com.
Frequently asked questions
Why do travel nurses fail standard tenant screening? Because standard screening uses employment tenure and rental history length as proxies for stability, and contract work produces short values for both by design. A nurse on a 13-week assignment shows about 30 days with her current employer, a per-diem stipend rather than a salary, and a previous tenancy measured in days or weeks. Each looks like a red flag on a model built for a 12-month lease, and each is simply a normal feature of the job.
Is the screening data itself wrong for mid-term applicants? No. The credit file, eviction search and criminal check are accurate and unchanged. The problem is the layer that interprets them and decides what counts as stability. Evidence like a signed assignment with a contracted rate, verified contractor income, or a highly rated previous stay is often stronger than the fields being scored, but has nowhere to go on a standard report.
Can a tenant screening company be held responsible for its score? A federal court has allowed such a claim to proceed. In Louis v. SafeRent, the District of Massachusetts rejected the argument that the vendor could not be liable because landlords made the final decision, and approved a roughly $2.3 million settlement in November 2024. Part of the criticism was that the score used data built to predict credit repayment in order to predict rent payment.
What should a mid-term screening model measure instead of tenure? Contract structure rather than continuity. That means the signed assignment and its end date, the contracted rate and who is paying it, the ratio of that rate to the rent, and rated previous stays regardless of length. The goal is not to lower the standard but to score the evidence that actually predicts payment across a 30 to 180 day stay.
How do I screen a contract worker if my software has no field for it? Until tooling catches up, the practical approach is to verify the assignment directly: ask for the signed contract or agency confirmation showing the rate and end date, confirm the paying agency, calculate rent as a multiple of contracted income rather than salary, and ask previous furnished hosts for a reference rather than relying on tenancy length. Record all of it against the application so the decision is documented.
Why does declining these applicants cost me money if I never see it? Because a decline never appears as a loss anywhere. There is no report line for a unit that stayed empty because the applicant who would have filled it was misread. The pool being filtered out, contract healthcare workers, project engineers and corporate relocations, is also the pool that pays above market for furnished units and returns to the same markets on later contracts.