Industry patterns · Government and councils

Grants application and assessment portal

An accessible grants portal: applicants apply and acquit online, assessors score with conflict checks, and decisions flow to finance and records.

A reference architecture from EITSAA, not a named client system. Service limits, prices and product features change, so confirm current details before you commit to a design.

  • WCAG 2.2 AA
  • Australian Privacy Principles
  • ACSC Essential Eight
  • State Records Act 1997 (SA)

Architecture

Architecture diagram. Tinted boundaries show regions, accounts, networks and trust zones. Numbered arrows match the flow below.
Grants application and assessment portal architectureApplicant to CloudFront + WAF: HTTPS. CloudFront + WAF to API on Lambda: submit. API on Lambda to S3 attachments: upload. API on Lambda to Round workflow: start. Round workflow to Aurora PostgreSQL: store. Assessors and panel to Aurora PostgreSQL: assess. Round workflow to Finance and records: pay, fileApplicants andassessorsAWS account · ap-southeast-2Agency or councilsystemsApplicantBusiness, club or residentAssessors and panelStaff SSO, conflict checkCloudFront + WAFPortal edge, rate limitsAPI on LambdaAPI Gateway, CognitoS3 attachmentsPresigned, malware scanRound workflowStep Functions, rulesAurora PostgreSQLApplications, scores,milestonesFinance and recordsPayments, EDRMS1HTTPS2submit3upload4start5store6assess7pay, filePlatform servicesAWS IAMAmazonCloudWatchAWS CloudTrailAWS KMS
  • People and clients
  • Network and edge
  • Compute and containers
  • Object and file storage
  • Messaging, events and workflow
  • Databases and data
  • SaaS and business systems
  • Security and identity
  • Monitoring, audit and analytics
  • Request or data flow
  • Asynchronous or optional
  • Boundary: region, account, network or trust zone

Request and data flow

  1. An applicant reads the round guidelines, runs a short eligibility self-check and starts an application they can save and return to. Forms meet WCAG 2.2 AA and work on a phone.

  2. Submissions pass the edge, WAF and rate limits to the API. Applicants sign in with Cognito so they can track progress, answer questions and later report on milestones.

  3. Quotes, budgets and letters of support upload straight to S3 with presigned URLs and are scanned for malware before any officer opens them.

  4. On submission, a Step Functions workflow runs the round's eligibility rules, flags missing items and sends an acknowledgement with a reference number.

  5. The application, its answers, versions and every status change are stored in Aurora PostgreSQL, so the record of what was submitted and when cannot drift.

  6. Assessors and panel members sign in with staff SSO, declare conflicts of interest, then score against the published criteria. Moderation and the delegate's decision are recorded with reasons.

  7. An approved grant raises a funding agreement and a payment request in the finance system, and the application and decision are filed as official records. Acquittal reports come back through the same portal.

Components and why they were chosen

ComponentWhat it doesWhy this choice
CloudFront and AWS WAFPublic edge for the portal.Absorbs the rush when a round opens and blocks scripted abuse.
Amazon CognitoApplicant accounts, with optional MFA.Applicants return for variations, milestones and acquittals.
API Gateway and LambdaApplication API.Low cost between rounds, scales on closing day.
AWS Step FunctionsRound workflow from eligibility to acquittal.Every application has a visible state and history.
Amazon Aurora PostgreSQLApplications, scores, conflicts and milestones.Relational data and reporting across rounds.
Amazon S3 with malware scanningAttachments and generated agreements.Encrypted, versioned and scanned.
Staff identity (Entra ID or council IdP)Assessor and delegate sign-in.Joiners and leavers handled in one place.
Integration to finance and recordsPayments, supplier set-up and records capture.Finance and the EDRMS stay authoritative.

Design decisions and trade-offs

Configure, buy or build

Use a grants product or your existing CRM where it fits; build the portal when rounds, criteria or integrations are unusual.

Why. Grants products cover common rounds well.

Trade-off. A custom portal needs an owner and ongoing support.

Scoring and decisions

People score and the delegate decides. Software totals scores and checks completeness only.

Why. Funding decisions must be explainable and accountable.

Trade-off. Assessor effort stays.

Conflicts of interest

Declared per application before scoring opens, with access blocked when a conflict is declared.

Why. Probity is the first thing reviewed after a round.

Trade-off. An extra step for panels.

Payments

Raise payment requests in the finance system and keep bank details out of the portal.

