Skip to main content

Flexible Grant Management Software: Long Term Considerations

My company InfoStrat has developed grant management systems for federal, state, and local governments as well as non-profits for nearly twenty years.  I have noticed a new emphasis on the requirement for flexibility in creating a system which can be easily modified to handle new grant programs and changes in business rules.

Here are my top dos and don'ts from our experience and that of our customers:

  1. Whether you are a grantor or a grantee, don't develop a new system for every program.  When a new program is created, it may seem simpler to start from scratch and spin up a new system in order to avoid changes to your existing system.  This approach is an easy trap to fall into, but later you will end up with multiple systems which separately need to be maintained, upgraded, and enhanced.  Creating reports that combine data from multiple systems is needlessly difficult compared to using a centralized, integrated approach from the beginning.
  2. Consider your enterprise architecture. 
  3. Do include the entire grants management lifecycle in your system. A typical grant has phases such as pre-award, award, post-award, closeout, and post-closeout. Even if you start by emphasizing only some of these phases, try to make your system encompass them all.  Over time you can add enhancements to flesh out the phases through which your grant progresses.
  4. Keep up with security and software versions.  In order to maintain a secure system, you must keep pace with releases and patches issued by your software vendor.  To allow yourself to slip one or two versions behind is an invitation to a lapse in security compliance.
  5. Consider cloud deployment. Most customers embarking on a new grant management system project will choose cloud deployment, but even those whose systems are deployed on premises today can consider hybrid cloud solutions for failover and disaster recovery. Going with a cloud vendor is one of the most painless approaches to maintaining security compliance, especially to keep pace with U.S. government standards such as FISMA and FedRAMP.
  6. Add analytics to your solution. Most grant management systems offer standard reports and reporting tools. Consider analytics products that can go deeper than most reports and identify patterns, offer visualization, and integrate with geographical data when appropriate. 
  7. Catch fraud and errors early. As you develop or maintain your grant management system, tighten audits and controls that will help you spot erroneous payment requests and flag grant ineligibility as early as possible.  Our customers have saved many times the cost of their grant management software by stopping fraud and errors. 
You can learn from the mistakes of others by reviewing solicitations for grant management systems.  The regrets that I see most often are picking a product which is difficult to maintain or customize, and choosing a solution from an obscure vendor that is acquired or goes out of business. These are some of the reasons that our customers have chosen Microsoft Grants Manager Plus, developed by InfoStrat.  It is based on the widely supported Microsoft Dynamics 365 product family, and benefits from millions of dollars of annual research and development by Microsoft.

For more information on grant management and Microsoft Grants Manager Plus, see my posts:

5 Ways to Ensure Compliance with Your Grant Management System
6 Things to Look for in Grant Management Software
Estimating the Cost of a Microsoft Grants Manager Plus Implementation
Extending Grants Manager Plus
Flexible Grant Management Software: Long Term Considerations
Grant Management for Community Development Block Grants (CDBG)
Grant Management Portal: What to Include
Grant Management with FedRAMP Certification: Microsoft Dynamics 365
Grants Manager Plus: Theme and Variations
InfoStrat Grants Manager Plus Review on FinanceOnline
InfoStrat Releases New Version of Grants Manager Plus
InfoStrat Releases New Videos on Grants Manager Plus
Microsoft Grants Manager Plus
Microsoft Grants Manager Plus Frequently Asked Questions (FAQ)
Online Resources for Microsoft Grants Manager Plus
Portal Options for Microsoft Grants Manager
Statewide Grant Management Systems
The DATA Act Driving Grant Management Automation
The Story of InfoStrat and Grant Management
Usage Scenarios for Microsoft Grants Manager
User Stories for Grants Manager Plus
Understanding Budget, Payments and Milestones in Grants Manager Plus
Understanding Grant Management Data: CDBG-DR Programs
Understanding Programs in Grants Manager Plus


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan