“The superintendent said they’ll fix it — so I don’t need a portal ticket” — myth

On the jobsite and after closing, Arizona new-home buyers hear a friendly shortcut: “Don’t worry — I’ll take care of it.” Or: “Tell the superintendent; you don’t need a ticket.” Or: “We already know about it — portal tickets just slow us down.” Or: “Text me photos and you’re covered.” Or: “If I said we’ll fix it, you don’t need to put it in writing.”

Those lines mix a real human workflow (supers and warranty techs often triage issues on the spot) with a false documentation map. A hallway promise can help schedule a crew. It does not freestandingly create a dated claim file, pause A.R.S. § 12-1365’s two-year new-home ROC window, rewrite Ariz. Admin. Code R4-9-108 workmanship standards, erase generally non-waivable implied warranty after Zambrano, or substitute for Purchaser Dwelling Act certified-mail notice under A.R.S. § 12-1363. Related: sales-promise warranty myth (purchase-time talk) and warranty-after-closing punch-list myth.

This guide is educational only. It is not advice for your warranty tickets, ROC filing, dwelling action, or settlement. Confirm your purchase/warranty packet, the live booklet text, statutes, and professional guidance before acting — especially before relying on an undocumented “they said they’d fix it” memory months later.

Myth: “The superintendent said they’ll fix it — so I don’t need a portal ticket.”

What’s true: Superintendents and warranty representatives often walk rooms, call trades, and schedule callbacks. Many Arizona production builders prefer (or require) warranty-portal tickets after closing so the desk can assign crews and close work orders. A verbal triage conversation can be the fastest way to get someone to look.

What’s not true: That a verbal “I’ll take care of it” freestandingly replaces the written claim process the booklet names, creates a funded holdback, tolls § 12-1365, or proves the defect was cured when personnel turn over and the hallway conversation vanishes. Related: already-fixed closes claim myth and open warranty tickets pause ROC myth.

Practical takeaway: Open the dated portal ticket the same day — even when the superintendent is helpful. Attach photos. Note the verbal conversation in the ticket notes.

Myth: “Texting the warranty rep photos means I’m covered.”

What’s true: Texts and email photos can be useful evidence. Some desks accept informal photo drops to schedule a visit. Keep those threads.

What’s not true: That a text thread freestandingly equals a booklet claim number, Purchaser Dwelling Act certified-mail notice, or an automatic pause of the two-year new-home ROC window. Ordinary portal messages and texts are still not automatic PDA notice — see PDA email / portal-notice myth.

Practical takeaway: Save the texts and open a formal ticket (or send the booklet-required written notice). Screenshot the conversation with dates.

Myth: “If they said they’d fix it, I can wait — the clock isn’t running.”

What’s true: Waiting a few days for a scheduled callback can be reasonable for non-emergency items once a ticket exists. Booklets sometimes ask owners to batch minor cosmetics after a settle-in period — that convenience tip is not Arizona’s exclusive claim map. Related: wait-60-days-before-warranty myth.

What’s not true: That a verbal promise freestandingly pauses § 12-1365 / § 32-1162’s two-year window from close of escrow or actual occupancy, whichever first, or that “they’re working on it” without a dated ticket rewrites R4-9-108. Related: must-exhaust-warranty-before-ROC myth.

Practical takeaway: Calendar ROC from close or occupancy with the warranty deadline calculator. Do not treat a hallway “we’ll get it” as tolling.

Myth: “No written ticket means I waived the defect / can’t file with the ROC.”

What’s true: Missing written tickets makes booklet enforcement harder and can leave gaps when staff change. Dated photos and portal history are how most Arizona warranty desks process claims.

What’s not true: That the absence of a portal ticket freestandingly waives R4-9-108 workmanship standards, wipes Zambrano implied warranty, substitutes for or against PDA notice, or bars the Registrar when the construction defect is otherwise documented and timely. Related: attorney-required ROC complaint myth and orientation-form waives claims myth.

Practical takeaway: Create the written record now. If you already waited on a verbal promise, open the ticket late with photos showing progression — then still calendar statutory layers separately.

What a verbal superintendent promise usually is — and isn’t

What you hear	What it usually is	What it is not
“I’ll take care of it”	Triage / scheduling talk	Automatic booklet claim or holdback
“Don’t bother with the portal”	Desk preference / informal workflow	Wipe of written-claim best practice
“Just text me photos”	Informal evidence path	PDA certified-mail notice
“We’re working on it — clock isn’t running”	Repair logistics talk	Freestanding § 12-1365 pause
“No ticket = you waived it”	Documentation gap risk	Automatic statutory waiver

Arizona already separates tracks: express booklet / portal process, helpful jobsite triage, the two-year new-home ROC window from close or occupancy, R4-9-108 workmanship standards, generally non-waivable implied warranty after Zambrano (2022), and Purchaser Dwelling Act civil notice-and-repair. Collapsing that stack into “the superintendent said they’d fix it, so writing it down is optional — or impossible later” is the myth.

What to do instead of relying on a hallway promise

1. Open a dated warranty-portal ticket the same day — leaks, safety hazards, progressive cracks, drainage ponding, and HVAC failure first.
2. Photograph and date every condition — same angles over time beat a memory of “they said they’d fix it.”
3. Note the verbal conversation in writing — who said what, when, and what they promised to schedule.
4. Keep texts and emails — but do not treat them as PDA certified-mail notice.
5. Do not treat “we’re working on it” as § 12-1365 tolling — calendar close or occupancy with the warranty deadline calculator.
6. After a visit, confirm the written status — “fixed” talk without a ticket trail is how recurring defects get dismissed later; see already-fixed closes claim myth.
7. Match the legal GC and ROC number on your packet via the builders directory and the ROC contractor search.
8. Use the apps and tools — documentation checklist, myth checker, and AZ HomeShield iOS / Android records — so a hallway conversation is never the only clock you keep.

Bottom line

A helpful superintendent or warranty rep can triage defects quickly — and many Arizona booklets still expect written portal tickets. A verbal “we’ll fix it” is not Arizona’s freestanding rule that written claims are optional, that ROC / R4-9-108 / implied-warranty / PDA layers are paused, or that undocumented hallway talk later becomes a nuclear waiver. Write it down. Photograph it. Calendar ROC from close or occupancy.

Primary sources

• Ariz. Admin. Code § R4-9-108 — workmanship standards
• A.R.S. § 12-1365 — new-home ROC complaint notice / two-year window
• A.R.S. § 32-1162 — ROC complaint timing
• A.R.S. § 12-1363 — Purchaser Dwelling Act notice and repair
• Arizona ROC — File a Formal Complaint
• Zambrano v. M & RC II LLC — residential implied warranty generally not waivable
• Typical production-builder warranty portal / written-claim procedures (contractual — not Arizona’s exclusive claim map)
• AZ HomeShield — sales-promise warranty myth, warranty-after-closing punch-list myth, PDA email / portal-notice myth