Application to payment

Carry the same record through every handoff.

A grant workflow is credible when staff can reconstruct what the applicant submitted, who reviewed it, why a decision was made, who approved payment and how the result returned to the file.

Book a ProtoGrants walkthrough
01

Guided intake

Create a complete application record at the front door.

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.

02

Evidence review

Bring the record into a review surface without losing its origin.

The read-only reviewer prototype retrieves Dataverse application, demonstration score and reviewer fields into one view.

Assignment, requests for information, conflict declaration and decision-write controls require approved workflow design before they become working claims.

03

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.

04

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.