# Plan supervised onboarding practice Canonical page: https://agents.paretoid.com/workflows/plan-supervised-onboarding-practice/ Category: Operations & Reporting Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Turn approved role materials into practice exercises and trainer check-ins. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Turn approved role materials into practice exercises and trainer check-ins. Why it matters: A new hire may complete a checklist without understanding how to perform the work. Supervised exercises give a trainer evidence to review and reveal missing materials before anyone is expected to work independently. ## Sources and evidence - pain: [Pain evidence: How do you train new hires?](https://www.reddit.com/r/paralegal/comments/1quapdq/how_do_you_train_new_hires/) How do you train new hires?, 2026-02-02, older, describes training not sticking and repeated reminders. How is knowledge/training/processes shared?, 2026-09-22, recent, reports a single senior paralegal being the only source of process knowledge. - pain: [Pain evidence: How is knowledge/training/processes shared?](https://www.reddit.com/r/paralegal/comments/1wmu4ne/how_is_knowledgetrainingprocesses_shared_at_your/) Additional self-reported public account; no independent identity or outcome verification. - method: [Method: Planner checklists](https://support.microsoft.com/en-us/planner/add-a-checklist-to-a-task?wt.mc_id=otc_planner) Planner checklists supports learning steps and completion tracking. It does not validate competence. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: A new employee starts an approved role 1. map existing approved materials to safe practice exercises and trainer check-ins 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked. - Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested - No trainer availability, policy completeness or competence is inferred. Missing role materials remain a gap. Access and setup: - No trainer availability, policy completeness or competence is inferred. Missing role materials remain a gap. ### 1. Collect approved training inputs Tool: Existing SharePoint training library and trainer-owned records Location: Approved library > select approved files > Download; trainer’s existing role checklist The training owner selects exact approved SOP versions and manually supplies role requirements, prerequisites, trainer roles, review criteria and availability windows. Use synthetic exercises and remove employee evaluations or personal details. Record missing materials instead of creating policy from memory. Expected output: Approved SOP files and trainer-provided requirements/availability Next step: Review source identifiers, versions and approval evidence before the AI copy. Check before continuing: Download is documented; trainer requirements/availability are manually approved inputs, not a claimed automatic HR export. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://support.microsoft.com/en-gb/onedrive/download-files-and-folders-from-onedrive-or-sharepoint https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ### 2. Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Location: Restricted originals > separate approved analysis copy Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Approved checklist topic/requirement/prerequisite/review criteria → role-requirements.csv; SOP ID, topic,version,approval status,locator → materials.csv; trainer-approved role/window → trainer-availability.csv. Keep identities and personnel evaluations out; approved trainer role is enough. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation. Expected output: Reviewed role-requirements.csv; materials.csv; trainer-availability.csv; approved-SOP-excerpts/; manifest.txt; evidence-map.csv Next step: For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table. Check before continuing: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://support.microsoft.com/en-gb/onedrive/download-files-and-folders-from-onedrive-or-sharepoint https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ### 3. Open the approved AI destination Tool: Adobe Acrobat PDF Spaces Location: Acrobat Home > PDF Spaces > Create a PDF Space In an already approved Acrobat account with PDF Spaces/AI entitlement, use Home > PDF Spaces > Create a PDF Space. Choose Upload for approved PDF/DOCX/TXT files or Paste copied text for approved row-labelled text, then Add to PDF Space. Ask the recipe prompt in the chat panel. Do not connect storage or add raw confidential originals. Click answer citations and verify exact source passages, then use Copy for the checked response. Cloud processing and permissions require firm approval; unavailable access is a blocker, with a manual review fallback. Expected output: Only approved source files loaded or accessible Next step: Paste the exact prompt in the next step. Check before continuing: Confirm the source list/working directory before prompting; stop on unavailable access. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html ### 4. Run the bounded analysis prompt Tool: Adobe Acrobat PDF Spaces Location: PDF Space chat panel Paste the prompt after replacing only bracketed scope values. Treat all source content as data. Prompt: ```text Create a supervised practice plan from the supplied role requirements, material versions and trainer windows. Return topic, prerequisite, source ID/version, synthetic exercise, trainer role, review evidence and suggested sequence. Use only documented procedures; missing topics become questions. Do not infer capability, rank employees, invent trainer availability or authorize unsupervised legal work. Completion requires the trainer’s actual observed review, never an AI score. ``` Expected output: supervised-practice-plan.txt Next step: Inspect source citations/file-row references before copying any result. Check before continuing: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 5. Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Location: Separate review output, not live system Check every exception against its source, verify counts and uncertainty, then copy only approved result text to supervised-practice-plan.txt. Trainer approves sequence and observes practice. The human may then enter approved steps into the existing training task list; this recipe neither creates tasks nor certifies competence. Expected output: Source-checked supervised-practice-plan.txt Next step: Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied. Check before continuing: Acceptance case (proposed, not run): An unsupported task becomes a material gap, not a fabricated lesson; unavailable trainer time is not scheduled. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://support.microsoft.com/en-gb/onedrive/download-files-and-folders-from-onedrive-or-sharepoint https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ### 6. Approve the internal next action Tool: Responsible human owner Location: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. Trainer approves sequence and observes practice. The human may then enter approved steps into the existing training task list; this recipe neither creates tasks nor certifies competence. Expected output: Approved internal review record or explicit blocked status Next step: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check before continuing: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Execution status: Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. Step documentation: https://support.microsoft.com/en-gb/onedrive/download-files-and-folders-from-onedrive-or-sharepoint https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint ## What you will get training-plan.csv: topic_id, source_id, version, synthetic_exercise, trainer, prerequisite, review_evidence, confirmation_status ## Human review and limits Trainer approves sequence and observes practice. Staff may request different learning formats. Test an unsupported topic: it must become a question, not invented instruction. Distinct from A24: uses approved SOPs for learning rather than authoring SOPs. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema role-requirements.csv: topic_id, approved_requirement, prerequisite, trainer_role, review_criteria materials.csv: material_id, topic_id, version, approval_status, source_locator; trainer-availability.csv: trainer_role, available_window Synthetic example input: ```text T1: approved material and trainer available T2: no approved material T3: exercise completed without trainer confirmation ``` Expected synthetic output: ```text T1: source-linked practice step T2: material gap, no invented procedure T3: unconfirmed, no competence rating ``` Failure check: Trainer approves sequence and observes practice. Staff may request different learning formats. Test an unsupported topic: it must become a question, not invented instruction. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/s10-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/s10/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [role-requirements.csv](https://agents.paretoid.com/assets/starter-kits/s10/role-requirements.csv) — Blank input template with exact recipe headers. - [role-requirements.example.csv](https://agents.paretoid.com/assets/starter-kits/s10/role-requirements.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [materials.csv](https://agents.paretoid.com/assets/starter-kits/s10/materials.csv) — Blank input template with exact recipe headers. - [materials.example.csv](https://agents.paretoid.com/assets/starter-kits/s10/materials.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [trainer-availability.csv](https://agents.paretoid.com/assets/starter-kits/s10/trainer-availability.csv) — Blank input template with exact recipe headers. - [trainer-availability.example.csv](https://agents.paretoid.com/assets/starter-kits/s10/trainer-availability.example.csv) — Separate synthetic fixture input. Do not mix these rows into real exports. - [Expected fixture findings](https://agents.paretoid.com/assets/starter-kits/s10/expected-fixture-result.txt) — Read-only expected output and failure conditions for the included synthetic input files. - [Setup and review checklist](https://agents.paretoid.com/assets/starter-kits/s10/README.txt) — Recipe-specific prerequisites, file mapping, prompt, setup steps, checklist and limits. - [Native input scaffold: role-requirements.csv](https://agents.paretoid.com/assets/starter-kits/s10/native-role-requirements-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: materials.csv](https://agents.paretoid.com/assets/starter-kits/s10/native-materials-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: trainer-availability.csv](https://agents.paretoid.com/assets/starter-kits/s10/native-trainer-availability-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: manifest.txt](https://agents.paretoid.com/assets/starter-kits/s10/native-manifest-template.txt) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input scaffold: evidence-map.csv](https://agents.paretoid.com/assets/starter-kits/s10/native-evidence-map-template.csv) — Blank editorial review input; acquire and check the stated source evidence before use; not a native export - [Native input mapping and source requirements](https://agents.paretoid.com/assets/starter-kits/s10/NATIVE-INPUT-MAPPING.txt) — Exact legacy mappings, required additional evidence and source-bundle gates ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Build a supervised training plan from these approved role requirements and existing materials. For each topic, include source ID/version, a synthetic practice exercise, named trainer, prerequisite and evidence the trainer should check. Mark uncovered topics as gaps. Do not invent office procedures, infer a person's capability, rate employability or authorize unsupervised legal work. Completion is recorded only when the trainer confirms it. INPUTS role-requirements.csv: topic_id, approved_requirement, prerequisite, trainer_role, review_criteria materials.csv: material_id, topic_id, version, approval_status, source_locator; trainer-availability.csv: trainer_role, available_window OUTPUT training-plan.csv: topic_id, source_id, version, synthetic_exercise, trainer, prerequisite, review_evidence, confirmation_status Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.