{"id":"cs-onboarding-30-60-90-table","audience":"customer-success","category":"support-work","technique":"constraints","track":"support","level":"intermediate","title":"Turn kickoff notes into a 30-60-90 onboarding table","free":false,"task":"Turn the notes into a 30-60-90 onboarding table with the header row exactly \"Day | Milestone | Owner | Exit test\" and three rows for Day 30, Day 60 and Day 90. Go-live is Day 60 at the earliest, not Day 45. Every Owner is a named person from the notes. Plain text, under 100 words, table only.","materialLabel":"Your material (attached to your prompt automatically)","material":"KICKOFF NOTES: Sable Logistics (CSM: Jun Park)\nSponsor: CFO Elena Ruiz. Project lead: Mateo Ortiz (operations). IT: Farah Khan. Our implementation engineer: Leo Brandt.\n\nWhat was agreed:\n- Month 1: connect the fleet data feed (Farah + Leo) and build the first 3 dashboards (Mateo). Done when the feed runs 7 days without gaps.\n- Month 2: train 40 dispatchers (Mateo) and run a live pilot at the Dallas hub. Go-live for Dallas after the pilot passes. Implementation says 60 days is the minimum, 45 is not possible.\n- Month 3: roll out to the remaining 3 hubs (Leo leads, Mateo supports). Done when all 4 hubs are live and 90% of dispatchers log in weekly.\n\nElena (CFO) said on the call: 'I'd love go-live by day 45.'\nSide topics: invoice format, parking at the Dallas office, a request for a custom report (not scoped).","rules":[{"type":"plainText"},{"type":"maxWords","max":100}],"mistakes":[{"title":"Promising Day 45","why":"The CFO's wish appears in the notes and the AI schedules it.","fix":"Say: \"Go-live is Day 60 at the earliest, not Day 45.\"","checks":["r1"]},{"title":"Teams as owners","why":"The AI writes 'IT team' or 'Customer Success' as the owner.","fix":"Say: \"Owners are named people from the notes.\"","checks":["r2"]},{"title":"Wrong table","why":"The AI adds notes or columns.","fix":"Give the exact header and three rows.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"Gives the header","patterns":["day \\|","header"]},{"label":"Fixes the go-live","patterns":["day 60","not day 45"]}],"hint":"Plans need the real dates and named owners. Give the header, fix the go-live rule, and ask for exit tests.","rubricLabels":["The header row is exactly \"Day | Milestone | Owner | Exit test\" and there are exactly three rows for Day 30, Day 60 and Day 90","Day 60 is the Dallas go-live after the pilot (not Day 45), and Day 90 is the rollout to the remaining 3 hubs","Every owner is a named person from the notes (such as Farah and Leo, Mateo, Leo), and the exit tests include the 7 days without gaps and the 90% weekly logins"]}