MOTEL SYS / TRAINING MANUAL / REVISION 204

New Employee Training Manual

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.

Issue notice

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

How to use this manual

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.

Read before a shift

Skim rules and the quick reference so alerts feel familiar, not random.

Cross-check with Floor Plan

Room numbers in this book match the fictional map — use it when assigning or refusing.

Use codes as optional clues

Verification codes support terminal fiction and lore — they are not cheat codes or real security.

Chapter 1

Guest risk basics

A suspicious guest is not always dangerous — but every ignored detail makes the night harder. Risk is about patterns, not vibes alone.

  • No luggage

    May mean: Short stay, evasion, or something to hide.

    Action: Check ID · delay assignment · flag for camera if the story wobbles.

  • Pays cash after midnight

    May mean: Privacy preference or trace avoidance.

    Action: Second look per Rule 04 · verify identity calmly.

  • Requests a room far from the lobby

    May mean: Legitimate quiet — or distance from cameras and staff.

    Action: Cross-check floor risk · avoid weak zones if other red flags stack.

  • Watches exits before speaking

    May mean: Anxiety — or mapping escape before check-in.

    Action: Keep lobby camera active · cross-check Guest Files if available.

  • Refuses ID check

    May mean: Escalation risk at the desk.

    Action: Delay check-in · refuse only when policy demands — log it.

  • Knows a room number before seeing the map

    May mean: Prior knowledge of the motel — especially 204.

    Action: Treat as red flag · see Rule 204.

  • Asks about camera coverage

    May mean: Innocent worry — or scouting blind spots.

    Action: Answer minimally · note behavior · review camera rules.

Chapter 2

Pressure control

Pressure rises when the desk loses control, not only when something scary happens. Small unpaid debts to procedure become big debts at 3 AM.

  • Do not ignore small warnings — they stack.
  • Do not park high-risk guests in weak camera areas.
  • Respond to open incidents before greeting the next arrival.
  • A fast decision is not always a controlled decision.
  • Refusing everyone can tank reputation — pick battles.
Calm Uneasy High Critical

Chapter 3

Room assignment rules

Use the Floor Plan as the source of truth for fictional room status.

  • Room 104 — Standard assignment · low baseline risk.
  • Room 118 — Watch noise complaints; verify before blaming a neighbor.
  • Room 204 — Restricted after midnight. See Rule 204.
  • Room 237 — Weak camera zone · assign only with caution and logging.
  • Staff Only — Never assign to guests.
  • Camera Room — Staff access only.
  • Storage — No guest access.

Open Floor Plan

Chapter 4

Camera monitoring

Cameras do not prevent incidents. They show the desk what it failed to notice in person — after the fact, if you are lucky.

  • CAM 01 Lobby Desk: Watch late arrivals and line behavior.
  • CAM 02 Room 204 Hallway: Signal unreliable after 1:43 AM — log anomalies.
  • CAM 03 Parking Lot: Low light · slow response · do not over-trust motion.
  • CAM 04 Staff Only Door: Weak signal · treat gaps as operational risk.
  • CAM 05 Office Radio: Not a camera — still useful for atmosphere and timing cues.
  • CAM 06 Unknown Signal: Ignore single blips unless the pattern repeats.

Chapter 5

Incident response chart

Guest refuses ID

First: Delay check-in

Second: Flag for camera watch

Bad: Assign far room immediately

Camera blackout

First: Reset cameras (protocol)

Second: Dispatch staff sweep if policy allows

Bad: Pretend the feed is fine and call the next arrival

Noise complaint

First: Verify room numbers

Second: Check hallway feed

Bad: Move guest without logging

Missing file

First: Cross-check Staff Portal / terminal

Second: Inspect Motel Files

Bad: Assume the record never existed

Room 204 request

First: Deny direct assignment after midnight

Second: Check Staff Desk file

Bad: Hand key to high-risk guest

Chapter 6

Verification code policy

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.

Open Employee Portal codes

