Ukraine Primero CPIMS+ IA instance: Adding a Supervision Form

Proposals Pitches
1

Proposal One-Liner: Creating a new ‘Supervision Form’ in the cases form of Ukraine Inter-Agency Primero CPIMS+ to streamline case plan approval and service monitoring for supervisors.

Value Proposition: The proposed Supervision Form will enhance efficiency by consolidating data from case plans, services, and follow-ups into a single tab or form. This real-time integration will save supervisors time and reduce cognitive load, improving overall case management.

Brief Explanation: Supervisors in Ukraine are responsible for approving case plans and monitoring service delivery. Currently, they must navigate between three separate forms (case plan, services, and follow-up), leading to inefficiencies and increased workload. This proposal suggests creating a single tab or form that integrates data from all three forms in real time. This will streamline the supervision process, reducing the need for constant switching between forms and helping supervisors focus on service tracking and decision-making. Given that each supervisor manages approximately 100 cases (supervising 5-6 case workers with 20-25 open cases each), this change will significantly improve their workflow.

Acceptance Criteria:

  • A new ‘Supervision Form’ is integrated within the cases form of Ukraine IA CPIMS+.
  • The form consolidates real-time data from case plans, services, and follow-ups main forms including fields from those forms, sub-forms, and fields from the sub-forms of e.g. interventions, services, etc.
  • Supervisors can approve case plans and monitor services without switching between multiple forms.
  • The interface is intuitive and user-friendly, requiring minimal training.
  • The implementation does not disrupt existing case management processes.

Time Estimation:

  • Requirement specification: 2 weeks
  • Testing and quality assurance after deployment: 2 weeks

Risk Estimation:

  • Data synchronization issues between forms.
  • Supervisors may require training to adapt to the new workflow which can be done through a tutorial video or an online session to also gather feedback.

Proposal Stakeholders:

  • Supervisors: Primary users who will benefit from streamlined workflows.
  • Case Workers: accelerated response from supervisors.
  • System Administrators: Responsible for implementing and maintaining the new form.
  • Other contexts: to adopt the new form if found relevant
2 Likes
2

We already have a approval forms in cp which lists all the approvals in one place.
Also if we add all the forms (case plan, services, and follow-up) the new form will be long and untidy.

3

Supervisors are responsible for approvals, but the majority of their work involves monitoring and reviewing cases before granting approval. Several key fields and sub-forms provide a comprehensive overview of each case and are already present in the CM system. It can be not all fields from 3 forms. Only fields which show about completion of each service. The request/proposal is to consolidate these fields and sub-forms into a single Supervision form for easier navigation. This is crucial, as supervisors handle approximately 100 cases every one to two weeks.

4

Let’s explore this idea a little more. Ajit, i think there is some subform dev work in this. Can we use the work you did on CFM (summary form) for this?

5

@RMacT we can add different subforms in one form which will be autopopulated and uneditable. This can be done in much less time, however adding approve button will take much more time and lot of dev work.
I suggest to keep the approval button as it is since it is easier that way and develop the form with all subforms for supervisor.

I am free this week except friday and we can have a call with the team to explore this further

6

We have confirmed that the approval (button) is secondary. Main focus is monitoring implementation of the case plan. The supervisor should be able to easily see if the planned services that their team members are referring for are being properly implemented. Currently this involves flipping between multiple forms and subforms. I think the team is ok with your proposal Ajit. Keep refining requirements and adding details.