# Strategy Guide — Scenario 62: "The Visit Notes"

*Game documentation for a fictional simulation in "The First 90 Days" (Tactic Watch). The family, the case, and every choice below are fictional. This guide is general information about how the scenario is built — it is not legal advice for any real case.*

## (1) The win

**Best ending: "Ending — The Note, Answered."**

State it honestly: this is a **partial** win, and it is the best this scenario offers. Both harmful entries in the visit notes — the bruise line and the word "flat," promoted by quotation into a "possible impairment concern" — are answered on the record, and Felicia's same-day notes sit in the file beside them, so no future reader can quote the entries without meeting their answers. Ezra does **not** come home at the end of this ending. He remains placed, visits remain supervised, and the case continues. The win is that the case's memory — the document every later decision will be read from — has been corrected while correction was still possible. There is no ending in this scenario where the review itself reunifies the family. Anyone selling you one is selling you a different game.

## (2) The route

Verified by walking the scenario graph from the start node (see the verification note at the end). Key decision points, in order — node title, winning choice, and what it changes:

1. **The Visit Routine** — the premise: Ms. Goss's notebook is the case's memory, and reviews will be written from it. Everything below is a response to that one fact.
2. **The Word ‘Flat’** — *Tell Ms. Goss plainly, before the visit starts: "I worked a double. I'm tired — I'm not checked out."* Hidden item: the supervisor was told, in the room, about the double shift. Said where the notebook is, the context at least has a chance of travelling with the word.
3. **That Night, at the Kitchen Table** — *Buy the notebook and write today's visit down tonight.* Cash −4. Sets **ownNotes** — the scenario's foundational flag; hidden item: same-day notes begun the night of the "flat" visit. Contemporaneous paper is the only kind a later correction can be built from without apology.
4. **Three Pages, Dated** — the habit forms: date, times, what was said, the shift. From tonight the case has two memories, and one of them is being written the same day things happen.
5. **A Good Visit, in Full** — the visits continue; the good ones go into the file in the same flat voice as everything else, which is why the exceptions matter so much.
6. **The Climbing Frame** — Ezra falls from low on the frame; Felicia reports it immediately and comforts him (a scraped arm; a sleeve held). This is fixed story, not a choice — the choice the scenario tests is what happens to the *account* of it.
7. **The Note, As Read to You** — Mr. Henley reads the note's line aloud: "Bruise observed on child's arm; mother offered no explanation initially." The lived version and the written version part company here.
8. **The Weeks Between** — summaries begin drafting themselves from the notes, quoted and slightly re-pointed at each stop.
9. **Quoted, Upgraded** — *"Flat" has become a "possible impairment concern."* This is the scenario's engine in one beat: an unanswered word, promoted by quotation.
10. **What Paper Answers a Word** — *Sign the written request for the record — visit notes, all of them.* Cash −5. Sets **recordsRequested**. Counsel's right and the release rule are stated here (42 Pa.C.S. § 6337; 55 Pa. Code § 3130.44(d)); the request, exercised in writing, is what turns an argument about a page into a reading of it.
11. **The Stamp** — the request goes in dated, with a copy kept. Weeks of ordinary waiting follow, on paper.
12. **Black Lines** — the notes arrive partly redacted: the supervisor's observations blacked out as "staff privacy." Even blacked, this is the first document Felicia and its readers hold in common.
13. **The Answer to Black Lines** — *Send the short written response on the redactions, citing the provision.* Sets **redactionAnswered**; hidden item: response in writing under 55 Pa. Code § 3130.44(f). One page; it cites rather than shouts.
14. **What the File Actually Holds** — read whole, the file answers itself in part: the bruise note's *second page* records Felicia's explanation in detail (the summary quoted only the first sentence), and one attended visit is marked missed — the error only a dated notebook page can correct cleanly.
15. **Answer in Writing, or Out Loud** — *File the written response, with your same-day notes attached.* Cash −6. Sets **correctionFiled**. From today, anyone quoting an entry from the file finds its answer in the same folder, at the same stop.
16. **Filed, Beside Them** — the correction lands: the fall in sequence, "flat" with its double shift re-attached, the wrong date corrected.
17. **The Packet, in Date Order** and **The Report on the Table** — the review report repeats both entries as mutual support, which is exactly the structure the filed packet exists to break.
18. **The Review** — *Open with the filed correction — your same-day notes attached, the redactions answered, both entries met on the record.* This choice is flag-gated: it is only available with **ownNotes** + **recordsRequested** + **correctionFiled** + **redactionAnswered** all set. It leads to **Ending — The Note, Answered**.

