Attach and Verify a Document

Select the right place

Open the target conversation or project and add a supported file through its attachment control.

Wait for processing

Review the upload and available extraction or processing status. Do not infer readable content from a filename or preview alone.

Ask a verifiable question

Choose a narrow question answered by the document. Compare the response with the original text and any source indicators.

Isolate a failure

Check supported type and size, processing status, model capability, and actual source delivery. Use one small attachment to narrow the problem.

Practice with a small text file

Create a harmless text file with three short facts you can verify. Select the intended conversation, use its attachment control, and wait for the available upload or processing result. Ask a question about one fact, then compare the answer with the file. Supported upload types are not a promise that every format can be read by every model.

Ask Friday to guide you

In an authorized FridayLocalAI conversation, try:

Help me verify whether you can read my attached practice file. Name the file you can access, quote one short passage, and answer this question from it: [question]. If it is unavailable, explain what I should check without inventing its contents.

Tell Friday what you can see and which step you have reached. If the instructions do not match your screen, say so; ask for the relevant Help topic or contact your operator. Friday cannot be assumed to see your screen or know your current settings.

Prepare a source you can check

For your first document task, choose a short, non-sensitive text file with facts you understand. Give it a meaningful filename and include a clear title or section heading in its contents. This makes it easier to identify the source and compare the answer with the original. Avoid beginning with a large scan or a complex archive when you are still learning the attachment workflow. Confirm that you are allowed to use the material in the intended deployment. A file being available on your device does not settle whether it should be supplied to an AI workflow. If it contains proprietary or personal information, follow your organization’s handling rules and ask the operator about the processing path. Use the smallest relevant source rather than uploading unrelated material as background.

Select the intended conversation

Open the project and conversation where the work belongs before using the attachment control. Check the active title and context, especially after navigating through search results or switching tasks. An attachment should support the question you are asking in that conversation. Clear placement also makes it easier to revisit the source-dependent exchange later. Use the interface’s supported upload mechanism and wait for the available result. The file picker may accept many types, but acceptance is only one stage. Different formats can require different processing, and some contents may not be available to the selected model. Do not infer universal readability from a filename, an attachment badge, or the ability to preview the file in the browser.

Test access with a narrow question

Ask something whose answer is clearly present in the source. For example, request the exact date stated under a known heading or ask for a short quotation from a particular section. Compare the response with the original file. A general summary can sound plausible even when source access is incomplete, so a narrow question is a stronger initial check. Tell Friday to say when it cannot access the content. Do not ask it to guess what a document probably contains from its title. If the answer includes a passage reference, confirm that the passage exists and supports the claim. This check does not guarantee complete understanding of the entire document, but it gives you evidence about whether the supplied material is being used for the specific question.

Move from verification to analysis

Once you have evidence that the relevant content is available, ask the actual question. Specify the section, comparison, or output needed. “Summarize the obligations described in section two and list ambiguities” is more focused than “analyze everything.” For an important task, keep source statements separate from interpretation and ask for references to the material supporting the answer. Review any extracted figures, names, and dates carefully. If a document contains tables, images, or scanned pages, verify that the relevant part was processed appropriately. An answer based on readable text may not account for information in an image. Ask Friday to identify limitations and unresolved items, then inspect the original source where the result depends on details that are easy to misread or omit.

Investigate unreadable material systematically

If the source is unavailable, describe the file type, approximate size, and visible upload or processing status. Try a small supported text sample to determine whether the issue is general or specific to the original file. Do not repeatedly upload the same private document without understanding what happened to earlier attempts. Ask the operator about supported processing when the file needs extraction or conversion. A smaller excerpt may help if you are allowed to share it, but keep the relationship to the original clear. Do not treat a pasted summary as equivalent to reviewing the full source. The useful question is which content reached the task and in what form, not simply whether a storage operation accepted the upload.

Keep source authority clear

FridayLocalAI can help explain, organize, and compare material, but the original document remains the reference for what it actually says. A generated answer can contain an omission or an interpretation that the source does not support. Where the result matters, verify the relevant passage and record any uncertainty rather than silently resolving it through guesswork. Instructions embedded in the document should also be distinguished from your own request. If the task is to summarize a document, text inside it is source material to analyze, not automatic permission to change files or contact a service. State the desired operation clearly. This makes document review more useful and helps keep the workflow aligned with your goal, the available capabilities, and the boundaries established for the deployment.