Claude's Files and Knowledge features let you upload documents, policies, price lists, past reports, so answers are grounded in what your business actually has on record, rather than a general answer that sounds plausible but isn't specific to you. Understanding what each feature actually does, rather than treating them as interchangeable, changes how reliably you can use them.
What Files and Knowledge each actually do
Uploading a file directly into a conversation gives Claude that document's full content for the current session, useful for a one-off task, reviewing a contract, summarising a report someone just sent you. Project-level knowledge, uploaded documents attached to a persistent Project, stays available across every conversation in that project, which suits an ongoing reference set: your current pricing, your brand voice guide, your standard terms. The distinction matters because a file dropped into a single chat won't be there next week, while project knowledge will.
Single-session file upload: available for that conversation only, good for one-off document work
Project-level knowledge: persists across every conversation in that Project, good for standing reference material
Connector-based retrieval (Google Drive, Notion): pulls live from the source, good when the source document changes often
Why grounding beats a general answer
Ask Claude a general question about, say, your refund policy without any document attached, and it will either decline to guess specifics or, worse, generate something plausible-sounding that isn't your actual policy. Attach the actual policy document, and the same question gets an answer traceable to a real source, which matters enormously for anything client-facing where a plausible-but-wrong answer is more damaging than an honest 'I don't have that information.'
A Sydney professional services example
A ten-person Sydney recruitment agency set up a Project with their current fee schedule, standard terms, and a library of past successful placement briefs as persistent knowledge. Consultants drafting a new client proposal now get language grounded in the agency's actual current terms rather than a consultant's memory of what the terms were six months ago, catching two instances in the first month where a consultant would otherwise have quoted an outdated fee structure, each worth roughly $1,500 in the difference between old and current pricing.
Keeping grounding honest
Connectors versus static uploads, choosing the right one
For source material that changes often, your current price list, a live product catalogue, a connector pulling directly from Notion, Google Drive, or a database beats a static upload every time, because it removes the maintenance burden of remembering to re-upload the latest version. For material that changes rarely, standard terms and conditions, a brand style guide, a static upload into project knowledge is simpler to set up and just as reliable, since the update frequency doesn't justify the extra connector configuration.
A useful habit for any business relying on grounded answers: periodically ask Claude to cite which document a specific answer came from, and spot-check that citation against the actual source. This catches two failure modes early, stale documents that should have been updated, and gaps where Claude is filling in from general knowledge rather than your actual materials because the relevant document was never uploaded in the first place.
A simple setup sequence for a first Project
Pick one recurring task where a wrong or outdated answer has caused a real problem before
Gather the two or three documents that genuinely define the correct answer for that task
Upload them as project knowledge and test with the exact questions staff actually ask
Assign an owner responsible for re-uploading whenever the source material changes
Starting narrow, one task, a small number of well-chosen documents, beats uploading an entire shared drive and hoping relevance sorts itself out. A tightly scoped Project with three current, accurate documents produces more reliable answers than a broad one with fifty documents of mixed vintage, because Claude has less conflicting or outdated material to weigh against the current answer.
One more distinction worth understanding: grounding reduces the chance of a wrong answer, it doesn't eliminate it. Even with the correct document attached, Claude can still misread a nuance or apply a general rule where a document has a specific exception. Treat grounded answers as a strong first draft checked against the source for anything genuinely high-stakes, a client contract term, a compliance answer, rather than as guaranteed-correct simply because a real document was involved.
Grounding only works if the underlying documents are current. A Project with stale pricing attached is worse than no attached knowledge at all, because it produces confident, traceable, wrong answers instead of an honest gap. Whoever owns the source documents needs to own keeping the Project's knowledge current, the same discipline as keeping a shared drive folder tidy, not a one-off setup task.
