What PM Twin does
Digital PM Twin watches the project evidence you explicitly enable. It can ask the team for missing delivery information, prepare concise reports and surface conditions that need a human decision.
It is designed as a controlled project-management cycle, not a generic chatbot and not a replacement for the project owner. It can prepare and perform only the actions permitted by the saved rules and approval boundary.
Three groups of rules
| Group | Purpose | Example |
|---|---|---|
| Ask the team | Collect missing delivery evidence | Expected dates or blockers |
| Tell me | Summarize conditions for the project owner | Schedule risk or weekly status |
| Allowed reactions | Permit bounded, reversible responses | Draft a task move or acknowledge a client question |
Use Ask the team to close evidence gaps
| Focus | What PM Twin checks | Typical result |
|---|---|---|
| Monday kickoff | Focus tasks, due-soon work and dependencies at the start of the week | A concise kickoff request |
| Sprint status | Done, in-progress and unresolved sprint work | A current status check rather than a generic reminder |
| Sprint close check | Unfinished work near the sprint boundary | A request for realistic final dates |
| Dependency watcher | Blocked work whose predecessor is not ready | A targeted blocker question |
| Blockers | What prevents completion | A request for the specific constraint and owner |
| Expected dates | Missing or outdated completion dates | A request for a new realistic date |
| Overdue tasks | Work beyond its planned date | A focused follow-up on only affected tasks |
| Client questions | New questions that need a calm response | A safe acknowledgement plus an owner notification when required |
Use Tell me for decision-ready summaries
| Focus | What the owner receives |
|---|---|
| Daily project digest | A short view of current delivery health |
| Schedule risks | Material delays, requested moves and timing risk |
| Invoice attention | Open payment reminders or invoice anomalies that need review |
| Expense concerns | Client questions or objections about a pending expense |
| Client attention | A question or condition that needs a real owner answer |
| Weekly summary | An end-of-week project status prepared for review |
Allowed reactions define bounded actions
| Reaction | What it may do | What it must not do silently |
|---|---|---|
| Neutral client acknowledgement | Post a short message that the team is checking the question | Promise an outcome or expose internal team context |
| Daily client status | Post a concise client-safe progress note | Expose rates, margin, blame or private team discussion |
| Payment reminders | Ask the client to pay an open invoice and remind after the configured boundary | Change invoice or payment state |
| Expense approvals | Ask the client to review a pending partner-managed expense | Approve the expense for the client |
| Notify me | Surface a delivery risk to the owner | Resolve the risk without an owner decision |
| Task move draft | Prepare a proposed task move with dates and impact | Apply the move without the required approval |
Set the reporting rhythm separately from project cadence
Project sprint cadence tells Collty how delivery periods are grouped. PM Twin report time tells the agent when a scheduled report should be prepared. Changing one does not silently rewrite the other.
The status summary should state whether scheduled reports are active and show the saved report time. When the agent is paused, the summary must say that no automatic PM cycle will run even though the settings remain configured.
- 1Choose the project
Settings always belong to the already selected project-agent relationship; there is no duplicate project selector inside the rules panel.
- 2Choose the report time
Set the time when the owner expects the scheduled digest or report.
- 3Save the rules
Wait for Saved before relying on the new time or focus areas.
- 4Start the agent
Use Start once. No additional scheduled-check toggle is required when the active relationship and saved rules already permit the cycle.
- 5Pause when needed
Pause persists immediately and blocks future scheduled cycles without erasing the configuration.
Examples
| Project condition | Useful PM Twin behavior |
|---|---|
| Three tasks are overdue and one team reply gives a new date | Summarize the reply, identify the affected task and prepare an approval-ready move proposal |
| A client asks for status while the answer is not final | Post a neutral acknowledgement and notify the owner about the real question |
| The sprint is healthy | Stay quiet or provide the configured concise digest instead of inventing actions |
| An invoice remains open | Prepare a client-safe payment reminder with the permitted invoice detail |
| A client questions an expense | Notify the owner with the concern and wait for a decision rather than arguing automatically |
Agent state is authoritative
If the expected report did not appear
- 1Check state
Paused and Stopped relationships never run scheduled cycles.
- 2Check Saved
Changes not saved means the visible draft is not yet authoritative for execution.
- 3Check report time
Confirm the saved time and the account timezone context.
- 4Check project evidence
Verify that the selected project has relevant tasks, dates, messages or commercial records.
- 5Check recent activity
Open the project-agent activity tooltip or inspector to see the last execution and any condition requiring attention.