Certified Strategic Project Leader

The Strategic Shift — From Administrator to Strategic Leader

Project managers spend the majority of their time on work that does not require a project manager: writing status updates, re-typing the same task list into three tools, chasing budget approvals by email, drafting the same kickoff deck for the fifth time this year. Industry studies consistently show that 60–80% of a PM's week is consumed by administrative overhead — planning logistics, documentation, status reporting, and re-keying data — leaving a minority of time for the activities that actually determine project success: judgment calls, risk anticipation, stakeholder alignment, and team coaching.

CoMng.AI is built AI-native from the ground up — not a legacy PM tool with a chatbot stapled on. Every object in the platform (a task, a budget line, a team member, a note, a change request) carries an AI action button that can generate, analyze, assess, or execute that object's content. The practical effect for you as a PM is that the entire "administrative layer" of project management — task breakdown, scheduling, budget drafting, documentation, status reporting — can be generated and maintained by AI, while you supervise, decide, and lead.

The Four Pillars of Strategic Leadership in CoMng.AI

Project Genesis & AI Framework Generation

Every project starts as a blank page — and the blank page is where administrative paralysis begins. CoMng.AI removes the blank page by giving you four entry points, each suited to a different starting condition.

Regenerating the Project Framework

Once a project exists, Project Settings exposes Generate Project Framework (or Regenerate, once one exists). This single AI action produces goals, milestones, success metrics, and risks directly from the project description. For best accuracy, write a description that includes: hard deadline, budget ceiling, known resource constraints, and known blockers — the AI factors all of these into milestone spacing and risk identification.

Regenerate is not a blind reset. When you click it on a project that already has a framework, the modal shows you the existing framework as context — so you are refining and updating your description in light of what's already there, not starting from a blank page. The AI then re-derives the full framework using both your edited description and that existing context.

Regenerate vs. Per-Item Estimate/Assess — Which One Should a Manager Use?

This is a real decision point, and the two tool families exist to solve different problems:

Keeping the Framework Current — Per-Item AI Assessment

A framework generated once at kickoff goes stale the moment execution starts. Project Settings gives every individual goal, milestone, metric, and risk its own AI assessment button so the framework can be refreshed item-by-item as reality unfolds, instead of only via a full regeneration:

Command Hub, Project Pulse & RAG Status

The Project Management Hub is your executive cockpit — the page you should open first every single day. Four stat gauges (Tasks, Time/Effort, Team, Budget) plus a unified timeline merging tasks, milestones, activities, and budget dates give you a single-glance status check that used to require pulling four separate reports.

The Project Tools Menu — Your AI Advisory Board

The same dropdown also holds five governance and distribution actions — covered in depth elsewhere in this course, but worth knowing they live right here on the Hub alongside the AI advisory tools:

Project Pulse — The Health Score

Pulse computes a 0–100 score from five sub-scores: Schedule (due-date adherence), Budget (spend vs. approved), Velocity (completion rate), Risk (open risk count/severity), and Team (workload balance). 70–100 is Healthy (green), 40–69 is Warning (orange), 0–39 is Critical (red).

RAG Status — The Five Dimensions

The overall RAG colour always equals the worst dimension — one Red dimension makes the whole project Red, regardless of how green everything else is.

Tasks & AI Task Automation

Tasks are the atomic unit of execution, and historically the single biggest time sink for a PM: writing descriptions, estimating effort, chasing assignment decisions, and re-explaining the same task to three different people. CoMng.AI attaches an AI action to nearly every step of this lifecycle.

Task Fundamentals

Each task carries: title, description, status (Pending / In Progress / Completed / Overdue / Cancelled), an automatically-calculated priority score (High ≥70, Medium ≥40, Low <40 — driven by due-date proximity, complexity, dependencies, and workload — never set manually), effort in hours, dates, assignee, type, subtasks, tags, dependencies, and a discussion thread.

Task Views

Four view toggles sit at the right end of the Tasks page toolbar — distinct from the separate Kanban Board, Gantt Chart, and Calendar pages covered in Module 4:

Filtering, Search, and Special States

The filter bar (present on both Outline and List views, and inside Bulk Edit) combines: Status, Type, Member (assignee), Due Date, Tag, and — once at least one parent task exists — a Parent filter that narrows the list to a single WBS branch. A free-text search box narrows by title. The Status dropdown also exposes two special states beyond the five normal statuses: 🚫 Blocked only (every task currently blocked, whether by an incomplete dependency or a manual block) and ⚠️ Scope Creep (tasks flagged as outside the original project scope — see Module 3B).

Dependency Focus Panel (Per-Task)

Click the dependency icon on any task card (in Outline or List view) to open the Dependency Focus Panel — a three-column visual graph: Before (tasks this task depends on — its blockers), Selected (the task you clicked), and After (tasks that depend on this one — what it blocks). This is the fastest way to see the blast radius of a delay before you reschedule anything. It's the per-task counterpart to the project-wide Grouped View on the dedicated Task Dependencies page (Module 3C) — use this panel for a quick "what does this one task touch?" check, and the dedicated page when you need to manage dependencies across the whole project.

Per-Task AI Dropdown

Project-Wide Toolbar AI Tools

Optimize Timeline — When to Use Which Mode

The hardest part of using Optimize Timeline well isn't running it — it's picking the right mode for the situation. Three common scenarios:

Two AI buttons appear directly on the card without opening a dropdown: Get Insights and AI Unblock (blocked tasks only). Each task can also be exported individually as a self-contained HTML document, and shared externally (Email, Teams, Slack, Google Chat, Jira, Copy Link) with optional password protection.

Bulk Edit — Full Toolbar

