A review routine before your next prompt.

1. Start with what you want to learn

Before uploading, write the task in one sentence. “Compare timelines across three proposals” is clearer than “analyze everything”. This gives you a reference for recognizing directions that try to change the objective.

Group files by purpose. A contract, résumé and manual may contain legitimate instructions for different readers. Knowing where each item came from helps you assess a suspicious sentence without losing context.

2. Analyze in batches, review each document

Doc Guard accepts multiple files in one batch, within batch limits and your plan allowance. Results remain separate. A document with no signals does not resolve alerts found in another.

In each report, read the file name, analysis status and coverage before reviewing the signals. If processing was interrupted or reading was partial, consider what was left out before sending the material to AI.

• Confirm the report matches the file you intend to use.
• Read the highlighted excerpt and its source information.
• Compare the detected instruction with the task criteria.
• Decide whether you need a new version, clarification or further review.

3. Stay in control of actions

OWASP recommends separating external content from instructions, limiting permissions and requiring human approval for sensitive operations. These measures complement inspection: finding a suspicious excerpt and preventing an unauthorized action are different responsibilities.

For example, a workflow that only compares proposals does not need to authorize payments or send files to new recipients. Define those decisions outside the received content, according to your team's rules.

4. Record what was reviewed

Doc Guard's history lets you revisit signals and excerpts by file name without storing the complete document. Use this evidence alongside your team's version control, especially when a new copy arrives after a correction.

Instruction detection also does not verify whether a document's facts are true or whether it meets your process requirements. Microsoft makes this distinction in its documentation on document attacks. Keep content review and the final decision as separate steps.