Not-for-Profit — SharePoint & Microsoft 365
TechRam builds SharePoint trackers for not-for-profits, holding grant milestones, acquittals and approvals on the licences you already hold. Funding brings reporting obligations that otherwise arrive on someone's calendar rather than in a system, and no new licensing is needed to put them somewhere accountable.
Funding brings reporting obligations that arrive on someone’s calendar rather than in a system. We build the trackers that hold milestones, acquittals and approvals without new licensing.
Where it usually starts
Acquittal dates remembered rather than tracked. Approvals routed to whoever is nearest. Policy versions multiplying.
What changes
Milestones and reporting dates against every grant, approvals routed on value, and one current policy set.
Common questions
01. Do you understand Not-for-Profit compliance, or do we have to explain it?
You will not be explaining what a grant or acquittal obligation is. You will have to tell us yours, because they differ by organisation and by state, and that is what the discovery sessions are for.
02. Is this a product for Not-for-Profit, or a project?
A project, and the distinction matters. There is no Not-for-Profit product here to configure into shape, which is why the scope is agreed against your process rather than against a feature list.
03. Do we need to buy a grants management system?
No. The trackers hold milestones, acquittals and approvals without new licensing, which is the constraint this is built to.
04. Acquittal dates are remembered rather than tracked. What changes?
Milestones and reporting dates sit against every grant, so a funding obligation is in a system rather than on somebody's calendar.
05. Policy versions keep multiplying. What fixes that?
One current policy set, and approvals routed on value rather than to whoever is nearest.