XenoFeels inspection workflow in the demo
The XenoFeels inspection workflow above plays out across multiple demo days: database photo checks at the window, visa cross-checks after day two, outdoor plate and bumper walks, and end-of-day CEO ratings. Use the footage as a visual companion while you memorize the written checklist below.
Inspection workflow TL;DR
Run this XenoFeels inspection workflow on every ship without skipping steps.
- Pull the file first — names, visa fields, registration, internal consistency.
- Open the database photo and compare face, headgear, clothing, and accessories.
- Listen at the window, then walk the vehicle for plate digits and exterior details.
- Scan cargo hatches for prohibited objects before any approve click.
- State the tell out loud, then choose approve, deny, or service shotgun.
- Log clue type after each case so patterns stick across demo days.
Why a XenoFeels inspection workflow matters
XenoFeels is a spot-the-difference customs sim at heart. Each arrival is a case file: documents claim one story, the traveler and ship show another. The inspection workflow turns that comparison into muscle memory so you never approve on autopilot.
Steam’s store page lists four impostor tells — document errors, poor disguises, fake license plates, and hidden contraband. Your XenoFeels inspection workflow should touch every category before the barrier opens. Skipping the plate because the face matched is how homeworld-ending mistakes happen.
Psychological horror ramps up late in a shift, but the workflow does not change. Voices, shifting posters, and CEO pressure are mood — not replacements for paperwork. When the booth feels unreliable, run the checklist twice instead of guessing.
This guide is the hub other articles link to: beginner guide for first-shift context, terrorist spotting for tell details, right answers for outcome choice. Master the workflow here first.
The inspection loop from ship arrival to decision
A XenoFeels inspection workflow starts when a ship enters the lane and ends when you raise the barrier, turn the traveler away, or reach for the service shotgun. Between those points you are a case reviewer, not a chat moderator.
The Inspector’s briefing sets the tone: compare the database photo to the arrival’s appearance, double-check everything, and remember homeworld destruction is the fail state. The workflow below operationalizes that speech into six repeatable steps.
Between ships you may clean the service weapon, read DBTF recruitment posters, or watch the queue counter tick down. Those beats are rest points — use them to reset attention before the next file opens.
Step-by-step inspection workflow
Core XenoFeels inspection workflow — run top to bottom every arrival.
| Step | Action | Look for |
|---|---|---|
| 1 | Document pass | Name, ID, visa fields, race, age — internal consistency |
| 2 | Database photo match | Face, silhouette, headgear, clothing vs file image |
| 3 | Window check | Disguise errors visible while traveler speaks |
| 4 | Vehicle exterior | Bumpers, lights, grills, damage vs declared model |
| 5 | License plate walk | Digits match registration on file character by character |
| 6 | Cargo scan | Seats, trunks, hatches for prohibited objects |
| 7 | Decision | Approve, deny, or service shotgun with one-sentence reason |
Step 1 — Document pass
Start every XenoFeels inspection workflow with the file on your terminal. Read traveler name, ship name, destination, race, sex, age, and visa identifiers before you glance at the window. Paper contradictions are document-error tells — often faster to spot than a bad disguise.
Day one leans on computer verification for many fields. That does not mean you skip reading. After day two the CEO announces visas are no longer auto-verified — your workflow must add manual ID-to-visa comparison on top of the photo check.
Absurd field values still fail inspection. Demo cases include race lines that describe a job title instead of a species, or gender entries that contradict visible anatomy. If the paperwork insults basic logic, stop the XenoFeels workflow at step one and prepare a deny.
Step 2 — Database photo match
The database photo is the spine of the XenoFeels inspection workflow. Open the panel every ship — even when dialogue sounds friendly or the queue feels easy. The Inspector explicitly warns that appearance must match the file image.
Compare face shape, color, horns, headgear, glasses, shirts, and small accessories. Demo impostors often miss details the file shows: hair pieces, pocket layouts, lipstick, or eyewear style. A traveler who “looks close enough” is not close enough for approval.
Sci-fi parody costumes can still be legitimate when photo and papers align. The workflow asks whether the image diff is zero, not whether you recognize the reference character.
Step 3 — Window check and dialogue
Step three in the XenoFeels inspection workflow is the live traveler at the glass. Disguise errors you could not see on paper may appear here — wrong prosthetics, missing hats, or silhouette changes under booth lighting.
Travelers talk. Comedy lines about Space Vegas, manual paperwork, or threats are common. Dialogue is not a workflow step outcome — it is a reminder to re-open steps one and two if something felt off. Approve only when files and photos still align after the rant ends.
Some ships keep side windows covered. You still compare what you can see to the database photo. If view is blocked, lean on documents, plate walk, and cargo before approving.
Step 4 — Vehicle exterior pass
Vehicles are active evidence in XenoFeels, not background art. Later demo briefings demand attention to bumpers, tail lights, grills, and spoilers — regulations outlaw unauthorized modifications, and impostors hide tells in exterior details.
Public demo play includes cases where a bumper light shown in the file is missing on the ship, or where body kit pieces do not match declared registration. Fold an exterior walk into your inspection workflow once outdoor inspection unlocks — usually the same day plate checks become mandatory.
Walk the lane systematically: front bumper, lights, side profile, rear bumper, plate mount. Rushing the vehicle pass is the most common workflow break after day three.
Step 5 — License plate verification
License plates get their own workflow step because Steam names fake plates as a primary terrorist tell. Compare every digit and letter on the physical plate to registration numbers on the file — not to what the traveler claims at the window.
Demo play shows clean photos with wrong plate codes, including alphanumeric strings that almost match but fail on one character. Read plates slowly; homeworld risk does not forgive typos you skimmed.
Memorizing a plate pattern across ships helps speed without skipping. Still re-verify each arrival — impostors count on officers who remember yesterday’s format instead of today’s digits.
Step 6 — Cargo and contraband scan
The final evidence pass in the XenoFeels inspection workflow is cargo. Prohibited objects in seats, trunks, or hatches invalidate a clean face and clean paper. Scan hatches even when documents passed — contraband is the tell that punishes officers who stop after step two.
Travelers who mention business, loot, or side deals in dialogue deserve a cargo pass, not an automatic deny. The workflow catches objects, not slang.
When contraband appears with weapons visible, the service shotgun may follow denial. Name the object first, then pick force level.
Step 7 — Decision and logging
The XenoFeels inspection workflow ends with a deliberate outcome: open the barrier, turn the ship away, or use the service shotgun. Each choice needs a one-sentence reason tied to a step above — “photo missing headgear,” not “felt suspicious.”
After deciding, log the clue type in a notebook: document, disguise, plate, cargo, or clean. Two demo days of logging reveal which workflow step you skip under pressure.
The CEO scores unnecessary victims at day end. Workflow discipline keeps shotgun use rare — denial handles most impostors once steps one through six are complete.
How the workflow gains fields across demo days
XenoFeels inspection workflow additions — same order, extra checks.
| Demo phase | Workflow addition | Why it matters |
|---|---|---|
| Day 1 | Database photo + basic documents | Inspector tutorial; computer-assisted verification |
| Day 2+ | Manual visa vs ID cross-check | Auto-verification disabled by HQ algorithms |
| Mid-demo | Outdoor plate and bumper walk | Fake plates and illegal modifications enforced physically |
| Late demo | Higher CEO scrutiny | Same steps — more pressure to rush |
Between ships — workflow hygiene
A strong XenoFeels inspection workflow includes reset habits between arrivals. Clean the service shotgun after heavy shifts — the game treats it as real equipment, and the animation forces a pause that clears panic clicks.
Read recruitment posters during downtime. DBTF ads and Families for Hire copy sometimes change wording between days. That trains attention without replacing traveler inspection — environmental spot-the-difference supports the same mindset as step two.
Watch the queue counter. Knowing how many ships remain helps pace — but never skip a step to beat the clock. The homeworld fail state cares about accuracy, not speed records.
Late-day pressure — stick to the workflow
Steam advertises psychological horror: voices, exhaustion, strange events by shift end. The XenoFeels inspection workflow is your anchor when the booth feels wrong.
Hearing voices is thematic — the store copy jokes you should not talk back. Do not let audio mood replace document comparison. If a file looks different than you remember, re-run steps one through six on the active ship.
Poster anomalies and environmental glitches are not traveler tells. Deny only when the current case file, photo, plate, or cargo fails — not when a wall ad looked odd during downtime.
Workflow breaks that cause false approvals
- Opening the barrier after step two when plate and cargo were never checked
- Assuming day-one computer verification still covers visas on day three
- Skipping the outdoor walk once plate inspection unlocks
- Denying on dialogue alone without re-running document and photo steps
- Shooting before completing the workflow — collateral damage hurts your rating
- Treating bumper and light checks as optional flavor text
- Approving parody travelers because the reference joke felt friendly
- Changing step order randomly so cargo never gets scanned
Efficiency without skipping steps
Speed in XenoFeels comes from repetition, not from cutting the inspection workflow. Officers who memorize plate formats and common document fields still open the database photo every ship.
Batch your attention: documents and photo at the terminal, body at the window, vehicle and plate outside, cargo last. Physically moving through those zones matches the demo layout and reduces backtracking.
Second demo runs should target your weakest logged column. If plate mismatches beat you twice, drill step five on every ship until outdoor walks feel automatic.
Practicing the XenoFeels inspection workflow
Install the Steam demo (App ID 4791300) and run two passes: first to learn UI zones, second with a printed copy of the step table above. The XenoFeels inspection workflow clicks after you can name the failing step without hesitating.
Pair this guide with terrorist spotting when you need tell examples, and with right answers when the workflow is clear but the outcome is not. All three share the same clue grammar from the Steam store page.
Report workflow bugs on the Steam community hub after patches — outdoor inspection and visa rules shipped in demo updates, and field order may expand again before the 2026 full release.
Related guides
Unofficial fan guide — not affiliated with KotaMota Games or Valve. Demo content and controls may change after patches; verify in-game.