For project managers
You spend your week asking people where things stand
Then you write it down, and by Thursday it is out of date again. SecondBrain 365 is an AI agent with its own email address inside your Microsoft 365: copy it in, invite it to meetings, and it does the asking, keeps the project record current, and leaves you the part that actually needs a project manager.
See how SecondBrain 365 supports project managers through the week — from the status round to the handover.
The project is fine. Finding out whether it is, is the job.
Three people owe you an update. One answered in a chat you cannot find, one said “almost done” at the stand-up, one has not replied. The plan still says what it said in March.
72%
of project professionals spend half a day or more every month just assembling reports by hand.
Wellingtone, State of Project Management 2026
60%
of project status reports were found to be distorted in a study of 56 experienced project managers — optimistic distortion was twice as likely as pessimistic.
Snow, Keil & Wallace, Information & Management, 2007
56%
say they often find the only way to get the information they need is to ask someone, or book a meeting.
Atlassian, State of Teams 2025
The PM stays. What changes is that the PM is no longer the one collecting the answers.
Where things stand
It does the asking
The agent knows what was committed and by when, because it read the documents and the meetings where it was said. When a date comes up, it posts the reminder — and records what comes back.
The deadlines were never typed in
They came out of the project documents, because your context file says that is what to look for. Nobody maintained a list.
The bad news arrives early
A date that moves is worth knowing while it is still cheap. It reaches you when someone says it, not at the next status meeting.
Silence becomes visible
It cannot make anyone answer. What it can do is show you, two days before the date, that nobody has — which is the part you usually find out too late.
Deadlines in this project
Pulled out of the project documents, because the context file says to.
- Supplier quotes for the hardwaredoneAnna· due Fri 12 SepWhat the agent did“The supplier quotes were due today — are they in?”Anna: “Sent this morning, all three came back.”Recorded as done, with the date it actually happened.
- Sign-off on the migration plandate movedLuca· due Mon 15 SepWhat the agent did“The sign-off was due yesterday — is it still on track?”Luca: “Not yet, we're slipping to the 22nd.”The new date is in the timeline — and everything that depended on it is flagged.
- Data migration test on stagingno answer yetSara· due Wed 17 SepWhat the agent did“The migration test is due tomorrow — anything blocking it?”No answer yet. Which is itself worth knowing, two days before the date.
Nobody chased any of this. The deadlines came out of the documents, the reminders went out on their own, and what came back is in the project record.
Action items
The task exists because it was said, not because someone typed it
“I'll check with the supplier by Friday” is a sentence in a meeting. It becomes a task with an owner and a date, and it keeps a link back to the minute it came from — so “who asked for this?” takes a click, not an archaeology session through six months of mail.
What is said
“Luca will check the sign-off with the infrastructure team by Friday.” — Status meeting, 17 Jul, minute 24.
What you get
A task: check sign-off with infrastructure · owner Luca · due Fri 21 Jul · from the 17 Jul status meeting.
A review of 618 studies found that what makes a meeting work is clarity about what was decided (r = .51), far more than having a formal agenda (r = .14). This is the clarity part — produced after the meeting, from the meeting. CIPD/CEBMa, Productive Meetings, 2023
Blockers
“I'm waiting on infrastructure” should not stay in a thread
It is said once, in a chat, on a Tuesday. It is the reason the date will move — and today it surfaces two weeks later, in a status meeting, when it has already cost you the two weeks.
What the agent does
It reads the same conversations you do. When something is described as waiting or blocked, it does not evaporate with the thread: it lands in the project record, attached to the item it is holding up. You see it while it is still cheap to solve.
What it does not do
It does not decide who should fix it, and it does not escalate over your head. Reading a room and knowing which blocker is real is the part of your job that does not delegate — this just makes sure you are looking at all of them.
The UK National Audit Office calls the opposite “good news cultures”: places where evidence is not acted on in time, and disagreements between stakeholders are never resolved. Lessons learned on mega-projects, March 2025.
A concrete case
The request that was out of scope. Until it wasn't.
March — Scope call: the export to the ERP is out of perimeter. The agent writes it into the requirements, with the date and who said it.
July — In a status meeting it comes up as a given — “the ERP export, we agreed that in spring”. Nobody goes back to check the March minutes.
Right after — The agent had read them. What it does next is on the right — and notice that it asks, it doesn't decide.
Anna Bianchi · 4 Mar · Scope call
Agreed: the ERP export stays out of scope for this phase.
Marco Realli · 17 Jul · Status meeting
We're demoing the ERP export on Friday.
SecondBrain 365Agent
Inconsistency on the project scope
The requirements say the ERP export is out of scope. Today's meeting treats it as in scope. Which one holds?
ERP export:out of scope
Until someone decides, the page keeps out of scope and the alert stays open.
Four months apart, in two different meetings. The agent is the only one who had read both — and it asks the team instead of deciding for them.
And none of it happens over your head
Three things people ask before they trust an agent with the project record.
You choose who is in
Only workspace members can send the agent anything. Someone outside cannot put a line into your project's record, by accident or otherwise.
You choose whether it writes, or asks first
Approval is a switch. Turn it on for the project under audit, and every page waits for your sign-off before it exists.
You write the filing rules
One folder for recaps, one for requirements, one for test results — in plain language, in a file you edit the day the project changes.
And when the project ends
The knowledge stays
Even when the person who held it in their head moves to another company.
The next PM
Finds it written down, and doesn't have to reconstruct a year of decisions from an inbox.
The audit
Every decision has a date and a source — because it was recorded when it was taken.
Microsoft retired Viva Topics, which promised exactly this. What a Viva Topics alternative has to do — and why finding pages was never the hard part.
FAQ
Questions project managers ask
No — and it does not work without you. The agent does the collecting: the deadlines, the reminders, the recaps, the trail of who decided what. Every judgement call stays yours, starting with the inconsistencies it raises — it asks which version holds, it does not pick one. What changes is that the part of your week spent gathering answers stops competing with the part spent running the project.
No. There is nothing for them to adopt: they keep working in Outlook, Teams and SharePoint. The only new thing in the project is an email address — the agent's — that you put in copy, invite to a meeting, or add to a Teams group. People who never open a single SecondBrain 365 screen still contribute to the project record.
They are the ones you would have sent yourself, so the volume is the same — what changes is that they are not coming from you, and they are tied to something the person actually committed to in a meeting. You decide which deadlines are worth following up in the context file: if a project does not need chasing, the agent does not chase.
Yes, and it is the common case. Add the agent to the existing Teams group and share the documents you already have: it reads what it is given and builds the record from there. It will not invent the six months it did not see — but from the day it joins, the record stops having holes in it.
Two answers. Before: you can require approval, so nothing enters the project record until you sign it off. After: the pages are ordinary SharePoint pages — you edit them by hand, exactly as you would any other document. The record is managed by the AI and by people together, not handed over to the AI.
In your own Microsoft 365 tenant: a SharePoint site under the project's Teams group. Nothing is copied to a third-party platform, and your existing permissions, retention and compliance rules apply to it, because it is not a separate system. The detail your IT will want is on the how it works page.
Need it for something else?
Same agent, same mechanism. What changes is the rules you write in the context file.
Product management
Why the product is the way it is — written down while you decide it
HR
The answer your team already wrote, found by the next person who asks
IT service desk
Forward the reply you just sent. That is the whole documentation step
ISO audit
Evidence recorded as it happens, not reconstructed the month before
RFP & bids
The tender's deadlines pulled out of the pack, and the chasing done for you
Onboarding & offboarding
What leaves with a person becomes smaller — and it is honest about the rest