Chatting with AI in the GovEagle platform is simply having a focused, back and forth conversation to get work done. You ask questions, give direction, and refine the output. The clearer and more specific you are about what you want, the better the results will be. AI works best when you treat is as a collaborator, not a search tool. Describe the outcome you want, iterate until the response is proposal ready/results you want and provide context.
Here are three golden rules that will help you get the best results when chatting with GovEagle.
Describe The Outcome You Want - Be specific
Vague prompts can lead to generic responses that miss the mark. AI responses will be improved when you can communicate what you need and expect in response. The more specific you are about sections, requirements, and desired outcomes, the more targeted and useful GovEagle's response will be.
❌ Instead of:
“Add examples”
✅ Try this:
“Find our past performance experience with the Navy and show how it meets the task area requirement for Subfactor A”
Iterate
The first response is just the beginning. If GovEagle's initial output doesn't match your expectations, you can respond with additional instructions. When drafting content, use follow-up prompts to change length, adjust tone, add details, reorganize content, or incorporate additional requirements.
✅ Try this:
“Shorten your last draft to two paragraphs while keeping the main points”
Provide Context
Guide GovEagle to the most relevant information by directing it to specific documents and references. By default, GovEagle has access to the solicitation documents that were used to create the opportunity you are chatting about (unless you have no opportunity selected). With each message, you can provide additional context to GovEagle by referencing or uploading content.
See also: Adding context and references to chat, Win Strategies
❌ Instead of:
“Write a management approach”
✅ Try this:
“Write a management approach based on our project management procedures in the 'Corporate Capabilities' folder and our org chart from this 'Team Structure' document that I am attaching”