Program Evaluation
Mission-driven engagements where donor relationships, program delivery, and governance determine impact.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Engagement Discovery
Clarify evaluation goals, decision-use questions, stakeholders, existing evidence, and constraints for the evaluation.
Discovery Questions
Why you're starting this evaluation
- Tell me the main decision or deadline that prompted you to seek an external evaluation now.
- Who on your team will coordinate with external evaluators day to day?
- Which program, cohort, or grant cycle should be included in scope?
- How many staff or sites are directly involved in delivering the program?
- Describe the primary audiences who must find the final report credible and useful.
- Estimate the funding or renewal amount tied to this evaluation decision.
- If the evaluation concludes before your next board meeting, would that change how you would use the findings?
Where the program stands today
- Imagine a skeptical board member asked you to prove the program works today, what pieces of evidence would you show first?
- List the routine metrics you already collect on participation and outcomes.
- Who currently owns the data and where is it stored, in a database, spreadsheets, or elsewhere?
- On a scale from 1 to 5, how confident are you in the quality of those outcome measures?
- Give a brief example of a recent report or dashboard you'd share with funders.
- Which single data gap would prevent an external evaluator from producing credible results?
What's getting in the way of clear answers
- Walk me through the last time a data or approval issue delayed a decision, what broke and what was the consequence?
- In your experience, which approvals or gatekeepers most commonly set the timeline back?
- To whom do requests for sensitive participant data typically go first?
- Do past vendor contracts or confidentiality clauses limit what external teams can access?
- Give an example of a political or donor sensitivity that shaped what you could publish previously.
- Name the single approval or constraint that, if not satisfied, would stop this evaluation from starting.
Who the evaluation must speak to
- If equity were the primary test of success, where do you expect your program to struggle most?
- List the participant subgroups and geographic contexts where outcomes may differ.
- In stakeholder conversations, what language is used to describe service gaps or unfairness?
- Name the community partners or oversight roles whose buy-in will make the findings credible.
- What kinds of harms or unintended effects are you most worried an evaluation could uncover?
- Should the evaluation indicate widening disparities, who has the authority to change program policy immediately?
How we'll design a study that people will trust
- Imagine an external reviewer will judge the study design, which design decision would most affect their verdict?
- Identify the three outcomes your leadership considers non-negotiable for drawing conclusions.
- Estimate the minimum sample size or number of sites you believe will convince funders.
- Do your stakeholders prefer randomized, quasi-experimental, or pre-post designs, or are they flexible?
- Select the deliverable format your board prefers, a 2-page brief, an executive memo, a full technical report, or a data appendix.
- Tell us the deadline or milestone that would force you to stop the study if we could not meet it.
The other options you're weighing
- Suppose your current provider gave you the same findings at no extra cost, what would still be missing?
- Provide the external vendors, internal teams, or academic partners you have already spoken with.
- What would have to be true about your current approach for you to keep it rather than hire an outside evaluator?
- Has anyone on your team proposed doing this evaluation internally instead of contracting an external firm?
- Rank the alternatives you are considering by likelihood you'll pick them, with 1 being most likely.
- Explain the one advantage the incumbent must demonstrably have for you to stay with them.
Practical readiness and gating issues
- Identify the single infrastructure or data access gap that would prevent the evaluation from proceeding on schedule.
- Does your data live in a central system with APIs, in multiple databases, or primarily in spreadsheets?
- Point to the role that will provide credentials and technical contacts for system access.
- Provide your best estimate of the percentage of records that are incomplete or inconsistent today.
- Are there IRB, ethics, or legal reviews required, and if so, what is the expected approval timeline?
- Please indicate whether your team has capacity to support interviews, recruitment, and data pulls, or whether you expect the evaluator to provide that capacity.
- Should key data access not be available within 6 weeks, will you postpone, rescope, or cancel the project?
How you'll know this evaluation succeeded and what comes next
- Explain the single finding that would cause leadership to change funding or scale the program immediately.
- To whom should final deliverables be addressed and who will lead the acceptance review?
- On a scale from 'sign now' to 'request more analysis', where would an ideal final brief land for your board?
- Within how many weeks would you want the evaluator to provide a draft for internal review after fieldwork ends?
- Select from the following follow-up supports that would increase adoption, and add any others.
- Are you prepared to commit funding to a scale-up within the next quarter if the pilot meets the agreed success criteria?
-
Engagement Scope
Define the study design, methods, deliverables, timeline, equity analysis approach, and success criteria.
Scope Configuration
- Administer standardized outcome surveys to participants
- Collect and clean administrative and program data
- Link participant records across datasets
- Conduct in-depth participant interviews
- Facilitate stakeholder focus groups
- Implement randomized assignment and trial procedures
- Perform quasi-experimental matching and comparative analysis
- Run statistical outcome modeling and subgroup tests
- Disaggregate outcomes by race, income, and geography
- Produce executive findings brief with specific recommendations
- Develop accessible data visualizations and dashboards
- Manage IRB submission and human-subjects compliance
Scope Questions
Administer standardized outcome surveys to participants
- Do you plan to administer surveys in person, by phone, by web, or a mix of modes?
- Which standardized instrument(s) do you intend to use for primary outcomes (for example PHQ-9 for depression, PROMIS for health, validated employment outcomes)?
- How many survey waves do you require (for example baseline, endline at 12 months, 6-month follow-up)?
- What target sample size do you expect per wave for the survey (approximate counts are fine)?
- Which language(s) must the instrument and consent materials be available in (list specific languages used by participants)?
- Who will provide the participant contact list and existing consent status for outreach to complete the surveys?
- Describe the expected nonresponse or attrition risk between waves and any strategies you require (for example phone reminders, incentives).
- What incentive strategy is acceptable to encourage survey completion (for example $25 gift card, raffle, no incentive)?
- Which data security measures must be applied during survey collection (for example SSL/TLS for web surveys, encrypted recorder for phone interviews)?
- How should we handle consent documentation for minors or legally protected populations if included?
Collect and clean administrative and program data
- What administrative sources will be available for extraction (for example case management database, LMS export, payroll files, enrollment rosters)?
- Which file formats will you provide for administrative exports (for example CSV, Excel, SQL dump)?
- Who will be the technical contact with access to the source systems and data dictionary for each administrative source?
- What minimum data quality thresholds should trigger remediation prior to analysis (for example >=95% completeness on primary outcome fields, <2% duplicate IDs)?
- What acceptance criteria will confirm the cleaned analytic dataset is ready for linkage and analysis (give measurable checks such as variable-level dictionary, completeness rate, resolved mismatches)?
- Are there regulatory or contractual restrictions on sharing raw administrative files (for example data-use agreements, state restrictions)?
- How do you prefer we document cleaning steps and changes to the source fields (for example annotated data dictionary, cleaning script with version control)?
- Which timeline do you require for initial data delivery and the cleaned deliverable (for example raw files within 2 weeks, cleaned analytic file within 6 weeks)?
- What out-of-scope activities should be noted for the engagement (for example ongoing operational support, full ETL pipeline maintenance, implementation of recommendations)?
- Are there agreed performance SLAs for turnaround on urgent data requests during analysis (for example 48-hour turnaround on ad-hoc extracts)?
Link participant records across datasets
- Which unique identifiers are present across datasets to support deterministic linkage (for example participant ID, email, phone, SSN last four)?
- What privacy constraints apply to identifiers (for example SSN cannot be transferred offsite, hashed IDs only)?
- Which fuzzy-match fields would you allow for probabilistic linkage if exact IDs are missing (for example first name, last name, date of birth, ZIP code)?
- How will you validate linkage quality (for example clerical review sample, match rate thresholds, false match checks)?
- Who will own the master linkage key and how should it be named and versioned in the analytic files?
- How should we handle duplicate or conflicting records across sources (for example preference order, most recent record wins)?
- Which governance approvals are required before attempting cross-system linkage (for example signed data-use agreement, IT firewall exception)?
- How should provenance of linked records be tracked in deliverables (for example source system column, match confidence score)?
Conduct in-depth participant interviews
- Which participant subgroups should be prioritized for in-depth interviews (for example non-responders, high-benefit, marginalized groups)?
- What is the target number of interviews and the expected duration for each interview (for example 30–60 minutes)?
- Which interview language(s) and interpreter arrangements are required for interviews?
- How should interview participants be recruited and consented (for example phone outreach by your staff, we recruit using provided contacts, consent at time of interview)?
- What recording and transcription standards do you require (for example verbatim transcript, time-stamped, translated transcripts)?
- Are there sensitive topics requiring special protocols for trauma-informed interviewing or referral resources?
- Which topic guides or domains must interviews cover based on your logic model or theory of change (for example barriers to participation, perceived program benefits)?
- Do you require verbatim quotations linked to participant demographic metadata for reporting (for example quote + age bracket + program dosage)?
Facilitate stakeholder focus groups
- Which stakeholder types should be convened for focus groups (for example frontline staff, program participants, partner agencies)?
- How many focus groups do you anticipate and what is the ideal group size per session?
- What facilitation style and deliverables do you prefer (for example recorded + transcript, facilitator summary with verbatim quotes, live synthesis session)?
- Which accessibility accommodations are required for participants (for example childcare stipend, remote access, ASL interpreters)?
- Who will coordinate participant recruitment logistics such as incentives, scheduling, and venue or virtual platform access?
- Are there confidentiality or power-dynamics concerns we should plan for when mixing stakeholder types in the same group?
- Which outputs do you expect from each focus group session (for example facilitator synthesis memo, thematic codebook, verbatim excerpts)?
Implement randomized assignment and trial procedures
- What is the planned unit of randomization (for example individual participant, site/center, cohort)?
- Which stratification or blocking factors should the randomization include (for example baseline risk score, region, ZIP code)?
- How should treatment assignment be documented and auditable (for example randomization script with seed, treatment assignment log, timestamped exports)?
- What minimum balance checks do you require post-randomization (for example p>0.10 for covariate differences, standardized mean differences <0.1)?
- Which monitoring or integrity safeguards should be in place to prevent contamination or treatment crossover (for example fidelity checks, site training, monitoring visits)?
- Who will be the authorized signatory for protocol deviations and emergency unblinding if needed?
- What timeline milestones are tied to randomization (for example baseline window closes then randomize within 7 days)?
Perform quasi-experimental matching and comparative analysis
- Which comparison group sources are available for matching (for example waitlist applicants, administrative records from similar sites, external cohort)?
- What baseline covariates should be prioritized for matching (for example prior outcomes, age, baseline score, ZIP code-level poverty rate)?
- Which matching method do you prefer or allow (for example propensity score matching, coarsened exact matching, nearest neighbor)?
- How should imbalance after matching be evaluated and reported (for example standardized differences table, visual diagnostics)?
- Are there exclusion criteria for comparison units you want enforced before matching (for example missing baseline outcomes, prior participation in pilot)?
- What level of documentation do you require for matching code and reproducibility (for example commented scripts, reproducible notebook, versioned code repository)?
- Are linked covariate data available at the individual or site level to support matching (for example individual prior outcomes, site-level baseline rates)?
Run statistical outcome modeling and subgroup tests
- Which primary outcome measures and time windows should models target (for example employment status at 6 months, test score change at endline)?
- What modeling approaches are acceptable (for example linear mixed effects, logistic regression, survival analysis)?
- What statistical significance threshold or confidence level should we use for hypothesis tests (for example alpha = 0.05, 95% confidence intervals)?
-
Agreement & Authorization
Finalize the SOW, fees, contracting, data-sharing agreements, and any required IRB/ethics approvals before fieldwork begins.
Agreement Modules
- Non-Disclosure Agreement (NDA)
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Fee Schedule & Payment Terms
- Data Sharing & Processing Agreement (DSA/DPA)
- IRB / Ethics Approval Confirmation
- Regulatory Compliance Addendum (conditional)
-
Fieldwork & Delivery
Conduct planned fieldwork, produce the evaluation report, and confirm client acceptance.
-
Fieldwork & Interviews
Execute qualitative fieldwork, surveys, administrative data pulls, and stakeholder interviews per the agreed protocol.
Working Sessions
- Fieldwork Kickoff and Protocol Confirmation
- Administrative Data Pull and Survey Launch
- Stakeholder Interview Schedule and Consent Log
- Midfieldwork Debrief and Protocol Adjustments
- Fieldwork Closeout and Raw Data Handover
- Launch targeted recruitment efforts for identified underrepresented subgroups.
- Consent log template and initial entries are agreed and ready for use.
- Contingency and accessibility plans for interviews are documented.
- Publish the finalized interview schedule with contact slots and modality notes.
- Populate and upload the consent log template with initial confirmed participants.
- Assign and document backup interview slots and interpreter contacts where required.
- Review response rates, completed interviews, and data quality flags
- A clear list of protocol amendments is agreed to address data quality or equity gaps.
- Decision on targeted recruitment actions for underrepresented subgroups is made.
- Timeline and ownerless action list for implementing amendments is confirmed.
- Update the protocol and instrument files with the agreed amendments and redistribute them.
- Reconfirm scope and success criteria
- Run an immediate quality check after amendments are implemented and report results at the next check-in.
- Confirm completion status of interviews, surveys, and data pulls
- All raw fieldwork files are accepted or a clear short list of outstanding items is recorded.
- Metadata, codebooks, and anonymization procedures are confirmed and sufficient for analysis.
- Handover timeline into the analysis phase is agreed and any remaining data requests are scheduled.
- Deliver the final organized folder of transcripts, recordings, survey exports, and admin extracts to the designated analysis endpoint.
- Upload complete metadata, codebook, and a data dictionary for all delivered files.
- Log any residual fieldwork queries and schedule their resolution before analysis starts.
- Signed-off final versions of all instruments and consent language are confirmed for use.
- Sampling frame and recruitment plan approved, including subgroup quotas for equity analysis.
- Fieldwork schedule and logistics confirmed with access and safety procedures documented.
- Distribute the final protocol document and instrument files in the shared workspace.
- Provide the initial contact list and any required site access credentials before the first field day.
- Publish the finalized field schedule with named roles and backup contacts.
- Agree required data elements and formats
- A complete data extract specification is approved and ready for execution.
- Secure transfer and storage procedures are confirmed for administrative data.
- Survey is ready to launch with response targets and monitoring plan in place.
- Deliver the finalized data extraction script or spec to the data steward with target delivery dates.
- Activate the survey and share the live link and reminder schedule in the shared workspace.
- Schedule recurring data quality checks and publish the monitoring cadence.
- Review and prioritize stakeholder list
- A timed interview schedule covering the target sample is finalized and published.
- Review inventory of transcripts, recordings, and raw datasets
- Discuss early qualitative themes and observed gaps
- Confirm interview modalities and timing windows
- Finalize data collection instruments and consent language
- Confirm extraction queries, timeframe, and validation rules
- Approve sampling, recruitment, and respondent quotas
- Authorize secure transfer and storage method
- Confirm anonymization, redaction, and metadata documentation
- Agree on consent tracking and documentation
- Assess equity coverage and sampling shortfalls
- Accept raw files for analysis and set any follow-up data requests
- Confirm logistics, access, and safety protocols
- Plan for no-shows, interpreters, and accessibility needs
- Survey launch checklist and response targets
- Decide protocol adjustments and document amendments
- Lock schedule and responsibilities
- Confirm timeline for implementing changes
- Handover timeline and next steps for analysis
- Establish data quality monitoring and escalation
-
Evaluation Deliverable
Analyze findings with an equity lens and produce specific reports, briefs, and data files for review and feedback.
- desired_state
- current_state
- stakeholders
- gaps
- success_criteria
- decision_readiness
- desired_state
- decision_readiness
- current_state
- success_criteria
- gaps
- stakeholders
- desired_state
- success_criteria
- stakeholders
- gaps
- current_state
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Delivery Acceptance
Confirm receipt, review, and formal sign-off of final deliverables against acceptance criteria before closing the engagement.
Checklist items
- Confirm all final deliverables uploaded to agreed repository
- Complete acceptance review of each deliverable against Engagement Scope criteria
- Obtain written acceptance sign-off from designated buyer approver
- Verify de-identification and data-sharing compliance for transferred datasets
- Provide IRB/ethics closure or compliance documentation where required
- Transfer analytic code, codebook, and documentation with access verification
- Secure written permission for any public dissemination or external sharing
- Confirm final invoice issued and financial close actions initiated
- Handover post-delivery monitoring and follow-up plan
- Archive project records and confirm retention/access instructions
-
-
Outcomes & Follow-Up
Support uptake of recommendations, monitor agreed indicators, and maintain a shared channel for issues and follow-ups.
Outcomes & Follow-Up
- Findings Acceptance Check (weeks 1-4)
- Roadmap Prioritization Workshop (weeks 4-10)
- Implementation Readiness Check (around day 60-90)
- Quarterly Follow-up and Uptake Review (ongoing quarterly)
Issues & Enhancements
- Client-side owners to update their initiative status in the shared tracker at least 5 business days before the next quarterly review.
- Compile and circulate a single tracker of identified implementation blockers with proposed resolution steps and deadlines.
- Client to confirm owners and update any timeline constraints within 7 business days.
- Status report on each prioritized initiative
- Confirm the percentage of implementation blockers resolved and decide whether readiness targets recorded in Engagement Scope are met.
- Agree remediation timelines for any remaining blockers that prevent initiative start or scale-up.
- Update the roadmap tracker with blocker resolution status and revised start/completion dates where applicable.
- Publish a short decision memo stating whether readiness targets recorded in Engagement Scope are met and listing conditional remediation items if applicable.
- Client to confirm internal resource commitments and finalize any required internal approvals within the agreed remediation timelines.
- Quarterly metric review
- Maintain or improve the implementation blockers resolved rate quarter over quarter and keep the prioritized action count on schedule.
- Ensure each initiative retains a named client-side owner who provides a status update before the next quarterly review.
- Circulate the quarterly status dashboard showing prioritized initiatives, blockers resolved, and the findings acceptance rate trend.
- Create a short issue tracker for any newly surfaced blockers with proposed resolution steps and target dates.
- Recap final deliverables and acceptance criteria
- Achieve a documented findings acceptance rate and record which report sections are accepted or disputed.
- Produce a discrete list of unresolved evidence gaps with remediation actions and deadlines.
- Distribute an annotated copy of the final deliverable marking accepted sections and disputed items for formal sign-off.
- Provide a dated list of remediation actions and the evidence required to raise the findings acceptance rate to target levels recorded in Engagement Scope.
- Client to submit formal acceptance status (accepted / conditionally accepted / not accepted) and any final comments within 5 business days.
- Review recommended initiatives and priority criteria
- Produce a ranked roadmap listing the prioritized action count with a named client-side owner assigned to each initiative.
- Capture the initial set of implementation blockers and a plan to resolve the highest-risk items before the readiness check.
- Publish the prioritized roadmap with assigned owners, tentative dates, and the scoring rationale to the shared workspace.
- Review acceptance feedback and audit findings acceptance rate
- Review implementation blockers resolved vs open
- Review status updates from client-side owners
- Score and rank initiatives
- Surface and triage new blockers
- Assign client-side owners and tentative timelines
- List unresolved evidence gaps or clarifying questions
- Root-cause diagnosis for stalled initiatives
- Adjust follow-up frequency or format if needed
- Decision on readiness to proceed
- Identify known implementation blockers
- Agree next steps to resolve open items
- Document acceptance status outcome
- Agree handoff and documentation for implementation