Responsible Use of AI Chat Tools
A practical staff guide for the Warnell School of Forestry and Natural Resources
Purpose
Use AI chat tools to improve the quality and speed of appropriate work while protecting people, university information, academic integrity, and professional judgment.
This guide is a practical companion to UGA policy and guidance. It does not replace university policy, a supervisor’s direction, course rules, sponsor requirements, research protocols, or professional standards. When they differ, the controlling requirement takes priority.
Start here
- Keep a person responsible for every decision and every final product.
- Do not enter sensitive or restricted UGA data unless the tool and use have been specifically approved.
- Use AI to assist thinking and production, then check the result against reliable sources.
- Choose the least resource intensive model and reasoning level that can do the task well.
- Stop, summarize, and begin a fresh chat when the conversation becomes long, confused, or shifts to a new purpose.
A five question check before you begin
| Question |
If the answer is no or unclear |
| Is this use allowed by UGA, my unit, the course, sponsor, publisher, or project? |
Pause and check the controlling rule. |
| Can I complete the task without sensitive, restricted, confidential, or personally identifiable information? |
Remove the data or obtain proper authorization and use an approved tool. |
| Will a qualified person review the output? |
Do not use AI for the task. |
| Can I verify important claims with reliable sources? |
Treat the output as ideas only, not as fact. |
| Will AI support rather than replace accountable human work? |
Redesign the task so a person remains responsible. |
How an AI chat session works
A large language model, or LLM, produces a response by predicting useful sequences of words from patterns learned during training and from the material available in the current chat. It does not understand a subject in the same way a person does, and a confident answer can still be incomplete, biased, outdated, or wrong.
| Part of the session |
What it means for you |
| Your prompt |
The instructions, background, source material, examples, and requested format you provide. |
| Conversation context |
The recent chat history the tool uses to interpret your next request. Long chats can accumulate irrelevant or conflicting details. |
| Model |
The engine selected for the work. Models differ in capability, speed, cost, tools, and how much reasoning they can apply. |
| Response |
A generated draft or analysis. It is not automatically a verified fact, official decision, or final work product. |
| Human review |
The person checks facts, sources, tone, policy, accessibility, fairness, and fitness for the actual purpose. |
A useful mental model
Treat the chat as a capable but fallible assistant working from your instructions and the information it can access. Give it a clear assignment, inspect its work, and keep final responsibility with a person.
Why a chat can drift
Each follow-up adds material to the session. The tool may give too much weight to an earlier instruction, mix two projects, repeat an error, or lose important details as the conversation grows. A new chat with a clean summary often produces a more focused result.
What the tool may not know
- Current facts unless the tool has access to reliable, up-to-date sources.
- Local Warnell procedures or the intent behind a decision unless you explain them.
- Whether material is confidential, copyrighted, restricted by a sponsor, or covered by a course rule.
- Whether a citation, quotation, calculation, species identification, regulation, or policy statement is accurate.
University rules come first
UGA guidance makes users responsible for the integrity and accuracy of their work. It also states that permission to access UGA data is not, by itself, permission to place that data in an AI tool. If AI informs a decision, explain how it was used; do not allow AI to make automated university decisions. UGA guidance also calls for disclosure when AI helps create public-facing content.
Sensitive and restricted data
Do not paste student records, personnel information, protected research data, health or financial details, confidential peer review material, export-controlled information, passwords, or other sensitive or restricted information into an AI chat tool unless UGA has expressly authorized the tool and the specific use. Removing names may not make a dataset safe.
Use AI as a force multiplier
AI is most useful when it expands a staff member’s capacity to explore, organize, draft, compare, or check work while the staff member supplies the purpose, subject knowledge, judgment, and accountability. Start with a small, reversible task and compare the result with your normal process.
| Good uses for assistance |
Uses that require caution or a different approach |
| Brainstorm questions, outlines, examples, or alternative explanations |
Make employment, admissions, grading, disciplinary, funding, safety, or other consequential decisions |
| Turn public source material into a first draft, checklist, agenda, or plain-language summary |
Process sensitive or restricted information in an unapproved tool |
| Improve clarity, grammar, organization, accessibility, or tone in text you own |
Replace direct engagement with student work, employee performance, research evidence, or stakeholder needs |
| Compare options using criteria chosen by a person |
Invent facts, citations, quotations, data, policies, or field observations |
| Create routine templates, formulas, or workflows for a person to test |
Publish or send output without review, attribution when required, and source checking |
| Identify possible gaps or questions for expert review |
Present AI output as expert, legal, medical, safety, or scientific advice |
The task test
A task is a better candidate when it is low risk, easy to check, reversible, and based on information you are permitted to use. The need for human review rises with the consequences of an error.
| Risk level |
Examples |
Expected review |
| Lower |
Ideas for a meeting agenda; rewriting public text; formatting a checklist |
Read the full output and correct it before use. |
| Moderate |
Summarizing public research; drafting guidance; comparing vendors from approved information |
Verify claims and sources; obtain subject matter review. |
| High |
Personnel, student, safety, compliance, research integrity, legal, financial, or reputational matters |
Use only within approved processes. AI must not be the sole basis for a decision; consult the responsible office or expert. |
A simple pilot approach
- Choose one repetitive or time-consuming task with low consequences if the first draft is imperfect.
- Record the current time, quality requirements, and review steps.
- Try the task with non-sensitive information and a clear prompt.
- Measure time saved after checking and correcting the output.
- Keep the approach only if quality, accessibility, and accountability are maintained or improved.
Create prompts that produce useful work
Good prompting is clear assignment design. The goal is not a magic phrase. Give the tool enough context to understand the work, define the result, and know how its work will be checked.
The CARE prompt pattern
| Element |
What to include |
Example |
| Context |
Audience, purpose, setting, and relevant background |
This is for county extension partners who know forestry but may not know our internal process. |
| Assignment |
The exact task and boundaries |
Draft a one-page checklist from the approved policy text below. Do not add requirements. |
| Requirements |
Format, length, tone, sources, exclusions, and success criteria |
Use plain language, six to eight steps, and cite the policy section after each step. |
| Evaluation |
How to handle uncertainty and how the result will be checked |
Flag any ambiguity. List claims that need a human or source check. |
Reusable prompt template
Copy and adapt
Context: I am [role] preparing [work product] for [audience and purpose].
Assignment: Help me [specific task]. Use only [supplied material or named sources].
Requirements: Produce [format and length] in [tone or reading level]. Include [must-have items]. Do not [important boundary].
Evaluation: If information is missing or uncertain, say so. Do not invent facts, quotations, or citations. At the end, list what I should verify before use.
Weak and improved prompts
| Weak prompt |
Improved prompt |
| Write an email about the meeting. |
Draft a 150-word email to Warnell staff confirming the October 12 safety meeting. Use a direct, courteous tone. Include the time, location, preparation needed, and a request to reply with accessibility needs. Use only the details below. |
| Summarize this report. |
Summarize the attached public report for an audience of education professionals. Use five bullets: purpose, methods, two key findings, limitations, and implications for our work. Preserve numbers and uncertainty. Cite page numbers. |
| Make this better. |
Revise this draft for clarity and plain language without changing its meaning. Keep all dates, requirements, and qualifications. Show a clean revision followed by a short list of substantive changes. |
Improve the session in small steps
- Ask for an outline or questions before requesting a full draft.
- Provide one good example when format or tone matters.
- Correct errors explicitly and restate the controlling instruction.
- Ask the tool to separate facts from suggestions and identify assumptions.
- For important work, request a verification checklist rather than accepting a confident answer.
Choose the model and reasoning level
Model names and limits change. Use the categories shown in your approved tool rather than relying on a particular product name. Start with the least intensive option that reliably meets the task. Move up when the work is genuinely complex or the smaller option fails a clear quality check.
| Work type |
Suggested starting point |
Examples |
| Routine and well defined |
Smaller or faster model with low reasoning |
Rewrite text, extract fields, classify items, create a simple agenda, format a list |
| Professional drafting and comparison |
Balanced general model with medium reasoning |
Draft guidance, compare options, synthesize several public sources, plan a workflow |
| Complex and high consequence |
Most capable approved model with high reasoning plus stronger human review |
Analyze competing requirements, inspect a difficult research method, plan a multi-step project, review a complex risk |
| Specialized media or tools |
Approved model built for the needed input or action |
Analyze images, work with a spreadsheet, search current sources, or transcribe audio |
Use a lower level to prepare higher level work
A smaller model can help define the problem before an expensive or limited model performs the hard analysis. This works best when the preparation itself is easy to review.
- Ask a smaller model to turn your notes into a structured brief with goals, constraints, known facts, unknowns, and desired output.
- Review and correct that brief yourself.
- Give the corrected brief and source material to the stronger model for analysis or drafting.
- Use the smaller model again for low-risk formatting only after the substantive work is approved.
Do not confuse effort with accuracy
A stronger model or higher reasoning setting may improve difficult work, but it does not make the answer automatically true. Clear instructions, reliable source material, and qualified review still matter.
When to move up or down
| Move up when |
Move down when |
| The task requires several dependent steps or reconciliation of competing requirements. |
The work is repetitive, tightly specified, and easy to check. |
| The model misses important constraints after one clear retry. |
You only need extraction, formatting, classification, or a simple rewrite. |
| The work requires nuanced synthesis of several reliable sources. |
Speed, cost, or usage limits matter more than marginal polish. |
| An error would require substantial rework and the stronger model remains approved for the data. |
A tested template or workflow already defines the correct result. |
Maintain usage thresholds
Usage limits vary by tool, license, model, and time. A practical threshold is a team rule for when to continue, simplify, switch models, start a new chat, or stop. The aim is to protect capacity for work that benefits from it and to avoid spending more time prompting than the task is worth.
A practical threshold plan
| Threshold |
Team practice |
| Before starting |
Estimate the value, risk, data classification, and review effort. Do not use AI when a normal template or quick human action is faster. |
| After two weak attempts |
Stop rewriting the same vague prompt. Clarify the goal, provide an example or source, change the workflow, or complete the task directly. |
| After several exchanges |
Ask for a concise session summary. Start a fresh chat if the topic has shifted or instructions have accumulated. |
| When using a premium model |
Reserve it for complex work. Use a smaller model for planning, cleanup, extraction, or formatting when quality is sufficient. |
| When limits approach |
Save the approved summary and source list, switch to a lower level for routine work, and defer non-urgent experiments. |
| At completion |
Record the reusable prompt or workflow, delete unnecessary copies of data, and close the session rather than continuing unrelated work. |
Measure value by completed work
Count the full effort: preparing material, prompting, waiting, checking, correcting, documenting, and obtaining review. A fast draft that requires extensive repair may not save time. Teams can track a small sample of tasks using the worksheet below.
| Task |
Without AI |
With AI including review |
Quality or risk notes |
Keep change or stop |
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
Suggested team habits
- Set a monthly or project-level budget where the tool provides usage reporting.
- Agree which tasks justify premium models and which should use standard tools.
- Share tested prompts and approved workflows so staff do not repeatedly solve the same setup problem.
- Review failed or costly uses without blame and improve the process.
- Do not evade vendor or university limits by creating extra accounts or moving work to unapproved tools.
Keep sessions focused and manageable
Begin a new chat when you change projects, audiences, data sensitivity, or goals. For a continuing project, carry forward a short, checked summary rather than the entire transcript. This reduces clutter and gives you a chance to remove mistakes and information that no longer matters.
When to summarize and restart
- The chat has moved through several drafts or more than one work product.
- The model repeats an error or seems to follow an old instruction.
- You must scroll extensively to find the current goal or approved facts.
- The task changes from brainstorming to final production or from one audience to another.
- You are about to use a stronger model and want to provide a clean brief.
- The session includes information that should not be carried into the next phase.
Prompt for a handoff summary
Copy and adapt
Create a concise handoff summary for a new chat. Include only:
1. The current goal and intended audience
2. Decisions I approved
3. Verified facts and their sources
4. Requirements and constraints
5. Unresolved questions or risks
6. The exact next task
Exclude abandoned ideas, repetition, and any sensitive information. Do not add new facts. Mark anything uncertain.
Check the summary before reuse
- ☐ Correct errors and remove outdated instructions.
- ☐ Remove sensitive, restricted, personal, or unnecessary information.
- ☐ Confirm that links, citations, dates, and numeric values match the sources.
- ☐ State who will review and approve the next output.
- ☐ Paste the checked summary into a new chat and attach only the source material needed for the next step.
Separate work by purpose
| Use one session for |
Start a separate session for |
| A single deliverable with one audience and stable source material |
A different deliverable, audience, policy context, or data classification |
| Related revisions where the same instructions still apply |
Exploratory brainstorming that should not influence final production |
| A defined phase such as outlining or source comparison |
Final drafting after the facts and requirements have been approved |
Review every AI assisted product
The staff member using the output remains responsible for it. Review should match the risk of the work. Important material needs source checking and, when appropriate, subject matter, policy, accessibility, communications, legal, privacy, safety, or research review.
Final review checklist
- ☐ Accuracy: I checked important claims, calculations, quotations, citations, names, dates, and links against reliable sources.
- ☐ Completeness: I confirmed that the output addresses the actual assignment and preserves required qualifications.
- ☐ Data protection: I did not expose information that the tool or use was not approved to handle.
- ☐ Human judgment: A qualified person made the decision and reviewed the final content.
- ☐ Fairness: I considered whether the output could disadvantage a group or reflect unsupported assumptions.
- ☐ Academic and research integrity: The use follows course, sponsor, publisher, authorship, and research requirements.
- ☐ Copyright and attribution: I checked ownership, permissions, quotations, and required citations or disclosure.
- ☐ Accessibility: The final product is usable by people with disabilities and does not replace approved accommodations.
- ☐ Transparency: I disclosed material AI use when required by UGA, the work context, or the intended audience.
- ☐ Records: I kept the prompt, sources, revisions, and approvals when the work requires documentation or reproducibility.
Common failure modes
| Failure |
Response |
| A plausible but false fact or citation |
Open the original source. If it cannot be verified, remove it. |
| A summary that changes the meaning |
Compare sentence by sentence with the source, especially numbers, exceptions, and uncertainty. |
| Biased or stereotyped language |
Identify the assumption, revise the criteria, seek relevant perspectives, and use human review. |
| Overly generic output |
Add audience, local context, a good example, clear constraints, and source material. |
| A long session that contradicts itself |
Create a checked handoff summary and restart. |
| A polished answer that exceeds policy |
Stop. Follow the controlling UGA, unit, course, sponsor, or legal requirement. |
Disclosure example
Adapt disclosure to the work and its governing rules. A simple statement may read: “AI was used to develop an initial outline and improve clarity. The author verified the facts, revised the content, and accepts responsibility for the final version.” This example is not a substitute for a required citation or disclosure format.
Quick reference for staff
| Before |
During |
Before sharing |
| Confirm the use is allowed.Classify the data.Choose the least intensive suitable model.Define the human reviewer. |
Use a clear CARE prompt.Provide approved sources.Keep one purpose per chat.Challenge assumptions and ask what needs verification. |
Check facts and sources.Review for privacy, fairness, copyright, accessibility, and policy.Revise in your own professional judgment.Disclose and document when required. |
Decision card
| Green light |
Yellow light |
Red light |
| Low-risk, reversible, easy to verify, approved information, human review planned |
Moderate consequences, unclear ownership or rules, unfamiliar tool, difficult verification |
Sensitive or restricted data in an unapproved tool, automated consequential decision, prohibited academic or research use, no qualified reviewer |
Supervisor discussion guide
- What outcome are we trying to improve?
- What information will the tool receive, and how is that information classified?
- Which UGA-approved tool and account should we use?
- What work must remain with a person?
- How will we verify quality and measure time saved?
- What disclosure, documentation, or approval is required?
- When will we stop, reassess, or retire the workflow?
Sources and continuing guidance
UGA AI Policy and Guidance hub - Current links to UGA AI policy, acceptable use guidance, research guidance, and data protection standards.
UGA Guidance on Acceptable Use of AI - University guidance on data, privacy, transparency, acceptable uses, and accountability. Revised August 2026.
UGA Considerations for Using AI in Research - Research responsibilities, data and intellectual property, verification, disclosure, and discretion.
UGA Teach with AI - Teaching guidance, supported tools, course expectations, assessment, accessibility, and faculty responsibility.
OpenAI Model Guidance - Current product documentation on model capabilities, prompting, and reasoning effort. Product names and settings change; consult the tool you are authorized to use.
Keep this guide current
AI products, UGA policies, supported tools, and license limits change. Check the UGA AI Policy and Guidance hub before adopting a new workflow or using a new category of information.
Questions or suggestions?
Share your feedback by posting a response to this article or emailing
warnelltech@uga.edu.