No new project-management software to adopt
Project management in Google Workspace.
Blue Chameleon sets up and tailors project registers, decision logs, working folders, and team routines in Google Sheets, Drive, and Docs. Your team gets a practical system in the workspace it already uses.
For small teams coordinating client delivery, operations, or field projects through spreadsheets, documents, and email.
The setup / 01
The records, the routine,
and the people using them.
We start with one workflow and agree what the team needs to record, review, and act on. A possible first setup includes:
| What we set up | Where it lives | What it makes clear |
|---|---|---|
| Project register | Google Sheets | A consistent project ID, owner, milestone, next action, due date, blocker, and last-updated date. |
| Decisions and changes | Google Sheets + linked Docs | A record of what is proposed, what is approved, who decides, and which source supports it. |
| Working files | Google Drive | An agreed folder structure and naming routine, with shared access reviewed with your team. |
| Playbooks and handoffs | Google Docs | Short instructions for updating records, escalating blockers, approving changes, and preparing the weekly review. |
| Attention view | Google Sheets or an agreed dashboard | A view of overdue actions, blocked work, and pending decisions, based on the working register. |
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 delivery changes.
The record keeps up.
Imagine a restoration team that already uses Google Workspace. A supplier changes a delivery date while the team is preparing the next phase of work.
Fictional example · not a customer resultWatch the 60-second demonstration ↗- 01
Capture the change
The project manager saves the supplier update in the agreed Drive folder, links it from CH-014, and records the new information in Sheets.
- 02
Make the decision visible
The register shows the affected milestone, the person responsible for confirming the date, and the next review point. A proposed schedule change stays pending until approved.
- 03
Prepare the weekly review
The team filters the register for blocked items and open decisions. If supported AI access is configured, it can help draft a briefing from the selected records; the team checks the sources before using it.
Useful AI support / 03
Use the AI you already have, where supported.
We assess Gemini or another AI tool you already use against a specific task: finding an approved record, drafting a status summary, or preparing a meeting brief. We test access to the actual files and agree what a person must review. The register and playbooks remain usable without AI.
Google says Gemini in Drive requires an eligible Google Workspace or Google AI plan. Plan eligibility, administrator settings, supported file types, and permissions affect what is possible.
Platform reference: Google’s guidance on Gemini in Drive. Reviewed October 16, 2026.
Before we build / 04
Clear expectations.
A practical scope.
Can Google Sheets work as our project register?
Yes, for a workflow whose scale and complexity fit a shared spreadsheet. We define the fields, views, update routine, and owners, then test them with a real project. If your needs require more advanced scheduling or controls, we identify that during scoping.
Do you give us templates or set up the system?
We set up and tailor the agreed system with you, adapt it to your existing records, test the handoffs, and train the team. It is a setup service with an agreed scope.
Will every email or file update the register automatically?
No. The core workflow includes a clear update routine. Any automation is scoped separately, checked against your tools and permissions, and tested before the team relies on it.
Do we need a new subscription or portal?
No new project-management platform or Blue Chameleon login is required for the core setup. Your existing workspace licenses still apply. Any additional AI, connector, or dashboard costs are agreed before the build.
Start with one workflow
Let’s make your next
handoff clearer.
Bring one current project sheet, an example Drive folder, and the update your team keeps chasing. We will use those to scope the first workflow.