How to Give Vesence Good Instructions

Vesence works best when your instruction gives enough context, a clear goal, and the source material Vesence should use.

You do not need to write technical prompts. A good instruction can be simple. The key is to tell Vesence what you want done, what material to use, what kind of output you expect, and what Vesence should treat carefully.

Start with the goal

Tell Vesence what you want to achieve.

Good examples:

• "Summarize this agreement for a non-lawyer."
• "Check this document for undefined terms and broken references."
• "Compare the agreement against the term sheet."
• "Draft a short reply based on this email thread."
• "Create a table of open issues from these documents."

Less helpful examples:

• "Look at this."
• "Fix it."
• "What do you think?"

Vesence can still ask follow-up questions, but a clear goal helps it produce a better first result.

Tell Vesence what material to use

If the task depends on files, emails, spreadsheets, presentations, or other source material, tell Vesence what to rely on.

Examples:

• "Use the uploaded term sheet as the source of truth."
• "Use the Word agreement and compare it against the Excel payment schedule."
• "Use only the current email thread and the attached PDF."
• "Use the template as the structure and the email as the deal terms."

If there are several versions, tell Vesence which one matters most.

• "Use the version dated 12 May as the source of truth. The older draft is only for comparison."

See: Working with Files and Source Material for more information.

Say what output you want

Tell Vesence what format would be most useful.

Common outputs include:

Examples:

• "Create a table with issue, document reference, risk level, and proposed next step."
• "Give me a short executive summary in bullets."
• "Draft the reply in a concise and neutral tone."
• "Make the edits as tracked changes where supported."

Give the audience and tone

If the output is for a specific audience, say so. Because Vesence can use context from your Outlook and previous material, you can also ask it to shape the language to match the tone of your earlier messages.

Examples:

• "Explain this for a client who is not technical."
• "Make this suitable for a partner review."
• "Use a concise internal tone."
• "Make the email firm but polite."
• "Use plain English."
• "Match the tone of my previous client emails."

Audience matters because the same source material can be written differently for a client, internal team, counterparty, board, or specialist reviewer.

Give the scope

If you only want Vesence to review part of something, say that.

Examples:

• "Review only liability and termination."
• "Check only definitions and cross-references."
• "Summarize only the commercial terms."
• "Ignore the appendices for now."
• "Focus on issues that require user judgment."

Scope helps Vesence avoid spending time on the wrong parts of the material.

Tell Vesence what not to do

If there are boundaries, include them.

Examples:

• "Do not change the legal meaning."
• "Do not use external sources."
• "Do not make edits yet; only identify issues."
• "Do not rely on the older draft except for comparison."
• "Do not send anything; only prepare a draft."

Clear boundaries help Vesence avoid making assumptions in matters where precision, judgment, or approval is important.

Ask Vesence to flag uncertainty

Vesence should not invent missing facts or silently decide material judgment calls.

You can ask Vesence to flag uncertainty directly.

Examples:

• "Flag anything that is unclear or missing."
• "List assumptions before drafting."
• "Ask me before making any material legal changes."
• "Identify points that need partner input."
• "If the documents conflict, tell me rather than choosing silently."

Strong instruction examples

Document review

Template drafting

Spreadsheet check

Email drafting

Quick formula for a good instruction

A strong instruction usually includes:

• Task — what you want Vesence to do
• Source — what Vesence should use
• Scope — what to include or exclude
• Output — what form the answer should take
• Tone — who the output is for
• Judgment — what Vesence should flag before deciding

Example: