How to Write Task Completion Criteria: Replace “Earn Their Trust” with Verifiable Events
“Make them happy” is hard to judge. Using a rehearsal room booking as an example, separate task completion, relationship changes, and permission to share publicly.

Introduction
The player finds the rehearsal room key, and a character says, “That's great.” Is the task complete?
If the task is to return the key, yes. If the task is to secure the rehearsal room for Saturday evening, the time slot, scope of use, and who has authority to approve it still need to be confirmed. Many ambiguous outcomes come from treating one easily observed event as proof of another that has yet to happen.
Start by Defining What the Task Must Deliver
“Earn the administrator's trust” sounds like a goal, but it is hard to tell when it has been achieved. You could rewrite the current task as: “Get confirmation to use the rehearsal room on Saturday from 19:00 to 21:00, and tell participants when they must clear the room.”
This specifies an object, a time, and an outcome. Whether the administrator likes the player can change gradually through conversation; it does not have to do all the work of three systems: access rights, room reservations, and personal closeness.
When choosing a genre you like on the text games page, you can also ask: what exactly should the player accomplish in this story? Writing it as something verifiable is usually more useful than starting with a list of attributes.
Keep Three Types of Records Separate
| Record | Event that can be confirmed | What cannot also be inferred |
|---|---|---|
| Task | The administrator confirms a specific time slot | This does not mean the player can enter whenever they want in the future |
| Relationship | The other person takes the initiative to suggest working together again | This does not mean a romantic relationship has begun |
| Permission | Both parties agree to share the group photo from this rehearsal publicly | This does not mean all conversations and photos can be made public |
A single action can affect several records, but each needs its own supporting evidence. A character saying “I really admire you” can change the mood between them, but that sentence cannot automatically produce approval to use the room.
Completion Criteria Need More Than a Verb
“Contact the administrator” might mean only sending a message; “the administrator confirms the time slot” means a reply has been received. “Submit an application” is not the same as “the application is approved,” and “obtain the documents” is not the same as “check the documents.” Distinguishing these verbs one by one when writing rules can prevent many disputes later.
This does not mean every task needs to become a lengthy form. For a short story, keep only records that affect choices: whether the time slot is confirmed, whether the requirement to clear the room has been passed on, and whether the deposit has been handled. There is no need to add values that serve no practical purpose.
Tell the Player What Is Still Missing
If the room booking has not been completed, the feedback should say, “The time slot is confirmed, but you have not yet told participants to clear the room by 21:00,” rather than simply “Insufficient trust.” The former tells players what they can still do; the latter can turn the outcome into a guessing game about a character's mood.
A mystery can conceal the contents of a piece of evidence while keeping known procedures consistent. If two independent records are required, do not suddenly add a third after the player submits them. If new circumstances change the requirements, present that change as a new event rather than retroactively invalidating steps already completed.
Relationships Can Continue; Tasks Need Closure
Once the room booking is settled, characters can still talk about the rehearsal, future collaboration, or their respective concerns. Giving a task an endpoint does not prevent a relationship from continuing. You can preserve this distinction when creating character IP, too: completing one activity together does not mean all the characters' problems are solved, much less that the user has accepted the next invitation.
When checking a criterion, try asking: “Which record would let an observer confirm that this happened?” If the answer is still “because the AI thinks the relationship is good enough,” take it one step further toward a concrete event.






