Final WDF Understanding + ERP Blueprint

One fund. Many programmes. Church wing has a product engine.

WDF is not only about churches. It supports SMEs, pre-schools, NPOs, NGOs, churches, and ESD programmes. But when churches are involved, the model becomes a network: church onboarding, member capture, cover verification, bursaries, healthcare, finance, stipends, and funder reporting.

WDF umbrella

The mistake would be to treat WDF as only a church product. The cleaner model is a multi-programme development platform, with the church wing having the strongest distribution network.

💼

SME support

Business registration, compliance, branding, systems, funding support, ESD readiness.

entrepreneur pipeline

🏫

Pre-school support

ECD funding, study aid, uniforms, bursary support, staff/admin help, setup services.

education pipeline

🤝

NPO / NGO support

Operational support, PBO/NPO compliance, systems, documents, funding readiness.

impact pipeline

⛪

Church support

Church onboarding, compliance, member capture, bursaries, clinics, stipends, equipment.

community network

🏭

ESD programmes

Corporate enterprise and supplier development execution with beneficiary tracking.

corporate reporting

Church wing process

This is the flow the system must automate. The church is not just an applicant. It becomes a verified node inside a bigger province-region-ward-member network.

📥

Application captured

Church details, leaders, documents, location, denomination, members, operating history.

lead intake

💳

R350 paid to ACPN

Starts the early foundation work within about 5 days.

phase 1 trigger

🧾

Name + compliance

NPC name reservation, registration prep, compliance file, early system onboarding.

foundation tasks

⏳

14-day clock

Church gets time to complete the R3,500 WDF membership payment.

payment SLA

💻

R3,500 confirmed

Unlocks deeper WDF membership services like telephone, hosting, fuller systems, and phase 2 work.

membership gate

👥

Members captured

Members, households, beneficiaries, bursary candidates, leaders, officers, graduates.

network data

🏥

Cover verified

Funeral and healthcare/medical support must be confirmed before funding can move.

eligibility gate

🚀

Support released

Bursaries, stipends, clinic work, equipment, renovations, education classes, funder reporting.

delivery + audit

Payment logic

Two fees. Different jobs.

R350 starts the ACPN foundation process. R3,500 activates full WDF membership. Financial products are a separate cover and lead-generation layer, especially for people who need funding, bursaries, or support.

R350

ACPN initial payment

Used to start name reservation, registration, compliance, system onboarding, and early Phase 1 tasks.

starts work

R3,500

WDF membership fee

Paid within about 14 days. Unlocks full membership services and deeper Phase 2 delivery.

unlocks phase 2

Cover

Funeral + medical support

Needed before funding is released, because funders want beneficiaries protected if something happens.

funding gate

Products

Monarch / Sacred Life / Episodic Health

These seem to provide or support the cover and lead-generation model through the church network.

product engine

Three operating lanes

This is the clean architecture: WDF programme work, church network work, and product/cover work must be linked but not mixed into one messy module.

🏗️

Lane 1: Programme delivery

All WDF support work across SMEs, pre-schools, NPOs, NGOs, churches, and ESD programmes.

Applications and applicant profiles

Documents and compliance tasks

Website, email, landline, systems setup

Funding readiness and approval tracking

Service delivery proof and reports

WDF admin engine

⛪

Lane 2: Church network

Specific church rollout structure: province, region, ward, church, pastor, member, household.

Provincial, Regional and Community Liaison Officers

Church onboarding and member capture

Bursary candidates and education classes

Clinic setup milestones

Stipend and support release triggers

community operating system

🏥

Lane 3: Cover + products

Healthcare, funeral, finance and financial inclusion products connected to the church/member network.

Plan selection and cover verification

Monthly subscription status

Provider and underwriter records

Claims, visits, benefits and service requests

Commissions, revenue projections and conversions

eligibility + revenue layer

Database blueprint

This is the DB backbone. Build the system around entities, milestones, payments, cover status, evidence, and audit logs.

Programmes

id, name, type, rules, required_docs, fee_rules, milestone_template

Applications

id, programme_id, applicant_type, status, province, region, ward, assigned_officer

Organisations

id, org_type, name, registration_no, NPO/PBO/NPC status, address, contacts

People

id, role, full_name, ID_no, phone, address, church_id, household_id

Church Network

church_id, pastor_id, ward_id, members_count, households_count, denomination

Liaison Officers

id, level, province_id, region_id, ward_id, target, performance, stipend_status

Payments

id, payer, amount, type, reference, proof, verified_by, verified_at

Milestones

id, application_id, phase, task, due_date, status, evidence_required, approver

Documents

id, owner_id, doc_type, file, expiry, verification_status, notes

Products

id, provider, product_name, plan, monthly_fee, benefits, compliance_docs

Member Cover

member_id, product_id, cover_type, active_status, start_date, proof, expiry

Benefits / Claims

id, member_id, type, request_date, provider, status, outcome, evidence

Classes

id, church_id, course, start_date, attendance, facilitator, portfolio_status

Clinics

id, ward_id, provider, setup_status, launch_date, verification, assigned_churches

Stipends

id, person_id, role, period, eligibility_rule, amount, approval, payment_status

Audit Logs

id, user_id, action, table_name, record_id, old_value, new_value, timestamp

Automation rules

The ERP must not just store data. It must move the process and block risky actions automatically.

✅ Trigger rules

1When R350 is verified, create Phase 1 tasks and start the 5-day SLA.

2When Phase 1 starts, open the 14-day R3,500 membership countdown.

3When R3,500 is verified, unlock Phase 2 tasks: telephone, hosting, full systems and compliance flow.

4When funding is requested, check funeral and medical/health cover before approval can continue.

5When education classes and clinic milestones are verified, stipend/support eligibility can activate.

⛔ Block rules

1No full membership benefits without verified R3,500 payment or approved exception.

2No funding release without active funeral and healthcare/medical cover.

3No stipend payment without milestone evidence and verifier approval.

4No product commission without member/product signup evidence.

5No reporting numbers without linked church, ward, region and province records.

Role access 🔐 Different dashboards for WDF admin, ACPN, provincial leaders, regional officers, community LOs, church leaders, finance, and verifiers.

Evidence first 📎 Every payment, milestone, class, clinic, cover, claim, stipend and funding decision needs proof and an audit trail.

Network reporting 📍 Dashboards must roll up from member to church, ward, region, province and national level.

Product separation 🧱 Products must be separate modules, linked to cover eligibility and lead generation, not hidden inside church onboarding.