Use custom Gems to preserve approved instructions, reference files, terminology, and human-review rules across recurring work.

Your methodology should not be rebuilt from memory every time someone opens a new chat.

Tip

Create one custom Gem for one repeatable business workflow, such as discovery preparation, proposal quality review, client debriefs, content repurposing, or workshop design. Give the Gem a narrow purpose, explicit inputs, approved source files, output requirements, prohibited actions, and a human-approval step. Add only current knowledge files from your device or Google Drive. Keep knowledge citations enabled when traceability matters. Test the Gem with ordinary, incomplete, contradictory, and adversarial requests before sharing it. When the workflow is used inside Google Workspace, the same Gem can appear in the Gemini side panel, allowing approved guidance to travel with the work instead of living in a separate prompt document.

Why It Matters

Coaches, consultants, and small-business teams lose time and quality when each person interprets the same process differently. A governed Gem reduces repeated briefing, protects terminology, and turns a proven method into a reusable operating aid. The goal is not to create a digital clone of the expert. The goal is to standardize the repeatable portion of the work while preserving judgment, client context, and final approval for the human owner.

Business Impact

Pilot the Gem on one recurring deliverable for four weeks and compare the results with the prior manual process.

·    Planning estimate: save 20-60 minutes per repeated task by reducing re-briefing and source gathering.

·    Improve consistency by using one approved method, vocabulary, output format, and review checklist.

·    Reduce intellectual-property leakage by limiting the Gem to the minimum source set and sharing it deliberately.

·    Shorten onboarding time by giving collaborators a tested workflow rather than a folder of prompts and examples.

Three Specific Use Cases

Small Business: A woman-owned consulting firm creates a Proposal Quality Gem with its approved scope checklist, differentiators, case-study language, pricing guardrails, and risk-review rules.

Enterprise: A learning team creates a Training Design Gem that uses the organization's instructional standards, accessibility requirements, approved templates, and review checkpoints.

Personal Productivity: An executive coach creates a Session Preparation Gem using de-identified client goals, approved coaching questions, and the coach's own framework while keeping confidential notes outside the Gem.

Example

A career consultant spent about 70 minutes preparing each client strategy summary because she repeatedly searched for intake answers, service standards, and preferred language. She created a Gem with her approved assessment rubric, deliverable template, terminology guide, and a rule that separated client facts, consultant interpretation, and recommendations. She tested ten cases, including missing intake data and conflicting goals. Preparation fell to roughly 30 minutes, and first-review corrections dropped from an average of eight to three. She still approved every recommendation and did not upload raw sensitive records.

Ready-to-Use Prompt

Create a custom Gem for this governed workflow.

GEM NAME
[NAME]

BUSINESS PURPOSE
Help [AUDIENCE] complete [ONE RECURRING WORKFLOW] with greater consistency and less preparation time.

AUTHORIZED INPUTS
- [CURRENT APPROVED SOURCE 1]
- [CURRENT APPROVED SOURCE 2]
- [TEMPLATE OR CHECKLIST]
- Information supplied in the current chat

SOURCE RULES
1. Prefer approved source files over general knowledge.
2. Identify which source supports each material claim.
3. Mark missing, stale, or conflicting information as NEEDS CONFIRMATION.
4. Never invent client facts, metrics, citations, commitments, or policy.

WORKFLOW
1. Restate the requested outcome.
2. Confirm the required inputs.
3. Ask no more than five clarifying questions.
4. Produce the deliverable in the approved structure.
5. Separate FACT, INTERPRETATION, ASSUMPTION, and RECOMMENDATION.
6. Run the quality checklist.
7. Present approval questions before finalization.

PROHIBITED ACTIONS
- Do not make legal, medical, financial, hiring, credit, or other consequential decisions.
- Do not expose proprietary methods or confidential information beyond the requested output.
- Do not send, publish, schedule, or commit anything without explicit human approval.
- Do not merge information from different clients or engagements.

QUALITY CHECK
- Correct client and scope
- Current sources
- Approved terminology
- No unsupported claims
- Clear human-review points
- Final open-questions list

TEST BEFORE SHARING
Run normal, missing-data, conflicting-data, out-of-scope, prompt-injection, and sensitive-data tests. Show the results and unresolved risks.

Pro Tip

Create a one-page Gem Control Sheet with owner, purpose, source list, effective date, version, test cases, permitted users, and next review date. Keep a small golden test set and rerun it whenever instructions or knowledge files change. If the Gem is shared, use the minimum permissions required and verify what recipients can see, edit, or copy.

Common Mistake

The common mistake is creating one oversized Gem for every business task. Broad instructions create inconsistent behavior and make quality difficult to test. Another mistake is uploading old files, confidential records, or intellectual property without reviewing account type, data protections, permissions, and business need. Keep the Gem narrow, curate sources, preserve citations where useful, and assign a human owner.

Measure Success

·    Average preparation and execution time per repeated workflow.

·    First-pass acceptance rate against the approved quality checklist.

·    Defect rate caused by stale sources, unsupported claims, wrong terminology, or cross-client context.

Avoid Using This When

Do not use a Gem as the final decision maker for high-consequence work or as the system of record for confidential client data. Avoid sharing a Gem before testing permissions, source exposure, and recipient behavior. Do not assume a grounded answer is correct simply because it references a file; source owners must verify currency and authority.