One evidence-based review across the whole project
Project Advisor reads the project's authorized source evidence and produces a structured health review and decision queue. It compares the brief and roadmap with the current team, tasks, dependencies, acceptance criteria, cadence, hours, costs and delivery signals instead of reacting to one isolated message.
It does not replace the project owner or claim to run the project autonomously. It explains risks, prepares evidence-based options and applies only validated changes explicitly selected by the owner.
Project Advisor and PM Twin have different responsibilities
| Agent | Owns | Typical output |
|---|---|---|
| Project Advisor | Project assessment and governed recommendations | Project health markers, quality findings, delivery risks and approval-ready decisions |
| Digital PM Twin | Ongoing attention and communication | Targeted status questions, follow-ups, owner summaries and client-safe updates |
| Project owner | Consequential authority | Approval or rejection of team, money, timing, client promise and invoice changes |
What the review uses
| Evidence | What Advisor checks |
|---|---|
| Brief and project source | Outcomes, constraints, non-negotiable requirements and missing context |
| Architect roadmap | Phases, concrete tasks, dates, dependencies, roles and acceptance criteria |
| Project Workspace | Actual task state, blockers, overdue work, assignment and completion evidence |
| Teams and profiles | Role coverage, verified capabilities, availability, collaboration evidence and capacity risk |
| Delivery policy | Weekly, two-week, monthly or continuous cadence plus time, cost, billing and invoice capabilities |
| Analytics and Team Pulse | Recent delivery movement, workload pressure and collaboration conditions |
| Commercial records | Budget boundary, tracked hours and relevant cost signals when the project enables them |
Choose the review and action level deliberately
| Mode | Advisor may do | Owner remains responsible for |
|---|---|---|
| Draft | Analyze evidence and prepare a complete plan | Approving every proposed action |
| Managed | Create missing tasks only after deterministic validation against saved quality gates | All consequential project changes |
| Within limits | Operate inside saved capabilities, variance and deadline boundaries | Every category marked Always ask approval |
Review decisions as alternatives, not yes-or-no prompts
- 1Read the reason
The decision card explains the observed project condition and why owner attention is required.
- 2Inspect evidence
Check the concrete tasks, dates, role gaps, hours or commercial boundary that support the recommendation.
- 3Compare options
Each option states its operational impact. The recommended option is identified, but it is not applied merely because the model prefers it.
- 4Choose or dismiss
Your decision is stored in the project run history. The next review incorporates the selected direction and avoids presenting the same unresolved choice as new work.
- 5Verify the result
Open Project Architect, Teams Canvas or Workspace from the review when you need to inspect the changed object in its native tool.
Quality gates validate every recommended action
Configure the first run
- 1Connect Project Advisor
In Agent Center, select the project, add Project Advisor and open its control panel.
- 2Select autonomy and rhythm
Start with Managed and Manual or Workdays until the project evidence and approval boundaries are stable.
- 3Choose the team source
Use My people, Saved teams, External or Best fit according to who may be considered for this project.
- 4Set approval boundaries
Keep team, budget, deadline, client commitment and invoice changes selected unless governance for the project explicitly permits otherwise.
- 5Save operating rules
The visible controls are only a draft until the panel confirms Saved.
- 6Run the review
Read quality findings first, then resolve decision cards or apply a validated task plan.
If Advisor does not apply a selected change
- Paused or detached agents do not run, even when an old plan is visible.
- Unsaved operating rules do not control the server runtime.
- A quality-gate failure intentionally blocks task creation; correct the source evidence or change the gate deliberately.
- Team, budget, deadline, client commitment and invoice changes wait for owner approval by default.
- A project without enough source evidence should return a bounded request for missing information rather than fabricated detail.
- Smart Console shows new owner decisions, blocked reviews and safe task plans once; open Agent Center for the full evidence.