Ask ChartHop for Org Rollouts

you can use ask charthop to help with your org rollout! try a prompt like the below for a guide specific to your organization 🐇 charthop rollout checklist generator — reusable prompt you are a charthop implementation specialist i need you to generate a comprehensive, instance specific pre launch rollout checklist for my organization please do the following 1 audit the instance — pull the following data list all actions and note if any are configured list all reports/dashboards including their filters and visibility settings list all scenarios including type (backfill, create job, general) and who created them list all content/resource pages list all templates (email and document) list all calendars list all comp bands and note which geo zones/currencies are present list all custom fields and note sensitivity levels where visible list the org's groups (departments, locations, cost centers, and any custom group types) check total headcount and employment type breakdown (full time, part time, contract) check countries/pay groups represented in the org 2 build the checklist in the following sections section 1 — already configured ✅ list what is clearly in place based on the data pulled above be specific — reference actual dashboard names, field names, group types, and headcount numbers found in the instance section 2 — not yet configured ⚠️ list what appears to be missing (no actions, no templates, no content pages, no calendars, etc ) with specific recommendations for what to build section 3 — manual verification required 🔲 build out each of the following sub sections in detail, tailored to this specific instance 3 1 visibility settings (admin > configuration) org chart card fields — recommend specific fields based on what's available in this instance toggleable fields — flag any sensitive custom fields that should be restricted from the employee role profile header group tags — list the actual custom group types in this instance and which should be employee visible job details panel — recommend what to show/hide based on fields present profile tabs (comp, equity, time off, files, history) — recommend visibility per tab sensitive field audit — list all custom fields grouped by recommended sensitivity level (highly sensitive, personal, org public, manager shared), calling out any budget, actuals, payroll, dei, or internal planning fields specifically 3 2 dashboard home page (org settings) welcome message recommendations people moves configuration — which change types to show, recommended time window based on org size announce dates reminder for any open scenarios 3 3 sso (access > settings > sso) flag if any identity provider clues are visible (okta, google, azure, etc ) list the steps to verify toggle, idp config, attribute mapping, end to end test flag any employee populations (e g , contractors) who may need password fallback 3 4 auto invite configuration (access > settings) recommend a phased rollout filter plan using the actual employment types, countries, departments, locations or other group data found in this instance include specific cql filter examples for each phase using real field values from this instance flag any population that should be excluded (contractors, part time, international, etc ) with the exact filter to use include a work email audit reminder with the specific cql to run is\ person and contact workemail "" 3 5 invitation email recommend customization based on org size and complexity list what the invite should include specific to this organization 3 6 user management settings re auth frequency, auto sign out, invite expiration, notification recipients 3 7 approval chains if applicable (admin > approvals) list the actual scenario types found in this instance and who has been creating them recommend approver types per chain (manager, grand manager, specific person, person field, cql expression) with explanations of what each does in the context of this org list 6 specific test scenarios to run before launch, tailored to the scenario types found include post test verification steps 3 8 dashboards — filtering & visibility for each dashboard found in this instance, create a table row showing dashboard name | current filter | current visibility | recommended visibility | action required explain what dashboard filter, visibility (private / highly sensitive / org public), and data sharing (normal vs full) mean, using examples from the actual dashboards in this instance flag any dashboards that appear to be test/verification dashboards and recommend cleanup 3 9 custom roles (access > users > roles) build a role access summary table tailored to this org's structure list role assignment recommendations for each team type present in this instance (hr, finance, ta, engineering, etc ) provide role scoping cql filter examples using the actual groups, cost centers, or departments in this instance list specific "preview as" tests to run, calling out the actual sensitive field names found in this instance that should be verified as hidden from the employee role 3 10 "view as" testing list specific personas to test based on the roles and populations in this instance call out specific sensitive fields from this instance to verify are hidden 3 11 pilot group recommend a pilot group based on the departments/teams present in this instance build a phased rollout plan table using actual pay groups, countries, and employment types found, with specific cql filters for each phase 3 12 rollout communication checklist of comms steps faq doc, leadership announcement, manager briefing, go live date, enabling daily sync last 3 13 quick reference invite population summary build a table showing each population segment found in this instance with estimated counts and notes 3 formatting rules use ✅ for confirmed complete, ⚠️ for needs setup, ☐ for manual verification required use real field names, dashboard names, group names, pay group values, and cql expressions from this instance — do not use placeholder examples where cql filters are recommended, validate them using the expression tool before including them use tables wherever a comparison or multi column view adds clarity keep the tone practical and action oriented — this is a working checklist, not a summary doc 💡 tips for best results tip detail run it early in implementation the more data loaded in the instance, the more specific and useful the output will be run it again pre launch run the prompt a second time closer to go live — the checklist will update to reflect what's been completed since the first run customize section 2 if the customer has forms, shoutouts, or teams configured, add those entity types to the audit list in step 1 add customer specific context prepend any known details (e g , "this is a 500 person retail company with us and uk employees and a workday integration") for even more tailored output use it as a living doc copy the output into notion, google docs, or confluence and check items off as you go through the implementation