The Bulk Edit view (table icon) opens a separate spreadsheet-style page — every task is a row, and clicking any cell edits it inline: Title, Parent Task, Type, Status, Due Date, Assignee, Effort (h), Priority (sortable), and Tags. The same filter bar as the main task list is present here too, plus column sorting on Status, Due Date, Effort, and Priority. Toolbar actions: Save Changes (writes every pending edit in one request — an unsaved-changes counter tracks how many rows you've touched since the last save), Discard Changes (reverts all unsaved edits), Add Task (appends a blank row), and Delete Selected (removes every checked row).

AI Task Organization — Structuring a Flat Backlog

Once a backlog grows past a few dozen items, the bottleneck shifts from creating tasks to organizing them. Four AI tools handle this restructuring work:

The AI Brief tool itself, when used for a larger scope addition, produces a full hierarchical work breakdown (Phases → Features → sub-tasks) with dates, effort, types, and descriptions — not just a flat list.

Task Hierarchy & Governance — WBS, Acceptance Criteria, Blocking, and AI Agent Offload

Once a project moves past a handful of tasks, the real administrative burden shifts from writing tasks to organizing, governing, and handing off the work. This module covers the layer of the Tasks page that does that: the WBS hierarchy, the definition-of-done mechanics, and the controls that keep a growing task list honest.

Building the WBS — Project Scaffold and Break Down Task

Tasks support a full parent/child hierarchy of unlimited depth — a true Work Breakdown Structure (WBS). Two AI tools build it top-down:

Every task is auto-assigned a WBS code reflecting its hierarchy position (1, 1.1, 1.2, 1.2.1 …) — visible in the WBS Tree View and impossible to set manually; it updates automatically as the hierarchy changes. If a task already has subtasks, Break Down Task warns that subtasks and child tasks will coexist: subtasks remain a lightweight checklist inside the task, while child tasks become independent, trackable rows in the WBS tree with their own status, effort, assignee, and dependencies.

Acceptance Criteria — the Third Definition-of-Done Mechanic

CoMng.AI actually has three related but distinct "what does done mean" mechanics, easy to conflate:

Use subtasks to track how work gets done, AC to define the review gate before sign-off, and DoD Analysis when you want a fuller document (e.g. for a handoff) rather than a quick checklist.

Block/Unblock, Scope Creep, and the Remaining Task Card Actions

Beyond the AI dropdown, every task card carries a row of utility actions:

Offload to AI Agent — Per-Branch, Not Per-Agent

Module 5 covers Generate Work Order (AI Agent) on the Team page — a briefing of every task currently assigned to one agent. This module's Offload to AI Agent action (in the task's AI dropdown) is different: it generates a complete Markdown work order for one task and its entire child hierarchy — the WBS sub-tree — regardless of who it's assigned to. The work order includes the root task plus all children with WBS codes, internal and external dependencies, subtasks, Acceptance Criteria, project context, and operating instructions referencing the CoMng.AI API so the agent can update statuses and post notes as it works. If your project has AI Agent team members, you can address the work order to a specific one; otherwise it's generated as a generic prompt. The result is both shown as Markdown (Copy / Download .md) and saved as a project note.

The End-to-End AI Agent Workflow

The pieces taught across this course click together into one repeatable, end-to-end sequence — typically under 20 minutes from a blank project to an AI agent actively updating it live:

This same pattern works for any kind of delivery, technical or not — from a content curriculum like the one in the worked example below to a full software build (the same workflow, applied to a personal finance dashboard with bank-transaction sync, runs five Epics from UI design through database and authentication setup, each broken into its own child tasks with real due dates).

Worked Example — A Real Offload, End to End

This is what an actual generated work order looks like, taken from a real project (lightly anonymized). A task — "Create Content Outline and Sequence" (CoMng Task ID 5974, 8 hours effort, due 2026-06-30) — was assigned to a team member of type AI Agent named "Gemini Agent" and offloaded. The resulting Markdown work order contained: the agent's identity (name, role, CoMng Member ID, CoMng Project ID), the full project context paragraph (goals, team, tech stack, stakeholders, constraints, risks, exclusions — everything Project Settings holds), the task table with WBS code and Definition of Done, and a complete API reference for every endpoint the agent might need.

Three sections turn that document from a briefing into something an AI agent can actually execute against your live project:

At the end of the session, the work order requires a Final Summary Note — not a bullet list of statuses, but a full narrative: what was built, what decisions were made and why, any deviations from the plan, issues encountered and how they were resolved, remaining risks, and an executive-summary paragraph. The instruction is explicit: "A teammate reading it should understand exactly what happened without needing to read every activity log." That final note is what you, the PM, actually read — the per-task activity log is the audit trail underneath it.

Task Dependencies — Sequencing the Project

Why Dependencies Matter

A dependency links a predecessor (runs first) to a successor (depends on it). This single relationship is the input that several of the platform's most important features rely on: the Gantt chart cannot sequence its timeline correctly without dependencies — without them, the chart has no way to know which tasks must wait for others. Analyze Critical Path (Module 2) identifies the task chain controlling your end date by walking the dependency graph — no dependencies means no meaningful critical path. Optimize Timeline (Module 3) factors dependencies into every rescheduling proposal. Skipping dependency mapping doesn't just leave a page empty — it silently degrades the accuracy of every scheduling and risk tool downstream of it.

First Visit & Dependency Types

The first time you open Task Dependencies on a project with none defined, a welcome dialog offers two paths: AI Suggest Dependencies (analyze everything in one click) or Add Dependency Manually (define one relationship yourself) — or dismiss with Skip for now. Four standard PM dependency types are supported:

KPI Bar

AI Suggest Dependencies — Project-Wide Auto-Detection

The toolbar's AI Suggest button analyzes every task's title, description, and logical execution order and creates a full set of Finish→Start dependency links in one click — existing dependencies are never deleted, only added to. This is the project-wide counterpart to Find Dependencies (Module 3B), which runs the same kind of suggestion for a single task. Use AI Suggest once, early, to build the whole map; use Find Dependencies afterward on individual newly-created tasks. The richer your task titles and descriptions, the more accurate the suggestions — run it after Project Scaffold/Break Down Task have produced well-described tasks, not before.

Grouped View — By Blocker or By Blocked

