Google AI use should be inventoried before teams debate duties. This free template creates a starter record, not a legal decision. Google AI inventory first, legal decision later.
Free Google AI inventory template

Google AI Feature Inventory Template for EU AI Act Readiness

If your team uses Gemini, Workspace AI, NotebookLM, Vids, AppSheet AI, or other Google AI features in business workflows, start with a small inventory record. Record the feature, owner, purpose, data touched, audience, review step, and next evidence route.

No loginFree browser templateNo legal decision
Google AI feature inventory template for EU AI Act readiness with service, owner, data, audience, review, and evidence route fields
Inventory first. Then route the use case to the right review path.

A Google AI inventory is the first control record.

Before debating Article 50, Article 4, deployer duties, vendor evidence, or privacy review, create a simple inventory entry. The entry should show which Google AI feature is used, who owns it, what data it touches, who sees the output, and which free EU AI Compass review route comes next.

Feature record

Name the Google AI surface: Gemini in Workspace, NotebookLM, Gemini app, Vids, Workspace Studio, AppSheet AI, or another business workflow.

Evidence signal

Route the use case to inventory, Article 50, Article 4, vendor evidence, privacy review, or human oversight where the facts justify it.

Review owner

Assign a person who can approve the use case, keep the record current, and escalate legal, privacy, security, or sector questions.

Keep the inventory short enough that teams will actually use it.

A useful Google AI inventory entry is not a policy document. It is a structured row that records the feature, business purpose, data touched, output audience, human review, owner, and the next free tool to run.

Google AI inventory evidence record with fields for service, purpose, data, output audience, human review, owner, and next route

Build one Google AI inventory record.

Answer eight questions. The result gives a starter inventory record and free next-tool route. It does not decide legal status.

Select the closest feature. Use a separate record for each material use case.

Minimum Google AI inventory fields

Start with these fields. Add legal, privacy, security, procurement, or sector-specific fields only when the use case needs them.

FieldWhy it mattersExample entry
Feature and serviceShows which Google AI surface is used.Gemini in Docs, NotebookLM, Meet notes
Business purposeSeparates productivity support from decision support.Summarise meeting notes for internal project tracking
Data touchedTriggers privacy, confidentiality, or sector review.Personal data, client file, public data
Output audienceRoutes Article 50 and communication review.Internal, customer-facing, public
Human review ownerCreates accountability before output is used.Marketing lead, DPO, product owner
Next evidence routeConnects inventory to action.Article 50 checker, vendor evidence, AI literacy planner

Route the inventory record to one free tool.

Do not run every tool. Use the next free tool that matches the risk signal in the inventory row.

Source basis and limits. Last reviewed: 23 May 2026. Source basis: Google Workspace with Gemini official documentation, Regulation (EU) 2024/1689, and AI Act Service Desk Article 50. This page is operational inventory support, not legal advice, privacy advice, security advice, certification, or a statement that Google AI use is automatically high-risk or automatically compliant.

FAQ

Common questions

These answers are for quick routing. They do not replace legal, privacy, security, procurement, or sector review.

Does the Google AI inventory template decide EU AI Act obligations?

No. The Google AI inventory template creates a starter record for internal review. It does not decide legal status, high-risk classification, provider or deployer role, GDPR role, or compliance. Use it to prepare facts before legal, privacy, security, procurement, or sector review.

Which Google AI features should be recorded in the inventory?

Record Google AI features when use is repeated, material, connected to business decisions, exposed to customers or the public, or used with personal, confidential, client-sensitive, regulated, or privileged data. A one-off experiment can stay light, but repeated use should have an owner and review route.

What fields should a Google AI inventory entry contain?

A useful Google AI inventory entry should contain the service, business purpose, owner, user group, data category, output audience, human review owner, Article 50 signal, AI literacy signal, vendor evidence need, and next review route. Keep the first record short enough to maintain.

Does this page store my Google AI inventory data?

No. This free page is designed for browser-based triage and evidence planning. Do not enter confidential, personal, privileged, regulated, client-sensitive, or trade-secret information unless your organisation has approved that use and verified the page implementation.

What should I do after creating the Google AI inventory record?

Use the Google AI inventory record to route the use case to one next review: deployer obligation assessment, Article 50 checker, vendor evidence request builder, AI literacy planner, privacy review, or human oversight log. The right next step depends on data, audience, decision impact, and review ownership.

Use the inventory record to start the right review.

This free Google AI inventory template helps you identify owner, data, audience, review, training, vendor, privacy, and disclosure gaps. Use the result for triage and internal planning, then validate legal, privacy, security, and sector questions with qualified professionals.