Assigning Rooms at an Inn: How Can Guests Receive Fair Consideration Without Disclosing Private Information?
Replace “Why do you need this?” with “Which arrangements are unacceptable?” Use requirement cards, a room-matching table, and an exchange process that allows refusal to keep allocation conflicts focused on limited resources rather than who will reveal more secrets.
Introduction
Ask what conditions a room must meet before comparing feasible arrangements. Sharing personal experiences should not be a prerequisite for consideration. To build fairness into choices, show players the basis for allocation, the costs of an exchange, and the options available after refusal, rather than having guests take turns recounting their hardships.
The fictional Bridge Crossing Inn serves as a teaching example below, with reusable requirement cards and a branching structure. This is not a real user case, a tested result, a DramaFork product feature, or a service standard for real inns.
1. Limit the Conflict to Three Rooms and Three Sets of Requirements
Bridge Crossing Inn has three single rooms left tonight. Room A faces the inner courtyard on the first floor: it is quiet and requires no stairs. Room B faces the inner courtyard on the second floor: it is quiet, but guests must use stairs to reach it. Room C faces the street on the first floor: no stairs are required, but nighttime traffic is audible. All three have identical bedding and the same period of occupancy; the story introduces no price differences.
Aran says, “I can't use stairs. A street-facing room is fine.” Wenzhou says, “I need quiet. Any floor is fine.” Xiaohe says, “I'd like a quiet room too, but a street-facing room is negotiable.” These statements are enough to begin allocating rooms. There is no need to add injuries, illnesses, family histories, or secret missions to prove who deserves more consideration.
The characters themselves confirm what “can't” and “negotiable” mean; the innkeeper only clarifies their meaning. For example, the innkeeper may ask Aran, “Would a first-floor room facing the street be acceptable?” They must not make answering “What's really going on with you?” a condition of continuing the check-in process. Characters may volunteer their backgrounds, but disclosing more does not give them greater priority in room allocation.
Explain the room differences at the start of the scene. Otherwise, players can choose only according to which character they like. The scarce resources are two quiet rooms, only one of which is on the first floor. The conflict comes from this combination of attributes, not from someone being insufficiently considerate.
2. Replace Accounts of Hardship with a Six-Field Requirement Card
The following card can go directly into a script outline, with one completed for each guest. It records the information needed to make arrangements, not the full personal reasons behind it.
| Field | What to record | Xiaohe's example |
|---|---|---|
| Essential conditions | Conditions without which the arrangement is unacceptable | None for now; awaiting her confirmation |
| Priority preferences | Desirable but negotiable conditions | Quiet |
| Possible exchanges | Specific alternatives the guest is willing to consider | A street-facing room plus an evening reading seat |
| Explicit refusals | Unacceptable arrangements | Sharing with a stranger |
| Disclosure scope | What may be relayed to others | Only acceptable room conditions |
| Confirmation status | Proposed, accepted, or withdrawn | Proposed; not yet accepted |
“None for now” does not mean a character has no requirements, and the innkeeper must not change it to “Anything is acceptable.” If a guest does not wish to answer a field, leave the relevant arrangement awaiting confirmation rather than assuming consent.
The exchange field must also identify where the resource comes from. In this example, the inn has a seat at a communal table that is unused in the evening and available for reading. It can accommodate Xiaohe's preference for reading before bed; it cannot make the street-facing bedroom quiet. Xiaohe must therefore decide whether this alternative is useful. The innkeeper cannot declare the two equivalent.
Disclosure scope is more than decorative wording. If Xiaohe allows only the innkeeper to know her exchange conditions, the public room-allocation notice may show only the room assignments and general rules. It cannot display her exact words for others to judge.
3. Find Feasible Combinations Before Proposing Exchanges
The player first maps the essential conditions into a matching table: Aran can stay in A or C, Wenzhou in A or B, and Xiaohe has not yet ruled out any room. A combination already exists that requires no exchange: Aran in C, Wenzhou in B, and Xiaohe in A. It meets the stated essential conditions and gives both Wenzhou and Xiaohe the quiet rooms they want.
This step matters: do not deliberately give Aran Room A first and then demand that Xiaohe prove why she needs quiet just to manufacture dramatic conflict. Looking at the complete combination first avoids turning an allocation oversight by the innkeeper into a sacrifice a guest must make.
Next, offer the player two concrete actions: “Confirm this arrangement with each guest” or “First ask whether any conditions have been missed.” The former moves check-in forward; the latter lets characters revise their cards. Neither requires them to disclose their reasons.
In the second branch, Xiaohe adds, “When I said it was negotiable, I meant where I read. I can't accept a bedroom facing the street.” The innkeeper moves quiet from a preference to an essential condition, and the original combination remains feasible. This moment shows the value of clarification without automatically treating a late-stated condition as deception.
If the player proposes a different arrangement—Aran in A, Wenzhou in B, and Xiaohe in C with use of the reading seat—Xiaohe may refuse. After refusal, return to the existing feasible combination. The effort the player spent proposing an exchange does not put the character under an obligation to cooperate.
4. When Essential Conditions Clash, Make Refusal a Complete Branch
Change one more condition: Aran confirms that a street-facing room is also unacceptable. All three guests now need quiet, but only two quiet rooms exist, and A is the only room Aran can accept. The matching table should explicitly state, “These requirements cannot all be met tonight.” Warm dialogue must not pretend the problem has been solved.
The innkeeper may separately ask Wenzhou and Xiaohe whether they would reconsider an arrangement. The questions must concern conditions, without requiring them to listen to each other's personal histories. If neither is willing to adjust, negotiations end there. Do not keep persuading the same person until they agree out of exhaustion.
This version can establish a public rule in advance: first reserve assignments for guests with only one feasible room, then draw lots between the two guests competing for B. Before the draw, explain that whoever does not receive B may still refuse C and end the discussion about staying at the inn. The result does not mean anyone's needs matter less. This is the procedure selected for this story, not the only correct definition of fairness.
A mediation option can read, “Ask another staff member to review the rooms and records.” The review checks for overlooked rooms, misrecorded conditions, or departures from the announced order. It does not judge anew whose reasons are more compelling. If no additional resources can be made available, mediation may also leave the situation unresolved.
Keep three distinct states at branch endings: accepted, refused, and awaiting review. Hand over the key only after acceptance. Silence or a pending response must not be written as a completed agreement.
5. Make the Costs Visible and Acknowledge the Rules' Limits
First come, first served is easy to explain, but the order must be established in advance, and an early arrival choosing A could leave Aran without the only feasible room. A pure lottery reduces the innkeeper's personal discretion, but it may produce a combination in which guests cannot stay. Prioritizing guests by how few feasible rooms they have accommodates those with fewer options, but also means some people have fewer opportunities to compete. Let characters question these costs rather than using narration to declare that everyone is satisfied.
Three types of branches are particularly easy to mishandle: a guest loses eligibility for refusing to explain their reasons; someone who accepts the street-facing room is praised as the only considerate person; or someone faces later retaliation for refusing an exchange. All three make “No disclosure required; refusal allowed” an empty promise. The story may retain disappointment and arguments, but it should distinguish dissatisfaction caused by scarce resources from the author's punishment of someone who refuses.
Before delivering the script, check every route: Have essential conditions been unilaterally downgraded to preferences? Has the guest confirmed the exchange? Does public dialogue exceed the permitted disclosure scope? Does the story honestly stop when no solution is available? Pay particular attention to branches the player does not see, so that characters retain their dignity on more than just the compliant route.
This structure also has clear limits: it depends on characters being able to express or revise their conditions and accepting the procedure announced in the story. Requirement cards alone cannot establish whether every statement is true. If the plot must address false claims, introduce separate, observable behavioral evidence. Refusing to disclose private information must not itself be treated as grounds for suspicion.
