# data[].attributes.body
Can there be a curated list of Context/Setting videos 101 for new folks?

# data[].attributes.body
101 trainings in Basecamp available for new folks?

# data[].attributes.body
Evaluation training Elevate Eval

# data[].attributes.body
Communication champions

# data[].attributes.headline
I liked that there was a Healthcare 101 that happened yesterday since a bunch of new people had started recently. I wish this was something that happened every few months so that I could have had this when I first started.

# data[].attributes.subject
I liked that there was a Healthcare 101 that happened yesterday since a bunch of new people had started recently. I wish this was something that happened every few months so that I could have had this when I first started.

# data[].attributes.body
Nothing against SMART goals. You don't know what's realistic or specific. Its subconsciously incorporated.

# data[].attributes.body
i should add that we occasionally will use data as part of the work plan development. I should consider adding more data as part of the work plan.

# data[].attributes.body
We're naturally doing the smart goals from the structure of the HUB. We don't go to that naturally.

# data[].attributes.body
Revising: Sometimes we have very limited information with a partner site. Sometimes we have to pivot. Same partnership but changing the context and setting changes needed.

# data[].attributes.body
Updating workplans; At what point do we sunset a project? Do we remove it and then we find out a year or two later they want to pick it up again? Sometimes we'll keep partner sites on board for example in CTF where we might need to do enforcement in a few years after PSE. With different bodies of work, when do we need to do a various request?

# data[].attributes.body
Revising workplan: Look as assessment results. You might find out work needs to shift. Look at SEWA or school assessments, take a look at that. Making sure when during the workplan, keep track of partner site IDs for the hub.

# data[].attributes.body
Resources: I have a fiscal person. CPA has the information needed for the right coding. I avoid REDCap requests because there is a delay. If there is a request that SHIP can't cover, I try to use other funds. I add it to the leverage tracker. We don't often like to be the fiscal host. We like to have our partners do the request and receiving. Then making sure that stuff gets added back to the Hub.

# data[].attributes.body
Internal communications: We are the fiscal host and we contract with our other counties. I work with our accountant who develops an excel spreadsheet. I take invoices which then goes to the accountant. Communicating regularly to make sure things are working properly. Besides the SEWA, I do the REDCap reporting. I forward questions and information on to coordinators. I make sure REDCap is mirroring workplans in the hub. Not perfect, but checking those as often as possible. When we have Community Partner Awards, we have an excel spreadsheet, and a gmail account thats just associated with the CPA. The CLTs approve the CPAs. The CPAs have sections for each context area and we already have a workplan developed for that partner. If things aren't allowed, we make sure to request via REDCap. Having the extra spreadsheets are helpful. REDCap is repetitive and put those in the Workplan. Making sure we have better detail in the invoice, not just the partner site, but also the activity.

# data[].attributes.body
Our CLT are more in another county. Wish they were a little bit more progressive/open. Maybe need time to revisit recruitment for CLT. Come up with our ideas with collaborative partners like a hunger team and work with them. Drafting the plan: Using REDCap. Outlines what those PSE changes need to be. So you don't need to look back, its already in the SHIP hub. Implementation Guide.

# data[].attributes.body
Resources: Utilize community leadership team to direct need. Data sources like Minnesota Student Survey. Go towards where there is momentum- CLTs will direct work towards us. Internal resources: Nightingale notes. Having those conversations with community partners, developing work plans with partners, see where work is going. A lot of PH have CHIP plans-aligning as much of our SHIP with CHIP work is really great to leverage funding opportunities.

# data[].attributes.body
Hub is great but doesn't always work. So make sure to have a paper copy with notes and updates. When its time to make updates, I do the updates in the Hub and hope that it works. I take updates from my counterpart.

# data[].attributes.body
Coordinators meet to talk through workplans. Go into the Hub and modify things in real time. Phenomenal to all have access to the workplans in real time. Reviewing the workplans on a monthly basis to make sure we're on track. We have our own ways of tracking our time internally.