--- title: The Need for Data Governance Request Triage for Increased Effectiveness description: IData Blog | What to Avoid when Creating a Data Governance Roadmap image: https://blog.idatainc.com/hubfs/StockSnap_RZCTEGBC2V_doctor_requesttriage_BP.jpg --- [![iData_notag_tm](https://blog.idatainc.com/hs-fs/hubfs/iData_notag_tm.png?width=184&name=iData_notag_tm.png)](http://www.idatainc.com) # The Need for Data Governance Request Triage for Increased Effectiveness ## The Need for Data Governance Request Triage for Increased Effectiveness [July 07, 2023](https://blog.idatainc.com/archive/2023/07) By  [Jim Walery](https://blog.idatainc.com/author/jim-walery) In [data](https://blog.idatainc.com/tag/data), [governance](https://blog.idatainc.com/tag/governance), [request](https://blog.idatainc.com/tag/request), [ticket](https://blog.idatainc.com/tag/ticket), [intelligence](https://blog.idatainc.com/tag/intelligence) ![StockSnap_RZCTEGBC2V_doctor_requesttriage_BP](https://blog.idatainc.com/hs-fs/hubfs/StockSnap_RZCTEGBC2V_doctor_requesttriage_BP.jpg?width=345&height=230&name=StockSnap_RZCTEGBC2V_doctor_requesttriage_BP.jpg)It is difficult to hire an expert on the data at your organization. Usually, this expertise comes from years of working at your organization. You do not want your subject matter experts (key data stewards) to be handling data governance-related requests that could be handled by a non-subject matter expert. Typical requests could be creating a new report, clarification on an existing report, reporting a data quality issue, or having a definition created. Check out our [“Who is Requesting Data and the Types of Requests” blog post](https://blog.idatainc.com/who-types-data-requests). It is more effective and less expensive to hire a person to triage the data requests that come in and handle the ones that they can. This person would have the data stewardship role of support/triage. Your data governance team could receive a wide range of requests (much like requests made to an information technology team that probably uses a ticketing system) every day, from the routine to the complex. To give each requester stellar customer service for their data governance-related requests, you need structure to your data governance and data intelligence. Data governance request triage is a way to organize and streamline how data-related requests are handled. This blog post will discuss what data governance request triage is, what it looks like in action and traits necessary in a triage person. **History of Triage** First, let’s talk about the history of triage. The term triage comes from the French verb, trier, meaning to separate out or to sort. It was first used for medical purposes during World War I, when it referred to the way medics prioritized the treatment of soldiers wounded in battle. The term was adopted for business purposes to allocate limited budgetary and other resources (human) to competing needs. We believe that triage is perfect for data governance requests. Our recommendation is to put a data governance request triage process in place along with a triage person to save your valuable data steward resources and to resolve data governance-related requests quickly and effectively. **Data Governance Request Triage Defined** Data Governance request triage involves having a triage person in place and the process of categorizing and prioritizing requests and routing them, if necessary, to the data stewards best prepared to handle the request. Triage ensures requesters get the service they need when they need it. The triage person will first decide if a request needs any special attention, any additional information, or maybe can be handled by them without the need for an experienced data steward. Maybe the triage person can point the requester to a specific document in the data governance knowledge base and close the request without the assistance of a  subject matter expert. If the triage person cannot handle the request, then the request is put into the data governance request process and sent to the appropriate data steward. Data Governance request triage can help organize an influx of requests and get the simple requests handled quickly and the more complex requests handled by the right data steward with the right urgency. **What Data Governance Request Triage Looks Like in Action** Here is how the data governance request triage process looks like in action: - The request enters the request queue via defined data governance points of engagement. Check out our [“Understanding Data Governance Points of Engagement” blog post](https://blog.idatainc.com/understanding-points-of-engagement). Data consumers should know how to enter in data governance-related requests. This will be greatly helped if you have a data governance solution in place like the [Data Cookbook](http://www.datacookbook.com). - The request enters the data governance request triage process and is reviewed by the triage person. The request is examined by the triage person for urgency, missing information, and if it can it be handled without other data stewardship involvement. - If this request is urgent, then the triage person routes it to the appropriate data steward depending on the technical expertise or functional area (such as Human Resources) required. - If this request is missing information or is unclear, then the triage person routes it back to the requester for this additional information. This will save subject matter expert time. - If this request can be handled by the triage person, such as referring requester to a specific piece of data governance content, then the request can be closed without subject matter expert involvement. - When necessary or if requested, the triage person communicates the status of the request to the requester. - When seen, the triage person can communicate to the data governance committee or data stewards on issues that can be fixed in the data or data governance process or the data governance knowledge base.   **What the Triage Person Will Do** Here are some of the tasks that the triage person would do: - Efficiently and effectively handle incoming data governance requests and be the first point of contact. - Assess the urgency, severity, and impact of incoming requests to determine the appropriate level of response and prioritize them accordingly. Kick the request up to a manager or a data governance committee when appropriate. Collaborate with other team members to escalate complex or critical requests that require further expertise or resources. - Gather relevant information from the requester to better understand the nature of their request and gather missing or unclear request information so that the request can be handled effectively and efficiently. - Handle the request if possible, such as pointing the requester in the direction of a data governance knowledge base piece of content. - Provide effective communication with requesters, keeping them informed about progress of the request and coordinating with internal teams. - Contribute to the development and enhancement of the data governance processes, data governance tools (such as the [Data Cookbook](http://www.datacookbook.com)), and data governance knowledge base content to improve the efficiency and effectiveness of the organization. **Traits of an Ideal Triage Candidate** Check out our [“Soft Skills and Traits of a Good Data Steward” blog post](https://blog.idatainc.com/data-steward-soft-skills) for more information on what’s needed in a data steward and a triage person. But here are some traits that this triage individual should have: - Ability to think outside the box and find the right person to handle the request. Maybe it could go to a person who is not an official data steward (but might be someone who should be). - Passion for delivering great customer service and a strong commitment to client satisfaction. - Capability to work under pressure, manage multiple tasks, and prioritize workload while maintaining attention to detail. - Work well with cross-functional teams and effectively communicate and coordinate with others (requesters and data stewards) to ensure seamless service delivery. - Great communication skills – verbal and written. - Good documenter, be detailed and accurately record all relevant details of requests and resolutions, in the appropriate data governance solution (like the [Data Cookbook](http://www.datacookbook.com)) or ticketing system. **Some Other Thoughts** - You are trying to eliminate the need for requests and data steward involvement as much as possible. As your data governance content gets better (report specifications, data quality rules, data catalog entries, etc.), data consumers can find the information they need in the data governance knowledge base. So, this self-service will save the organization time and money, and eliminate many requests. - You want to automate the data governance process as much as possible. This includes routing the requests to the appropriate data steward automatically after triage review and request approval. - Besides having a data governance knowledge base in place, you want to have [data stewards](https://blog.idatainc.com/data-stewardship-resources) in place so that requests can be sent to them. Make sure to place your data stewards in the right roles that align with their strengths. When the right data stewards handles a request, the resolution time will go down, and your data governance request costs may also decrease. **Data Governance Request Triage Make Your Organization More Effective** Solid data governance request triage: - Saves subject matter expert (data steward) time thus saving the organization money as some requests could be handled by the lower costing triage person. - Addresses the most urgent requests earlier and sends them to data stewards who are most qualified to help. - Helps boost data governance metrics, such as average resolution time, average request cost, and response time. - Since requests will be handled more quickly, greater trust in the organization’s data will be gained as well as additional use of data governance content and processes. Usually this leads to additional requests which builds your data governance knowledge base. We hoped that this blog post convinced you about the need for a data governance triage person. This individual will save time and effort of your more experienced data stewards. And this individual will make the data governance process run smoother, thus increasing the use at your organization.  Additional resources (videos, blog posts, recorded webinars) on data governance and data intelligence can be found at [www.datacookbook.com/dg](http://www.datacookbook.com/dg). IData has a solution, the [Data Cookbook](http://www.datacookbook.com/tour/), that can aid the employees and the organization in its data governance, data intelligence, data stewardship and data quality initiatives. IData also has experts that can assist with data governance, reporting, integration and other technology services on an as needed basis. Feel free to contact us and let us know how we can assist.  [![Contact Us](https://no-cache.hubspot.com/cta/default/4171032/6765be6f-f024-407e-aadb-a1418a68ab0f.png)](https://cta-redirect.hubspot.com/cta/redirect/4171032/6765be6f-f024-407e-aadb-a1418a68ab0f) Photo Credit: StockSnap\_RZCTEGBC2V\_doctor\_requesttriage\_BP #B1265 ![Jim Walery](https://app.hubspot.com/settings/avatar/e2a751ec95ddcd02d65a750bc8aea9dc) ##### About the Author Jim Walery is a marketing professional who has been providing marketing services to technology companies for over 20 years and specifically those in higher education since 2010. Jim assists in getting the word out about the community via a variety of channels. Jim is knowledgeable in social media, blogging, collateral creation and website content. He is Inbound Marketing certified by HubSpot. Jim holds a B.A. from University of California, Irvine and a M.A. from Webster University. Jim can be reached at jwalery\[at\]idatainc.com. ### Subscribe to Email Updates ### Recent Posts ### Archives - [February 2018 (13)](https://blog.idatainc.com/archive/2018/02) - [May 2019 (6)](https://blog.idatainc.com/archive/2019/05) - [January 2019 (5)](https://blog.idatainc.com/archive/2019/01) - [February 2019 (5)](https://blog.idatainc.com/archive/2019/02) - [October 2019 (5)](https://blog.idatainc.com/archive/2019/10) - [March 2021 (5)](https://blog.idatainc.com/archive/2021/03) - [June 2021 (5)](https://blog.idatainc.com/archive/2021/06) - [July 2021 (5)](https://blog.idatainc.com/archive/2021/07) - [September 2021 (5)](https://blog.idatainc.com/archive/2021/09) - [March 2022 (5)](https://blog.idatainc.com/archive/2022/03) - [October 2018 (4)](https://blog.idatainc.com/archive/2018/10) - [March 2019 (4)](https://blog.idatainc.com/archive/2019/03) - [June 2019 (4)](https://blog.idatainc.com/archive/2019/06) - [July 2019 (4)](https://blog.idatainc.com/archive/2019/07) - [December 2019 (4)](https://blog.idatainc.com/archive/2019/12) - [April 2020 (4)](https://blog.idatainc.com/archive/2020/04) - [May 2020 (4)](https://blog.idatainc.com/archive/2020/05) - [June 2020 (4)](https://blog.idatainc.com/archive/2020/06) - [August 2020 (4)](https://blog.idatainc.com/archive/2020/08) - [January 2021 (4)](https://blog.idatainc.com/archive/2021/01) - [April 2021 (4)](https://blog.idatainc.com/archive/2021/04) - [May 2021 (4)](https://blog.idatainc.com/archive/2021/05) - [August 2021 (4)](https://blog.idatainc.com/archive/2021/08) - [January 2022 (4)](https://blog.idatainc.com/archive/2022/01) - [June 2022 (4)](https://blog.idatainc.com/archive/2022/06) - [July 2022 (4)](https://blog.idatainc.com/archive/2022/07) - [August 2022 (4)](https://blog.idatainc.com/archive/2022/08) - [November 2022 (4)](https://blog.idatainc.com/archive/2022/11) - [February 2023 (4)](https://blog.idatainc.com/archive/2023/02) - [September 2023 (4)](https://blog.idatainc.com/archive/2023/09) - [May 2018 (3)](https://blog.idatainc.com/archive/2018/05) - [November 2018 (3)](https://blog.idatainc.com/archive/2018/11) - [April 2019 (3)](https://blog.idatainc.com/archive/2019/04) - [August 2019 (3)](https://blog.idatainc.com/archive/2019/08) - [September 2019 (3)](https://blog.idatainc.com/archive/2019/09) - [November 2019 (3)](https://blog.idatainc.com/archive/2019/11) - [January 2020 (3)](https://blog.idatainc.com/archive/2020/01) - [February 2020 (3)](https://blog.idatainc.com/archive/2020/02) - [March 2020 (3)](https://blog.idatainc.com/archive/2020/03) - [July 2020 (3)](https://blog.idatainc.com/archive/2020/07) - [September 2020 (3)](https://blog.idatainc.com/archive/2020/09) - [October 2020 (3)](https://blog.idatainc.com/archive/2020/10) - [November 2020 (3)](https://blog.idatainc.com/archive/2020/11) - [December 2020 (3)](https://blog.idatainc.com/archive/2020/12) - [February 2021 (3)](https://blog.idatainc.com/archive/2021/02) - [October 2021 (3)](https://blog.idatainc.com/archive/2021/10) - [November 2021 (3)](https://blog.idatainc.com/archive/2021/11) - [December 2021 (3)](https://blog.idatainc.com/archive/2021/12) - [February 2022 (3)](https://blog.idatainc.com/archive/2022/02) - [May 2022 (3)](https://blog.idatainc.com/archive/2022/05) - [October 2022 (3)](https://blog.idatainc.com/archive/2022/10) - [January 2023 (3)](https://blog.idatainc.com/archive/2023/01) - [January 2024 (3)](https://blog.idatainc.com/archive/2024/01) - [June 2024 (3)](https://blog.idatainc.com/archive/2024/06) - [August 2024 (3)](https://blog.idatainc.com/archive/2024/08) - [September 2025 (3)](https://blog.idatainc.com/archive/2025/09) - [December 2025 (3)](https://blog.idatainc.com/archive/2025/12) - [March 2026 (3)](https://blog.idatainc.com/archive/2026/03) - [April 2026 (3)](https://blog.idatainc.com/archive/2026/04) - [May 2026 (3)](https://blog.idatainc.com/archive/2026/05) - [June 2026 (3)](https://blog.idatainc.com/archive/2026/06) - [July 2026 (3)](https://blog.idatainc.com/archive/2026/07) - [August 2026 (3)](https://blog.idatainc.com/archive/2026/08) - [December 2018 (2)](https://blog.idatainc.com/archive/2018/12) - [April 2022 (2)](https://blog.idatainc.com/archive/2022/04) - [September 2022 (2)](https://blog.idatainc.com/archive/2022/09) - [December 2022 (2)](https://blog.idatainc.com/archive/2022/12) - [March 2023 (2)](https://blog.idatainc.com/archive/2023/03) - [April 2023 (2)](https://blog.idatainc.com/archive/2023/04) - [May 2023 (2)](https://blog.idatainc.com/archive/2023/05) - [June 2023 (2)](https://blog.idatainc.com/archive/2023/06) - [July 2023 (2)](https://blog.idatainc.com/archive/2023/07) - [August 2023 (2)](https://blog.idatainc.com/archive/2023/08) - [October 2023 (2)](https://blog.idatainc.com/archive/2023/10) - [November 2023 (2)](https://blog.idatainc.com/archive/2023/11) - [February 2024 (2)](https://blog.idatainc.com/archive/2024/02) - [March 2024 (2)](https://blog.idatainc.com/archive/2024/03) - [April 2024 (2)](https://blog.idatainc.com/archive/2024/04) - [July 2024 (2)](https://blog.idatainc.com/archive/2024/07) - [September 2024 (2)](https://blog.idatainc.com/archive/2024/09) - [November 2024 (2)](https://blog.idatainc.com/archive/2024/11) - [December 2024 (2)](https://blog.idatainc.com/archive/2024/12) - [January 2025 (2)](https://blog.idatainc.com/archive/2025/01) - [February 2025 (2)](https://blog.idatainc.com/archive/2025/02) - [March 2025 (2)](https://blog.idatainc.com/archive/2025/03) - [April 2025 (2)](https://blog.idatainc.com/archive/2025/04) - [May 2025 (2)](https://blog.idatainc.com/archive/2025/05) - [June 2025 (2)](https://blog.idatainc.com/archive/2025/06) - [July 2025 (2)](https://blog.idatainc.com/archive/2025/07) - [August 2025 (2)](https://blog.idatainc.com/archive/2025/08) - [January 2026 (2)](https://blog.idatainc.com/archive/2026/01) - [February 2026 (2)](https://blog.idatainc.com/archive/2026/02) - [June 2013 (1)](https://blog.idatainc.com/archive/2013/06) - [July 2013 (1)](https://blog.idatainc.com/archive/2013/07) - [March 2014 (1)](https://blog.idatainc.com/archive/2014/03) - [May 2015 (1)](https://blog.idatainc.com/archive/2015/05) - [July 2015 (1)](https://blog.idatainc.com/archive/2015/07) - [August 2015 (1)](https://blog.idatainc.com/archive/2015/08) - [January 2017 (1)](https://blog.idatainc.com/archive/2017/01) - [March 2017 (1)](https://blog.idatainc.com/archive/2017/03) - [May 2017 (1)](https://blog.idatainc.com/archive/2017/05) - [June 2017 (1)](https://blog.idatainc.com/archive/2017/06) - [August 2017 (1)](https://blog.idatainc.com/archive/2017/08) - [November 2017 (1)](https://blog.idatainc.com/archive/2017/11) - [December 2017 (1)](https://blog.idatainc.com/archive/2017/12) - [January 2018 (1)](https://blog.idatainc.com/archive/2018/01) - [June 2018 (1)](https://blog.idatainc.com/archive/2018/06) - [July 2018 (1)](https://blog.idatainc.com/archive/2018/07) - [August 2018 (1)](https://blog.idatainc.com/archive/2018/08) - [September 2018 (1)](https://blog.idatainc.com/archive/2018/09) - [December 2023 (1)](https://blog.idatainc.com/archive/2023/12) - [May 2024 (1)](https://blog.idatainc.com/archive/2024/05) - [October 2024 (1)](https://blog.idatainc.com/archive/2024/10) - [October 2025 (1)](https://blog.idatainc.com/archive/2025/10) - [November 2025 (1)](https://blog.idatainc.com/archive/2025/11) - [September 2026 (1)](https://blog.idatainc.com/archive/2026/09) ### Categories - [2019 (1)](https://blog.idatainc.com/tag/2019) - [2020 (1)](https://blog.idatainc.com/tag/2020) - [2024 (1)](https://blog.idatainc.com/tag/2024) - [acceptance (1)](https://blog.idatainc.com/tag/acceptance) - [access (3)](https://blog.idatainc.com/tag/access) - [accountability (1)](https://blog.idatainc.com/tag/accountability) - [action (3)](https://blog.idatainc.com/tag/action) - [actions (3)](https://blog.idatainc.com/tag/actions) - [Admissions (1)](https://blog.idatainc.com/tag/admissions) - [adoption (6)](https://blog.idatainc.com/tag/adoption) - [adult (1)](https://blog.idatainc.com/tag/adult) - [advantages (1)](https://blog.idatainc.com/tag/advantages) - [agile (1)](https://blog.idatainc.com/tag/agile) - [agreements (1)](https://blog.idatainc.com/tag/agreements) - [ai (12)](https://blog.idatainc.com/tag/ai) - [analytics (22)](https://blog.idatainc.com/tag/analytics) - [answers (2)](https://blog.idatainc.com/tag/answers) - [approach (8)](https://blog.idatainc.com/tag/approach) - [areas (1)](https://blog.idatainc.com/tag/areas) - [artificial (17)](https://blog.idatainc.com/tag/artificial) - [assessment (11)](https://blog.idatainc.com/tag/assessment) - [assistance (1)](https://blog.idatainc.com/tag/assistance) - [at-risk (1)](https://blog.idatainc.com/tag/at-risk) - [avoid (2)](https://blog.idatainc.com/tag/avoid) - [back (1)](https://blog.idatainc.com/tag/back) - [barriers (2)](https://blog.idatainc.com/tag/barriers) - [base (4)](https://blog.idatainc.com/tag/base) - [begin (1)](https://blog.idatainc.com/tag/begin) - [benefit (3)](https://blog.idatainc.com/tag/benefit) - [benefits (7)](https://blog.idatainc.com/tag/benefits) - [best (26)](https://blog.idatainc.com/tag/best) - [BI (2)](https://blog.idatainc.com/tag/bi) - [binder (2)](https://blog.idatainc.com/tag/binder) - [blog (2)](https://blog.idatainc.com/tag/blog) - [book (1)](https://blog.idatainc.com/tag/book) - [brainstorming (1)](https://blog.idatainc.com/tag/brainstorming) - [business (25)](https://blog.idatainc.com/tag/business) - [buy (1)](https://blog.idatainc.com/tag/buy) - [buyin (6)](https://blog.idatainc.com/tag/buyin) - [capabilities (1)](https://blog.idatainc.com/tag/capabilities) - [cases (1)](https://blog.idatainc.com/tag/cases) - [catalog (12)](https://blog.idatainc.com/tag/catalog) - [ccpa (1)](https://blog.idatainc.com/tag/ccpa) - [CDO (3)](https://blog.idatainc.com/tag/cdo) - [certification (2)](https://blog.idatainc.com/tag/certification) - [challenges (5)](https://blog.idatainc.com/tag/challenges) - [change (3)](https://blog.idatainc.com/tag/change) - [checklist (1)](https://blog.idatainc.com/tag/checklist) - [chief (3)](https://blog.idatainc.com/tag/chief) - [citizen (1)](https://blog.idatainc.com/tag/citizen) - [clean (1)](https://blog.idatainc.com/tag/clean) - [cleanup (1)](https://blog.idatainc.com/tag/cleanup) - [cloud (1)](https://blog.idatainc.com/tag/cloud) - [collaboration (1)](https://blog.idatainc.com/tag/collaboration) - [committee (13)](https://blog.idatainc.com/tag/committee) - [communication (27)](https://blog.idatainc.com/tag/communication) - [community (2)](https://blog.idatainc.com/tag/community) - [complexity (1)](https://blog.idatainc.com/tag/complexity) - [compliance (3)](https://blog.idatainc.com/tag/compliance) - [components (3)](https://blog.idatainc.com/tag/components) - [connectors (2)](https://blog.idatainc.com/tag/connectors) - [consulting (1)](https://blog.idatainc.com/tag/consulting) - [consumer (3)](https://blog.idatainc.com/tag/consumer) - [content (43)](https://blog.idatainc.com/tag/content) - [contents (4)](https://blog.idatainc.com/tag/contents) - [continuous (1)](https://blog.idatainc.com/tag/continuous) - [control (1)](https://blog.idatainc.com/tag/control) - [controlling (1)](https://blog.idatainc.com/tag/controlling) - [cookbook (32)](https://blog.idatainc.com/tag/cookbook) - [corporation (1)](https://blog.idatainc.com/tag/corporation) - [creation (7)](https://blog.idatainc.com/tag/creation) - [CRM (4)](https://blog.idatainc.com/tag/crm) - [cultural (1)](https://blog.idatainc.com/tag/cultural) - [culture (12)](https://blog.idatainc.com/tag/culture) - [curated (3)](https://blog.idatainc.com/tag/curated) - [curating (3)](https://blog.idatainc.com/tag/curating) - [custodian (1)](https://blog.idatainc.com/tag/custodian) - [customer (3)](https://blog.idatainc.com/tag/customer) - [cybersecurity (1)](https://blog.idatainc.com/tag/cybersecurity) - [cycle (1)](https://blog.idatainc.com/tag/cycle) - [dashboards (2)](https://blog.idatainc.com/tag/dashboards) - [data (312)](https://blog.idatainc.com/tag/data) - [Data Cookbook (185)](https://blog.idatainc.com/tag/data-cookbook) - [databases (3)](https://blog.idatainc.com/tag/databases) - [decision (2)](https://blog.idatainc.com/tag/decision) - [definition (7)](https://blog.idatainc.com/tag/definition) - [definitions (9)](https://blog.idatainc.com/tag/definitions) - [deliverables (5)](https://blog.idatainc.com/tag/deliverables) - [department (1)](https://blog.idatainc.com/tag/department) - [description (1)](https://blog.idatainc.com/tag/description) - [desk (3)](https://blog.idatainc.com/tag/desk) - [dictionary (4)](https://blog.idatainc.com/tag/dictionary) - [digital (1)](https://blog.idatainc.com/tag/digital) - [dimensions (1)](https://blog.idatainc.com/tag/dimensions) - [direction (1)](https://blog.idatainc.com/tag/direction) - [discovery (1)](https://blog.idatainc.com/tag/discovery) - [distribution (1)](https://blog.idatainc.com/tag/distribution) - [dx (1)](https://blog.idatainc.com/tag/dx) - [dynamic (1)](https://blog.idatainc.com/tag/dynamic) - [ed (19)](https://blog.idatainc.com/tag/ed) - [education (84)](https://blog.idatainc.com/tag/education) - [educause (3)](https://blog.idatainc.com/tag/educause) - [efficiencies (1)](https://blog.idatainc.com/tag/efficiencies) - [efficiency (1)](https://blog.idatainc.com/tag/efficiency) - [elemens (1)](https://blog.idatainc.com/tag/elemens) - [elements (4)](https://blog.idatainc.com/tag/elements) - [emergent (1)](https://blog.idatainc.com/tag/emergent) - [employee (4)](https://blog.idatainc.com/tag/employee) - [enablement (1)](https://blog.idatainc.com/tag/enablement) - [enforcement (1)](https://blog.idatainc.com/tag/enforcement) - [engagement (19)](https://blog.idatainc.com/tag/engagement) - [entry (4)](https://blog.idatainc.com/tag/entry) - [erp (5)](https://blog.idatainc.com/tag/erp) - [ETL (2)](https://blog.idatainc.com/tag/etl) - [examples (2)](https://blog.idatainc.com/tag/examples) - [executive (1)](https://blog.idatainc.com/tag/executive) - [expectations (1)](https://blog.idatainc.com/tag/expectations) - [failure (1)](https://blog.idatainc.com/tag/failure) - [features (1)](https://blog.idatainc.com/tag/features) - [flow (4)](https://blog.idatainc.com/tag/flow) - [football (1)](https://blog.idatainc.com/tag/football) - [forum (1)](https://blog.idatainc.com/tag/forum) - [framework (20)](https://blog.idatainc.com/tag/framework) - [friction (1)](https://blog.idatainc.com/tag/friction) - [front (1)](https://blog.idatainc.com/tag/front) - [functional (4)](https://blog.idatainc.com/tag/functional) - [gaps (1)](https://blog.idatainc.com/tag/gaps) - [gatekeeper (1)](https://blog.idatainc.com/tag/gatekeeper) - [GDPR (2)](https://blog.idatainc.com/tag/gdpr) - [getting (2)](https://blog.idatainc.com/tag/getting) - [glossary (27)](https://blog.idatainc.com/tag/glossary) - [governance (297)](https://blog.idatainc.com/tag/governance) - [government (1)](https://blog.idatainc.com/tag/government) - [guidance (1)](https://blog.idatainc.com/tag/guidance) - [HE (42)](https://blog.idatainc.com/tag/he) - [health (2)](https://blog.idatainc.com/tag/health) - [healthcare (1)](https://blog.idatainc.com/tag/healthcare) - [HEDW (1)](https://blog.idatainc.com/tag/hedw) - [help (3)](https://blog.idatainc.com/tag/help) - [helping (3)](https://blog.idatainc.com/tag/helping) - [higher (86)](https://blog.idatainc.com/tag/higher) - [hiring (1)](https://blog.idatainc.com/tag/hiring) - [how (3)](https://blog.idatainc.com/tag/how) - [idata (143)](https://blog.idatainc.com/tag/idata) - [idatahub (1)](https://blog.idatainc.com/tag/idatahub) - [implementation (3)](https://blog.idatainc.com/tag/implementation) - [import (1)](https://blog.idatainc.com/tag/import) - [importance (4)](https://blog.idatainc.com/tag/importance) - [improve (1)](https://blog.idatainc.com/tag/improve) - [improvement (1)](https://blog.idatainc.com/tag/improvement) - [in (2)](https://blog.idatainc.com/tag/in) - [included (1)](https://blog.idatainc.com/tag/included) - [inexpensive (1)](https://blog.idatainc.com/tag/inexpensive) - [information (5)](https://blog.idatainc.com/tag/information) - [initiative (3)](https://blog.idatainc.com/tag/initiative) - [institutional (2)](https://blog.idatainc.com/tag/institutional) - [integration (22)](https://blog.idatainc.com/tag/integration) - [intelligence (280)](https://blog.idatainc.com/tag/intelligence) - [intervention (1)](https://blog.idatainc.com/tag/intervention) - [inventory (22)](https://blog.idatainc.com/tag/inventory) - [investment (2)](https://blog.idatainc.com/tag/investment) - [ipeds (1)](https://blog.idatainc.com/tag/ipeds) - [ir (1)](https://blog.idatainc.com/tag/ir) - [issues (3)](https://blog.idatainc.com/tag/issues) - [it (1)](https://blog.idatainc.com/tag/it) - [items (2)](https://blog.idatainc.com/tag/items) - [iteration (2)](https://blog.idatainc.com/tag/iteration) - [JIT (8)](https://blog.idatainc.com/tag/jit) - [journey (3)](https://blog.idatainc.com/tag/journey) - [just (9)](https://blog.idatainc.com/tag/just) - [K-12 (1)](https://blog.idatainc.com/tag/k-12) - [key (3)](https://blog.idatainc.com/tag/key) - [know (1)](https://blog.idatainc.com/tag/know) - [Knowledge (20)](https://blog.idatainc.com/tag/knowledge) - [knowledgebase (25)](https://blog.idatainc.com/tag/knowledgebase) - [language (1)](https://blog.idatainc.com/tag/language) - [leadership (1)](https://blog.idatainc.com/tag/leadership) - [learning (3)](https://blog.idatainc.com/tag/learning) - [lessons (2)](https://blog.idatainc.com/tag/lessons) - [level (1)](https://blog.idatainc.com/tag/level) - [levels (1)](https://blog.idatainc.com/tag/levels) - [libary (1)](https://blog.idatainc.com/tag/libary) - [librarian (1)](https://blog.idatainc.com/tag/librarian) - [library (1)](https://blog.idatainc.com/tag/library) - [life (1)](https://blog.idatainc.com/tag/life) - [lifecycle (3)](https://blog.idatainc.com/tag/lifecycle) - [lineage (6)](https://blog.idatainc.com/tag/lineage) - [lists (5)](https://blog.idatainc.com/tag/lists) - [literacy (10)](https://blog.idatainc.com/tag/literacy) - [loop (1)](https://blog.idatainc.com/tag/loop) - [maintain (1)](https://blog.idatainc.com/tag/maintain) - [maintenance (2)](https://blog.idatainc.com/tag/maintenance) - [management (32)](https://blog.idatainc.com/tag/management) - [manufacturing (1)](https://blog.idatainc.com/tag/manufacturing) - [map (3)](https://blog.idatainc.com/tag/map) - [market (1)](https://blog.idatainc.com/tag/market) - [matrix (3)](https://blog.idatainc.com/tag/matrix) - [measurement (3)](https://blog.idatainc.com/tag/measurement) - [metadata (3)](https://blog.idatainc.com/tag/metadata) - [method (1)](https://blog.idatainc.com/tag/method) - [migrating (3)](https://blog.idatainc.com/tag/migrating) - [migration (1)](https://blog.idatainc.com/tag/migration) - [model (1)](https://blog.idatainc.com/tag/model) - [monkey (1)](https://blog.idatainc.com/tag/monkey) - [new (1)](https://blog.idatainc.com/tag/new) - [non-profit (1)](https://blog.idatainc.com/tag/non-profit) - [not (1)](https://blog.idatainc.com/tag/not) - [office (1)](https://blog.idatainc.com/tag/office) - [officer (3)](https://blog.idatainc.com/tag/officer) - [onboarding (3)](https://blog.idatainc.com/tag/onboarding) - [operations (2)](https://blog.idatainc.com/tag/operations) - [organization (2)](https://blog.idatainc.com/tag/organization) - [organizational (1)](https://blog.idatainc.com/tag/organizational) - [organizations (1)](https://blog.idatainc.com/tag/organizations) - [out (1)](https://blog.idatainc.com/tag/out) - [oversight (8)](https://blog.idatainc.com/tag/oversight) - [own (1)](https://blog.idatainc.com/tag/own) - [owner (1)](https://blog.idatainc.com/tag/owner) - [ownership (3)](https://blog.idatainc.com/tag/ownership) - [parts (1)](https://blog.idatainc.com/tag/parts) - [path (2)](https://blog.idatainc.com/tag/path) - [people (36)](https://blog.idatainc.com/tag/people) - [plan (3)](https://blog.idatainc.com/tag/plan) - [planning (2)](https://blog.idatainc.com/tag/planning) - [platform (1)](https://blog.idatainc.com/tag/platform) - [playbook (1)](https://blog.idatainc.com/tag/playbook) - [points (8)](https://blog.idatainc.com/tag/points) - [policies (15)](https://blog.idatainc.com/tag/policies) - [policy (2)](https://blog.idatainc.com/tag/policy) - [portal (2)](https://blog.idatainc.com/tag/portal) - [potential (1)](https://blog.idatainc.com/tag/potential) - [practices (20)](https://blog.idatainc.com/tag/practices) - [pragmatic (3)](https://blog.idatainc.com/tag/pragmatic) - [principles (2)](https://blog.idatainc.com/tag/principles) - [priorities (3)](https://blog.idatainc.com/tag/priorities) - [priorization (2)](https://blog.idatainc.com/tag/priorization) - [privacy (2)](https://blog.idatainc.com/tag/privacy) - [problem (2)](https://blog.idatainc.com/tag/problem) - [process (35)](https://blog.idatainc.com/tag/process) - [processes (2)](https://blog.idatainc.com/tag/processes) - [processing (7)](https://blog.idatainc.com/tag/processing) - [products (2)](https://blog.idatainc.com/tag/products) - [project (11)](https://blog.idatainc.com/tag/project) - [projects (3)](https://blog.idatainc.com/tag/projects) - [protection (2)](https://blog.idatainc.com/tag/protection) - [purpose (1)](https://blog.idatainc.com/tag/purpose) - [quality (38)](https://blog.idatainc.com/tag/quality) - [questions (5)](https://blog.idatainc.com/tag/questions) - [quick (1)](https://blog.idatainc.com/tag/quick) - [quotes (1)](https://blog.idatainc.com/tag/quotes) - [reasons (1)](https://blog.idatainc.com/tag/reasons) - [recap (1)](https://blog.idatainc.com/tag/recap) - [reference (17)](https://blog.idatainc.com/tag/reference) - [regulation (1)](https://blog.idatainc.com/tag/regulation) - [related (8)](https://blog.idatainc.com/tag/related) - [report (12)](https://blog.idatainc.com/tag/report) - [reporting (19)](https://blog.idatainc.com/tag/reporting) - [repository (1)](https://blog.idatainc.com/tag/repository) - [request (25)](https://blog.idatainc.com/tag/request) - [research (3)](https://blog.idatainc.com/tag/research) - [resiliency (1)](https://blog.idatainc.com/tag/resiliency) - [resolution (2)](https://blog.idatainc.com/tag/resolution) - [resources (33)](https://blog.idatainc.com/tag/resources) - [responsibilities (3)](https://blog.idatainc.com/tag/responsibilities) - [return (2)](https://blog.idatainc.com/tag/return) - [review (1)](https://blog.idatainc.com/tag/review) - [road (3)](https://blog.idatainc.com/tag/road) - [roadmap (16)](https://blog.idatainc.com/tag/roadmap) - [ROI (7)](https://blog.idatainc.com/tag/roi) - [roles (3)](https://blog.idatainc.com/tag/roles) - [SaaS (3)](https://blog.idatainc.com/tag/saas) - [savings (1)](https://blog.idatainc.com/tag/savings) - [schedule (1)](https://blog.idatainc.com/tag/schedule) - [science (1)](https://blog.idatainc.com/tag/science) - [scientist (1)](https://blog.idatainc.com/tag/scientist) - [score (2)](https://blog.idatainc.com/tag/score) - [security (4)](https://blog.idatainc.com/tag/security) - [self-service (2)](https://blog.idatainc.com/tag/self-service) - [sensitive (1)](https://blog.idatainc.com/tag/sensitive) - [service (7)](https://blog.idatainc.com/tag/service) - [services (1)](https://blog.idatainc.com/tag/services) - [session (1)](https://blog.idatainc.com/tag/session) - [shadow (7)](https://blog.idatainc.com/tag/shadow) - [sharing (2)](https://blog.idatainc.com/tag/sharing) - [shelf (1)](https://blog.idatainc.com/tag/shelf) - [silo (3)](https://blog.idatainc.com/tag/silo) - [single (1)](https://blog.idatainc.com/tag/single) - [SIS (1)](https://blog.idatainc.com/tag/sis) - [situations (1)](https://blog.idatainc.com/tag/situations) - [skills (3)](https://blog.idatainc.com/tag/skills) - [smarter (1)](https://blog.idatainc.com/tag/smarter) - [soft (2)](https://blog.idatainc.com/tag/soft) - [software (1)](https://blog.idatainc.com/tag/software) - [solis (1)](https://blog.idatainc.com/tag/solis) - [solution (3)](https://blog.idatainc.com/tag/solution) - [source (1)](https://blog.idatainc.com/tag/source) - [specification (4)](https://blog.idatainc.com/tag/specification) - [specifications (2)](https://blog.idatainc.com/tag/specifications) - [spotlight (1)](https://blog.idatainc.com/tag/spotlight) - [sprawl (3)](https://blog.idatainc.com/tag/sprawl) - [staff (3)](https://blog.idatainc.com/tag/staff) - [stakeholders (2)](https://blog.idatainc.com/tag/stakeholders) - [start (10)](https://blog.idatainc.com/tag/start) - [started (4)](https://blog.idatainc.com/tag/started) - [steward (34)](https://blog.idatainc.com/tag/steward) - [stewardship (47)](https://blog.idatainc.com/tag/stewardship) - [story (2)](https://blog.idatainc.com/tag/story) - [strategy (2)](https://blog.idatainc.com/tag/strategy) - [student (2)](https://blog.idatainc.com/tag/student) - [students (1)](https://blog.idatainc.com/tag/students) - [success (8)](https://blog.idatainc.com/tag/success) - [summary (1)](https://blog.idatainc.com/tag/summary) - [support (3)](https://blog.idatainc.com/tag/support) - [supporting (1)](https://blog.idatainc.com/tag/supporting) - [survey (4)](https://blog.idatainc.com/tag/survey) - [system (23)](https://blog.idatainc.com/tag/system) - [systems (5)](https://blog.idatainc.com/tag/systems) - [tacit (1)](https://blog.idatainc.com/tag/tacit) - [team (2)](https://blog.idatainc.com/tag/team) - [technical (4)](https://blog.idatainc.com/tag/technical) - [technology (21)](https://blog.idatainc.com/tag/technology) - [telling (1)](https://blog.idatainc.com/tag/telling) - [thoughts (3)](https://blog.idatainc.com/tag/thoughts) - [ticket (3)](https://blog.idatainc.com/tag/ticket) - [time (7)](https://blog.idatainc.com/tag/time) - [tool (5)](https://blog.idatainc.com/tag/tool) - [tools (5)](https://blog.idatainc.com/tag/tools) - [top (2)](https://blog.idatainc.com/tag/top) - [topics (2)](https://blog.idatainc.com/tag/topics) - [training (25)](https://blog.idatainc.com/tag/training) - [traits (1)](https://blog.idatainc.com/tag/traits) - [transformation (1)](https://blog.idatainc.com/tag/transformation) - [transition (1)](https://blog.idatainc.com/tag/transition) - [trend (1)](https://blog.idatainc.com/tag/trend) - [triage (1)](https://blog.idatainc.com/tag/triage) - [trust (17)](https://blog.idatainc.com/tag/trust) - [trusted (2)](https://blog.idatainc.com/tag/trusted) - [truth (1)](https://blog.idatainc.com/tag/truth) - [types (1)](https://blog.idatainc.com/tag/types) - [urban (1)](https://blog.idatainc.com/tag/urban) - [use (1)](https://blog.idatainc.com/tag/use) - [used (1)](https://blog.idatainc.com/tag/used) - [uses (1)](https://blog.idatainc.com/tag/uses) - [valid (6)](https://blog.idatainc.com/tag/valid) - [value (7)](https://blog.idatainc.com/tag/value) - [versioning (1)](https://blog.idatainc.com/tag/versioning) - [vertical (1)](https://blog.idatainc.com/tag/vertical) - [visualization (1)](https://blog.idatainc.com/tag/visualization) - [warehouse (5)](https://blog.idatainc.com/tag/warehouse) - [warehousing (1)](https://blog.idatainc.com/tag/warehousing) - [way (1)](https://blog.idatainc.com/tag/way) - [webinar (1)](https://blog.idatainc.com/tag/webinar) - [what (5)](https://blog.idatainc.com/tag/what) - [where (1)](https://blog.idatainc.com/tag/where) - [who (2)](https://blog.idatainc.com/tag/who) - [why (7)](https://blog.idatainc.com/tag/why) - [wins (1)](https://blog.idatainc.com/tag/wins) - [workflow (1)](https://blog.idatainc.com/tag/workflow) - [writing (1)](https://blog.idatainc.com/tag/writing) ### Address 1727 King Street, Suite 250 Alexandria, VA 22314 USA - - [Jobs](http://www.idatainc.com/about-us/jobs/) - [Contact Us](http://www.idatainc.com/about-us/contact-us/) Copyright © 2026 [IData Incorporated](http://idatainc.com). All rights reserved