Using Pipelines to Manage Grant Applications in Humanitru
Humanitru Pipelines give your organization a structured, purpose-built way to track grant applications from start to finish — from the moment you identify a funding opportunity through submission, award decision, and post-award reporting. Rather than piecing together tags, campaigns, and manual notes, Pipelines keep everything related to a single grant application in one place, with clear stages, assigned owners, logged actions, and running totals.
This article walks you through how to set up and use a Grant Management Pipeline in Humanitru, with guidance on each stage and how to track your team’s work throughout the grant lifecycle.
When to Use This GuideUse this guide when you want to:
- Set up a Pipeline to manage grant applications to foundations, government agencies, or other institutional funders
- Track the status of individual grant opportunities across your team
- Log actions such as application submissions, site visits, and award notifications
- Understand how Humanitru’s pipeline stages can be mapped to your real-world grant process
Read the Pipelines Overview & FAQs article before this one if you are new to Pipelines and want a foundational understanding of how the module works.
Step-by-Step Instructions
Part A: Navigate to Pipelines
- Log in to Humanitru and click Pipelines in the left-hand navigation menu.
- The All Pipelines page loads. You will see two tabs: Pipelines (a summary view of all your Pipelines) and All Opportunities (a table of every individual Opportunity across all Pipelines).
- To create a new Grant Pipeline, click the green Create New Pipeline button in the top right corner.

Fill out the Pipeline creation form with the following information:
- Pipeline Name — Give the Pipeline a name that identifies the grant program or funder. For example: "Community Foundation Grants 2027" or "Capital Campaign Grants." Names must be unique across your organization.
- Goal Amount — Enter the total funding you are seeking across all grant applications in this Pipeline. This becomes the benchmark for tracking progress.
- End Date — Enter the target close date for this Pipeline (for example, the end of your grant cycle or fiscal year). End dates must be in the future.
- Description (optional) — Add a brief description to distinguish this Pipeline from others, especially useful if you manage multiple grant programs at once.
- Campaigns (optional) — Associate relevant Campaigns with this Pipeline so that all Actions logged to its Opportunities are automatically tagged.

When you configure your Pipeline’s stages, you define the steps a grant application moves through from initial identification to final outcome. The screenshot below shows a recommended set of stages for a Grant Management Pipeline. You can customize stage names to match your organization’s terminology and needs.
|
Stage |
What It Represents |
|---|---|
|
Application Due |
The funder’s deadline is approaching. Use this stage for grant opportunities where you are actively preparing or finalizing your application materials. |
|
Application Submitted |
The application has been submitted to the funder. Move an Opportunity here once your team has confirmed submission. Log the submission date as an Action. |
|
Grant Awarded |
The funder has approved the grant and notified your organization. Move the Opportunity here upon receiving an award letter or verbal notification. Log the award amount as a verified Donation Action to populate the Actual Amount field. |
|
Declined (locked — always present, cannot be removed) |
The funder did not approve the application. This stage is locked in every Pipeline and cannot be removed. Use it for any grant that was rejected, withdrawn, or did not result in a gift. |
|
Stewardship (locked — always present, cannot be removed) |
The grant has been awarded and your organization is fulfilling its obligations to the funder. This stage is locked in every Pipeline and cannot be removed. Use it to track ongoing funder relationships, required check-ins, and reporting milestones. |
|
Grant Outcome Reporting Due |
A reporting deadline is approaching. Move Opportunities here when a progress or final report is due to the funder. Log the report submission as an Action once complete. |
Note: Stages can be reordered by dragging and dropping them during Pipeline setup. The Declined and Stewardship stages are fixed and will always appear regardless of order.
Part D: Add Grant Opportunities to Your PipelineOnce the Pipeline is saved, you are ready to add individual Opportunities — one per grant application or funder relationship.
- From your Pipeline’s Overview or Opportunities tab, click Add Opportunity.
- Search for and select the constituent (foundation, agency, or individual funder) associated with this grant.
- Enter the Ask Amount (the amount you are requesting from this funder) and, if known, a Projected Amount (your team’s best estimate of what will come in).
- Assign the Opportunity to the staff member responsible for this application.
- Set the initial stage. Most new grant applications will start in Application Due.

Actions are the heartbeat of an Opportunity — they record every meaningful touchpoint in the grant relationship. As your application moves through stages, log Actions to build a complete audit trail.
Common grant-related Actions to log:
- LOI submitted — log with the submission date
- Full application submitted — log with the deadline date and any confirmation number
- Site visit or funder meeting — log as a meeting Action with notes
- Award notification received — log as a Donation Action and verify it to populate the Actual Amount
- Decline notification received — log the date and move the Opportunity to Declined
- Progress or final report submitted — log when moving through Grant Outcome Reporting Due
Future-dated Actions are marked Unverified and excluded from summary statistics until the date passes and a user manually verifies them. Past-dated Actions are auto-verified.
You can add Actions directly on the Opportunity or you can add existing Actions to an Opportunity by applying the Opporunity ID Campaign.
Pro Tips / Common Mistakes|
★ Create one Pipeline per grant cycle or program area, not one Pipeline per funder. This keeps your goal amounts and summary statistics meaningful. ★ Use the Grant Outcome Reporting Due stage actively. Post-award reporting is one of the most common places grant management falls through the cracks. Having a dedicated stage makes it visible in your Pipeline. ★ Log award notifications as Donation Actions — not just notes. Only verified Donation Actions populate the Actual Amount field, which drives your Pipeline’s fundraising totals. ★ When an application is declined, move it to Declined rather than deleting the Opportunity. Deleting is only possible if no Actions exist, and you want to keep your history. The Declined stage preserves the data. ★ Use the Description field on each Opportunity to capture the grant program name or project title, especially when a single funder has multiple open applications. |