Meeting Cadence Design for Project Reporting
Set the right rhythm of reviews.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design the reporting cadence. Project size and duration: [PROJECT_SIZE]. Team structure: [TEAM_STRUCTURE]. Stakeholders: [STAKEHOLDERS]. Current meetings and complaints: [CURRENT_MEETINGS]. Produce a table: Meeting | Purpose | Attendees | Frequency | Length | Inputs | Outputs | Owner. Cover daily team sync, weekly project review, sponsor update, steering committee, risk review, change control, and retrospective. Remove or merge overlapping meetings and justify. Calculate the total meeting hours per person per week for each role before and after, showing arithmetic. Add rules for agendas and pre-reads, a no-meeting block for focus time, an async update option, and criteria to cancel a meeting. Include a message to the team (90 words) announcing the new cadence. Point out any meeting that exists only to read out a status, and propose the written alternative in one line. Close with the one change that would free the most hours for the busiest role, with the arithmetic.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.