Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Reporting Ux topic

No spam. Unsubscribe anytime.

Washington participants request exportable 'Washington measures' report and clearer service‑status wording in Visit Tracker

Visit Tracker training (Data Keeper) / Department of Children, Youth, and Families (DCYF) · March 20, 2026
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Attendees asked for a single exportable Washington‑measures report (rather than multiple CSV form‑two extracts) and flagged confusing new status text for referrals; David said a state‑specific report would require DO/DCYF coordination and development resources.

During the Q&A, multiple participants asked for an exportable report that mirrors the Washington measures summary and can be downloaded to Excel for program QA and funder reporting. Lori, representing Early Head Start programs, said a consolidated "Washington measures report" that pulls the same fields together would be helpful for regular reporting.

David Tindell recommended that programs use the available form‑two CSV data as a workaround to assemble numerators and denominators, but acknowledged that a dedicated Washington measures export would require coordination with the Department of Children, Youth and Families (DCYF) and development work. He encouraged DO/DCYF and the community to follow up to scope a state‑specific report.

Participants also raised user‑experience issues: a text change introduced new status choices for services ("initiated/continued/discontinued/completed") that some users find harder to map to practice than the previous single "received services" flag. Attendees said the selection list can be confusing when programs receive ongoing services and simply want to indicate that a family is receiving support. Tindell agreed the change created unintended confusion and invited further discussion with DO/partners on clearer wording.

David encouraged administrators to set up reminder rules (accountwide) to generate consistent reminder lists for supervisors and home visitors; he recommended using the rules feature and asked administrators to file support tickets for record‑specific calculation anomalies so the development team can investigate.

The session closed with organizers noting the meeting recording and a follow‑up survey; they asked program leads to send feedback and tickets for both reporting and wording issues.