[{"data":1,"prerenderedAt":543},["ShallowReactive",2],{"document-business-process-mapping-D12991":3},{"document":4,"label":23,"preview":11,"thumb":24,"thumb600":25,"description":5,"descriptionCustom":6,"apiDescription":5,"pages":8,"extension":10,"parents":26,"breadcrumb":30,"related":38,"customDescModule":184,"customdescription":6,"mdFm":185,"mdProseHtml":542},{"description":5,"descriptionCustom":6,"label":7,"pages":8,"size":9,"extension":10,"preview":11,"thumb":12,"svgFrame":13,"seoMetadata":14,"parents":16,"keywords":15},"A Brief Guide on Business Process Mapping A Condensed Guide to Help You Understand How Business Process Mapping Works Table of Contents Introducing the Business Process Mapping Concept 3 Why Do You Need Business Process Mapping? 3 The Steps for Business Process Mapping 4 Step #1: Set the Process Context 4 Step #2: Set Your Goals 4 Step #3: Identify Your Knowledge Sources 4 Step #4: Meet With Key Stakeholders 5 Step #5: Select Your Preferred Business Process Map 5 Step #6: Define a Start and End Point for the Process 6 Step #7: List All of the Tasks 6 Step #8: Create a Sequence Order 7 Step #9: Determine Who is Responsible for Each Task 7 Step #10: Produce Your Baseline Map 7 Step #11: Identify Task Redundancies 8 Step #12: Analyze the Baseline Map to Find Improvements 8 Step #13: Create Your Master Map 8 Step #14: Continually Monitor the Master Map 8 Map Your Processes 9 Introducing Business Process Mapping Business process mapping is a tool within the business process management system. It aims to provide a visual representation of the steps your people follow to complete a process. Through business process mapping, you visually define every stage of a process so that all key stakeholders can understand the process and execute it where relevant. Business process mapping uses a combination of flowcharts, standard charts, and symbols to provide answers for the following three questions: What tasks are involved in the process? Who completes each of these tasks? When must each task be completed to ensure the success of the process? Why Do You Need Business Process Mapping? Your business needs business process mapping for a simple reason. Without it, your employees are left to devise their own methods for completing the various tasks assigned to them. Allowing this to happen can create confusion. It can also lead to situations where certain individuals in your organization are the only ones who know how to complete a process, which could prove troublesome should those individuals leave. The Steps for Business Process Mapping Creating a business process map requires collaboration with your team. The result is a standardized and repeatable process that anybody can learn. Step #1: Set the Process Context What is the purpose behind the process you aim to map? What problem does it solve and what are the key organizational drivers behind needing to have this process in place? Will your process help you to solve a problem or create an opportunity to improve the way things are done within your business? Answering these questions provides early context into your process to show you whether it's worth investing time into developing a business process map. Step #2: Set Your Goals Define the intended outcome you aim to achieve through mapping your business process. This goal can vary. You may map a process to understand every step involved in that process. Alternatively, you may create a business process map to identify areas where you can improve efficiency or implement new tasks. Aim to tie your goals in with the strategic goals of your company. Step #3: Identify Your Knowledge Sources A knowledge source is anywhere that provides you with information about the process. For example, any basic flowcharts or process documentation you already have is considered a knowledge source. If a team member who completes a task has not documented the task, that team member is a knowledge source, as you will need their help when creating your business process map. This stage is all about figuring out who and what is involved in the completion of the process. Who are the key stakeholders and what tools do they use to complete their tasks? Step #4: Meet With Key Stakeholders A key stakeholder is anybody who will be, or is currently, involved in the process. At this early stage, gathering input from these people helps you to better understand the process and the steps involved. If there is no previous process map in place, this step also allows you to determine how everyone involved in the process completes their tasks. This information may serve as the foundation for your process. Alternatively, the information may reveal inefficiencies in the existing process that your new process aims to solve. Step #5: Select Your Preferred Business Process Map There are five tools you may use to visually represent a process in your business: Flowcharts - The most common type of business process map, flowcharts can be used to represent simple processes. However, they may lack the flexibility required for multi-layered and more complex tasks. Value Stream Map - Often used in six sigma applications, value stream maps go into far more detail than flowcharts. These maps typically detail steps, people requirements, technical information, and timeframes in a single chart. Swimlane Chart - While this map functions similarly to a flowchart, it allows you to divide tasks between different departments. Use this tool if you want a better idea of which department handles each step of a process. SIPOC - A simplified process map, SIPOC stands for Supplier, Inputs, Processes, Outputs, Customer. You create table fields for each of these five things, writing a list of the tasks required for each in the appropriate field.",null,"Business Process Mapping","3",513,"doc","https://templates.business-in-a-box.com/imgs/1000px/business-process-mapping-D12991.png","https://templates.business-in-a-box.com/imgs/250px/12991.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12991.xml",{"title":15,"description":6},"business process mapping",[17,20],{"label":18,"url":19},"Business Plan Kit","/templates/business-plan-kit/",{"label":21,"url":22},"Administration","/templates/business-administration/","Business Process Mapping Template","https://templates.business-in-a-box.com/imgs/400px/12991.png","https://templates.business-in-a-box.com/imgs/600px/12991.png",[27,17,20],{"label":28,"url":29},"Templates","/templates/",[31,32,35],{"label":28,"url":29},{"label":33,"url":34},"Production & Operations","/templates/production-operations/",{"label":36,"url":37},"Standard Operating Procedures","/templates/standard-operating-procedures/",[39,43,47,51,56,60,64,68,72,76,80,84,88,104,120,136,150,168],{"label":40,"url":41,"thumb":42,"extension":10},"Business Process Management","/template/business-process-management-D12896","https://templates.business-in-a-box.com/imgs/250px/12896.png",{"label":44,"url":45,"thumb":46,"extension":10},"How to Improve any Business Process","/template/how-to-improve-any-business-process-D12577","https://templates.business-in-a-box.com/imgs/250px/12577.png",{"label":48,"url":49,"thumb":50,"extension":10},"Checklist Hiring Process","/template/checklist-hiring-process-D13919","https://templates.business-in-a-box.com/imgs/250px/13919.png",{"label":52,"url":53,"thumb":54,"extension":55},"Process Documentation Template","/template/process-documentation-template-D13372","https://templates.business-in-a-box.com/imgs/250px/13372.png","xls",{"label":57,"url":58,"thumb":59,"extension":10},"Business Process Automation Everything You Need To Know","/template/business-process-automation-everything-you-need-to-know-D13316","https://templates.business-in-a-box.com/imgs/250px/13316.png",{"label":61,"url":62,"thumb":63,"extension":10},"How to Setup a Purchasing Process","/template/how-to-setup-a-purchasing-process-D12597","https://templates.business-in-a-box.com/imgs/250px/12597.png",{"label":65,"url":66,"thumb":67,"extension":10},"How to Steps for Client Onboarding Process","/template/how-to-steps-for-client-onboarding-process-D12601","https://templates.business-in-a-box.com/imgs/250px/12601.png",{"label":69,"url":70,"thumb":71,"extension":10},"The Risk Management Process Explained","/template/the-risk-management-process-explained-D13408","https://templates.business-in-a-box.com/imgs/250px/13408.png",{"label":73,"url":74,"thumb":75,"extension":10},"New Product Development Process Explained","/template/new-product-development-process-explained-D13366","https://templates.business-in-a-box.com/imgs/250px/13366.png",{"label":77,"url":78,"thumb":79,"extension":10},"Create Process Goals and Enjoy Greater Success","/template/create-process-goals-and-enjoy-greater-success-D13094","https://templates.business-in-a-box.com/imgs/250px/13094.png",{"label":81,"url":82,"thumb":83,"extension":10},"Business Continuity Policy","/template/business-continuity-policy-D13461","https://templates.business-in-a-box.com/imgs/250px/13461.png",{"label":85,"url":86,"thumb":87,"extension":10},"Business Processes Management","/template/business-processes-management-D12992","https://templates.business-in-a-box.com/imgs/250px/12992.png",{"description":89,"descriptionCustom":6,"label":89,"pages":90,"size":9,"extension":55,"preview":91,"thumb":92,"svgFrame":93,"seoMetadata":94,"parents":96,"keywords":95,"url":103},"Project Plan","6","https://templates.business-in-a-box.com/imgs/1000px/project-plan-D12775.png","https://templates.business-in-a-box.com/imgs/250px/12775.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12775.xml",{"title":95,"description":6},"project plan",[97,100],{"label":98,"url":99},"Sales & Marketing","sales-marketing",{"label":101,"url":102},"Marketing Plan","marketing-plan","/template/project-plan-D12775",{"description":105,"descriptionCustom":6,"label":106,"pages":107,"size":108,"extension":10,"preview":109,"thumb":110,"svgFrame":111,"seoMetadata":112,"parents":113,"keywords":118,"url":119},"SERVICE LEVEL AGREEMENT This Service Level Agreement (the Agreement\") is effective as of [DATE] (the \"Effective Date\"). BETWEEN: [YOUR COMPANY NAME] (the \"Service Provider\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [CLIENT NAME] (the \"Client\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] RECITALS This Agreement sets forth the terms and conditions under which Client will provide Service Provider with certain Equipment under bailment and Service Provider will provide certain support services to Client on specified Service Provider premises (hereinafter referred to as the \"Service Provider Network Location(s)\"). WHEREAS, Service Provider is desirous and capable of providing support services for certain Client-Provided Equipment which interconnects to Service Provider transmission services; and WHEREAS, Client desires to have the Equipment supported by Service Provider in a designated portion of certain Service Provider Network Location(s), as set forth in Exhibit A of this agreement (hereinafter referred to as the \"Location and Equipment Summary\"), which is attached hereto and made a part hereof; and WHEREAS, Client and Service Provider (hereinafter referred to cumulatively as the \"Parties\" and singularly as the \"Party\") have agreed on the terms which shall govern the bailment and support of the Equipment as set forth in Exhibit B of this agreement (hereinafter referred to as the \"Statement of Work\"), which is attached hereto and made a part hereof, and as set forth in Exhibit C of this agreement (hereinafter referred to as the \"Non-Recurring and Monthly Recurring Pricing Summary\"), which is attached hereto and made a part hereof; NOW, THEREFORE, in consideration of the mutual agreements and promises contained herein and for other good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, the Parties agree as follows: UNDERTAKINGS Client will provide for the inside delivery of the Equipment at the Service Provider Network Location(s) as specified in the Location and Equipment Summary with proper and timely notification as specified in the Statement of Work. Client will install the Equipment at the Service Provider Network Location(s) as specified in the Location and Equipment Summary in accordance with Service Provider and Industry standards and practices as specified in the Statement of Work. Service Provider will connect the Equipment to Service Provider services at the Service Provider Network Location(s) as specified in the Location and Equipment Summary in accordance with Service Provider standards and practices as specified in the Statement of Work. Service Provider will hold the Equipment in bailment for use only at the Service Provider Network Location(s) as specified in the Location and Equipment Summary and only for the purposes contemplated herein. During the term of the bailment, Service Provider shall provide space, power, testing, environment and other support services for the Equipment as set forth in the Statement of Work and Service Provider shall have no other responsibility for the Equipment. Client shall cooperate fully with Service Provider in the provision of these support services and agrees to perform those activities identified as Client Responsibilities in the Statement of Work. TERM AND TERMINATION The initial term of this Agreement shall commence on the [DATE], shall continue for a period of [NUMBER] years, and then shall terminate on [DATE]. This Agreement is binding when executed by Client and subsequently accepted by Service Provider and once accepted by Service Provider, the rates and charges provided in this Agreement will be effective from the first day of the next billing cycle following Client's signature date (the \"Effective Date\"). Either Party may terminate this Agreement following the giving of [NUMBER] calendar days prior written notice of termination to the other Party. If Client terminates this Agreement prior to the expiration of the initial [NUMBER] year term, Client will pay Service Provider, in addition to all other charges due, per Service Provider Network Location, which amount shall represent liquidated damages that Client agrees are reasonable. Client shall remove its Equipment from the Service Provider Network Location(s) within [NUMBER] calendar days of the termination of this Agreement and, if Client fails to do so, Service Provider may itself remove the Equipment and store the same at Client's expense and at Client's sole risk. Any expenditure by Service Provider for the removal and storage of the Equipment shall bear interest at the lesser of [%] per annum or the maximum rate permitted by law. The rights and duties in Article D, \"Warranty and Liability\" shall survive the termination of this Agreement. FINANCIAL PROVISIONS Client shall pay Service Provider a non-recurring fee for Site Preparation, Additional AC or DC Power Circuits and Circuit Interconnection at each of the Service Provider Network Location(s) as set forth in the Non-Recurring and Monthly Recurring Pricing Summary. Client shall pay Service Provider on a monthly recurring basis for Location Management Fee(s), an Uninterruptable Power Supply (UPS) for [115V OR OTHER] AC Power Circuits and for Service Provider First-Level Maintenance Support at each of the Service Provider Network Location(s) as set forth in the Non-Recurring and Monthly Recurring Pricing Summary. Client shall pay Service Provider a one time charge of [AMOUNT per circuit when, at the Client's request, Service Provider provided cabling is added, moved or changed after the initial Site Preparation work listed in the Equipment and Location Summary is completed by Service Provider. This charge is in addition to any other charges specified in the applicable tariff or contract from the entity from which the facility or service is obtained. For equipment moves made pursuant to Client's request, Client shall pay for each unit of Equipment this is moved to a different location within the same Service Provider Network Location after the initial Site Preparation work listed in the Equipment and Location Summary is completed by Service Provider. Client shall pay directly or reimburse Service Provider, as applicable, for all taxes, duties, and similar liabilities which may result from this Agreement, or any support services specified hereunder, exclusive of taxes based on Service Provider's net income. All invoices shall be due and payable in [CURRENCY] within [NUMBER] calendar days upon receipt as set forth in the Non-Recurring and Monthly Recurring Pricing Summary. WARRANTY AND LIABILITY Service Provider warrants that its undertakings hereunder shall be performed in a professional and workmanlike manner and that it will provide Support Services in accordance with this Agreement. NO OTHER WARRANTIES ARE EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ANYWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Client warrants that it has the unrestricted right to place the Equipment at Service Provider's Location(s) listed in the Location and Equipment Summary for the term of this Agreement. Except as otherwise set forth herein, neither Party shall be deemed negligent, at fault or liable in any respect to the other for any delay, interruption or failure in performance hereunder resulting from fire, flood, water, the elements, explosions, acts of God, war, accidents, labor disputes, strikes, shortages of equipment or suppliers, unavailability of transportation or other cause beyond the reasonable control of the Party delayed or prevented from performing.","Service Level Agreement","12",89,"https://templates.business-in-a-box.com/imgs/1000px/service-level-agreement-D778.png","https://templates.business-in-a-box.com/imgs/250px/778.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#778.xml",{"title":6,"description":6},[114,117],{"label":115,"url":116},"Software & Technology","software-technology-business",{"label":115,"url":116},"service level agreement","/template/service-level-agreement-D778",{"description":121,"descriptionCustom":6,"label":122,"pages":8,"size":9,"extension":10,"preview":123,"thumb":124,"svgFrame":125,"seoMetadata":126,"parents":128,"keywords":127,"url":135},"NON-DISCLOSURE AGREEMENT (NDA) This Non-Disclosure Agreement (the \"Agreement\") is made and effective [DATE], BETWEEN: [YOUR COMPANY NAME] (the \"Disclosing Party\"), a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] AND: [RECEIVING PARTY NAME] (the \"Receiving Party\"), an individual with his main address located at OR a corporation organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] WHEREAS, Receiving Party has been or will be engaged in the performance of work on [DESCRIBE]; and in connection therewith will be given access to certain confidential and proprietary information; and WHEREAS, Receiving Party and Disclosing Party wish to evidence by this Agreement the manner in which said confidential and proprietary material will be treated. NOW, THEREFORE, it is agreed as follows: NON-DISCLOSURE OF CONFIDENTIAL INFORMATION Both Parties understand and agree that each Party may have access to the confidential information of the other party. For the purposes of this Agreement, \"Confidential Information\" means proprietary and confidential information about the Disclosing Party's (or it's suppliers') business or activities. Such information includes all business, financial, technical, and other information marked or designated by such Party as \"confidential\" or \"proprietary.\" Confidential Information also includes information which, by the nature of the circumstances surrounding the disclosure, ought in good faith to be treated as confidential. For the purposes of this Agreement, Confidential Information does not include: Information that is currently in the public domain or that enters the public domain after the signing of this Agreement. Information a Party lawfully receives from a third Party without restriction on disclosure and without breach of a non-disclosure obligation. Information that the Receiving Party knew prior to receiving any Confidential Information from the Disclosing Party. Information that the Receiving Party independently develops without reliance on any Confidential Information from the Disclosing Party. Each Party agrees that it will not disclose to any third Party or use any Confidential Information disclosed to it by the other Party except when expressly permitted in writing by the other Party. Each Party also agrees that it will take all reasonable measures to maintain the confidentiality of all Confidential Information of the other Party in its possession or control. TERM The term of this Agreement is [number] of [years/months] from the date of execution by both Parties. TITLE The Receiving Party agrees that all Confidential Information furnished by the Disclosing Party shall remain the sole property of the Disclosing Party. DISCLAIMER","Non Disclosure Agreement Nda","https://templates.business-in-a-box.com/imgs/1000px/non-disclosure-agreement-nda-D12692.png","https://templates.business-in-a-box.com/imgs/250px/12692.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#12692.xml",{"title":127,"description":6},"non disclosure agreement nda",[129,132],{"label":130,"url":131},"Legal Agreements","business-legal-agreements",{"label":133,"url":134},"Confidentiality Agreements","confidentiality-agreement","/template/non-disclosure-agreement-nda-D12692",{"description":137,"descriptionCustom":6,"label":138,"pages":90,"size":139,"extension":10,"preview":140,"thumb":141,"svgFrame":142,"seoMetadata":143,"parents":144,"keywords":148,"url":149},"INDEPENDENT CONTRACTOR AGREEMENT This Independent Contractor Agreement (\"Agreement\") is made and effective [Date], BETWEEN: [INDEPENDENT CONTRACTOR NAME] (the \"Independent Contractor\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [COMPLETE ADDRESS] AND: [YOUR COMPANY NAME] (the \"Company\"), a company organized and existing under the laws of the [State/Province] of [STATE/PROVINCE], with its head office located at: [YOUR COMPLETE ADDRESS] RECITALS Independent Contractor is engaged in providing [Describe] business services, its Employer Tax I.D. Number is [Insert], and its Business License Number is [insert]. Independent Contractor has complied with all Federal, State, and local laws regarding business permits, sales permits, licenses, reporting requirements, tax withholding requirements, and other legal requirements of any kind that may be required to carry out said business and the Scope of Work which is to be performed as an Independent Contractor pursuant to this Agreement. Independent Contractor is or remains open to conducting similar tasks or activities for clients other than the Company and holds themselves out to the public to be a separate business entity. Company desires to engage and contract for the services of the Independent Contractor to perform certain tasks as set forth below. Independent Contractor desires to enter into this Agreement and perform as an independent contractor for the company and is willing to do so on the terms and conditions set forth below. NOW, THEREFORE, in consideration of the above recitals and the mutual promises and conditions contained in this Agreement, the Parties agree as follows: TERMS This Agreement shall be effective commencing [Date], and shall continue until terminated at the completion of the Scope of Work which shall occur no later than [Date] or by either party as otherwise provided herein. STATUS OF INDEPENDENT CONTRACTOR This Agreement does not constitute a hiring by either party. It is the parties intentions that Independent Contractor shall have an independent contractor status and not be an employee for any purposes, including, but not limited to, [laws]. Independent Contractor shall retain sole and absolute discretion in the manner and means of carrying out their activities and responsibilities under this Agreement. This Agreement shall not be considered or construed to be a partnership or joint venture, and the Company shall not be liable for any obligations incurred by Independent Contractor unless specifically authorized in writing. Independent Contractor shall not act as an agent of the Company, ostensibly or otherwise, nor bind the Company in any manner, unless specifically authorized to do so in writing. TASKS, DUTIES, AND SCOPE OF WORK Independent Contractor agrees to devote as much time, attention, and energy as necessary to complete or achieve the following: [Describe]. The above to be referred to in this Agreement as the \"Scope of Work\". It is expected that the Scope of Work will completed by [Date]. Independent Contractor shall additionally perform any and all tasks and duties associated with the Scope of Work set forth above, including but not limited to, work being performed already or related change orders. Independent Contractor shall not be entitled to engage in any activities which are not expressly set forth by this Agreement. The books and records related to the Scope of Work set forth in this Agreement shall be maintained by the Independent Contractor at the Independent Contractor's principal place of business and open to inspection by Company during regular working hours. Documents to which Company will be entitled to inspect include, but are not limited to, any and all contract documents, change orders/purchase orders and work authorized by Independent Contractor or Company on existing or potential projects related to this Agreement. Independent Contractor shall be responsible to the management and directors of Company, but Independent Contractor will not be required to follow or establish a regular or daily work schedule. Supply all necessary equipment, materials and supplies. Independent Contractor will not rely on the equipment or offices of Company for completion of tasks and duties set forth pursuant to this Agreement. Any advice given Independent Contractors regarding the scope of work shall be considered a suggestion only, not an instruction. Company retains the right to inspect, stop, or alter the work of Independent Contractor to assure its conformity with this Agreement. ASSURANCE OF SERVICES Independent Contractor will assure that the following individuals (the \"Key Employees\") will be available to perform, and will perform, the Services hereunder until they are completed (identify by title and name as applicable): [Name of Key Employee, Title] [Name of Key Employee, Title] The Key Employees may be changed only with the prior written approval of the Company, which approval shall not be unreasonably withheld. COMPENSATION Independent Contractor shall be entitled to compensation for performing those tasks and duties related to the Scope of Work as follows: [Describe] Such compensation shall become due and payable to Independent Contractor in the following time, place, and manner: [Describe] NOTICE CONCERNING WITHHOLDING OF TAXES Independent Contractor recognizes and understands that it will receive a [specify tax] statement and related tax statements, and will be required to file corporate and/or individual tax returns and to pay taxes in accordance with all provisions of applicable Federal and State law. Independent Contractor hereby promises and agrees to indemnify the Company for any damages or expenses, including attorney's fees, and legal expenses, incurred by the Company as a result of independent contractor's failure to make such required payments. AGREEMENT TO WAIVE RIGHTS TO BENEFITS Independent Contractor hereby waives and foregoes the right to receive any benefits given by Company to its regular employees, including, but not limited to, health benefits, vacation and sick leave benefits, profit sharing plans, etc. This waiver is applicable to all non-salary benefits which might otherwise be found to accrue to the Independent Contractor by virtue of their services to Company, and is effective for the entire duration of Independent Contractor's agreement with Company. This waiver is effective independently of Independent Contractor's employment status as adjudged for taxation purposes or for any other purpose. Neither this Agreement, nor any duties or obligations under this Agreement may be assigned by either party without the consent of the other. TERMINATION This Agreement may be terminated prior to the completion or achievement of the Scope of Work by either party giving [number] days written notice. Such termination shall not prejudice any other remedy to which the terminating party may be entitled, either by law, in equity, or under this Agreement. NON-DISCLOSURE OF TRADE SECRETS, CUSTOMER LISTS AND OTHER PROPRIETARY INFORMATION Independent Contractor agrees not to disclose or communicate, in any manner, either during or after Independent Contractor's agreement with Company, information about Company, its operations, clientele, or any other information, that relate to the business of Company including, but not limited to, the names of its customers, its marketing strategies, operations, or any other information of any kind which would be deemed confidential, a trade secret, a customer list, or other form of proprietary information of Company. Independent Contractor acknowledges that the above information is material and confidential and that it affects the profitability of Company. ","Independent Contractor Agreement",62,"https://templates.business-in-a-box.com/imgs/1000px/independent-contractor-agreement-D160.png","https://templates.business-in-a-box.com/imgs/250px/160.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#160.xml",{"title":6,"description":6},[145],{"label":146,"url":147},"Consultant & Contractors","consulting-contractor-business","independent contractor agreement","/template/independent-contractor-agreement-D160",{"description":151,"descriptionCustom":6,"label":152,"pages":153,"size":154,"extension":10,"preview":155,"thumb":156,"svgFrame":157,"seoMetadata":158,"parents":159,"keywords":166,"url":167},"Employee Handbook Understanding employment at [YOUR COMPANY NAME] Revised on [DATE] Prepared By: [YOUR NAME] [YOUR JOB TITLE] Phone 555.555.5555 Email info@yourbusiness.com www.yourbusiness.com Table of Content Table of Content 2 Welcome to [YOUR COMPANY NAME]! 5 1. Organization Description 6 1.1 Introductory Statement 6 1.2 Customer Relations 6 1.3 Products and Services Provided 7 1.4 Facilities and Location(s) 7 1.5 The History of [YOUR COMPANY NAME] 7 1.6 Management Philosophy 7 1.7 Goals 8 2. The Employment 9 2.1 Nature of Employment 9 2.2 Employee Relations 9 2.3 Equal Employment Opportunity 10 2.4 Diversity 10 2.5 Business Ethics and Conduct 12 2.6 Personal Relationships in the Workplace 13 2.7 Conflicts of Interest 13 2.8 Outside Employment 14 2.9 Non-Disclosure 15 2.10 Disability Accommodation 16 2.11 Job Posting and Employee Referrals 17 2.12 Whistleblower Policy 18 2.13 Accident and First Aid 20 3. Employment Status and Records 21 3.1 Employment Categories 21 3.2 Access to Personnel Files 22 3.3 Personnel Data Changes 23 3.4 Probation Period 23 3.5 Employment Applications 24 3.6 Performance Evaluation 24 3.7 Job Descriptions 25 3.8 Salary Administration 25 3.9 Professional Development 26 4. Employee Benefit Programs 27 4.1 Employee Benefits 27 4.2 Vacation Benefits 27 4.3 Military Service Leave 29 4.4 Religious Observance 29 4.5 Holidays 29 4.6 Workers Insurance 30 4.7 Sick Leave Benefits 31 4.8 Bereavement Leave 32 4.9 Relocation Benefits 33 4.10 Educational Assistance 33 4.11 Health Insurance 34 4.12 Life Insurance 35 4.13 Long Term Disability 35 4.14 Marriage, Maternity and Parental Leave 36 5. Timekeeping / Payroll 40 5.1 Timekeeping 40 5.2 Paydays 40 5.3 Employment Termination 41 5.4 Administrative Pay Corrections 42 6. Work Conditions and Hours 43 6.1 Work Schedules 43 6.2 Absences 43 6.3 Jury Duty 45 6.4 Use of Phone and Mail Systems 45 6.5 Smoking 46 6.6 Meal Periods 46 6.7 Overtime 46 6.8 Use of Equipment 47 6.9 Telecommuting 47 6.10 Emergency Closing 48 6.11 Business Travel Expenses 49 6.12 Visitors in the Workplace 51 6.13 Computer and Email Usage 51 6.14 Internet Usage 52 6.15 Workplace Monitoring 54 6.16 Workplace Violence Prevention 55 7. Employee Conduct & Disciplinary Action 57 7.1 Employee Conduct and Work Rules 57 7.2 Sexual and Other Unlawful Harassment 58 7.3 Attendance and Punctuality 60 7.4 Personal Appearance 60 7.5 Return of Property 61 7.6 Resignation and Retirement 61 7.7 Security Inspections 62 7.8 Progressive Discipline 62 7.9 Problem Resolution 64 7.10 Workplace Etiquette 65 7.11 Suggestion Program 67 Acknowledgement of Receipt 68 Welcome to [YOUR COMPANY NAME]! On behalf of your colleagues, we welcome you to [YOUR COMPANY NAME] and wish you every success here. At [YOUR COMPANY NAME], we believe that each employee contributes directly to the growth and success of the company, and we hope you will take pride in being a member of our team. This handbook was developed to describe some of the expectations of our employees and to outline the policies, programs, and benefits available to eligible employees. Employees should become familiar with the contents of the employee handbook as soon as possible, for it will answer many questions about employment with [YOUR COMPANY NAME]. We believe that professional relationships are easier when all employees are aware of the culture and values of the organization. This guide will help you to better understand our vision for the future of our business and the challenges that are ahead. We hope that your experience here will be challenging, enjoyable, and rewarding. Again, welcome! [PRESIDENT NAME] President & CEO 1. Organization Description 1.1 Introductory Statement This handbook is designed to acquaint you with [YOUR COMPANY NAME] and provide you with information about working conditions, employee benefits, and some of the policies affecting your employment. You should read, understand, and comply with all provisions of the handbook. It describes many of your responsibilities as an employee and outlines the programs developed by [YOUR COMPANY NAME] to benefit employees. One of our objectives is to provide a work environment that is conducive to both personal and professional growth. No employee handbook can anticipate every circumstance or question about policy. As [YOUR COMPANY NAME] continues to grow, the need may arise and [YOUR COMPANY NAME] reserves the right to revise, supplement, or rescind any policies or portion of the handbook from time to time as it deems appropriate, in its sole and absolute discretion. Employees will be notified of such changes to the handbook as they occur. 1.2 Customer Relations Customers are among our organization's most valuable assets. Every employee represents [YOUR COMPANY NAME] to our customers and the public. The way we do our jobs presents an image of our entire organization. Customers judge all of us by how they are treated with each employee contact. Therefore, one of our first business priorities is to assist any customer or potential customer. Nothing is more important than being courteous, friendly, helpful, and prompt in the attention you give to customers. [YOUR COMPANY NAME] will provide customer relations and services training to all employees with extensive customer contact. Customers who wish to lodge specific comments or complaints should be directed to the [TITLE AND NAME OF THE PERSON RESPONSIBLE] for appropriate action. Our personal contact with the public, our manners on the telephone, and the communications we send to customers are a reflection not only of ourselves, but also of the professionalism of [YOUR COMPANY NAME]. Positive customer relations not only enhance the public's perception or image of [YOUR COMPANY NAME], but also pay off in greater customer loyalty and increased sales and profit. 1.3 Products and Services Provided You will find more information about our products and services by reading the [YOUR COMPANY NAME] Corporate Brochures. 1.4 Facilities and Location(s) Head Office: [ADDRESS] [CITY], [STATE] [ZIP/POSTAL CODE] [COUNTRY] 1.5 The History of [YOUR COMPANY NAME] [DESCRIBE THE HISTORY OF YOUR COMPANY HERE] 1.6 Management Philosophy [YOUR COMPANY NAME] management philosophy is based on responsibility and mutual respect. Our wishes are to maintain a work environment that fosters on personal and professional growth for all employees. Maintaining such an environment is the responsibility of every staff person. Because of their role, managers and supervisors have the additional responsibility to lead in a manner which fosters an environment of respect for each person. People who come to [YOUR COMPANY NAME] want to work here because we have created an environment that encourages creativity and achievement. [YOUR COMPANY NAME] aims to become a leader in [DESCRIBE YOUR COMPANY'S FIELD OF EXPERTISE]. The mainstay of our strategy will be to offer a level of client focus that is superior to that offered by our competitors. To help achieve this objective, [YOUR COMPANY NAME] seeks to attract highly motivated individuals that want to work as a team and share in the commitment, responsibility, risk taking, and discipline required to achieve our vision. Part of attracting these special individuals will be to build a culture that promotes both uniqueness and a bias for action. While we will be realistic in setting goals and expectations, [YOUR COMPANY NAME] will also be aggressive in reaching its objectives. This success will in turn enable [YOUR COMPANY NAME] to give its employees above average compensation and innovative benefits or rewards, key elements in helping us maintain our leadership position in the worldwide marketplace. 1.7 Goals [DESCRIBE YOUR COMPANY'S GOALS HERE] 2. The Employment 2","Employee Handbook","34",280,"https://templates.business-in-a-box.com/imgs/1000px/employee-handbook-D712.png","https://templates.business-in-a-box.com/imgs/250px/712.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#712.xml",{"title":6,"description":6},[160,163],{"label":161,"url":162},"Human Resources","human-resources",{"label":164,"url":165},"Company Policies","company-policies","employee handbook","/template/employee-handbook-D712",{"description":169,"descriptionCustom":6,"label":170,"pages":171,"size":9,"extension":10,"preview":172,"thumb":173,"svgFrame":174,"seoMetadata":175,"parents":177,"keywords":176,"url":183},"Risk Management Plan Your business slogan here. Prepared By: [YOUR NAME] [YOUR JOB TITLE] Phone 555.555.5555 Email info@yourbusiness.com www.yourbusiness.com Table of Contents Letter from the CEO 3 Executive Summary 4 1. Purpose of the Risk Management Plan 5 1.1 Purpose 5 1.2 Why Do We Need a Plan? 5 2. Risk Management Procedure 6 2.1 Process 6 2.2 Roles and Responsibilities 6 2.3 Risk Identification 8 2.4 Risk Analysis 8 2.5 Risk Response Planning 9 2.6 Risk Monitoring, Controlling, and Reporting 10 3.Tools and Practices 11 4. Closing a Risk 12 5. Lessons Learned 13 Letter from the CEO Every business faces the possibility of unexpected incidents like loss of funds, or injury to staff, customers, or visitors. Hence, every company needs to properly identify the key risks that can impact their establishment. These risks should be in two classifications, which are those that have immediate or early effect and futuristic ones. In [COMPANY NAME], we prioritize the importance of having an actionable Risk Management Plan for members of the company. The stakeholders can easily and proactively identify and review the impact of all possible risks to the company. Based on the procedure in this document, [COMPANY NAME] trains its staff to avoid and minimize the effect of each risk. In extreme cases, the document also helps the company have an actionable plan towards coping with the risk's impact. In the following pages, you will discover how [COMPANY NAME] plans to manage risks within the premises of the organization. This document focuses on the various types of risks that may occur in the company, including the hazard risks, business risks, and strategic risks. It's in everyone's interest that they stay aware of the plan in order to be prepared. Enjoy your reading and thank you for your participation. [CEO NAME] Executive Summary [COMPANY NAME] has developed a Risk Management Plan to prevent or manage various forms of loss, including physical, strategic, finance and operations. Write more content under the executive summary that provides a brief, but descriptive breakdown of the key components of the Risk Management Plan. In order to ensure that this summary is clear and comprehensive, it's advisable to write content under it after the other sections of the documents have been written. A first-time reader should be able to read the executive summary by itself and comprehend what the Risk Management Plan involves. Ensure that the summary stands alone and doesn't directly refer to any part of the plan. The executive summary should motivate readers to continue reading the rest of the document. It should be one to three pages in length. 1. Purpose of the Risk Management Plan 1.1 Purpose The purpose of this Risk Management Plan is to allow [COMPANY NAME] to identify and record possible risks to the company. This plan also serves the purpose of assessing each risk, responding to, monitoring, controlling, and reporting them. This specific plan defines how risks associated with [COMPANY NAME]'s project will easily get identified, analyzed, and effectively managed. Furthermore, this document highlights how [COMPANY NAME] will perform, record, and monitor risk management activities throughout various project lifecycles. Since unmanaged risks can prevent a project in [COMPANY NAME] from achieving its set objectives, risk management is imperative. Before the initiation of a project, the Risk Management Plan is imperative. It's also a crucial document during planning and execution of a project in [COMPANY NAME]. [ADD ANY ADDITIONAL CONTENT HERE.] 1.2 Why Do We Need a Plan? A Risk Management Plan is an important component in every project lifecycle. It ensures that risks are generally managed properly. With a Risk Management Plan, there's a higher chance for a project to be successful. Here's why we need a plan: To reduce negative risks To report risks to senior management, including the project sponsor and team To increase the impact of opportunities throughout the project lifecycle [ADD ANY ADDITIONAL CONTENT HERE.] 2. Risk Management Procedure 2.1 Process [Give a detailed breakdown of the required steps for responding to project risks in the company.] In [COMPANY NAME], the project manager, working alongside the project team and sponsors, ensures that risks are identified effectively. The individual responsible also ensures risks are analyzed and managed carefully throughout the project lifecycle. The project team in [COMPANY NAME] identifies risks as early as possible to minimize the impact of risks. The steps to carefully identifying, analyzing, and managing the risk are stated in later sections of the document. [PROJECT MANAGER'S NAME OR OTHER DESIGNEE] is the risk manager assigned for this project. 2","Risk Management Plan","13","https://templates.business-in-a-box.com/imgs/1000px/risk-management-plan-D13391.png","https://templates.business-in-a-box.com/imgs/250px/13391.png","https://templates.business-in-a-box.com/svgs/docviewerWebApp1.html?v6#13391.xml",{"title":176,"description":6},"risk management plan",[178,180],{"label":18,"url":179},"business-plan-kit",{"label":181,"url":182},"Starting a Business","starting-a-business","/template/risk-management-plan-D13391",false,{"seo":186,"reviewer":198,"legal_disclaimer":202,"quick_facts":203,"at_a_glance":205,"personas":209,"variants":234,"glossary":262,"clauses":296,"how_to_fill":347,"common_mistakes":388,"faqs":413,"industries":441,"comparisons":466,"diy_vs_lawyer":481,"jurisdictions":494,"related_template_ids_curated":515,"schema":528,"classification":529},{"meta_title":187,"meta_description":188,"primary_keyword":189,"secondary_keywords":190},"Business Process Mapping Template | BIB","Free business process mapping template in Word. Document workflows, assign responsibilities, and standardize operations.","business process mapping template",[191,192,193,194,195,196,197],"business process mapping template word","business process mapping template free","process mapping document template","business process map example","workflow mapping template","standard operating procedure map","business process flow template",{"name":199,"credential":200,"reviewed_date":201},"Bruno Goulet","CEO, Business in a Box","2026-05-02",true,{"difficulty":204,"legal_review_recommended":202,"signature_required":202,"notarization_required":184},"medium",{"what_it_is":206,"when_you_need_it":207,"whats_inside":208},"A Business Process Mapping document is a formal record that captures, in structured written and visual form, the sequential steps, decision points, assigned roles, inputs, outputs, and governance rules of a defined business process. This free Word download gives you a ready-to-edit framework you can tailor to any department, export as PDF, and use as an enforceable reference in contracts, service agreements, or compliance audits.\n","Use it when formalizing a repeatable workflow for onboarding, procurement, approvals, or service delivery — especially when multiple parties, vendors, or departments must follow the same steps with defined accountability. It is also required when a regulatory body, auditor, or contracting party asks for documented proof of process controls.\n","Process scope and objectives, defined roles and responsibilities (RACI), step-by-step workflow with decision logic, inputs and outputs at each stage, performance metrics, exception-handling procedures, version control, and approval and signature blocks for all accountable parties.\n",[210,214,218,222,226,230],{"title":211,"use_case":212,"icon_asset_id":213},"Operations managers","Standardizing cross-departmental workflows to reduce errors and rework","persona-operations-director",{"title":215,"use_case":216,"icon_asset_id":217},"Compliance officers","Documenting controls required for ISO, SOC 2, or regulatory audits","persona-compliance-officer",{"title":219,"use_case":220,"icon_asset_id":221},"Business analysts","Capturing current-state and future-state processes before a system migration","persona-business-analyst",{"title":223,"use_case":224,"icon_asset_id":225},"IT and systems teams","Mapping data flows and integration touchpoints for ERP or CRM implementation","persona-it-manager",{"title":227,"use_case":228,"icon_asset_id":229},"HR managers","Formalizing employee onboarding and offboarding procedures with assigned ownership","persona-hr-manager",{"title":231,"use_case":232,"icon_asset_id":233},"Consultants and process improvement leads","Delivering documented as-is workflows to clients as a project deliverable","persona-consultant",[235,239,243,246,250,254,258],{"situation":236,"recommended_template":237,"slug":238},"Mapping a high-level end-to-end business process for executive review","Business Process Map (Summary Level)","business-process-management-D12896",{"situation":240,"recommended_template":241,"slug":242},"Documenting a detailed step-by-step operational procedure for front-line staff","Standard Operating Procedure (SOP)","hotel-standard-operating-procedure-D13703",{"situation":244,"recommended_template":245,"slug":238},"Capturing swim-lane workflows across multiple departments or roles","Cross-Functional Process Map",{"situation":247,"recommended_template":248,"slug":249},"Analyzing a process to identify waste and inefficiency for Lean or Six Sigma","Value Stream Map","value-chain-analysis-D13861",{"situation":251,"recommended_template":252,"slug":253},"Mapping data flows for GDPR, HIPAA, or privacy compliance purposes","Data Flow Diagram","affinity-diagram-D121",{"situation":255,"recommended_template":256,"slug":257},"Documenting an IT service or software deployment workflow","IT Process Flow Template","how-to-manage-cash-flow-D12585",{"situation":259,"recommended_template":260,"slug":261},"Outlining procurement or vendor approval steps with sign-off requirements","Procurement Process Map","procurement-policy-D13854",[263,266,269,272,275,278,281,284,287,290,293],{"term":264,"definition":265},"Process Map","A visual and written representation of the sequential steps, decision points, and roles involved in completing a defined business activity.",{"term":267,"definition":268},"RACI Matrix","A responsibility assignment chart identifying who is Responsible, Accountable, Consulted, and Informed for each step in a process.",{"term":270,"definition":271},"Swimlane Diagram","A process map format that organizes steps into horizontal or vertical lanes, each representing a different role, team, or system.",{"term":273,"definition":274},"Current State (As-Is)","The documented version of how a process actually operates today, before any improvement or redesign is applied.",{"term":276,"definition":277},"Future State (To-Be)","The designed version of a process showing how it should operate after improvements, automation, or restructuring are implemented.",{"term":279,"definition":280},"Decision Gate","A point in a process flow where a yes/no or multi-option condition determines which path the process follows next.",{"term":282,"definition":283},"KPI (Key Performance Indicator)","A measurable value used to evaluate whether a process is achieving its defined objectives within acceptable thresholds.",{"term":285,"definition":286},"Exception Handling","The documented procedure for managing scenarios where a process step fails, a condition is not met, or an input is outside normal parameters.",{"term":288,"definition":289},"Version Control","A system for tracking changes to a document over time, recording who made each change, when, and what was altered.",{"term":291,"definition":292},"Process Owner","The individual or role formally accountable for the performance, compliance, and ongoing maintenance of a defined process.",{"term":294,"definition":295},"Handoff Point","A step in the process where responsibility for an activity transfers from one role or system to another.",[297,302,307,312,317,322,327,332,337,342],{"name":298,"plain_english":299,"sample_language":300,"common_mistake":301},"Process identification and scope","Names the process being mapped, defines its start and end triggers, and explicitly states what is and is not included in scope.","Process Name: [PROCESS NAME]. Scope: This map covers the workflow from [START TRIGGER] through [END CONDITION]. Out of scope: [EXCLUDED ACTIVITIES OR SYSTEMS].","Defining scope so broadly that the map covers five sub-processes at once — the resulting document is unreadable and impossible to audit or enforce.",{"name":303,"plain_english":304,"sample_language":305,"common_mistake":306},"Objectives and success criteria","States the measurable goals the process is designed to achieve and the KPIs used to determine whether it is performing correctly.","Objective: [PROCESS OBJECTIVE]. Success criteria: [KPI 1] target of [VALUE] measured [FREQUENCY]; [KPI 2] target of [VALUE] measured [FREQUENCY].","Listing aspirational goals like 'improve efficiency' without attaching a measurable target — making it impossible to determine whether the process is working or needs revision.",{"name":308,"plain_english":309,"sample_language":310,"common_mistake":311},"Roles and responsibilities (RACI)","Assigns every process step to a specific role — identifying who performs the step, who is accountable for its outcome, and who must be consulted or informed.","Role: [ROLE TITLE]. Responsible for: [STEP(S)]. Accountable to: [MANAGER OR GOVERNANCE BODY]. Consulted: [ROLE(S)]. Informed: [ROLE(S)].","Assigning a step to a department rather than a named role or position — creating shared accountability that in practice means no accountability.",{"name":313,"plain_english":314,"sample_language":315,"common_mistake":316},"Step-by-step workflow","Documents each step in the process in sequential order, with the action required, the role performing it, and the expected output at completion.","Step [#]: [ACTION DESCRIPTION]. Performed by: [ROLE]. Input: [DOCUMENT OR DATA]. Output: [DELIVERABLE OR RECORD]. Completion criterion: [CONDITION].","Writing steps at such a high level that two people following the same map would perform the step differently — defeating the purpose of standardization.",{"name":318,"plain_english":319,"sample_language":320,"common_mistake":321},"Decision logic and branching conditions","Defines every decision point in the workflow — the condition evaluated, the possible outcomes, and the path taken for each.","Decision Gate [#]: [CONDITION EVALUATED]. If [OUTCOME A]: proceed to Step [X]. If [OUTCOME B]: proceed to Step [Y]. If [OUTCOME C]: escalate to [ROLE] within [TIMEFRAME].","Omitting decision gates entirely and drawing a straight-line flow — real processes have conditions, and omitting them means exceptions are handled inconsistently.",{"name":323,"plain_english":324,"sample_language":325,"common_mistake":326},"Inputs and outputs","Specifies what information, documents, or materials are required to begin each step and what is produced or recorded upon completion.","Inputs for Step [#]: [DOCUMENT / DATA / SYSTEM RECORD]. Outputs: [DELIVERABLE]. Stored in: [SYSTEM OR LOCATION]. Retention period: [DURATION].","Listing outputs without specifying where they are stored or who has access — creating gaps during audits when reviewers cannot locate the records.",{"name":328,"plain_english":329,"sample_language":330,"common_mistake":331},"Exception-handling procedures","Documents the approved response for each identified failure mode, edge case, or out-of-tolerance condition in the process.","Exception: [CONDITION]. Responsible role: [ROLE]. Required action: [STEP]. Escalation path if unresolved within [TIMEFRAME]: [ESCALATION CONTACT / COMMITTEE].","Including a single generic exception clause ('escalate to management') instead of defining specific exceptions by type — resulting in ad hoc responses that vary by person and incident.",{"name":333,"plain_english":334,"sample_language":335,"common_mistake":336},"Performance monitoring and review cycle","Sets the schedule and method for measuring process KPIs, reviewing outputs, and triggering a formal process update when performance falls outside targets.","KPIs reviewed [FREQUENCY] by [ROLE]. Review meeting: [SCHEDULE]. Trigger for process revision: [KPI] falls below [THRESHOLD] for [CONSECUTIVE PERIODS]. Revision owner: [ROLE].","Documenting a review cycle but not assigning ownership — the review never happens and the process map becomes outdated within six months.",{"name":338,"plain_english":339,"sample_language":340,"common_mistake":341},"Version control and change log","Records the document version number, the date of each revision, the nature of the change, and the name of the person who authorized it.","Version: [X.X]. Effective date: [DATE]. Change summary: [DESCRIPTION OF REVISION]. Revised by: [NAME / ROLE]. Approved by: [APPROVER NAME / ROLE].","Maintaining multiple copies of the map in different folders with no version number — teams end up following different versions of the process simultaneously.",{"name":343,"plain_english":344,"sample_language":345,"common_mistake":346},"Approval and sign-off block","Captures the signatures of the process owner, department head, and any compliance or legal reviewer, confirming the document has been reviewed and formally adopted.","Process Owner: [NAME / TITLE] — Signature: ___ Date: [DATE]. Department Head: [NAME / TITLE] — Signature: ___ Date: [DATE]. Compliance Reviewer: [NAME / TITLE] — Signature: ___ Date: [DATE].","Treating the sign-off block as optional because 'everyone already agreed verbally' — without a signed document, there is no enforceable record that any party accepted the defined process.",[348,353,358,363,368,373,378,383],{"step":349,"title":350,"description":351,"tip":352},1,"Define the process scope and trigger events","Write the process name and identify the exact start trigger (e.g., 'customer submits a purchase order') and the end condition (e.g., 'payment received and order closed in the system'). Explicitly list what is out of scope.","If you cannot state the start and end in one sentence each, the scope is too broad — split it into two separate process maps.",{"step":354,"title":355,"description":356,"tip":357},2,"List all roles involved and draft the RACI","Enumerate every role — internal and external — that touches the process. For each role, assign R, A, C, or I for each major step. Confirm that every step has exactly one Accountable owner.","If two roles are both marked Accountable for the same step, the process will stall at that point under real conditions — resolve the conflict before publishing.",{"step":359,"title":360,"description":361,"tip":362},3,"Document each step with action, input, and output","Write each step as a specific action verb phrase (e.g., 'Finance reviews invoice against PO'). Record the input required, the role performing the step, and the output or record produced.","Test each step by asking whether a new hire could perform it correctly without verbal instruction — if not, add detail.",{"step":364,"title":365,"description":366,"tip":367},4,"Add decision gates and branching logic","Identify every point in the workflow where a condition determines the next step. Document the condition, list all possible outcomes (typically two to four), and map each outcome to the correct next step or escalation path.","Walk through the map with someone from operations who has never seen it — they will surface decision points you assumed were obvious.",{"step":369,"title":370,"description":371,"tip":372},5,"Document exception-handling procedures","List the most common failure modes — late inputs, system errors, rejected approvals — and write a specific response for each. Assign a responsible role and a resolution timeframe.","Pull your top five exceptions from the last six months of incident or help-desk logs rather than guessing — real data produces far more useful procedures.",{"step":374,"title":375,"description":376,"tip":377},6,"Set KPIs and the review cycle","Define two to four measurable KPIs for the process (e.g., average cycle time, error rate, on-time completion percentage). Set targets, measurement frequency, and the threshold that triggers a formal revision.","Tie at least one KPI to a time measure and one to a quality measure — processes optimized only for speed often degrade in accuracy.",{"step":379,"title":380,"description":381,"tip":382},7,"Complete version control and obtain signatures","Assign the document a version number (start at 1.0), enter the effective date, and route to the process owner, department head, and any required compliance reviewer for signature.","Store the signed document in a single, access-controlled location and immediately archive any previous versions with a clear 'superseded' label.",{"step":384,"title":385,"description":386,"tip":387},8,"Communicate and train before the effective date","Share the finalized map with all roles listed in the RACI at least five business days before the effective date. Schedule a brief walkthrough for any step with a new or changed procedure.","A signed process map that no one has read is no more effective than no document at all — build a confirmation step into the launch checklist.",[389,393,397,401,405,409],{"mistake":390,"why_it_matters":391,"fix":392},"Mapping the ideal process instead of the actual process","A map of how the process should work — rather than how it does work — creates a gap between documentation and reality that auditors flag immediately and that frontline staff simply ignore.","Conduct structured interviews or observation sessions with the people who actually perform each step before drafting. Document the as-is state first, then design the to-be state as a separate document.",{"mistake":394,"why_it_matters":395,"fix":396},"Assigning accountability to a department instead of a named role","Departmental accountability means that when a step fails, everyone assumes someone else is responsible — resulting in no follow-up and repeat failures at the same point in the process.","Assign every step to a specific job title. If a role does not yet exist, flag it as a gap and assign a temporary owner by name until the role is filled.",{"mistake":398,"why_it_matters":399,"fix":400},"Omitting exception-handling procedures","Processes without documented exceptions generate inconsistent responses — two employees handling the same edge case in opposite ways, creating compliance exposure and customer experience failures.","Review at least three months of incident logs, tickets, or escalation emails to identify the most frequent exceptions, then document a specific response for each.",{"mistake":402,"why_it_matters":403,"fix":404},"No version control or change log","Teams operating from different versions of the same process map introduce errors, audit discrepancies, and contractual non-compliance that are difficult to trace back to their source.","Assign a version number and effective date to every published version, maintain a change log in the document footer, and store all superseded versions in a clearly labeled archive.",{"mistake":406,"why_it_matters":407,"fix":408},"Skipping the sign-off block","An unsigned process map has no formal authority — staff can claim they were unaware, management cannot enforce adherence, and auditors treat it as an informal working document rather than a control.","Route every process map through the process owner, department head, and any relevant compliance reviewer before the effective date, and collect wet or electronic signatures.",{"mistake":410,"why_it_matters":411,"fix":412},"Never reviewing or updating the map after initial publication","A process map that is 18 months old in a changing business environment is almost certainly inaccurate — and an inaccurate map actively misleads staff and auditors.","Build a mandatory review date into the document (typically 12 months from the effective date or immediately following any system change, reorganization, or regulatory update affecting the process).",[414,417,420,423,426,429,432,435,438],{"question":415,"answer":416},"What is a business process map?","A business process map is a structured document — combining written descriptions and visual flow diagrams — that records every step, decision point, role, input, and output in a defined business activity. It serves as the authoritative reference for how a process should be performed, who is accountable for each step, and what constitutes a successful outcome. Organizations use process maps to standardize operations, train staff, satisfy audits, and support system implementations.\n",{"question":418,"answer":419},"What is the difference between a process map and a standard operating procedure?","A process map focuses on the flow of a process — the sequence of steps, decision branches, and handoff points between roles, often presented visually as a flowchart or swimlane diagram. A standard operating procedure (SOP) is a text-heavy document that provides granular, step-by-step instructions for performing a single task within a process. Process maps show the big picture; SOPs provide the detail for individual steps. Most organizations use both — the map for navigation, the SOP for execution.\n",{"question":421,"answer":422},"Who should sign a business process mapping document?","At minimum, the process owner and the relevant department head should sign. For processes with compliance, legal, or financial implications, add the appropriate compliance officer, legal counsel, or CFO to the sign-off block. For processes governed by a third-party contract or service agreement, the counterparty may also need to acknowledge the documented procedure. Unsigned process maps carry no formal authority and are difficult to enforce.\n",{"question":424,"answer":425},"How detailed should a business process map be?","The appropriate level of detail depends on the audience and the consequence of deviation. A high-level map for executive review might have five to ten steps. An operational map used by frontline staff should have enough detail that a new employee could follow it without verbal coaching — typically 10 to 25 steps for most business processes. Maps used for regulatory compliance or ISO certification audits require the greatest specificity, including inputs, outputs, decision criteria, and exception paths.\n",{"question":427,"answer":428},"Is a business process mapping document legally binding?","A process map can be incorporated by reference into a legally binding contract — such as a service agreement, outsourcing contract, or franchise agreement — making adherence to the documented process a contractual obligation. On its own, a signed process map is generally enforceable as an internal governance document and can be used in employment, compliance, and regulatory proceedings as evidence of agreed procedures. Whether it rises to the level of a binding contract depends on the language used and the jurisdiction. Consider having a lawyer review process maps that will be attached to commercial agreements.\n",{"question":430,"answer":431},"How often should a business process map be updated?","A formal review should occur at least annually. Outside the scheduled review, update the map immediately whenever a relevant system changes, a role or department is restructured, a regulatory requirement shifts, or an audit finding reveals the documented process no longer matches actual operations. Each update should increment the version number, be logged in the change record, and go through the sign-off process before the new version takes effect.\n",{"question":433,"answer":434},"What notation or format should I use for a business process map?","BPMN 2.0 (Business Process Model and Notation) is the international standard for formal process diagrams and is required for some regulatory and ISO submissions. For most business purposes, a swimlane flowchart using standard shapes — rectangles for steps, diamonds for decisions, arrows for flow — is universally readable and sufficient. The Business in a Box Word template uses a structured written format with an accompanying flow diagram that works for audits, contracts, and operational reference without requiring specialized diagramming software.\n",{"question":436,"answer":437},"Can I attach a business process map to a vendor or outsourcing contract?","Yes — and it is good practice to do so when the vendor is performing a process that must meet specific standards, timelines, or compliance requirements. Attaching the map as a schedule or exhibit to the contract makes adherence to the documented steps a contractual obligation. Ensure both parties sign the map (or the schedule cover page) and that the contract includes a mechanism for updating the map when the process changes without requiring a full contract amendment.\n",{"question":439,"answer":440},"What is a RACI matrix and why does it belong in a process map?","A RACI matrix is a responsibility assignment tool that classifies every role involved in a process as Responsible (performs the step), Accountable (owns the outcome), Consulted (provides input before the step), or Informed (notified after the step). Including it in a process map eliminates ambiguity about ownership — the single most common cause of process failures at handoff points. Every step in the map should have exactly one Accountable role; having two creates a shared-accountability gap that guarantees the step will be mishandled during high-pressure situations.\n",[442,446,450,454,458,462],{"industry":443,"icon_asset_id":444,"specifics":445},"Financial services","industry-fintech","Anti-money laundering (AML) controls, loan origination workflows, and trade settlement procedures all require formally documented and signed process maps for regulatory examination by the FCA, SEC, or OSFI.",{"industry":447,"icon_asset_id":448,"specifics":449},"Healthcare","industry-healthtech","Patient intake, medication administration, and claims processing workflows must be documented to HIPAA standards and reviewed during Joint Commission or CMS audits.",{"industry":451,"icon_asset_id":452,"specifics":453},"Manufacturing","industry-manufacturing","ISO 9001 certification requires documented control of production and quality processes, including version-controlled maps with defined inputs, outputs, and responsible roles at each step.",{"industry":455,"icon_asset_id":456,"specifics":457},"Technology / SaaS","industry-saas","SOC 2 Type II audits require documented evidence of change management, incident response, and access provisioning processes — signed process maps are primary audit artifacts.",{"industry":459,"icon_asset_id":460,"specifics":461},"Professional services","industry-professional-services","Consulting and outsourcing firms attach process maps to managed-service contracts to define service delivery standards, escalation paths, and performance obligations for each engagement.",{"industry":463,"icon_asset_id":464,"specifics":465},"Government and public sector","industry-government","Procurement, grants management, and citizen-service delivery processes must be formally documented and signed to meet public accountability standards and freedom-of-information obligations.",[467,470,473,477],{"vs":241,"vs_template_id":468,"summary":469},"D{SOP_PLACEHOLDER_ID}","A standard operating procedure provides granular, text-based instructions for executing a single task — it is the detailed script for one step. A business process map shows the entire workflow across multiple roles and steps, including decision logic and handoff points. Use the process map to design and govern the end-to-end flow; use the SOP to give frontline staff the precise actions for each step within that flow.",{"vs":89,"vs_template_id":471,"summary":472},"project-plan-D1252","A project plan documents the tasks, milestones, timeline, and resources for a one-time initiative with a defined end date. A business process map documents a repeatable, ongoing operational workflow with no fixed end date. Process maps govern how routine work is done every day; project plans govern how a specific change or deliverable gets built.",{"vs":474,"vs_template_id":475,"summary":476},"Service Level Agreement (SLA)","service-level-agreement-D13282","A service level agreement defines the performance standards — uptime, response time, quality thresholds — that a service provider must meet. A business process map documents how the service is delivered step by step. An SLA sets the what; a process map documents the how. Attaching a process map to an SLA as a schedule strengthens enforceability by specifying the delivery method alongside the performance standard.",{"vs":478,"vs_template_id":479,"summary":480},"Workflow Automation Specification","D{WORKFLOW_AUTOMATION_PLACEHOLDER_ID}","A workflow automation specification translates a process map into technical requirements for a software implementation — it is the engineering handoff document. A business process map is the governance document that defines what the process must do and who is accountable; the automation spec defines how software replicates it. The process map must exist and be signed off before an automation spec is written.",{"use_template":482,"template_plus_review":486,"custom_drafted":490},{"best_for":483,"cost":484,"time":485},"Internal operational documentation, audit preparation, ISO or SOC 2 readiness for standard business processes","Free","2–4 hours per process",{"best_for":487,"cost":488,"time":489},"Process maps attached to vendor contracts, outsourcing agreements, or regulatory submissions","$300–$800 for a legal or compliance review","1–3 days",{"best_for":491,"cost":492,"time":493},"Highly regulated industries (finance, healthcare, pharma), cross-border outsourcing with multi-jurisdiction compliance obligations, or litigation-sensitive process documentation","$1,500–$5,000+","1–3 weeks",[495,500,505,510],{"code":496,"name":497,"flag_asset_id":498,"note":499},"us","United States","flag-us","Process maps used as exhibits in commercial contracts are governed by the contract's choice-of-law clause. In heavily regulated sectors — financial services (SEC, FINRA), healthcare (HIPAA, CMS), and food production (FDA) — documented and signed process controls are a compliance requirement, not merely good practice. California, New York, and Texas courts have used process documentation as evidence in breach-of-contract and employment disputes.",{"code":501,"name":502,"flag_asset_id":503,"note":504},"ca","Canada","flag-ca","Federally regulated industries in Canada (banking, telecoms, transportation) require documented process controls reviewed by OSFI, CRTC, or Transport Canada respectively. In Quebec, process documents incorporated into commercial contracts must meet French-language requirements under the Charter of the French Language if the counterparty is a Quebec-based entity. Provincial privacy legislation (PIPEDA successor laws and Quebec Law 25) increasingly requires documented personal-data handling processes.",{"code":506,"name":507,"flag_asset_id":508,"note":509},"uk","United Kingdom","flag-uk","The UK Financial Conduct Authority (FCA) requires FCA-regulated firms to maintain documented operational processes as part of their Systems and Controls (SYSC) obligations. ISO 9001 certification — widely required in UK government procurement — mandates version-controlled, signed process documentation. Post-Brexit, UK GDPR requires data processing activities to be documented and, where applicable, covered by a signed data processing agreement referencing the relevant process map.",{"code":511,"name":512,"flag_asset_id":513,"note":514},"eu","European Union","flag-eu","GDPR Article 30 requires controllers and processors to maintain a Record of Processing Activities (ROPA), which in practice requires documented process maps for any workflow involving personal data. The EU AI Act (effective 2026) mandates documented risk and control processes for high-risk AI systems. ISO 9001 and ISO 27001 certification, required for many EU public procurement contracts, both mandate formally signed and version-controlled process documentation.",[516,517,518,519,520,521,522,523,524,525,526,527],"project-plan-D12775","service-level-agreement-D778","non-disclosure-agreement-nda-D12692","independent-contractor-agreement-D160","employee-handbook-D712","risk-management-plan-D13391","change-management-plan-D12880","business-requirements-document-D13873","pestle-analysis-D13747","swot-analysis-D12676","strategic-planning-template-D13857","quality-assurance-plan-D13381",{"emit_how_to":202,"emit_defined_term":202},{"primary_folder":530,"secondary_folder":531,"document_type":532,"industry":533,"business_stage":534,"tags":535,"confidence":541},"production-operations","standard-operating-procedures","guide","general","all-stages",[536,537,538,539,540],"process","operations","workflow","business-process-mapping","documentation",0.85,"\u003Ch2>What is a Business Process Mapping document?\u003C/h2>\n\u003Cp>A \u003Cstrong>Business Process Mapping\u003C/strong> document is a formal, signed record that captures every step, decision point, role, input, output, and exception-handling rule of a defined business process in structured written and visual form. It functions as the authoritative governance document for how a repeatable workflow must be performed — assigning clear accountability through a RACI matrix, setting measurable performance criteria, and recording version history so that all parties are always working from the same approved procedure. When incorporated into a contract or service agreement, it creates enforceable obligations that go beyond informal verbal instructions or undocumented tribal knowledge.\u003C/p>\n\u003Ch2>Why You Need This Document\u003C/h2>\n\u003Cp>Without a formally documented and signed process map, accountability gaps compound into operational failures: steps are performed differently by different people, handoffs between departments stall because no one knows who owns the next action, and auditors cannot verify that controls exist. In regulated industries — financial services, healthcare, manufacturing, and technology — the absence of documented process controls is itself a compliance violation that attracts fines, delayed certifications, and failed audits. When a vendor or outsourcing partner is involved, an undocumented process means you have no enforceable standard to hold them to when quality or timing falls short. This template gives you a structured, signature-ready starting point that works equally well as an internal governance document and as a binding schedule attached to a commercial agreement — eliminating ambiguity before it becomes a dispute.\u003C/p>\n",1781185957438]