Grant Preparation to Final Close Out

Follow the file through every handoff.

Evaluate the application record, review decisions and finance handoff. The managed package and the demonstrated end-to-end operating model have different scope.

Plan implementation
Package boundary

Confirm the release behind the demonstration.

The Microsoft Marketplace listing describes application records, evidence and decision forms, a reviewer workspace and finance status fields. The broader workflow below is an operating model to configure and test for your program. Public portals, integrations and production acceptance are separate implementation scope.

Grant preparation

Set the terms before a program opens.

Configuring a funding opportunity, eligibility rules, application form, scoring rubric, reviewer pool, timeline and total funding pool, happens before any applicant sees the program.

Guided intake

Create a complete application from the start.

The current live demonstration guides a visitor through fixed eligibility checks and required application fields. Final submission creates a Dataverse Grant Application record.

Account-bound drafts, applicant-specific status, document upload and correction workflows remain future product slices.

Application review

Review the application and request missing evidence.

Where program rules permit, staff can issue a formal request that identifies the required evidence, authority, due date and consequence of not responding.

The recipient returns to a guided task before or after payment. The request, reminders, response and reviewer outcome stay attached to the original case.

Human decision

Keep authority and rationale visible together.

ProtoGrants is designed around accountable human decisions. Demonstration scores may support a scenario, but program staff own the decision and its reason.

No AI resource is connected. Any future assistive scoring would require explicit authorization, governance and a clearly bounded human review path.

Payment and reconciliation

Return the financial result to the application record.

The product storyboard follows manager approval, finance-neutral handoff, payment status and reconciliation by application reference.

These transaction controls are prototype direction. A production release must prove the approval action, finance exchange, exception handling and audit evidence for the buyer's actual system.

Monitoring

Track the award against its own baseline.

Once an agreement is signed, the approved scope, budget and milestones become the baseline. Grantee progress reports, budget tracking and risk flags are compared against that baseline for the life of the award, with any amendment requests handled along the way.

Final close out

Reconcile what was promised against what was delivered.

At the end of the award period, a final report compares what was proposed to what was delivered, reconciles the budget and flags any funds subject to recovery where deliverables went unmet or funds went unspent. A designated approver signs off before the file is archived.

Published · Updated