Implementing the United Way Extension requires coordinated planning, data readiness, and alignment with the standardized process established by Bonterra’s CyberGrants platform. To ensure a smooth rollout, customers must define business logic early, engage in thorough testing, and provide accurate data files.
The following steps will guide you through the implementation process for this extension, from initial planning through post-implementation management best practices.
Pre-implementation planning
Step 1: Define the United Way organization search strategy
Determine whether donors will:
- Be allowed to search for a United Way organization, or
- Be restricted to only their default organization.
Determine if United Way-funded agencies or focus areas (designations) will be used.
Step 2: Set search radius parameters
Specify the radius (up to 50 miles) to identify the local United Way based on the work or home ZIP code provided through the Human Resources (HR) data feed.
Step 3: Identify the default organization
Provide the default United Way organization that will display when no match is found in the Gift Link file.
Step 4: Secure required files
- Gift Link file (ZIP code to organization)
- iGuide file (organization to designations)
Ensure files are free of duplicates and formatted according to CyberGrants specifications.
Step 5: Allocate resources and stakeholders
Assign internal teams (e.g., program managers, IT, compliance) to work with the CyberGrants Business Analyst throughout the project.
Implementation process
Step 6: Review functional requirements
Collaborate with your CyberGrants Business Analyst to define and approve the extension’s requirements and configuration scope.
Step 7: Upload and validate files
Submit clean and complete Gift Link and iGuide files. CyberGrants will validate the files but will not manipulate the data.
Step 8: Configure and test the portlet
Set up the featured organization search portlet, customizing the search and display preferences based on your requirements.
Step 9: Conduct User Acceptance Testing (UAT)
Participate in a full UAT cycle to validate all functionality. This step is mandatory and must be signed off on before the extension moves to production.
Post-implementation management
Step 10: Monitor donor feedback and behavior
Collect feedback on donor experience and engagement with the United Way selection process to inform potential future changes.
Step 11: Plan for annual change request
Remember that only one change per calendar year is permitted within the scope of the extension. Coordinate internal stakeholders to align on necessary adjustments.
Step 12: Maintain file quality
Continue to ensure that all United Way files (Gift Link and iGuide) are updated regularly and free of errors before submission.
Step 13: Coordinate with CyberGrants on modifications
Any post-launch changes that affect custom logic may require additional costs and extended timelines. Always consult your Business Analyst before initiating changes.
What else do you need help with?
Not what you're looking for? Navigate to United Way Extension Overview
Looking for training?
Explore this feature at your own pace - access training video content or watch a recorded webinar by clicking the link below.
