Tips for better results

The AI assistants work best when you're clear about what you want. These tips apply to both the chat and email assistants.

How to write better prompts

Be specific

Vague questions get vague answers. The more details you provide, the better the response.

Use clear, measurable language

Avoid vague terms the AI might interpret differently than you intended.

Say what you want, not what you don't want

Positive instructions are clearer than negative ones.

Be direct

Skip polite phrases—you don't need to say "please" or "thank you" to the AI. Just tell it what you need.

Ask for a specific format

If you want a list, table, or bullet points, say so.

• "List the requirements as bullet points"

• "Summarize in a table with columns for requirement and code section"

• "Give me a numbered checklist"

Break complex requests into steps

For complicated questions, split them up. One clear question gets better results than three questions jammed together.

Instead of: "What's the zoning, setbacks, and height limit for this property, and what permits would I need for a 500 sq ft addition, and are there any critical areas?"

Try asking one at a time, or say: "Answer these questions separately: 1) What's the zoning? 2) What are the setbacks? 3) Are there critical areas?"

Give examples

If you want a specific style or format, show it.

• "Write it like this: 'Thank you for your inquiry. Based on the property at [address], the setback requirement is...'"

• "Format the answer like: Requirement: [value] Code section: [reference]"

Put important context first

Lead with the key details. If there's an address, property type, or specific code section that matters, mention it upfront rather than burying it at the end.

Chat assistant tips

Use the project context sidebar

For property-specific questions, always enter the address in the project context sidebar on the right—don't just mention it in your message. The sidebar pulls GIS data from your jurisdiction's mapping system (zoning, critical areas, setbacks, lot coverage) and feeds it directly into the AI's context.

This matters because:

• The AI gets structured property data, not just an address string

• You can see the GIS information yourself and verify it's the right parcel

• Every question in that chat session uses the same property context

To use it: type the address in the project context area, confirm the map shows the correct property, then ask your question.

Check the citations

Every answer includes source citations. Use them to verify the information is current, dig deeper into the code section, or share the source with applicants.

Start fresh when needed

If the conversation gets confusing or you're switching topics, start a new chat. Each conversation has its own context.

When an answer seems wrong

Often a wrong answer means the question was missing context. Try adding a follow-up question, check that the project context sidebar has the right address, or rephrase with more specifics. Check the citations to see if it pulled from the right source. If it's still off, use the feedback button.

Email assistant tips

Use the style options (Outlook plugin)

Click the style options before generating to quickly set the tone:

• Friendly vs Formal - Casual or professional tone

• Simple vs Technical - Plain language or industry terminology

• Concise vs Detailed - Brief response or comprehensive explanation

• Request Info - When you need more details from the sender

Add custom instructions

Shape the response with instructions like:

• Scope: "Only answer the zoning question" or "Skip the fees question—I'll handle that separately"

• Audience: "The applicant is a contractor who knows the process" or "This person is new to permitting"

• Specifics: "Include the code section number" or "Mention they need to schedule an inspection"

Regenerate with refinements

Not happy with the draft? Add new instructions and click Generate again. Each regeneration keeps your previous instructions, so you can layer refinements: "More casual" → "Shorter" → "Add the deadline."

Edit freely

You don't have to use the draft verbatim. Copy it, take the pieces you like, rewrite the rest. The goal is to save time, not replace your judgment.

What the AI is good at

Think of it as a research assistant that reads the code faster than you can. It's great for:

• Finding specific requirements ("What's the minimum lot size in R-7.5?")

• Exploring scenarios ("Can this property add an ADU given the existing lot coverage?")

• Pulling together information scattered across multiple code sections

• Drafting responses that you then review and refine

What the AI is not for

• Making final determinations (that's your job)

• Replacing professional judgment on complex cases

• Providing legal advice

• Accessing information outside the knowledge base

Always verify important information—and use the feedback button when something's off.