Knowledge card L3 · Workflows informational

Attach Knowledge Files for Grounded Answers

What it is

A grounding step for Custom GPTs: upload the authoritative documents the GPT should answer from — policies, specs, FAQs — and instruct it to rely on them rather than its general knowledge.

ground it in your docsUpload authoritative docsInstruct: answer from theseGrounded, checkable replies
Answers drawn from your files, not the model's general memory.

Why it works

Without source files, a Custom GPT answers from generic training, which is fine until it confidently states something wrong for your specific context. Knowledge files anchor it to your actual material, so answers reflect your policies and facts — and you can point it to say 'not covered' instead of inventing, which is what makes a support or reference GPT trustworthy.

When to use it

Any Custom GPT that should answer about specific, stable material: company policies, product docs, a style guide, a curated FAQ.

When not to use it

General-purpose assistants meant to draw on broad knowledge, or material that changes so often the uploaded files would be stale — those need a live source, not attachments.

Prompt

For this Custom GPT, I've uploaded <the documents>. In the instructions, add: answer from these files first; quote or reference the relevant part; if something isn't covered by the files, say so plainly rather than guessing from general knowledge.

Example

An HR-policy GPT grounded in the actual handbook answers 'how many sick days do I get?' from the document — and says 'that's not in the handbook, check with HR' instead of inventing a number.

Common mistakes

  • Relying on general training for questions that need your specific facts.
  • Uploading files but not instructing the GPT to prefer them.
  • Leaving stale documents attached, so it answers from outdated policy.

Related