A housing team needs a resident-facing lease-addendum explanation based on the current policy Word file. What should they ask Copilot to do?
Select an answer to reveal the explanation.
Short Explanation
Policy is the source of truth—ask Copilot for a lease-addendum explanation grounded in the current Word policy. Don’t invent rent rules the file doesn’t support.
Full Explanation
Housing policy communications must track the adopted Word policy file, not social chatter or invented rent rules. When the team needs a resident-facing lease-addendum explanation, they should ask Copilot to generate a revised explanation document from the current policy Word file so eligibility, timelines, and obligations remain authorized. That is grounded document drafting for resident literacy while preserving the policy as source of truth for AB-730-style municipal content work.
Pasting full tenant Social Security numbers into the prompt for personalization fails privacy and identity-theft safeguards; SSNs are never needed to explain an addendum. Rewriting the policy so residents are told rent caps the policy does not authorize fails legal accuracy and can create false expectations or fair-housing risk. Ignoring the policy Word file and inventing addendum rules from social media comments abandons the authoritative municipal source.
Exam caveat: stems that cite a current policy Word file point to generate-from-that-file. Prefer grounded resident explanation over PII injection, unauthorized rent promises, or social-media invention.
Operational check: attach the current policy Word file, prompt for a plain-language lease-addendum explanation limited to rules present in that file, omit all SSNs and case identifiers, have housing counsel or program leads verify rent and eligibility language, then publish with a policy effective-date citation.