# data[].attributes.body
Internally practicing with TIPS meeting minute guide first and then invite TAPs to join with feedback

# data[].attributes.body
MTSS Intro by TAPs Virtually - Doodle by Shawna by 9/5/25

# data[].attributes.body
TIPS Model Meeting Virtually - Date TBD, Doodle by Shawna by 9/5/25

# data[].attributes.body
Coaching Action Plans

# data[].attributes.body
Peru Goals

# data[].attributes.body
Gathering more information from EOs

# data[].attributes.body
TAPs joining in person work to provide prompting, modeling, and feedback

# data[].attributes.body
Sept. 3 and Sept. 4 TIPS training at Franklin Essex BOCES (SAME ROOM)

# data[].attributes.body
Modeling of tools (RTFI, TFI, DCA)

# data[].attributes.body
FACE- develop aligned actions

# data[].attributes.body
process, big picture

# data[].attributes.body
if they don't have data/can't produce data- this is probably area of need that can be addressed via support plan

# data[].attributes.body
aligned content for at risk TSG

# data[].attributes.body
at risk TSG planning

# data[].attributes.body
data systems: what to do when districts can't find their data, what resources they should be looking for, etc.

# data[].attributes.body
facilitator skills: language / selling the innovations and tools in a less jargon-y way (R-TFI/MTSS for Literacy)

# data[].attributes.body
Current data provided by the district and publicly released, data that provides evidence of past practices and their impact

# data[].attributes.body
Current data on student outcomes, data on past practices that have been successful or unsuccessful, data related to district capacity

# data[].attributes.body
Develop a team that has buy in on the work, and to determine an innovation that will meet the need and ensure feasibility of implementation

# data[].attributes.body
Data that the district has or can be sourced to reflect on what is needed in the district.

# data[].attributes.body
To determine with a team, what practice you are going to implement and make sure it meets the needs of all stakeholders

# data[].attributes.body
To evaluate if a program or practice meets the needs of all stakeholders (students, teachers, community, etc.), if the program or practice matches the values of all stakeholders and if the district has the capacity to implement the program or practice with fidelity

# data[].attributes.body
Current data, or lack thereof, to assist EOs in accessing, interpreting, and then changing their data trends.

# data[].attributes.body
To learn what is specific to this EO, past practices, beliefs, and needs; that way, their plan can be unique, individualized, and targeted based on the information and data provided.

# data[].attributes.body
Virtual Intro to TSG - Shawna, RPC, FACE (Virtual- July 3rd @ 9am-11am)

# data[].attributes.body
Continue conversation about support planning process- TAPS, RPC, FACE (in person date: August 20th 9am-3pm)

# data[].attributes.body
TAP Support with Planning (TAP, RPC, FACE)

# data[].attributes.body
internal planning and dates RPC/FACE

# data[].attributes.body
organization of COA files in google- Abby

# data[].attributes.body
Administrative support, collaboration - team approach, shared vision - our why

# data[].attributes.body
Lack of training to all staff members, scheduling/time, implementation was too fast

# data[].attributes.body
1. Staff who are difficult or "not on board" with the initiatives were invited as part of the team.

2. Plans were made to implement with fidelity.

3. The Team asked for feedback

# data[].attributes.body
Lack of time for staff training, unclear supervision/admin structures, lack of follow-up/monitoring of initiatives

# data[].attributes.body
1. Open communication and discussion before beginning

2. Continuous positive feedback about progress

3. Team celebrations of successes and reached milestones

# data[].attributes.body
1. The plan was floated to a team of stakeholders prior so the idea could be made into a clear plan

2. The plan was then adjusted based on feedback and supporting resources added.

3. The plan was rolled out to all with clear expectations, check-ins, a timeline, resources, and communication lines.

# data[].attributes.body
1. Lack of communication protocols.

2. The right people weren't in the room.

3. Implementation was too quick and too large

# data[].attributes.body
1. Not creating a team with mulitple perspectives (one person making shelf art)

2. Lack of planning and research to make informed decisions

3. Not measuring fidelity of implementation

# data[].attributes.body
1. Lack of clarity

2. Not a clear WHY

3. Lack of resources/process

# data[].attributes.body
Create a welcoming space

# data[].attributes.body
Promote understanding between group members

# data[].attributes.body
Identify relevant group members

# data[].attributes.body
Be a bridge

# data[].attributes.body
Use pgs 10 -13 of ISP practice profile

# data[].attributes.body
Use pgs 8 & 9 of ISP practice profile

# data[].attributes.body
Think of a time where you observed/experienced successful implementation.​

1. ​Identify at least 3 contributors to the successful implementation.​

2. Jot them down

# data[].attributes.body
Think of a time where you observed or experienced implementation barriers.​

1. ​Identify at least 3 contributors of the implementation struggles.​

2. Jot them down