Services · Scale-Up

Functional Requirements Document (FRD) Process and Change Request Justification

FRD

Prepares functional requirements and change-request justification for finance systems/process changes, including need, benefits, risks, scope and approval rationale.

What changes

More reliable financial data, better reporting, stronger audit readiness and improved system-enabled finance operations.

What you get

Functional Requirements Document prepared for each in-scope change FRD001
Change request justification with impact assessment and cost-benefit analysis FRD002
Requirement prioritisation matrix FRD003
Change register with status, approvals and deployment dates FRD004
UAT plan and sign-off template FRD005
Post-implementation review checklist FRD006

What has to come first

NAHNeeds Assessment Report - National Head Quarters or NABNeeds Assessment Report - Branch/District Recommended

Needs assessment findings identify the control and process gaps that drive system changes
SAA“As is” assessment of accounting software, including sustainability analysis Recommended

The as-is assessment of accounting software establishes the baseline the changes depart from

Who is involved

From the National Society's side. This is what the engagement asks of your people.

Your own staff work alongside the adviser throughout, so this is a commitment of their time as well as the Centre's. Ask in the request and you are given the day estimate per role before anything is signed.

Role	What they do
HNS Finance Director / finance systems owner	Business owner, owns the process
ICT / MIS manager or service provider	Technical counterpart
Process owners (procurement, HR/payroll, PMER, logistics, branch operations)	Requirement input
Senior Management Team	Approval of major changes
Vendors / implementation partners	Build and deploy approved changes
Internal audit / risk function	Control and governance input
GFDC delivery team	Guides the process and drafts the templates

How it is measured

Indicator	Target	Evidence
Every implemented change has an approved FRD signed off by the business owner before build	100% of deployed changes	Change register cross-checked against signed FRDs
Change requests follow the approval workflow; no informal changes	100% of CRs in the register	Change register vs system configuration audit logs
Change requests receive an approval decision within target time of submission	4 weeks or less	Change register timestamps
Deployed changes carry documented UAT sign-off before go-live	100% of deployments	UAT sign-off records (FRD005)

Tools

6 of 6 ready to download.

FRD001 Functional Requirements Document Template DOCX
FRD002 Change Request Justification Template DOCX
FRD003 Requirement prioritisation matrix Template XLSX
FRD004 Change register Tracker XLSX
FRD005 UAT plan and sign-off template Template DOCX
FRD006 Post-implementation review checklist Checklist DOCX

Standards

COSO Internal Control - Integrated Framework
GFDC Operational Framework (intake, triage, service workflow)
ERP configuration documentation and vendor manuals
External audit management letters and prior year adjustments
HNS IT/ICT policies and data protection policy
HNS Delegation of Authority (DoA) and governance ToRs
Vendor contracts, SLAs and product lifecycle documentation
ITIL 4 change enablement practice guidance

Describe the problem, not the service

You do not need to know which of the 124 to ask for.

Request support