What's New in Planner
Planner documentation now reflects the current product direction: schedule intelligence, schedule editing, quality governance, AI-assisted review, comparison, resource analysis, and schedule-to-report workflows.
Current development themes
| Area | What to document |
|---|---|
| Schedule review | Import schedules, inspect activities, navigate Gantt views, and validate structure before sharing findings. |
| Quality governance | Run checks, interpret category scores, tune thresholds, and turn findings into action lists. |
| AI schedule work | Ask questions, generate narratives, request grid updates, and confirm changes before applying them. |
| Comparison | Compare baseline/current or two schedule versions and explain movement in activities, WBS, dates, and resources. |
| Planner reporting | Convert schedule views, quality findings, comparison deltas, and AI narratives into shareable reports. |
| Exports | Package schedule data and reporting outputs for project teams and stakeholders. |
Planner reporting
Planner reporting should be documented as the reporting path for schedule analysis work. Use it when the source evidence is schedule quality, schedule comparison, resource loading, or AI-generated schedule narratives.
Use Report Forge when the team needs governed recurring report blueprints, structured contributor updates, review history, and polished report packages across many reporting cycles.
Documentation guardrail
Do not publish unfinished or unapproved feature marketing in public docs. Keep advanced schedule-analysis features that are still under active development out of user-facing pages until they are ready for release documentation.