## (3) Why this wins — the law as it is supposed to work

Only principles from the scenario's verified set are stated here:

- **Agency records are obtainable on request** — 55 Pa. Code § 3130.44(d) ("shall be released upon request"). Steps 10–14 are that right, exercised in writing: the visit notes, read whole, contained both the problem (the bruise line, the wrong date) and half its answer (the explanation recorded on the note's own second page, which no summary had quoted).
- **The release rule is not to be read to protect agency employees' privacy** — 55 Pa. Code § 3130.44(f), used exactly as far as v1 used it and no further: as the answer to over-redaction. A supervisor's observations of a visit are the agency's work about the family, and the written response at step 13 is what gets them released.
- **Counsel assembles, attaches, and files** (42 Pa.C.S. § 6337) — the correction is a filing, not a speech, because filings travel with the entries they answer and speeches travel only as far as the next summary carries them.
- **A framing note, kept record-dependent as Scenario 14 teaches:** corrected, contemporaneous records are the raw material every later stage of a case runs on — including, at the permanency end of a case, the federal timeline under which a child in care for 15 of the most recent 22 months changes the agency's filing duty unless an exception is documented (42 U.S.C. § 675(5)(E)). This scenario states no placement date and computes no such date; it makes the narrower point that *if* a record is ever argued over, the argument is won or lost on paper like this — entries, answers, and dates — assembled while assembly was still possible.

## (4) The traps

1. **Trusting your memory at "That Night, at the Kitchen Table."** Cost: no **ownNotes**. The correction can still be filed, but it is built from recollection — so at **The Review** the best available lead is the filed correction alone, and the outcome is **Ending — Two Versions, One File**: your version exists, late and contested, beside theirs. The missed-visit date, in particular, becomes your word against the file's.
2. **Deferring the record request at "What Paper Answers a Word."** Cost: no **recordsRequested**, no packet, no second page. You never learn that the note itself recorded your explanation — the single most useful sentence in the file — and the correction is built from a summary of a summary. Two Versions is the ceiling; the win's gate closes here.
3. **Accepting the black lines at "The Answer to Black Lines."** Cost: no **redactionAnswered**. The supervisor's observations reach the review unexamined, and the win's gate closes — the filed correction, presented alone, reaches the middle ending.
4. **Answering orally at "Answer in Writing, or Out Loud."** Cost: no **correctionFiled**. A sincere, well-rehearsed answer whose survival is decided by the next summary — the same process that promoted "flat." It reaches **Ending — Two Versions, One File** on the strength of being partly carried into the review's own summary.
5. **Letting the report stand at "The Review."** Cost: everything. Unanswered, the two entries hold each other up and harden into findings: **Ending — Flat, As Recorded**.

## (5) What no strategy controls

Whether the supervisor writes the fall note whole the first time (on a fuller day, with a smaller caseload, she might have — and none of this would have been necessary). Whether the reviewer keeps concern language even against a complete packet; some do. Mr. Henley's habits, the report writer's quoting hand, and plain luck all hold pieces of every ending here. The route above controls none of that. It controls only whether, when the uncontrollable happens, the file contains an answer with a date on it. Outcomes in this system turn on workers, reviewers, and luck as much as on any parent's choices — the strategy's whole claim is narrower: the parts that *were* yours — a notebook started the same night, a request signed, a letter citing the right provision, a correction filed — were done in writing, in time, beside the entries they answer.

---
*Verification: this route was walked programmatically against `scenario-62.json` — each named choice was followed from the start node in order; every intermediate node and choice exists; every flag-gated choice's requirements were satisfied by flags set earlier on the walk; the walk terminates at the ending node titled "Ending — The Note, Answered" after visiting 20 nodes, with $95 of the $110 starting cash remaining. Walked path: start -> flat_visit -> that_night -> notebook_started -> good_visit -> fall_visit -> fall_aftermath -> weeks_pass -> quote_upgrade -> lawyer_beat -> request_sent -> packet_redacted -> f_beat -> read_file -> correction_beat -> correction_filed_node -> review_prep -> review_notice -> review -> end_answered.*