GrantOps application review mark HALO GrantOps

HALO BUSINESS SYSTEMS / WORKFLOW DEMO 04

Good ideas deserve
a clear path.

For foundations and grant teams juggling applications, reviewer questions and progress reports. Keep each request, decision and next step together so everyone knows what to do next.

Start as an applicant, then follow the people who check, review and decide. Made-up records only; nothing is sent to a foundation.

COMMUNITY ARTS / 2026

Application ART-001

Light on
the River

Riverlight Collective

Proposal£12,000
01Apply02Review03Award
✦ Know who does what next

ONE FUNDING ROUND. FIVE ROLES.

See what each person
needs to do next.

AFTER A GRANT IS APPROVED

See how a team handles a report that needs changes.

Start with a made-up approved grant. Submit a progress report, answer a request for more detail, and see the coordinator accept the revised report. Then ask the director for more time to report.

You will be asked before replacing your saved demo progress. Changing roles lets you try another person’s view; it is not a sign-in. No report is sent and no money moves.

IS THIS LIKE YOUR TEAM’S WORK?

Review applications.
Follow funded projects.

See how your team could replace scattered emails and spreadsheets with a shared record of each application, decision and progress report.

This example is for foundation and grant-program teams. It uses made-up organizations in one arts-funding round. It does not accept real applicants, provide secure sign-in, send payments or connect to accounting software.

Before funding: review the application

Check that the application has what you need. Ask for missing details, check whether a reviewer has a personal connection, and record their recommendation. The director chooses whether to fund it and explains why. A score cannot approve funding.

You will be asked before replacing the demo progress saved in this browser.

After funding: follow the project

Read the project’s progress report, ask for changes and record which report was accepted. A director decides any request for more reporting time. Finance can mark demo milestones as recorded; it cannot send money.

See the reporting example

From application to progress report

  1. Apply
  2. Check for missing details
  3. Review and recommend
  4. Director approves or declines
  5. Review project progress
What could we discuss about your process?

Tell us where applications get stuck, who makes each decision, what reviewers need to see, and how your team follows funded projects. We would discuss sign-in, other software and live use separately.

SEE THE WORKFLOW

Watch each role in action.

These narrated videos use real screens from this made-up grant example. They are assembled from captured screens, rather than one continuous recording. Some navigation and help text has since been made clearer.

Technical details

This is a browser-only example using fictional records. Changes are saved in this browser’s local storage. Reset restores the original records. There is no server account or real authentication; switching roles only changes the view.

Funding totals and next steps are calculated from the demo records. People must record award and timeline decisions. There are no live banking, accounting or applicant-intake integrations. Access controls, security requirements and connections to other software would need a separate design for live use.

Start the demo again?

This restores the twelve made-up applications and starts again with the applicant’s draft. Your saved demo changes in this browser will be replaced.