[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241839-105":53,"doc-detail-241839-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","developing-a-data-plan-data-plan-template","Developing a Data Plan - Data Plan Template","","Developing a Data Plan outlines a step-by-step framework to reduce data management challenges by turning scattered databases and tools into a coherent data process and architecture. It explains the role of a CRM such as VAN, guides teams in defining program goals, membership, communications, data sources, and obstacles, then structures the plan around key components including metrics, list matching, infrastructure, and a wish list. The document also introduces dataset assessment, tagging or coding standards, data archiving, and maintaining a data dictionary to preserve definitions and avoid duplicated or lost work.",{"@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":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/developing-a-data-plan-data-plan-template/241839/",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/developing-a-data-plan-data-plan-template/241839.png","ImageObject",442,249,{"name":88,"@type":89},"Mabel","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-07","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":47},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of establishing a Data Plan for an organization?","Question",{"text":108,"@type":109},"A Data Plan helps reduce day-to-day data management challenges by creating a database structure that supports strategic goals and identifies areas for improvement. It also helps document and memorialize the processes an organization implements.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What questions should be considered before creating a Data Plan?",{"text":113,"@type":109},"Consider broad program goals and their connection to SIP, past program types and member interactions, how members are defined, communication channels, existing data types and locations, tool and integration needs, and biggest data obstacles.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the document recommend organizing and standardizing supporter information?",{"text":117,"@type":109},"Create a standard set of tags or codes for supporters to distinguish different supporter types and actions. Evaluate existing activist codes and survey questions, archive outdated items instead of deleting, and keep the system simple so tags can be expanded later.","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},241839,1790614760,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":47,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":76},7971474920318,"https://ap-avatar.wpscdn.com/avatar/74000ee537e6b0ca360?x-image-process=image/resize,m_fixed,w_180,h_180&k=1788430171632181674","Developing a Data Plan  \nMany organization utilize online databases, but it can feel overwhelming to approach all of the programs and features available. While there is no one size fits all solution, establishing a Data Plan can help alleviate some of the day to day challenges of data management. Analyst Institute has provided the following framework for the development of a simple data process & architecture that are widely applicable, no matter your area of advocacy. We walk through this step by step and have provided you with a blank template at the end for your use. While we spend some time discussing the Voter Action Network (VAN) because it is a common tool in advocacy work, this process can be useful no matter what CRM you may be utilizing. In addition to this document, we recommend the Member Engagement Guide and Building Power & Your List: Top 5 Data guidelines.  \nSoftware overview  \nThe Voter Action Network (VAN) 1 is a Customer Relationship Management (CRM) software developed for progressive organizations. It is unique in that it provides tools for organizing and political outreach, but primarily creates a database structure for organizations. While it may not serve every purpose for your organization, it is far more robust for progressive organizations than many private sector alternatives (such as Salesforce) .  \nDeveloping context  \nData and data systems should never exist in a vacuum. The goal of a database is to help you create a structure to inform and more easily attain your strategic goals. Before you begin a Data Plan, consider the following questions:  \n● What are your broad program goals generally and as they connect to SIP? Will you be focused on particular legislation, elections or other issues?  \n● What kind of programs have you run in the past? How did you interact with members, supporters and voters?  \n● Do you have “members”? If so, how do you define those members (ex: email sign-up, attends events, etc.)?  \n● How do you communicate with members and volunteers or voters? (ex: in person meetings, email, text, social media, etc.)  \n● What types of data do you currently track? Where does that data live? (Email platforms, excel sheets, etc.)  \n● What do you think your organization needs for your data to serve you better? This could include tool and data integration, staff time, better metrics, etc.  \n1 The technology company is NGPVAN, but the advocacy tools are often simply referred to as “VAN”  \n● What are your biggest data obstacles? (ex: staff need more training on making reports)  \nData plan  \nThe following is a structure for a Data Plan. We recommend breaking a Data Plan into several parts: metrics, list matching, infrastructure, and wish list. The primary goal is to identify areas for improvement and to memorialize processes that you implement. Whether you are using VAN or another CRM for the first time or have been utilizing it for years, this can be a useful exercise foryour organization.  \nMetrics  \nFirst, conduct a general dataset assessment  \n1. What types of data do you currently track? For each data set type, approximately how large is your list?  \na. Membership lists (opted in lists)  \nb. Voter file data  \nc. Email subscriptions  \nd. Text message subscriptions  \ne. Fundraising data, including payments  \nf. Other    \n2. For what geographies do you have voter file access? Are there any limitations to your usage of voter file data that you are aware of?2  \n3. Is there a software or repository other than VAN that you consider your master data set? For example, your email software may be your primary data source if you mainly interact with members via email.  \na. How much of your data do you think is currently captured in that master data set?(e.g. how much data is floating in random spreadsheets)  \nb. What do you think is missing?  \nNext, evaluate and create a simple data “architecture” Imagine entering a chaotic storage closet to find a box of staples, but you can’t because there’s no organi","cbCaiiJncuxIjoHo","https://ap.wps.com/l/cbCaiiJncuxIjoHo","pdf",219185,8,"English","# Developing a Data Plan\n## Software overview\n## Developing context\n## Data plan\n## Metrics\n## Next, evaluate and create a simple data architecture\n## Make a data dictionary","[{\"question\":\"What is the purpose of establishing a Data Plan for an organization?\",\"answer\":\"A Data Plan helps reduce day-to-day data management challenges by creating a database structure that supports strategic goals and identifies areas for improvement. It also helps document and memorialize the processes an organization implements.\"},{\"question\":\"What questions should be considered before creating a Data Plan?\",\"answer\":\"Consider broad program goals and their connection to SIP, past program types and member interactions, how members are defined, communication channels, existing data types and locations, tool and integration needs, and biggest data obstacles.\"},{\"question\":\"How does the document recommend organizing and standardizing supporter information?\",\"answer\":\"Create a standard set of tags or codes for supporters to distinguish different supporter types and actions. Evaluate existing activist codes and survey questions, archive outdated items instead of deleting, and keep the system simple so tags can be expanded later.\"}]","Developing a Data Plan - Data Plan Template | PDF",1789181884]