Your policies set the rules.
The PMO Agent follows through.
One PMO Agent manages the people and AI workers in a project group. Every step lands in a WeDrive tracker, and every notice cites the policy behind it.
Pick a stage to see what happens in the project group
Space, trackers and group in one go
BeforeIn week one the PM builds folders, plans and risk logs by hand; inherited risk logs often have descriptions only, with no rating, owner or review date.
What AIPaddle does- Pick a template and the WeDrive space is created: 11 standard folders, 12 required documents, plan and risk sheets
- "@PMO bind 〈project ID〉" in the group links the group and the project one-to-one
- AI drafts the first plan and risk log by template stage; for existing projects it fills only empty fields and never overwrites what people wrote
@Leasing lead R-02 anchor negotiation failure is assigned to you, review on 13 Oct.
Policy as configuration: your project rules become executable
BeforeMeeting, reporting and approval rules are well written, but nobody reminds on time, escalates on thresholds or finds the right approver.
What AIPaddle does- The PMO extracts draft rules from the meeting, reporting, management and approval policies
- Once the PM confirms, six controls and the daily report switch on
- A project health check lists conflicts and gaps between plan, policies and records for confirmation
| Meetings | Project weekly Mon 9:30 · leasing Thu 14:00 · business review on the 25th |
|---|---|
| Reports | Weekly Fri 17:00 · monthly on the 25th |
| Status updates | Update task status by Monday 12:00 |
| Tolerance | Escalate after 5 working days overdue; ≥ 10 days variance goes to the sponsor |
| Approvals | Milestone delay ≤ 7 days: PM approves; > 7 days: executive approves |
The health check found 4 items for you: ① 14 tasks with stages that differ from the template; ② policy and records disagree on the project start; ③ the approval matrix names roles but not people; ④ 3 sections marked "to be completed".
One sentence into the tracker, @-mentioning the owner
BeforeWork assigned verbally in the group has no ID and no deadline; when someone is on leave, nobody picks it up.
What AIPaddle does- "Assign to 〈name〉: …, by Friday" is parsed by rule, not by a model, written to the plan and @-mentions the owner
- Missing deadlines get a follow-up question; duplicate names get asked, never guessed
- Deadline changes run directly and can be undone; leave hand-overs move tasks in bulk and show the receiver's load
Due-soon warnings, overdue escalation, status chasing
BeforeOverdue work is found only at the weekly report; the Monday status rule is never checked.
What AIPaddle does- Checks every working day at 08:00, counting working days with the holiday calendar
- Two working days before due it @-mentions the owner; overdue work escalates to the PM by tolerance
- At Monday 12:00 it finds tasks without an update and asks the owners
Due soon: T-004 lease ledger review (8 Oct) @Asset manager
Overdue: T-007 renovation options is 5 working days late, escalated to @Project managerBasis: Project Management Policy · overdue = 5 working days past plan
Log, analyze, assign, track, close
Before"The facade sample hasn't arrived" gets said in the group and then forgotten, and nobody works out what it affects.
What AIPaddle does- "@PMO log an issue: …" creates I-001 and syncs it to the issue log
- Automatic analysis: affected tasks and milestones, likely causes, 2–3 options with a recommendation, and a suggested owner
- Reply "go with the recommendation" to assign; on closing, "issue · cause · fix" is kept for reuse
Impact: T-009 facade design (due 12 Oct)
Options: ① chase the supplier for a delivery date (recommended) ② confirm from drawings, re-check when the sample arrives ③ switch to the backup supplier
Suggested owner: @Renovation lead, by 8 Oct
Acceptance, approvals and gates, all on record
BeforeWho accepts deliverables and who approves delays is verbal; gate materials are scrambled together just before review.
What AIPaddle does- Tasks with deliverables move to "awaiting acceptance" and @-mention the reviewer; after 3 working days without review they return automatically
- Delays, cancellations and changes create approval requests per the matrix and take effect only when the approver replies "approve"
- Before each gate: a checklist (complete / missing / awaiting acceptance) and a draft gate report
Daily, weekly and monthly reports on time
BeforeThe PM compiles the weekly report by hand on Friday night, usually late, then rewrites it for external readers.
What AIPaddle does- Working days 18:00: done today, new today, overdue, due tomorrow, all from the trackers
- Weekly on Friday 17:00 and monthly on the 25th, posted to the group and saved to the project space
- External versions are drafts only, never sent automatically; fields without a data source say "not connected" instead of inventing numbers
Done today 3: T-004 lease ledger review …
New today 2: T-022 anchor load and height check …
Overdue 1: T-007 (5 working days)
Due tomorrow 2: T-009, I-003
Work records collected automatically, KPIs by template
BeforeReviews rely on impressions; the PM has to ask everyone what they did this week.
What AIPaddle does- Work records: sheet edits, uploads, approvals and @PMO interactions, collected per person per day
- KPIs by template weights: on-time 40%, first-pass acceptance 30%, change closure 20%, meeting actions closed 10%
- KPIs are never posted to the group, only shown to the PM, sponsor and admins; anything that cannot be computed is not made up
Assets & leasing 86 · Renovation 72 · Operations & marketing 81
Renovation lost points mainly on T-007 overdue and I-003 closed late.
Assigned by role, delivered by AI, accepted by people
Agents, digital employees and digital teams can hold project roles as AI workers, each with a human owner. Step through one full assignment.
Want to see it running in your business?
A 30-minute online demo built around your industry, including how we would connect to your WeCom and ERP.