21 request templates for Docsi AI
A good request names the source, the scope, the output and the limits. These 21 templates come from the Docsi AI guides – from study sheets and meeting minutes to a table of receipts. Copy a template, adapt files and pages, and check the result with the list below it.
How a good request is built
- Source: which file, which chapter, which pages – and that only this material counts.
- Result: what should come out, with size and structure, for example ten terms and eight questions.
- Format: PDF, Word, Excel, CSV or Markdown – depending on how you continue working.
- Limits: what to leave out and how unclear points are flagged instead of guessed.
Which content an AI task uses is explained in the guide Which content an AI task uses. Merging, converting and text recognition need no AI request and never cost credits.
Study and work
Your first task with Docsi
Add a file, give a clear task, review the sources and save a finished document: your introduction to Docsi.
Create a discussion brief from the attached project description: the goal in two sentences, five unresolved questions and a table of explicitly stated next steps. Give a source for each material statement. Do not invent dates or owners. Flag missing attachments. Output a Word document so I can edit the questions before the discussion.
Check afterwards
- The correct file version is attached; older versions are not accidentally included.
- The draft identifies missing information instead of filling gaps with plausible details.
- The saved output opens and contains the reviewed sections and sources.
Common problem: Task does not start – Check licence status and the selected AI connection. Local functions also require an active licence.
Turn course material into a study sheet
Use Docsi to create clear study sheets, review questions and glossaries from your own course material.
Create a study sheet for chapter 3 with ten key terms, a process explanation and eight self-test questions. Put answers in a separate section. Use only the attached course material, flag unclear terms and give the page for definitions. Exclude chapter 4 and outside additions. Output a PDF.
Check afterwards
- Every requested learning goal has a section and at least one checkable question.
- Answers are separate so you can attempt the self-test without seeing them.
- Terminology, units and exceptions match the course material.
Common problem: Questions are too general – Provide concrete learning goals and an example of the desired question depth.
Read the full guide: Turn course material into a study sheet
Understand sources and check statements
Use Docsi source references, check PDF pages and understand the limits of a sourced AI response.
Check the draft against the attached sources. Create a table of claim, evidence, qualification and review status. Pay particular attention to numbers, dates and words such as “may”, “at most” and “provided that”. Flag unsupported conclusions. Do not add new sources or resolve conflicting claims without explaining the basis.
Check afterwards
- Evidence and conclusion have the same scope and comparison baseline.
- Page references lead to the correct original version, including an OCR image check.
- Conflicts and unsupported claims are visibly marked in the result.
Common problem: Quote matches, claim does not – Read adjacent paragraphs and rephrase the claim with its conditions.
Read the full guide: Understand sources and check statements
Use a visible window as a source
Understand window drop and screen text in Docsi: the visible view, local recognition and limits of captured content.
Explain the visible error in this window capture. First describe exactly what is visible. Separate visible evidence from assumptions and give three diagnostic steps. Do not claim access to hidden windows, unseen columns or the full article. Ask for missing text if the region is insufficient to explain the issue.
Check afterwards
- The selected window and visible region match the question.
- Private notifications, addresses and unrelated documents were reviewed before capture.
- The answer separates visible information from assumptions about missing content.
Common problem: Important area is clipped – Reposition and recapture the window or add the original file.
Compare two document versions clearly
Compare old and new document versions with evidence, without claiming a technical exhaustive diff or legal assessment.
Compare “old” and “new” only for actions, deadlines and amounts. Table: topic, old wording, new wording, possible meaning, source in both versions. Separate added, removed, changed and merely moved content. Do not claim a complete legal review. List uncertain differences separately; I will check them in the originals.
Check afterwards
- Both versions are clearly labelled and the comparison question is bounded.
- Each material change has traceable passages in the relevant originals.
- Unreviewed or missing attachments are openly identified.
Common problem: Versions reversed – Explicitly name roles and dates and check the first comparison row.
Turn meeting notes into clear next steps
Structure existing meeting notes into decisions, actions and unresolved questions with explicit review rules.
Organise the attached notes into decisions, actions and unresolved questions. Put actions in a table with owner, due date and evidence. Use “not specified” where information is missing. Separate proposals from confirmed decisions. Do not invent participants, dates or calendar actions. Create a Word draft for review before sharing.
Check afterwards
- Proposals and decisions are separate.
- Missing deadlines were not filled in.
- Every ownership assignment is traceable in the source.
Common problem: Too many supposed decisions – Check modal wording in the original and mark uncertain points as proposals.
Read the full guide: Turn meeting notes into clear next steps
Use a web page as text rather than only a link
Distinguish URL, browser capture and visible window and choose the appropriate Docsi context for web pages.
Summarise only the article text actually imported. Name title and URL where present. Flag missing sections and infer nothing from the URL alone. Give five key statements with text references and separate unresolved questions. Do not claim access to paywalled content or other tabs.
Check afterwards
- The intended tab is the actual source.
- The required text sections were imported.
- Gaps are explicitly identified in the result.
Common problem: Only a URL is present – Supply readable text or a deliberate browser capture.
Read the full guide: Use a web page as text rather than only a link
Files and outputs
Recognise text in scanned PDF pages
Local text recognition in Docsi: read scanned PDFs automatically during a task, recognise German and English, and review the results.
Use the attached scanned pages for a table of invoice number, date, currency and total. Check visible numbers for consistency and mark every uncertain character sequence “check original”. Do not fill in missing digits. Give the page for each record. Create a reviewable draft first; I will confirm values before further use.
Check afterwards
- Digits, decimal marks and names were compared with the actual page images.
- The recognised page range is clear; unrecognised pages are not treated as reviewed.
- Uncertain words stay marked instead of silently becoming verified facts in the export.
Common problem: Text is barely readable – Provide straight, sharp scans with complete page edges; avoid shadows and clipped lines.
Convert files and choose a format
PDF, DOCX, TXT, Markdown, CSV and XLSX in Docsi: supported inputs, local conversion and important format limits.
Convert the attached file into a readable PDF. Preserve headings and section order. Keep numbers and names unchanged. Present tables so every column remains readable. Do not summarise the content. Report unsupported or incompletely imported elements instead of silently dropping them.
Check afterwards
- The output includes the beginning, middle and end plus a sample of each special content type.
- Tables and special characters are readable in the actual saved format.
- The source file is kept separately and was not replaced by the export.
Common problem: Layout differs – Separate content preservation from layout fidelity; consider PDF merging for original PDF pages.
Combine several PDFs into one file
Merge PDFs locally with Docsi, check their order and save a separate combined document.
Merge the attached PDF files into one PDF. The sources have already been added in the desired order: cover letter, report, appendix. Preserve the original PDF pages. Do not summarise or rewrite. I will check the page count and joins afterwards. Report any protected or damaged file.
Check afterwards
- At least two accessible PDFs have been inserted in the intended order.
- The page count matches the source total; every join page is checked.
- The saved package contains the last page and correct appendix version.
Common problem: Wrong order – Remove and re-add sources in the intended order; changing only the request is insufficient.
Analyse spreadsheets and explain the results
Analyse CSV and XLSX with Docsi: check numeric values, groups, key figures and charts transparently.
Analyse the September table. Use the Net amount column in EUR, exclude rows marked cancelled and group by category. Show count, sum and average. List empty amounts, duplicate invoice numbers and ambiguous dates separately. Explain selection rules and the result without estimating missing values.
Check afterwards
- The result explicitly names the column, unit, period and exclusion rules.
- A small subset was calculated independently and compared with the analysis.
- Missing values and duplicates are visible instead of silently changing metrics.
Common problem: Too many or too few rows – Check filters, date format and sheet selection; request the included record count.
Read the full guide: Analyse spreadsheets and explain the results
PDF, Word, Excel or Markdown?
Choose the right Docsi export format and review text, tables, charts and print layout before sharing.
Prepare the reviewed report for sharing: clear headings, short paragraphs, a metrics table and a source list. Do not change confirmed numbers. Create a PDF report for readers and an Excel output of the table for further work. Clearly mark unresolved review points and choose formats according to the actual content.
Check afterwards
- The recipient can open the chosen format in the intended application.
- Sources, table headers and units remain in the saved export.
- File name and folder distinguish the draft, reviewed version and older exports.
Common problem: Excel is not offered – The result needs at least one table. Structure the content appropriately first.
Transfer receipts into a reviewable table
Transfer invoice numbers, amounts and dates from supplied receipts and check each important digit.
Transfer each attached receipt into one table row: source, document number, date, currency, net, tax, gross, review note. Do not fill missing values. Flag unreadable digits and possible duplicates. Sum only reviewed amounts per currency. Output an Excel table; original receipts remain the authoritative reference.
Check afterwards
- Amounts and identifiers were checked against originals.
- Currencies and gross/net are clearly separated.
- Duplicates and unreadable fields remain visible.
Common problem: Amount differs by factor ten – Check the decimal mark and OCR image, not only cell formatting.
Read the full guide: Transfer receipts into a reviewable table
Create a chart with a clear message
Prepare a table for a traceable Docsi chart and review axes, units and comparison baselines.
Create a bar comparison of reviewed net totals per category in EUR. Show the values and counts used alongside it. Label axes and period. Sort descending and flag missing data. Explain the largest visible difference in two sentences without inferring a cause. Output a PDF report.
Check afterwards
- Values and categories match the table.
- Axes, period and units are readable.
- The explanation claims no unsupported cause.
Common problem: Plausible chart, wrong values – Show the data alongside and compare each category.
Check CSV data before analysis
Check CSV columns, separators, decimal values and identifiers before analysis and preserve the original.
Check the CSV before calculating. Show headers, record count and five sample rows. Customer identifiers are text; amounts are EUR; dates use day/month/year. Flag empty fields and possible duplicates. Do not change original values. List structural problems and questions separately from later analysis.
Check afterwards
- Columns and row count were reviewed.
- Identifiers retain leading zeros.
- Missing values and date convention are documented.
Common problem: Everything appears in one column – Check delimiter and source export; correct structure before analysis.
Use text from images and screenshots carefully
Use images as Docsi sources, check locally recognised text and account for crop, resolution and character errors.
Read the visible text in this image. List numbers, dates and names separately, marking uncertain characters. Then explain only the notice actually visible. Separate estimates from confirmations. Do not complete clipped words or claim knowledge of the entire document. I will check the characters against the image.
Check afterwards
- The image contains the necessary context.
- Identifiers were checked character by character.
- The explanation does not exceed the visible scope.
Common problem: Text is tiny – Use original resolution or a readable crop with context.
Read the full guide: Use text from images and screenshots carefully
Diagnose protected files and import errors
Distinguish password protection, damaged files and unsupported content during Docsi import and PDF merging.
Process only the attached files that are actually accessible. If a source is protected, damaged or incomplete, identify the file and limitation. Do not fill missing content. Produce the requested output only when sources are complete. I will review a legitimately created working copy separately.
Check afterwards
- The working copy opens in the source application.
- Pages and tables were compared with the original.
- The limitation and affected source are documented.
Common problem: Password required – Use your own access rights; Docsi does not bypass protection.
Read the full guide: Diagnose protected files and import errors
AI, data and subscription
Which content an AI task uses
Distinguish local processing from AI tasks in Docsi: select sources, review text and share data deliberately.
Create a general checklist using only the currently attached file. Do not use information from older conversations. List the sources used at the start. Do not include personal names, addresses or identifiers in examples. Flag missing information instead of filling it from other context. Output Markdown for my own editing.
Check afterwards
- The source list contains only material needed for this specific task.
- The selected AI connection is known; local and cloud processing are distinguished deliberately.
- The completed output contains no unintentionally reused personal details from other tasks.
Common problem: Old information appears – Start a new chat, inspect sources and specify the permitted scope.
Manage credits, licence and devices
Find Docsi credits and devices, activate a licence key and manage your subscription in the customer portal.
I want to process a long report. First help me split the task into a short overview, source review and final export. Use only the attached file. Identify missing information early. Avoid unnecessary repetitions. I will inspect the displayed licence and credit status in settings before carrying out the next step.
Check afterwards
- The current plan and actual credit balance were checked in the app.
- The new device is activated; unused slots are released deliberately.
- The task scope is bounded and avoids repeated ambiguous requests.
Common problem: Licence key is rejected – Check the full key and correct product licence; do not attach keys to support email.
Continue interrupted tasks deliberately
Diagnose Docsi interruptions using status, source, connection and credits and avoid blind retries.
Process only the specified section of the attached source. First create a brief overview and flag missing or unreadable parts. Do not use an incomplete earlier response as a verified basis. Report the concrete limitation if the task cannot complete. I will review the draft before a larger follow-up.
Check afterwards
- The error was read and diagnosed.
- The new scope is smaller and unambiguous.
- The successful export was actually opened.
Common problem: Same error repeatedly – Test source and connection rather than repeatedly submitting the complete task.
Read the full guide: Continue interrupted tasks deliberately
Organise local drafts and retention deliberately
Organise Docsi drafts and important exports and distinguish local retention from cloud content.
Create a closing checklist for this project: approved outputs, needed original sources, unresolved review points and unambiguous file names. Do not delete anything. Distinguish local app drafts, exported files and cloud documents. I will decide retention periods and check the existing files myself.
Check afterwards
- Final exports open outside the app.
- Original sources are retained as needed.
- Local and cloud periods were checked separately.
Common problem: Draft missing after cleanup – Check retention and your export collection; do not assume an unavailable recovery feature.
Read the full guide: Organise local drafts and retention deliberately
Good to know
The templates are examples from the guides; replace chapters, pages and file names with your own. Docsi understands requests in German and English. Always check important statements, figures and quotations against the original – the list under each template shows what matters. The glossary explains technical terms.