Dependencies display as collapsible group panels, not a flat list, with a toggle between two grouping modes:

Each row shows the dependency type badge, a direction arrow, the related task's title (linking straight to it on the Tasks page), due date, status, and a Blocked badge if flagged. Each row has an info button (opens the Dependency Detail panel — predecessor/successor blocks plus an AI Explain button that generates a plain-language reason the link makes sense, re-runnable with Explain Again) and a delete button for that single dependency.

Adding, Filtering, and Cleanup

Add Dependency requires a Dependency Type, a Predecessor Task, and a Successor Task (must differ from the predecessor — the form blocks self-referencing links). The filter bar combines the By Blocker/By Blocked toggle, a Dependency Type filter, a Task filter (narrows to every dependency involving one specific task, as either role), and a free-text search box across both task titles and the dependency type — a live counter shows "Showing X of Y." Remove All deletes every dependency for the project after confirmation — irreversible, use only to start over.

How Dependencies Surface Elsewhere

Kanban, Gantt, Calendar & Mind Map

Visualization tools turn the same underlying task and milestone data into the view each audience actually needs — and every one of them is generated automatically with zero manual diagramming.

Kanban Board

Three view modes: Status (drag-and-drop updates status), Tag (a task can appear in multiple tag columns; no drag-and-drop), and Assignee (drag-and-drop reassigns; dropping in Unassigned removes the assignee — this does not change status). Cards show a priority border: red = overdue, orange = due today, green = due within 7 days. Suggest Task Details on the add/edit form fills description, type, due date, resources, effort, costs, success factors, and assignee from just a title. Export View saves the filtered board as a PNG.

Gantt Chart — Layout and Task List Panel

Day / Week / Month views; colour-coded bars (Yellow=Pending, Blue=In Progress, Green=Completed, Grey=Cancelled, Red=Overdue, reproduced in a legend at the bottom). Only tasks with at least one date (start, end, or due) appear — dateless tasks are silently excluded. The chart auto-scrolls to today's date on load and renders a maximum of 300 tasks; narrow with filters if you see a "too many tasks" message. The two panels — Task List (left) and Timeline (right) — scroll together as one unit, with a sticky date header.

The Task List Panel shows, per row: a colour-coded dot (diamond for milestones), the name, a meta line (assignee + due date for tasks; just due date for milestones), and on regular tasks a crosshair icon that opens the Dependency Path Panel. Clicking any row highlights it, scrolls/centres the matching bar in the timeline, opens the Task Details Panel, and — for regular tasks — highlights that task's dependency arrows.

Task Highlighting & Dependency Arrows

Dependencies render as green arrows from predecessor bars to successor bars. Click any task bar (or its Task List Panel row) to highlight its dependency chain: the clicked bar gets a solid yellow border, every directly connected predecessor/successor gets a dashed yellow border, the connecting arrows glow yellow with a drop shadow, and every unrelated task dims to 30% opacity so the chain stands out. Click the same task again (or click empty space) to clear the highlight.

For a structured view instead of a visual one, click the crosshair icon next to any task in the Task List Panel to open the Dependency Path Panel — a modal showing Before (Prerequisites), This Task (with status badge and tags), and After (Dependents). Clicking any task inside that panel closes it and jumps straight to that task in the chart.

Milestones & Task Details Panel

Milestones (managed in Project Settings) always appear regardless of the Status/Assignee/Tag filters — only the search box can hide one, by name. They show as a diamond dot + due date in the Task List Panel, as a pair of dashed vertical lines spanning the full chart height in the timeline, and as a 🏁 pill pinned in the sticky date header. Clicking a milestone row centres its lines in view and flashes them briefly.

Clicking any bar or row opens the Task Details Panel from the right. For a regular task: start/end/due dates, status badge, assignee (or "Unassigned"), description (if any), effort (if set), tags (if any), and a View Full Task Details button to the Tasks page. For a milestone: due date, description, and a Manage Milestones button to Project Settings.

Filtering & Search

A live counter shows "Showing X of Y tasks." All four filters combine, and the Task List Panel updates in lockstep with the timeline.

Baselines

A baseline is a named snapshot of every visible task's calculated start/end dates at the moment you save it (e.g. "Sprint 3 Start" or "Client Sign-off 2026-06-01"). Once at least one exists, a Baseline dropdown appears in the toolbar — selecting one activates comparison mode: a thin outlined ghost bar appears behind each current bar at its original baseline position. No visible ghost means the task hasn't moved; a ghost to the left of the current bar means the task has slipped (delayed); a ghost to the right means it moved earlier (accelerated). Select "No Baseline" to return to normal view. Deleting a baseline only removes the snapshot — it never touches actual task dates. Baselines do not auto-update; save a new named one after each re-plan rather than overwriting an old one, building a history of schedule changes over time.

How Task Bar Dates Are Calculated

End date: explicit end date → due date → one day after creation. Start date: explicit start date → backward from end date using effort (hours ÷ 7 hours/day) → one day before end date if no effort is set either. Tasks are sorted by start date in both panels. Set explicit start/end dates whenever precision matters — effort-derived bars drift from reality if effort estimates go stale.

Project Calendar

A read-only monthly grid merging Tasks (blue), Activities (green), Milestones (red), and Budget items with due dates (yellow). Navigate with the ◀ / ▶ arrows or jump back instantly with Today. The URL updates as you navigate and can be bookmarked or shared directly: project_calendar.php?id={project_id}&month={1–12}&year={year} — paste a month-specific link into a team message to point colleagues straight at a busy sprint week.

A task displays on its due date; if that's empty, the calendar falls back to start date, then end date — a task with none of the three is invisible on the calendar entirely. Budget items only appear if a due date is set on the line. Clicking any item opens a detail panel scoped to its type — Task shows description, date, status, type, assignee, effort, and costs; Activity adds duration; Milestone shows just description, date, and status; Budget item adds category, vendor, amount, and payment status. The calendar itself is view-only — edit the item on its source page (Tasks, Activities, Milestones, or Budget) and the calendar reflects the change automatically.