Why. Finance controls and fraud checks stay in one place.

Trade-off. Integration work with the finance system.

Well-architected pillars

Security

Private networking, IAM Identity Center and Cognito with MFA, encryption with customer-managed keys, least-privilege roles and WAF on the public edge.

Reliability

Multi-AZ services, backups with tested restores and queue-based retries for integrations.

Performance

Edge caching for public content, asynchronous processing for anything slow and indexes tuned to the main queries.

Cost optimisation

Scale with demand, use reservations or savings plans for the steady baseline and set budgets and alerts per environment.

Operational excellence

Infrastructure as code, pipeline deployments with rollback, dashboards on service-level objectives and runbooks for the top failure modes.

Sustainability

Right-size, schedule down non-production and archive data to colder tiers on a retention schedule.

Network, identity and data

Networking

VPC with public, private and isolated data subnets and VPC endpoints. Public ingress only through the edge service with WAF. Private connectivity to on-premises or partner systems by VPN or dedicated link.

Identity and least privilege

Applicants via Cognito with optional MFA and verified contact details. Assessors, panel members and delegates via the agency or council IdP with MFA, limited to the rounds and applications assigned to them.

Data and encryption

Applications hold personal, business and sometimes financial information. Collect only what the round needs, encrypt with KMS, keep data in the Sydney region, log every view of an application and set retention from the disposal schedule that covers grants.

Security and compliance mapping

ControlHow this design addresses it
Multi-factor authenticationRequired for staff and administrators. Essential Eight.
Restrict administrative privilegesJust-in-time elevation and separate admin accounts. Essential Eight.
Regular backupsAutomated backups with a copy held outside the workload account or subscription. Essential Eight.
Privacy and security of personal informationEncryption, access logging and retention support APP 11.
LoggingCentral, tamper-resistant logs support ISM event logging guidance and ISMF expectations.

Mappings show how the design supports each control. They are not certifications, and EITSAA does not claim IRAP assessment or compliance for any reference architecture.

Failure modes, targets and scaling

  • Target RTOUnder 4 hours, with a published extension rule if the portal fails near a closing date
  • Target RPOSeconds to minutes with point-in-time recovery
  • Scaling and limitsSized from measured peak demand with a load test before go-live. Check service quotas early.
Failure modeMitigation
Closing-day surgeServerless scaling, a load test at the expected peak and a published rule for extensions if the portal is unavailable.
Bank detail change fraudVerify changes through a known phone number before payment and alert on recent changes.
Conflict found after scoringConflict register, access logs and re-assessment of the affected applications.
Finance or records system downQueue payment requests and records captures, with retries and daily reconciliation.

Observability and runbooks

  • Service-level objectives for availability and latency with burn-rate alerts.
  • Audit log review for sensitive actions.
  • Queue depth and integration error dashboards with a named owner.

Cost drivers and levers

Compute, database, data transfer and licences for any SaaS components.

  • Reserve the baseline.
  • Schedule non-production down.
  • Cache and compress at the edge.
  • Archive old data.

Implementation and fit

Phased approach

  1. Discovery: process, data and obligations mapped with the business owner.
  2. Foundation: landing zone, network, identity and pipeline.
  3. Thin slice: one journey end to end in production for a small group.
  4. Expand and harden: remaining journeys, load and penetration testing.

Anti-patterns to avoid

  • Building before the decision rights and audit needs are agreed.
  • A single shared admin role.
  • Personal data in logs and test data.
  • Integrations without retries or a dead-letter path.

When to use it

  • Agencies and councils running several grant or sponsorship rounds a year.
  • Programs that need probity, milestone reporting and acquittal in one place.

When not to

  • A single small round a year that a simple online form handles well.
  • Automating eligibility or scoring decisions with no accountable person.

More in industry patterns

  • Health

    Health referral and intake workflow

    Structured digital referrals into a clinical service, with consent, secure messaging and clinical system integration, hosted in Australia with strong audit.

  • Education

    Student and learner services platform

    One front door for enrolment, support requests and communications, integrated with the student information system and learning platform, with safeguarding built in.

  • Not-for-profit

    Not-for-profit case management and reporting

    Case notes, referrals and outcomes tracked securely by small teams, with funder reporting generated from the same data and strict access to sensitive client information.

Related insights

Discuss this architecture

Tell us your systems, constraints and timeline. We reply within one business day, and the initial conversation is free.