# data[].attributes.body
Should resource management clarifications (eg costing of manpower hours, justification for why we need specific headcount, logistical costs, etc) be a part of the programme planning phase?

Consideration: to justify requiring specific funding from funders, how will this cost be justified thru the outcome/ROI

# data[].attributes.body
Aside going to collect data, perhaps a note/FAQ on identifying what workable "data" is? So workers can understand data is something we are already collecting eg attendance, debrief themes vs something we need to separately collect

# data[].attributes.body
Programme lead - How to assess the expertise resources at each stage? for example, for data analyses how to assess the staff is competent in various data analyses, whether SHINE has internal resources, when to look for external resources?

# data[].attributes.headline
Must we always use client-centric evaluation for data collection

# data[].attributes.subject
Must we always use client-centric evaluation for data collection

# data[].attributes.body
Difficulties in assessing and evaluating pre-post results for youths, especially when questions tend to be very arbitrary and lacking a lot more context or nuances. Wondering if professionals-led data collection and assessment/evaluation might also be accepted as data collection?

(E.g. using the YLSCMI assessment tool for pre-post evaluation)

# data[].attributes.body
to add in checklist:

# data[].attributes.body
need to check accuracy of the transcription

# data[].attributes.body
double-check that the requisites of each stage are met

# data[].attributes.headline
develop shared language for data analyses

# data[].attributes.subject
develop shared language for data analyses

# data[].attributes.body
develop or educate - does not mean staff need to have expertise

# data[].attributes.body
Is there a list of people we can turn to if we have concerns/require clarifications? To consider using AI models/tools?

# data[].attributes.body
to include in FAQs:

# data[].attributes.body
If want to publish - IRB is strongly recommended. Otherwise, internal IRB etc

# data[].attributes.body
How can we help to educate ground staff and inculcate the importance & essentality of data collection and how it is already weaved into daily processes, such that it is done purposefully

# data[].attributes.headline
Data collection - Meaningful data collection

# data[].attributes.subject
Data collection - Meaningful data collection

# data[].attributes.body
To educate both planning & ground staff to ensure that the data collection means and methods are able to meet the data collection aim.

# data[].attributes.body
How can we incentivize participants to respond, and the guidelines for incentivisation?

# data[].attributes.body
For emerging/new programmes, team may have some outcomes in mind, but there may be some important outcomes or benefits to the youths which they feel is important as well.

# data[].attributes.headline
What is benchmarks and where to find it?

# data[].attributes.subject
What is benchmarks and where to find it?

# data[].attributes.body
links to SEF benchmarks, and other benchmarks of normed tools etc

# data[].attributes.body
1) Fidelity checklist - to include an example of a script used in FGD/ guidelines on how to design a script used in qualitative interviews.

2) Examples of benchmarks for a good fidelity training

3) Inclusion of Internal Ethics Review form

4) Guidelines of how to decide minimum sample size for data collection & on how and how much to follow up on participants that did not respond/missed surveys

5) Guidelines on whether we should reconsider participant criteria if there is low response rate, and if so, how should we restructure the criteria while meeting the intended aim of the data collection

6) Inclusion of sector-specific governance for data collection (NCSS sector eval framework) & Inclusion of SHINE specific policies regarding data collection from clients

7) Inclusion of a document to highlight different methods of data collection (pros and cons), and to also be able to justify the choice of data collection method.

# data[].attributes.headline
how to use the data analysis tools responsibly and mentioned that they are free

# data[].attributes.subject
how to use the data analysis tools responsibly and mentioned that they are free

# data[].attributes.body
Ways to review data collection fidelity (e.g. reviewing of recordings of FGD to ensure the FGD was done according to plan)

# data[].attributes.body
Need clarification about what "having a call to action" means

# data[].attributes.body
Having sections customised to different stakeholders is useful, makes it easy to understand what each stakeholder might be looking for.

Resources also useful because they're all located in one place

# data[].attributes.headline
Identifying stakeholders should be done in earlier stages

# data[].attributes.subject
Identifying stakeholders should be done in earlier stages

# data[].attributes.body
Stakeholders should already have been identified to ensure that the necessary data for each stakeholder has been collected. Rather, the focus should be on how to strategically engage each stakeholder e.g. how to present data to stakeholders, and what is each specific stakeholder particular about?

# data[].attributes.body
Must take into account that content of the eval depends on what the funder is looking for. E.g. if they're only concerned about what the tangible return on each dollar of their investment is, they might not be so concerned about the programme's impact

# data[].attributes.body
Would be useful to have resources on possible factors to bear in mind when looking for funders. E.g. track record of potential funder's past partnerships, administration and budgeting procedures (example, disbursement vs reimbursement method)

# data[].attributes.body
Actually knowing Power BI is enough, AI models might not be so relevant if we know how to use Power BI. But need to use additional brain space to learn Power BI

# data[].attributes.headline
how to identify stakeholders at ToC/LM stage? 

# data[].attributes.subject
how to identify stakeholders at ToC/LM stage? 

# data[].attributes.body
who is important? will be different for every programme coz at different life stage. who are essential etc

# data[].attributes.body
Is the objective of the tool to articulate impact or outcome? Is it supposed to help differentiate outcome vs impact?

# data[].attributes.body
After gathering feedback, how to prioritise what to follow up on?/How to know which gaps to tackle first? Some kind of framework to decide would be useful

# data[].attributes.body
Step 0 and Step 1:

• Is there a need for this service? Inward alignment and external alignment

• Who are the interested parties? Who are our competitors? Who will be supportive?

• Program decision tree (finance?)

• Obtaining inputs from key stakeholders for further refinement

○ May/not precede ToC and LM

○ Youth-led is if input from key stakeholders come first, professional-led is if it does not come before ToC and LM

○ For certain programmes (e.g., CRESTY), the key stakeholder input is alr determined before ToC and LM

# data[].attributes.body
Fidelity checklists - implement for higher risks situation e.g. heavily run by volunteers

# data[].attributes.headline
how to engage stakeholders and hold them responsible for the parts of the evaluation as agreed

# data[].attributes.subject
how to engage stakeholders and hold them responsible for the parts of the evaluation as agreed

# data[].attributes.headline
toolkit inclined to programmes where team has full control. 

# data[].attributes.subject
toolkit inclined to programmes where team has full control. 

# data[].attributes.body
many programmes tend to have stakeholders involved in different stages.

# data[].attributes.headline
Do we need a guide to help users decide which stage the programme is at?

# data[].attributes.subject
Do we need a guide to help users decide which stage the programme is at?

# data[].attributes.body
if each stakeholder has indicated different outcomes, how to align the different outcomes yet reduce survey fatigue?