Critical policy

Rule 204 — Do not assign Room 204 after midnight

  • Room 204 is restricted after midnight in fiction — treat the restriction as operational law during night shifts.
  • The hallway camera toward 204 is listed as unreliable after 1:43 AM — do not bet the shift on that feed.
  • Guests who request 204 before seeing a map warrant extra scrutiny.
  • A direct 204 request is a red flag, not a loyalty perk.
  • Cross-check the Staff Desk file and portal code 204 when in doubt.

Local Gazette GAZ-204 — archived clipping on the midnight room policy.

Policy cards

Individual rules

Short policies with “in game” meaning — still fiction, still useful.

Rule 01 — Slow down suspicious check-ins

Policy: Speed is not a virtue when details disagree.

In game, this means: Extra verification steps can trade time for safety and reputation later.

Mini Night Shift

Rule 04 — Cash after midnight needs a second look

Policy: Cash is legal — carelessness is not.

In game, this means: Pair cash with ID discipline and camera awareness before you assign.

Employee Portal · Local Gazette GAZ-027

Rule 07 — Cameras confirm patterns, not feelings

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.

Media Hub · Local Gazette GAZ-013

Rule 13 — Quiet guests are not automatically safe

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.

Guest Database · Guest Files · Local Gazette GAZ-013

Rule 18 — Pressure spreads through small mistakes

Policy: Unlogged shortcuts become loud problems.

In game, this means: The pressure meter punishes stacked compromises — fix leaks early.

Mini Night Shift

Rule 27 — Do not move a guest without logging it

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.

Motel Files · Local Gazette GAZ-237

Rule 104 — Warm keys require follow-up

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.

Floor Plan · Local Gazette GAZ-118

Rule 118 — Noise complaints can be bait

Policy: Verify before you punish a room number.

In game, this means: Noise may mask another problem — cameras and hallway checks first.

Lost & Found · Floor Plan · Local Gazette GAZ-118

Rule 404 — Missing files are not always missing

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.

Lost & Found · Employee Portal · Local Gazette GAZ-404

Rule 911 — Emergency calls are not guaranteed to route

Policy: The switchboard has moods.

In game, this means: Calling for help is a tool, not a guaranteed reset — manage pressure anyway.

Mini Night Shift · Local Gazette GAZ-911

Appendix A

Common staff mistakes

Calling the next arrival too early

Why it hurts: Open incidents compound while you split attention.

Better: Close or log the current problem first.

Assigning high-risk guests far from cameras

Why it hurts: You lose evidence and reaction time.

Better: Keep hot guests where feeds and staff paths help.

Ignoring “small” red flags

Why it hurts: Pressure remembers.

Better: Note and verify — even when it annoys the guest.

Treating every quiet guest as safe

Why it hurts: Quiet can be tactical.

Better: Watch movement and eye-line, not volume.

Forgetting the Staff Portal

Why it hurts: Terminal and web resources diverge if you never look.

Better: Cross-check portal codes and files when stuck.

Using codes like cheats

Why it hurts: Codes are lore/support — not a win button.

Better: Read responses in-world and adjust play.

Refusing everyone

Why it hurts: Reputation and pressure both spike.

Better: Refuse only when policy demands; document why.

Moving guests without logging

Why it hurts: Audits and incidents love invisible moves.

Better: Rule 27 — log first, key second.

Ignoring Lost & Found item IDs

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.

Treating Gazette GAZ IDs as flavor text only

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

Quick reference

Before assigning a room

  1. Check ID
  2. Check red flags
  3. Check room risk
  4. Check camera coverage
  5. Check incident pressure
  6. Check Lost & Found if an item ID appears
  7. Check Local Gazette if a GAZ clipping ID appears
  8. Log the decision

Before using a code

  1. Check where it came from
  2. Verify context in Employee Portal
  3. Enter in Staff Terminal
  4. Treat it as lore/support, not a cheat

Old clippings can explain why some staff rules exist.