RETVEST DEPLOYMENT PLANNING BRIEF Version: 14 October 2026 Guide: https://retvest.com/docs/self-hosted-ai/ Use this brief to prepare a walkthrough with Retvest and your infrastructure team. Keep the first version high level. Do not include credentials, private documents, personal records or sensitive network details. Organisation or team: Person responsible for the workflow: Date: 01 THE WORKFLOW What task should the team complete? Who uses the result, and what makes the current process difficult? What would a useful outcome look like? 02 PEOPLE AND ACCESS Which roles need access? Who reviews the result before it is used? Who owns the source information? 03 THE ENVIRONMENT Preferred location: company premises or company cloud account? Who operates the application host, network and persistent storage? Is the model planned for the same host or a separate model host? 04 THE MODEL Is a company model endpoint already available? Which tasks and context sizes must it support? What level of simultaneous use should the pilot assess? Who will establish model memory and GPU requirements? 05 COMPANY KNOWLEDGE Which approved sample collection can be used for the pilot? Who decides what each role may access? Are any external services or tools proposed as part of the workflow? Who will approve the information flow before sensitive data is introduced? 06 THE RIL RECORD Which supported work needs to be enrolled and recorded? Which inputs, activity, review decisions and outputs should be retained? Who may view or export those records? What retention requirements apply? 07 OPERATING RESPONSIBILITIES Who owns access changes and credentials? Who owns updates, backups and recovery? Who is the contact for deployment issues? 08 DECIDING WHETHER TO EXPAND What evidence will the business and infrastructure owners review? What limitations or unanswered questions need to be resolved? Who approves more users, information or integrations? NEXT STEP Discuss the workflow and proposed environment with Retvest: https://retvest.com/contact/ This is a planning template, not a deployment contract or an acceptance result. Availability, integrations, versions, commercial scope and operating responsibilities are agreed for each walkthrough or pilot.