No new project-management software to adopt
Project management in Microsoft 365.
Blue Chameleon sets up and tailors project registers, decision logs, shared files, and review routines in your Microsoft 365 environment. Excel, SharePoint, Word, and Teams get clear roles in how the work moves forward.
For teams whose project facts are spread across workbooks, shared folders, meeting notes, and Teams conversations.
The setup / 01
The records, the routine,
and the people using them.
We agree which file or record is authoritative and how the team keeps it current. A possible first setup includes:
| What we set up | Where it lives | What it makes clear |
|---|---|---|
| Project register | Excel in an agreed shared location | Active projects, owners, milestones, next actions, blockers, and a consistent last-updated field. |
| Change and decision log | Excel + linked source files | Separate proposed changes from approved decisions, with the responsible person and supporting evidence. |
| Shared project files | SharePoint or OneDrive, as appropriate | A clear home for specifications, approved documents, and working records, with access reviewed for the people using them. |
| Playbooks | Word | Practical guides for updating records, checking sources, preparing meetings, and completing handoffs. |
| Team routine | Teams + the agreed records | Links to the current files and a regular review routine so decisions in conversation are reflected in the record. |
We build the agreed setup, test it with a real workflow, document how it works, and train your team. Optional support is scoped separately.
A practical example / 02
A proposed change.
A traceable decision.
Imagine a project delivery team working in Microsoft 365. The purchasing record lists one material, while the approved specification calls for another.
Fictional example · not a customer resultWatch the 60-second demonstration ↗- 01
Check the source
The engineer opens the specification in SharePoint and records the mismatch in the change log, including a link to the supporting document.
- 02
Prepare the handoff
The project manager records the proposed correction, expected impact, and the senior project manager responsible for the decision. Teams is used to point colleagues to that record.
- 03
Record the outcome
Once a person approves or rejects the change, the owner updates the log. A weekly attention view shows remaining blockers and pending decisions without treating proposals as approvals.
Useful AI support / 03
Give Copilot or your supported AI a clearer starting point.
We identify the records your AI should use, check the account and supported access, and test a briefing against a known project example. Reading information, changing a workbook, and running a scheduled routine are separate capabilities. Each is agreed and tested if included in your scope.
Microsoft states that Copilot only surfaces organizational information the individual user has permission to view. We review the underlying access with your team; AI does not fix overly broad file permissions. Features also depend on your product, license, and administrator settings.
Platform reference: Microsoft’s guidance on Copilot and organizational data. Reviewed October 16, 2026.
Before we build / 04
Clear expectations.
A practical scope.
Can we keep using Excel and Teams?
Yes. We start with your existing tools and agree which records belong where. Teams can remain the place for discussion, with decisions and next actions captured in the agreed project register.
Does everyone need Copilot?
AI is optional. The records, playbooks, and review routine should work on their own. If AI support is included, we confirm the required product, licenses, and permissions for the people using it.
Will this replace every specialist project tool?
We scope the work around your needs. A shared register may suit a coordination workflow, while complex scheduling, resource planning, or specialist controls may need different tools. We identify that before agreeing the build.
Where do the files and instructions stay?
The core records and playbooks stay in your Microsoft workspace. We document the structure and train the team. Any additional dashboard hosting, connectors, or automation are explicitly agreed.
Start with one workflow
Let’s make your next
handoff clearer.
Bring one project workbook, an example shared folder, and a decision that got lost between a meeting and the next handoff. We will map a practical first setup.