Read before a shift
Skim rules and the quick reference so alerts feel familiar, not random.
MOTEL SYS / TRAINING MANUAL / REVISION 204
Issued for night desk trainees, temporary managers, and staff who still answer the lobby phone after midnight.
Fictional game-world document. Not real workplace guidance, HR policy, or motel employment training.
This manual is fiction for the Dead End Motel game. It borrows the tone of an old employee handbook to teach strategy — pressure, guest risk, rooms, cameras, incidents — without pretending to be a real employer.
Orientation
The manual gives optional strategy and lore. The game remains playable without reading it. Reading helps you understand guest risk, pressure, room assignment, incidents, and how staff codes tie into the Staff Terminal and Employee Portal.
Skim rules and the quick reference so alerts feel familiar, not random.
Room numbers in this book match the fictional map — use it when assigning or refusing.
Verification codes support terminal fiction and lore — they are not cheat codes or real security.
Table of rules
Jump to a policy card. All anchors are on this page.
Chapter 1
A suspicious guest is not always dangerous — but every ignored detail makes the night harder. Risk is about patterns, not vibes alone.
May mean: Short stay, evasion, or something to hide.
Action: Check ID · delay assignment · flag for camera if the story wobbles.
May mean: Privacy preference or trace avoidance.
Action: Second look per Rule 04 · verify identity calmly.
May mean: Legitimate quiet — or distance from cameras and staff.
Action: Cross-check floor risk · avoid weak zones if other red flags stack.
May mean: Anxiety — or mapping escape before check-in.
Action: Keep lobby camera active · cross-check Guest Files if available.
May mean: Escalation risk at the desk.
Action: Delay check-in · refuse only when policy demands — log it.
May mean: Prior knowledge of the motel — especially 204.
Action: Treat as red flag · see Rule 204.
May mean: Innocent worry — or scouting blind spots.
Action: Answer minimally · note behavior · review camera rules.
Guest Database · Guest files (Motel Files) · Verification codes (Employee Portal) · Mini Night Shift preview
Chapter 2
Pressure rises when the desk loses control, not only when something scary happens. Small unpaid debts to procedure become big debts at 3 AM.
Chapter 3
Use the Floor Plan as the source of truth for fictional room status.
Chapter 4
Cameras do not prevent incidents. They show the desk what it failed to notice in person — after the fact, if you are lucky.
Chapter 5
First: Delay check-in
Second: Flag for camera watch
Bad: Assign far room immediately
First: Reset cameras (protocol)
Second: Dispatch staff sweep if policy allows
Bad: Pretend the feed is fine and call the next arrival
First: Verify room numbers
Second: Check hallway feed
Bad: Move guest without logging
First: Cross-check Staff Portal / terminal
Second: Inspect Motel Files
Bad: Assume the record never existed
First: Deny direct assignment after midnight
Second: Check Staff Desk file
Bad: Hand key to high-risk guest
Chapter 6
Verification codes are fictional staff references shared by the game and website. They may unlock terminal notes, lore, or future build hints. They are not real security credentials.
Codes in circulation include 204, 204-13, DEM-204, 013, 404, and 911. Full copy-and-paste reference lives on the portal.
Critical policy
Local Gazette GAZ-204 — archived clipping on the midnight room policy.
Policy cards
Short policies with “in game” meaning — still fiction, still useful.
Policy: Speed is not a virtue when details disagree.
In game, this means: Extra verification steps can trade time for safety and reputation later.
Policy: Cash is legal — carelessness is not.
In game, this means: Pair cash with ID discipline and camera awareness before you assign.
Policy: Footage supports logs; it does not replace them.
In game, this means: Use feeds to corroborate — not to argue yourself into ignoring a guest read.
Policy: Low volume is not a risk clearance.
In game, this means: A quiet guest can still raise suspicion if they avoid cameras or watch exits.
Policy: Unlogged shortcuts become loud problems.
In game, this means: The pressure meter punishes stacked compromises — fix leaks early.
Policy: If it is not in the log, it did not happen — until it does.
In game, this means: Room changes without paper trail fuel incidents and audits.
Policy: A key handed over is a promise the room matches the guest.
In game, this means: Check back on sensitive assignments; 104 is baseline but not invisible.
Policy: Verify before you punish a room number.
In game, this means: Noise may mask another problem — cameras and hallway checks first.
Policy: Blind spots earn paperwork and escorts.
In game, this means: Avoid stacking risk in 237 unless you are logging every step.
Guest Database · Lost & Found · Floor Plan · Local Gazette GAZ-237
Policy: “Not found” is a status, not a verdict.
In game, this means: Check the Employee Portal and Motel Files before you assume a clue is gone.
Policy: The switchboard has moods.
In game, this means: Calling for help is a tool, not a guaranteed reset — manage pressure anyway.
Appendix A
Why it hurts: Open incidents compound while you split attention.
Better: Close or log the current problem first.
Why it hurts: You lose evidence and reaction time.
Better: Keep hot guests where feeds and staff paths help.
Why it hurts: Pressure remembers.
Better: Note and verify — even when it annoys the guest.
Why it hurts: Quiet can be tactical.
Better: Watch movement and eye-line, not volume.
Why it hurts: Terminal and web resources diverge if you never look.
Better: Cross-check portal codes and files when stuck.
Why it hurts: Codes are lore/support — not a win button.
Better: Read responses in-world and adjust play.
Why it hurts: Reputation and pressure both spike.
Better: Refuse only when policy demands; document why.
Why it hurts: Audits and incidents love invisible moves.
Better: Rule 27 — log first, key second.
Why it hurts: LF tags can anchor room–guest–incident chains you will need later.
Better: When an item ID surfaces, check the archive — it is optional, not mandatory.
Why it hurts: Clippings explain why some rules exist and which rooms kept repeating incidents.
Better: When a GAZ ID appears, skim the Local Gazette — optional lore, not a requirement to play.
Tear-off card
Old clippings can explain why some staff rules exist.
Sound starts only after you choose a radio mode and press Start radio.