[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-242172-105":53,"doc-detail-242172-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","process-process-template-process-documentation-system-blueprint","Process Process-TEMPLATE - Process documentation system blueprint","","Process Process-TEMPLATE defines how to document business and technical processes in a documentation system, clarifying the Who, What, When, Where, Why, and How structure. It specifies workflow governance through roles like the Documentation Czar, change request handling, and weekly update reviews. It also standardizes document naming, writing style, revision formatting, and storage rules for internal processes, SOPs, and picture assets, including client-facing instruction requirements and screenshot-friendly steps.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/process-process-template-process-documentation-system-blueprint/242172/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/process-process-template-process-documentation-system-blueprint/242172.png","ImageObject",442,249,{"name":88,"@type":89},"Pentious","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-11","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":9},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of the Process Process-TEMPLATE document?","Question",{"text":108,"@type":109},"It serves as the blueprint for documenting processes in a documentation system, explaining Who, What, When, Where, Why, and How so the team can create and find documentation consistently.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Who oversees the documentation platform and how are changes requested?",{"text":113,"@type":109},"The Documentation Czar oversees the platform. For new documents or needed improvements, submit a change request that includes a link to the document, the suggested change, and the reason.",{"name":115,"@type":106,"acceptedAnswer":116},"How should processes and revisions be formatted and named?",{"text":117,"@type":109},"Name documents clearly and specifically for searchability, and follow writing style guidance (font and headings). Revisions must include who changed what and when, using initials and a YYMMDD date with brief notes.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},242172,1791726001,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":135,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":73},1374404730887,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","EurekaProcess  \nPROCESS PROCESS  \nTemplate for creating your Process Process  \nProcess Process-TEMPLATE  \nWhy  \nThe Process Process is the blueprint of our documentation system. It explains the Who, What, When, Where, Why, & How process documentation. By having this pivotal document, our entire team can stay on the same page when creating and finding documentation and processes. This is a key process.  \nWhere  \nAll processes are to be created and kept in our documentation system, \u003CDocumentation System Here> . The What section will give more detailed instructions on where each type of documentation will be stored within our documentation system.  \nWho  \n\u003CRole Name> oversees our documentation platform and is referenced as the Documentation Czar. If you have needs or concerns about our documentation system, please see them.  \nWhen  \n\u003CSAPLING> \u003CNEW GROWTH> As stated in Ways to Succeed, all processes and documentation are to be created, updated, and referenced while performing work. Everyone has permission to make changes as needed. The only way documentation will stay up to date is if we are reading it during the work and able to make modifications as we see any need for improvement. We will review updates weekly during team meetings.  \n\u003COLD GROWTH> As stated in Ways to Succeed, all processes and documentation are to be referenced while performing work. If you created a new document, a change is needed, or you’d like to make an improvement suggestion, please submit a \u003Cchange request> to our Documentation Czar. Make sure the request includes a link to the document in question, what change you would suggest, and why.  \nHow  \nBe clear and specific about what is inside the document when naming it. Think about what someone would likely be searching for when this document is needed. There are some additional considerationsin the “What” section below, but we recommend including:  \n• Commonly used “slang” such as  \no acronyms you use often (E.g., WYSIWYG)  \no client short names (e.g., EP for Eureka Process)  \n• The name of any product that may be involved, include  \no Long form (E.g., ConnectWise Manage), and  \no Short form (E.g., CWM)  \n• Any other terms you can add to make global searches easier  \nFollow the below style guides for your processes:  \n Word Example: Use Calibri font at size 11. Left justified. Use the default Title style for the title and Heading 1 for Headings.  \n Example: Use default headings and text sections in our documentation platform.  \nCreate a section to address each below prompt:  \nWhy/Purpose: Explain what the document is about, so the next person knows they found the right document.  \nBody: List each step and how to do it.  \nNext steps: \u003CEscalate, go to next document, hand off to another person, or ?>  \nNotes: Improvements, Caveats, Gotchas, Pro Tips  \nRevisions: Who change what when: \u003CInitials> \u003CYYMMDD> – \u003Cbrief notes>, centered at bottom, size 8 font, italicized  \nWhat  \nInternal Processes  \nThese are processes that we follow as a business and not for technical resolution of issues. Examples include Ways to Succeed and our Client Onboarding Process. Store these in our documentation platform under \u003CInternal Processes (Internal Company)> .  \nInternal Technical Processes  \nThese types of processes are step-by-step instructions to be followed by our in-house technical staff. They should be written to a level of detail that any technician on our team can reproduce the solution.  \nBe wary of click-by-click instructions and screenshots as these details can change quickly with technology updates.  \nAs an example, to reset a password in Active Directory, specify OUR way of accomplishing this. E.g., In our RMM tool, deploy the Reset Password script from the Help Desk folder to the agent. Make sure to note that you ran this script in the ticket notes.  \nFurther, any SOPs created or updated should be stored with the name “SOP – “ and the name of the process in our documentation platform, under the organization \u003Cinternal","cbCainNO3eMIB71h","https://ap.wps.com/l/cbCainNO3eMIB71h","pdf",2549582,7,6,"English","# Process Process-TEMPLATE\n## Why\n## Where\n## Who\n## When\n## How\n## What\n### Internal Processes\n### Internal Technical Processes\n## Pictures\n## Client Facing Instructions","[{\"question\":\"What is the purpose of the Process Process-TEMPLATE document?\",\"answer\":\"It serves as the blueprint for documenting processes in a documentation system, explaining Who, What, When, Where, Why, and How so the team can create and find documentation consistently.\"},{\"question\":\"Who oversees the documentation platform and how are changes requested?\",\"answer\":\"The Documentation Czar oversees the platform. For new documents or needed improvements, submit a change request that includes a link to the document, the suggested change, and the reason.\"},{\"question\":\"How should processes and revisions be formatted and named?\",\"answer\":\"Name documents clearly and specifically for searchability, and follow writing style guidance (font and headings). Revisions must include who changed what and when, using initials and a YYMMDD date with brief notes.\"}]","Process Process-TEMPLATE - Process documentation system blueprint | PDF",1789187367]