The prompt
Score 10 of 10, Excellent
Use it when A policy is accurate but hard to read, and you want an FAQ employees can follow, with every answer traceable to the policy text.
- {{policy_text}}
- {{common_questions}}
- {{audience}}
- {{contact}}
- {{owner}}
Full prompt and why it works
Prompt
<policy> {{policy_text}} </policy> <common_questions> {{common_questions}} </common_questions> <constraints> - Answer only from the policy above. Do not add rules, numbers, eligibility conditions or exceptions that it does not state, because employees will treat the FAQ as the policy. - After each answer, cite the section or heading of the policy it comes from, in brackets. - Keep every condition and exception in the policy, even awkward ones. Plain language must not change the meaning. - Write for the employees it covers ({{audience}}), in the second person, at about a US grade 8 reading level. Spell out acronyms the first time. - Do not give legal advice or explain how the law applies to someone's situation. Where a question depends on local law or personal circumstances, say who to ask: {{contact}}. </constraints> <format> Markdown: - A two-sentence summary of what the policy covers and who it applies to. - 10 to 15 questions as level-3 headings, phrased the way an employee would ask them, for example "Can I carry unused days into next year?", each with an answer of up to 80 words. - Start with the questions listed in common questions, then add the ones the policy text makes most likely. </format> <task> Using the policy above, write an FAQ for employees. It is a draft for {{owner}} to check against the policy before it is published. Each answer should be complete enough that the employee does not need to open the policy for that question. If the policy does not answer a common question, or the answer is unclear, do not guess: list it under a final heading "Not answered by the policy" so the policy owner can decide. </task>
Variables
- {{policy_text}}
- The policy, pasted in full, with its section numbers or headings.
- {{common_questions}}
- Questions employees already ask about this policy, one per line. Write "none" if you have none.
- {{audience}}
- Who the policy applies to, for example "all US hourly staff".
- {{contact}}
- Who employees should ask, for example "your HR business partner".
- {{owner}}
- Who checks the FAQ before it goes out, for example "the HR policy owner".
Why it works
- What to avoid. Answers come only from the policy and cite its section, so anyone can check an answer against the text.
- If unsure. Questions the policy does not settle are listed for the policy owner instead of being answered with a plausible guess.
- Layout. The policy comes first, then constraints and format in tags, with the task last, as Google's guidance for Gemini suggests.