Frequently Asked Questions (FAQs) web page should be used very rarely.

Plainlanguage.gov guidelines

• f you write clear web content that is easy to navigate and answers your readers questions, you will not need to create a FAQ.
• Frequently Asked Questions (FAQs) can be overwhelming and leave your customers searching through a sea of content.
• Often your best solution is a clear, well-organized main content page explaining a process.
• Use real customer feedback. Do not assume what kinds of questions people will have. Monitor customer calls and emails to create helpful FAQs.Use language that non-experts will understand. Use plain language when drafting FAQs. Do not burden your reader with insider jargon or undefined acronyms.

Read the plainlanguage.gov article

City guidelines

• Rather than using a common questions web page, publish content on a web page as informational statements. 
• If you are receiving questions repeatedly, make your existing web content more clear and add any missing information.
• Never use a common questions web page as the only source of the information. It should be presented on a web page first.

What to include a page

• The page header should be Common questions.
• Include frequently asked questions in the summary sentence.
• Put the FAQs in an accessible PDF.
• Use a document gateway page.