The Meeting Planner generates a structured agenda from current project context — it works best mid-sprint with real activity data; running it on an empty project returns generic output.

The Subscribe button issues a private iCal/WebCal feed (90-day lookback, 2-year forward window) for Google Calendar, Outlook, or Apple Calendar — each team member gets a unique URL. The Subscribe modal has separate tabs: Google / Apple (one URL scheme) and Outlook (a separate webcal:// URL — using the wrong tab's link is the most common subscription error). External apps poll the feed roughly hourly; Google Calendar can take up to 24 hours to reflect changes. 🔄 Regenerate link invalidates the old URL immediately — any existing subscription using it stops updating and must be re-added with the fresh URL, so only regenerate if the link was shared unintentionally.

Mind Map — Nodes, Colours, and Interaction

The Mind Map renders the project as a live, interactive node graph — the centre node is the project itself, surrounded by branches; everything is drawn directly from current project data with nothing to configure. Node colour indicates type: Blue (Project centre), Teal (Work Streams), Pink (Milestones), Orange (Team Health), Red (Risks), Cyan (Budget), Green (Tasks) — and a legend showing this, plus the status icons, stays visible in the bottom-right corner. Status emoji overlay on nodes: 🟢 Healthy, 🟡 Warning, 🔴 Critical, ⚠️ Issue, ✓ Complete.

Click a node to open its Detail Panel on the right (full item detail plus a Go to Page button that navigates straight to that item's source page — e.g. a task node takes you to the Tasks page with that task highlighted); click the central node specifically to open the Executive Dashboard instead. Hover shows a quick tooltip (name, status, key metric). Right-click a task node opens a context menu: view details, navigate to Tasks, or mark complete — directly from the map. The map auto-arranges with a brief physics simulation on load; drag any node afterward to reposition it, though custom layouts are not saved between sessions — every load re-runs the simulation. Canvas navigation: drag an empty area to pan, mouse wheel or the zoom buttons to zoom, Fit to centre and show every node, Center to reset to 100% zoom at the origin (one-finger drag / pinch on mobile).

The Five Map Views

Use the search box (left of the toolbar) to highlight matching nodes by task name, milestone title, team member name, or risk description — the map zooms and centres on the results. Export downloads the current canvas as a PNG; click Fit first so nothing is clipped.

Executive Dashboard — Five Sections

Open it from the toolbar button or by clicking the central project node:

The Health Score gauge is a composite of task completion rate, overdue task count, open risks, and budget consumption — above 70 is generally healthy, below 50 needs attention.

Project Status View — Five Sections

Click Project Status to replace the canvas entirely with a full-screen structured report built for stakeholder meetings, with no node-graph clutter:

Click Back to Map to return to the node canvas.

Resource Planner & Project Lists

Not every workload question needs a Gantt chart, and not every tracked item needs to be a full task. These two lightweight tools round out your operational toolkit.

Resource Planner

A week-by-week grid showing each team member's utilization across a rolling window of 8–24 weeks. Each cell shows effort hours, capacity percentage, and task count for a member/week combination, colour-coded:

Clicking a cell opens a panel listing the exact tasks driving that load. Summary cards show total team members, total hours, average utilization, and the count of overloaded member-weeks. You can adjust weekly capacity per member, filter out completed tasks, and navigate Prev / Next / Today — the grid itself is read-only; workload changes are made on the Tasks page.

Project Lists (a.k.a. Lists View)

Named, colour-coded checklists attached to a project — for requirements lists, deployment checklists, country regulations, stakeholder contacts, or anything that needs simple tracking without full task fields (effort, assignee, dependencies, due dates). This is the same feature reachable as the Lists View toggle on the Tasks page (Module 3) — a dedicated space for reference checklists that aren't really "work" in the task sense.

Each list is a named, colour-coded card holding a flat checklist of items. Unlike tasks, an item is lightweight: a checkbox, the item text, and optional remarks (e.g. "confirmed with legal on March 3"). Ticking an item prompts for remarks and records who completed it and when; unchecking clears that record. Create multiple lists, each its own colour; edit or delete a list (deleting removes all its items — not undoable); add, edit, or delete items individually, or bulk-import a set of items at once.

AI Generate List — rather than typing every item by hand, click AI Generate List to populate a brand-new list, or the magic-wand icon on an existing list to add more items to it. Optionally describe what you need ("compliance items for an EU SaaS launch," or mention a specific count like "50 main cities"); AI reads the project's name, description, and business area plus the list's own content to propose new entries, told what already exists so it won't suggest duplicates. Every suggestion is selected by default — untick anything you don't want, then confirm; nothing is added until you do.

Activities — Time & Work Tracking

Tasks describe what needs to happen; Activities describe what actually happened. A single task — say, "Migrate the database" — might accumulate five separate Development activities logged over five days, each with its own duration, cost, and result. Without Activities, that history lives only in memory or scattered chat messages; with it, every hour and every dollar spent is a permanent, exportable record tied back to the work it served.

KPI Bar

Adding an Activity — the Full Field Set

Title (required), Description, Type (free-text with built-in suggestions: Meeting, Research, Development, Planning, Testing, Documentation, Design, Collaboration, Review — required), Status (Pending / Started / In Progress / Completed / Cancelled — required), Date (defaults to today — required), Duration in hours (0.5h increments — feeds the Hours Tracked KPI), Team Member (optional), Related Task (optional — links the activity to a task; the link is clickable from both the card and the task), Results (what was produced), Notes (observations/follow-ups), Resources Used, and Costs ($). The same side-panel form is used for both Add and Edit, and a confirmation prompt protects against accidentally discarding unsaved edits.

Activity Cards, Filters, and Status Changes

Each activity is a collapsible card. Collapsed, it shows the title, a colour-coded status badge, duration, and a discussion-count badge if any messages exist. Expanded, it adds a description preview, type/date/team member, the Related Task link, and a results preview. Three filter dropdowns (Status, Type, Member) plus a free-text search box combine in real time, with a live counter showing how many activities are currently visible. The Change Status action opens a compact modal to switch status without opening the full edit form.

Card & Detail-View Actions

Export Activities Report & Deep Linking

Export Report (toolbar) downloads every activity on the project regardless of active filters — the activity record fields only; discussion messages are never included. Deep links: &activity_id={id} opens one activity's detail view directly; &task_id={id} opens the Add Activity panel with Related Task pre-set and the title/description pre-filled from that task — this is exactly what happens when you click Log Activity on a task card (Module 3B).

Team Leadership & AI Agents

Team leadership is where the strategic shift is most visible: instead of personally drafting job descriptions, SOWs, and workload spreadsheets, the PM directs AI to produce them and spends the reclaimed time on coaching, conflict resolution, and capability-building.

KPI Summary Bar & Member Card

The Project Team page opens with four counters: Total Members, Internal, Contractors, and Partners — a one-glance read on team composition before you even open a single profile. Each member card then shows name, project role, department, member type badge, email, skills with proficiency levels, and the reports-to relationship.

Member Types & the AI Agent Concept

Beyond Internal Employee, External Contractor, and Partner/Vendor, CoMng.AI treats AI Agent as a first-class member type — Claude Code, GPT-4o, Gemini, Devin, GitHub Copilot, and others can be added as team members, assigned tasks directly, and briefed via a Generate Work Order (AI Agent) action that produces a structured markdown document listing every assigned task with full project context (descriptions, due dates, priorities, effort, dependencies, blockers) — ready to hand to an automation pipeline.

Adding a Member — Skills, Suggest Details, and AI Agent Autocomplete

The Add/Edit Member form captures: Name, Role, Department, Member Type, Email, Phone, Reports To, Expertise/Responsibilities, and one or more Skills rows (each a skill name plus a proficiency level — Beginner, Intermediate, Advanced, or Expert). Recorded skills and proficiency are exactly what Smart Assign and Workload Analysis read when matching people to tasks, so an under-filled skills section quietly degrades every downstream AI recommendation.

Suggest Details (AI) — available in both Add and Edit modes — fills in role description, typical skills, and department based on just the name and role you've typed, the same pattern as Suggest Fields on project creation. When the Member Type is set to AI Agent, the Name field also offers autocomplete suggestions for common AI systems: Claude Code, Claude Sonnet, Claude Opus, GPT-4o, GPT-4o mini, Gemini CLI, Gemini 2.0 Flash, GitHub Copilot, Cursor AI, Devin, Midjourney, Stable Diffusion, Perplexity AI, OpenAI o3.

Toolbar & Per-Member AI Actions

Suggested Required Expertise Panel

Running Suggest Required Expertise doesn't just list missing roles — it renders a panel of suggested-role cards below the team grid, each with three independent actions: Add to Team (creates the member immediately from the suggestion), Create Recruitment Task (logs a formal recruitment task in the project task list), and Job Description (generates a job description note for the suggested role even before anyone is hired).

Budget & Financial Stewardship

Budget management used to mean manually building a spreadsheet, chasing approvals by email, and writing a justification memo from scratch every time a stakeholder asked "why do we need this?" CoMng.AI generates the entire budget skeleton, the justification, and the financial framing automatically.

KPI Bar & Two Independent Lifecycles

Five KPIs: Total Budget, Approved, Spent (driven by actual payment records, not line amounts), Remaining (red if overspent), % Utilized (green <70%, orange 70–89%, red ≥90%). Two lifecycles run independently: Approval status (Draft → Pending → Approved/Denied, or Removed for audit-preserving exclusion) and Payment status (Unpaid → Partial → Paid), tracked via a per-line payment ledger.

Adding/Editing a Budget Line

The add/edit form captures: Title, Category (Software, Hardware, Services, Consulting, Development, Training, Marketing, Advertising, Office Supplies, Travel, Other), Vendor, Description, Amount, Currency (USD, ILS, EUR, GBP — multi-currency lines show KPIs per currency, with no automatic conversion), Status, Payment Status, Payment Due Date, Payment Method, External Reference (invoice/PO number), Approver Name, Approver Remarks (markdown supported), Related Tasks, and Tags. As with Tasks and Team, Suggest Details takes a typed description and fills in the rest — title, amount, currency, payment method, approver remarks — based on project context, without overwriting anything you've already entered.

The Payment Ledger

Each budget line carries its own payment ledger, separate from the line's approval status. Record one full payment or several partial payments over time; each payment entry has its own Amount, Date, Method (Bank Transfer, Credit Card, Cash, Check, PayPal, Other), Reference/Receipt number, and Notes. A progress bar on the line shows amount paid against the total line amount. This ledger — not the Payment Status label and not the line's face amount — is what actually drives the Spent and Remaining KPIs at the top of the page.

Export CSV & Full Budget Report

Export CSV downloads every budget line in the project as a CSV file — for reconciliation in a spreadsheet, import into a finance system, or attaching to an expense report. Full Budget Report opens a formatted HTML report in a new tab, covering every line with its status, payments, and KPIs in a printable, shareable layout — the budget equivalent of Export Project to HTML, scoped to just the financials.

AI Tools for Budget

Change & Risk Governance

Change Management is the governance layer that turns "someone asked for a change" into a controlled, auditable, AI-assessed decision — instead of an ad-hoc scope creep conversation in a hallway or a Slack thread that nobody remembers six months later.

The Change Request Lifecycle

Draft → Submitted → Pending Approval → Approved → Applied → Closed, with side-statuses Deferred and Rejected. A CR carries Title, Description, Category (Scope/Budget/Schedule/Resource), and Priority (Low/Medium/High/Critical).

Seven Ways a CR Gets Created

Once Submitted, Run AI Assessment analyses the CR against full project context and produces an impact assessment across scope, budget, schedule, and resources, moving the CR to Pending Approval. From there: Export for Approval (a standalone HTML document for offline sign-off), Authorize, Defer, or Reject. Once Approved, impact items can be applied individually or all at once with Apply All; each item can instead be Skipped without affecting the rest.

The Three Real-World Paths Into a Change Request

Scope changes rarely arrive as a tidy, ready-to-formalize request — they arrive as a stray sentence in a meeting note, a casual customer email, or an attached document nobody has read yet. Without a fast conversion path, these get absorbed informally: no impact assessment, no budget check, no audit trail, and the project quietly drifts from its approved scope. Three paths funnel exactly this kind of informal input into a governed CR:

Whichever path it travels, the result is the same: a CR with a full impact assessment, sitting at Pending Approval, traceable backward to the exact note, email, or document that started it — so a budget dispute six weeks later can be settled by following that trail instead of arguing from memory.

RAID+ and Risk Governance

The RAID+ Register (Risks, Assumptions, Issues, Dependencies, plus anything else AI identifies) is generated from the Hub's Project Tools menu as a single comprehensive note. In Project Settings, each identified risk has a per-risk Risk Assess button producing likelihood, impact, early-warning indicators, and mitigation strategy as a saved note.

Knowledge Base, Whiteboard & ARI

Knowledge work — meeting minutes, risk registers, onboarding guides, decisions — is exactly the kind of writing that consumes a PM's evenings. The Notes module and the Whiteboard's AI assistant ARI exist to absorb that writing load.

Notes — AI-Generated, Template-Based, and Imported

AI-generated note types: Project Key Questions, Risk Assessments, Project Risk Analysis, Analyze Project Item, Competitor Analysis, Roadmap Builder. Template-based: Project Scope, Business Case, Schedule Document, Communication Plan, Expected Deliverables, Stakeholders Definitions, Project Org Chart, Roadmap, Decision, Document, Meeting Notes, Action Items.

Import sources — each one read and summarised by AI into a structured note: PDF (reads and summarises the document), Image (extracts text and describes visual content), Webcam Capture (photographs a physical whiteboard or document and analyses it), Web Page (paste a URL and AI extracts/summarises the page), Draw.io Diagram (analyses and documents the diagram), Configuration Files (YAML, JSON, XML, or any similar config format — AI analyses the structure), CSV File (analyses and summarises the data), and Text File (imports plain text content).

Per-Note Actions — Card Toolbar and AI Dropdown

Every note card carries a consistent set of actions, independent of how the note was created:

The robot-icon AI dropdown on each note card adds a second layer of actions on top of the note's existing content:

Ask Me, What-if, Voice Note, Project Files, and Export Notes

Ask Me offers two modes: Project Answer (full project context — tasks, team, budget, timeline) or General Answer (no project context, general business/world knowledge only). General Answer is the right mode whenever your question isn't really about this project's data at all — drafting a business model canvas for a new offering, validating a raw idea before it becomes a project, exploring a growth-strategy framework, or asking a generic "how do other companies typically approach X?" question. Project Answer is for everything that needs your actual tasks, budget, or team to answer correctly. Both modes save the conversation as a knowledge base note for future reference.

What-if Scenario analyses an alternative ("what if we reduce the team by 2 people?") and saves the findings as a note. Voice Note transcribes live recordings or uploaded audio and extracts key points and action items. Project Files (toolbar button) opens a browser for every file attached to the project across all sources — uploaded documents, imported files, embedded note attachments — in one place. Export Notes (toolbar button) downloads every note in the project as a single, formatted HTML report — your entire knowledge base as one shareable, archivable document.

Whiteboard & ARI — Preview

The Whiteboard is a full collaborative visual canvas with AI built in, covered in depth in Module 8B — including the complete tool palette, ARI's AI panel and quick actions, sharing, and live collaboration. This module's demo and practice focus on Notes; head to Module 8B for the Whiteboard's own hands-on exercises.

Whiteboard Deep Dive — Canvas, ARI, and Sharing

Why We Have It

Every project generates ideas faster than it generates structure: a kickoff workshop, a "what if" debate, a risk-mapping session. In a room with a physical whiteboard, that thinking either gets photographed and forgotten, or someone spends an evening manually re-typing it into tasks and notes. The Whiteboard exists to remove that translation tax entirely — and because teams are distributed, it also replaces the physical whiteboard itself, with the added advantage that nothing typed on it is ever lost (auto-save) and an AI teammate, ARI, sits inside the session ready to convert raw sticky notes into structured project objects the moment the conversation ends.

Boards & Tabs

Each project can have multiple boards, organized as tabs along the bottom bar; "Board 1" is created automatically on first visit. Switch boards by clicking a tab (or the dropdown for many boards), create a new one with the + button, rename via the pencil icon, and delete via the ✕ icon — deletion is permanent and removes every element on that board, with no recovery.

Tool Palette & Canvas Navigation

The vertical left-side palette holds: Select (V), Pan (H, or hold Space), Sticky Note (N), Text (T), Rectangle (R), Ellipse (O), Diamond (D), Triangle, Line (L), Arrow (A), Pen — freehand (P), Frame — labelled grouping area (F), Image upload (I), and Templates. After placing a shape, the tool automatically reverts to Select so you can immediately reposition it.

Bottom-right canvas controls: Zoom out/in (Ctrl+−/Ctrl+=), zoom percentage display, Fit to Screen (Ctrl+0 — zooms/pans so every element is visible), a dot-grid toggle for alignment, Export PNG, and a Minimap toggle for navigating large boards.

Context Toolbar (Element Selected)

Templates

Blank, Brainstorm (central idea + surrounding sticky notes), SWOT Analysis (4 labelled frames), Sprint Retro (What Went Well / To Improve / Action Items columns), Mind Map (central node + branches), Kanban (To Do / In Progress / Done columns). Applying a template replaces all existing content on the current board — confirm you're on the right tab first.

ARI — the AI Panel and Quick Actions

Open ARI via the AI button in the context bar header. Type a message and press Enter (Shift+Enter for a new line without sending) — ARI has full project context (tasks, budget, team, activities) and places generated elements directly on the canvas, confirming how many it added.

Task → Board — the Reverse Direction

The flow doesn't only go from board to project objects — it also runs the other way. The Brainstorm action in any task's AI dropdown (Module 3) reads that task's title, description, type, status, effort, and success criteria, generates a cluster of relevant sticky notes (approaches, open questions, risks, solution ideas), creates a brand-new board pre-populated with them, and drops you straight into it. From there you can add your own notes, group with Frames, then run Board → Tasks or Board → Change to turn the refined thinking back into structured work.

Sharing with Third Parties

Click Share in the context bar header. Set an optional password (blank = open access) and an expiry (Never, 1 day, 7 days, 30 days), then Generate Link. Recipients need no CoMng.AI account and get view-only access to the board as it existed when they open the link — exactly the same sharing pattern used for Tasks, Notes, and the whole Project (Modules 3, 8, 10).

Comments, Voting, and Live Collaboration

Select any element and click Comment to open a threaded discussion scoped to that element, or Vote to upvote it (useful for democratic prioritization — let the team surface the sticky notes that matter most). When multiple people open the same board, presence indicators show who's viewing; cursor positions sync roughly every 3 seconds and element changes sync every 5 seconds — changes from one person appear on everyone else's screen automatically, no refresh needed.

Customer Insights (CII) & Email Automation

External input — customer feedback, support escalations, stakeholder emails — traditionally arrives scattered across inboxes and gets manually re-typed into the project. CII and Email Integration eliminate that re-typing entirely.

Customer Insights (CII)

Insights arrive manually (New Insight) or automatically via a dedicated per-project email address (prj-{customerId}-{projectId}@comng.ai) using a regenerable secret CII token. Each insight records received date/time, source, content, status, and PM Notes (internal-only annotations). From the detail modal, one click converts an insight into any of: Task, Note, Budget, Calendar, Milestone, Issue, Assumption, Requirement, Risk, or Metric — after which it is marked converted so it cannot be actioned twice.

AI Intent Classification

Every insight can be automatically classified into one of 8 intent types — happening automatically on inbound emails, or triggerable manually from the insight detail view for anything entered by hand: Complaint, Bug Report, Feature Request, Question, Feedback, Praise, Suggestion, and Other. The AI reads the full message text and picks the best fit; you can always override its choice by editing the insight. The classification is a first pass, not a final verdict — spot-check a few insights per week, especially from new customers, until you trust the quality for your context.

Insight Status Workflow

Every insight moves through a status lifecycle distinct from its intent classification: New → In Progress → Acknowledged → Resolved, with three alternative terminal states — Closed (no full resolution, e.g. duplicate or out of scope), No Solution (reviewed, no solution currently available), and Canceled (retracted or no longer relevant). The Status Summary bar at the top of the CII page gives a live count per status — click any status to filter the list to just that state.

Email Integration

Each project has a unique inbound address. Two separate tokens exist: the Internal Secret Token (for internal/automated emails — never shared externally) and the Customer Insights Token (CII Token) (shared with customers so their mail routes to CII, not internal project objects). The Email Pipe toggle can pause automated processing while still receiving and storing mail. AI classifies each email into Task, Note, Budget, Calendar, Activity, CII, or Ignored, with per-email statuses Pending, Processing, Done, Failed, or Ignored, and per-email actions Process Now, Retry, and Delete.

Sharing, API & Security Governance

Strategic leaders are accountable not just for delivery but for information governance — knowing exactly what has been shared with whom, for how long, and revoking access the moment it's no longer needed.

Shared Items Management

A central registry of every share link across five shareable object types: Task, Note, Whiteboard, Whiteboard Pro, and Project. Each row shows item type, title, creator, creation date, expiry (or Never), and status (Active/Expired). Copy Link, Edit (Project-type shares only), and Delete (immediate revocation) are available per link. A collapsible Recent Failed Access Attempts panel surfaces the last 10 wrong-password attempts with timestamp and IP — your early-warning system against brute-force probing.

API Management — Who Can Access, and the Dashboard

API Management and the API Sandbox are both restricted to the Admin role — Project Managers and Members cannot create or view API keys; ask your organization's admin if you need access. Every API request authenticates with an X-API-Key header (or an Authorization: Bearer token), and the External API currently exposes 28 documented endpoints across 8 resource categories: Projects, Tasks, Notes, Subtasks, Team Management, Budget Management, Activities, and Reports.

Four dashboard cards summarize activity: Total Keys (all ever created, including inactive), Active Keys, Today's API Calls, and Avg Response Time. Below them, a Security Alerts panel surfaces recent failed authentication attempts — repeated failures from the same IP can indicate a misconfigured integration or a leaked key being probed.

Creating a Key — Fields and Permissions

Granular action checkboxes restrict exactly what the key can do, grouped by the same 8 resource categories listed above (e.g. Task Management: list/create/update/delete task; Budget: get/create/update/delete budget item). Apply the principle of least privilege — a webhook that only reads tasks should not be able to delete budget items.

Rate Limits, Expiry, and IP Whitelisting

Each key has its own hourly (default 1,000) and daily (default 10,000) request limit; exceeding either returns HTTP 429. An optional expiration date auto-rejects the key afterward even without manual revocation — ideal for contractor or temporary integration access. An optional IP whitelist (one address per line, CIDR supported) rejects requests from any other IP with HTTP 403; for any server-to-server integration with a fixed source IP, this is the single most effective safeguard against a leaked key being misused.

Managing Existing Keys

The keys table shows name, masked value, status, covered projects, last-used timestamp, and usage counters. Per key: toggle Active/Inactive (suspend without deleting), View details (full permission set, limits, expiry, whitelist), and Revoke/Delete (permanent — any integration using that key immediately starts receiving 401 errors). To rotate a key safely: create the replacement first, update your integration, then revoke the old one — never revoke before the replacement is live.

API Sandbox — Building and Reading a Request

Two panels: Request (left) and Response (right). Building a request: select an active API key from the dropdown (the sandbox authenticates as that key — and sandbox calls do count against its rate limit) → choose a resource category (Tasks, Budget, Team, etc.) → choose an endpoint (shown with its HTTP method badge — GET/POST/DELETE — and description) → fill in parameters (required ones are marked with an asterisk; submitting without them returns 400) → Send Request.

The response panel shows the HTTP status code (200/201/400/401/403/429/500), response time in milliseconds, a syntax-highlighted JSON body with a Copy button, and ready-to-run cURL and wget command equivalents you can paste straight into a terminal or hand to a developer.

The Studio — AI Document, Plan, Presentation & Report Generation

Why the Studio Exists

Every pillar from Module 0 eventually produces the same artifact: a document someone outside the platform needs to read — a board update, a vendor RFP, a risk register, a pitch deck, a compliance scorecard. Historically this is where AI-assisted project management quietly reverts to manual work: the data is structured, but turning it into a polished email, a 40-page business plan, or a stakeholder presentation still meant opening a blank document and writing it yourself. The Studio is the answer — four generation tools, all reading from the same live project data, that produce the actual deliverable instead of just the data behind it.

The Four Tools at a Glance

Email & Document Composer

Templates are organized into 12 categories — Project Communication, Risk & Issue Management, Team Management, Stakeholder Relations, Vendor & External Relations, Financial Management, Marketing & Launch, Project Planning Documents, Strategy & Analysis, Operations & Process, Compliance & Governance, and Business Development — spanning everything from a Project Kickoff Email or Risk Escalation Email to a full Business Case Document or Data Privacy Policy. Filter the library by Email/Document type or search by keyword.

Selecting a template reveals a customization form: Recipient/Target Audience (always), and for emails — Subject, Sender Name/Title, Tone (Formal/Professional/Friendly/Urgent), Length (Brief/Standard/Detailed); for documents — Title, Length, Include Executive Summary, Include Appendices. Many templates add their own specific fields (e.g. a Business Plan template asks for Business Type and whether to include Financial Projections; a Delay Notification asks for Delay Length and Primary Reason). An Additional Context/Instructions box is always available. Click Generate to produce the composition, then Copy to Clipboard, Save as Note, or Download as an HTML file.

Project Plans Maker — the Three-Step Workflow

Nearly 30 plan types are available: Work Plan, Business Plan, Risk Management Plan, Change Management Plan, Cost Management Plan, Resource Management Plan, Stakeholder Management Plan, Project Execution Plan, Communication Plan, Quality Management Plan, Procurement Management Plan, Implementation Plan, Strategic Plan, 1/3/5 Year Business Plan, Contingency Plan, Training & Development Plan, Performance Management Plan, Technology/IT Management Plan, Safety & Compliance Plan, Marketing Plan, Sales Plan, Financial Plan, Succession Plan, Integration Plan (M&A), Exit Strategy Plan, Sustainability/ESG Plan, Crisis Management Plan, Data Management Plan, Capacity Planning, and a fully open-ended Custom Plan.

Unlike the Composer's single-shot generation, a Plan is built in three explicit steps so you can review structure before committing to content:

1. 1. Generate Sections — AI proposes the plan's section outline (you can optionally steer it first with Special Instructions — preset suggestions include "Create only the 10 most essential sections," "Focus on sections required for investor presentations," or "Include industry-specific best practices"). You can manually add or remove sections before continuing.
2. 2. Generate All Content — AI writes the full content for every section in sequence, with a live progress bar ("Generating section 3 of 10: 'Risk Register'") and a Stop button if you need to interrupt it.
3. 3. Combine Plan — assembles every section into one document with an auto-generated Table of Contents.

From there: Export Plan as HTML or Save Plan as Note.

Presentation Outline Maker

A single dropdown organizes roughly 60 presentation types into categories: Project Management (Status Overview, Milestone Review, Post-Mortem, Lessons Learned, Roadmap...), Governance & Leadership (Steering Committee, Board of Directors, Executive Briefing, QBR...), Financial & Investment (Budget Review, Fundraising Pitch Deck, ROI Assessment...), Strategy & Business, Team & HR, Marketing & Sales, Technology & Innovation, Operations & Process, Risk & Compliance, Stakeholder Relations, and Corporate Responsibility. Add optional custom instructions, then click Generate Presentation Outline for a full slide-by-slide structure, or Generate a Visual Element to have AI produce a standalone chart/graphic (e.g. a pie chart of completed tasks) you can drop straight into a deck you're already building elsewhere. Outline actions: Regenerate, Copy to Clipboard, Save as Note, Download Presentation.

Report Maker

Report types are grouped by category — Project Management (Task Progress, Timeline & Milestone, Dependencies Analysis, Project Health Dashboard, Project Forecasting...), Financial Management (Budget Analysis, Cost-Benefit, Budget Variance, Cash Flow Projection, Financial Health Score...), Team Performance (Team Performance, Productivity Trends, Workload Balance, Skills Gap, Team Morale), Resource Management, Risk & Compliance (Risk Assessment, Compliance and Governance, Security & Privacy, Audit Trail, Regulatory Compliance Scorecard), Quality Assurance, Stakeholder Relations, Strategic Planning, and Operational Excellence. Each report type exposes its own relevant filters — a Budget Analysis report lets you filter by category and approval status, a Risk Assessment report by severity and category, a Team Performance report by team member and metric — plus a universal date-range filter (All Time, Last Week/Month/Quarter, YTD, Custom Range) and a detail level (Brief — 1 page, Detailed — 2-3 pages, Comprehensive — 4+ pages). Generate, Regenerate, or Export as HTML.

Capstone Simulation — Run a Project as a Strategic Leader

The capstone is a single scenario that forces you to touch every module covered in this course, in the order a real initiative would require them, while you track and justify every strategic decision you made along the way.

Certification Final Exam

30 questions drawn across every module. A score of 80% or higher is required to unlock your certificate below.

Your Certificate