Questions, answered

Click Get started, then use Proto to configure Social Welfare Scheme Mgmt for your business. Begin with a funded program, its owner and a case team using an agreed criteria version. Rehearse an eligible assessment, its planned benefit and the payment-reference handoff before expanding.

The action validates the linked program and award amount, activates the program and creates standard kickoff activities and milestones. Program Manager inspects their ownership and evidence expectations. Repeated processing recognizes the standard names.

Case Worker applies the organization’s agreed assessment criteria and records the supported outcome with its criteria version. The capture action validates the program and permitted state handling; staff remain responsible for the assessment process.

Capturing an Eligible assessment creates a linked Planned benefit due 30 days after the assessment date. Its amount remains empty for authorized preparation. Repeating equivalent processing for the same assessment must not create another planned benefit.

Approval requires the linked assessment to be Eligible. Benefits Officer checks that context before moving Planned work to Approved.

Both states require a nonempty payment reference. Agree the separate payment process and inspect its actual confirmation evidence before recording the corresponding progress. The status action leaves the amount unchanged.

No. The verification checks a positive amount, present category and Active program, then produces Approved or Rejected. Paid requires the separate externally confirmed payment event.

A missing or zero denominator makes the ratio unavailable. Keep the underlying inputs and evidence, and do not publish an impact or percentage derived from that invalid basis.

Case Worker reviews Appealed Assessments with the program and criteria version that informed the original decision. The case team handles the appeal under its agreed procedure; the appeal alone does not authorize a benefit.

Program Manager reviews My Activities against the signed-in staff identity, due dates and completion dates. For a milestone that appears due, check its completion date and evidence before treating it as unfinished.