Use Glass as your chief of staff

Overview

Early Access. For access information, see Request access to Glass.

Give Glass your responsibilities, priorities, and approved context, then ask it to prepare a brief about what needs your attention. Use the workflow to reconcile updates and open actions, while keeping decisions, ownership, and outreach under your control.

Who this is for: People preparing for operating reviews, leadership meetings, or decisions.

Prepare your Glass briefing sources

Gather the following approved context before setting up the workflow. Use reference examples for structure and style, not as proof of current facts or approval to take an action.

• Your responsibilities, goals, current priorities, and briefing preferences.
• Operating rules that explain which source controls each fact, plus a dated decision log.
• Dated updates, meeting notes, and an action register with confirmed owners, original deadlines, statuses, and completion evidence.
• Relevant metric definitions and snapshots, including whether numbers are certified or directional.
• One strong brief example for structure and style only.

Review who can access your project before adding sensitive information. If you need information from a connected app, check the project's plugin access; a personal connection is not proof that the project can use it.

Set up your Glass chief-of-staff workflow

In Glass, choose a project with an appropriate audience. Add the sources listed above and paste this prompt. For setup help, follow Get started with Glass.

Draft reusable chief-of-staff guidance using my approved context:

- Reuse my saved role, goals, priorities, and preferences. Establish the meeting or decision, audience, brief date, timezone, source cutoff, and emphasis; ask only for missing intake.
- Reconcile controlling sources using explicit superseding decisions. Exclude after-cutoff updates. Separate facts, directional metrics, proposals, recommendations, and approvals. Use example briefs for style only.
- Deduplicate actions, preserve original deadlines, and require completion evidence. Never infer or choose owners; leave missing owners unassigned. Keep a separate reconciliation register including completed actions.
- Brief me on priorities, changes, decisions needing me, follow-ups, unresolved questions, and sources. Ask a focused question about missing intake or conflicting sources; draft uncontested content without inventing answers or finalizing unresolved facts.
- Retain standing feedback only with explicit approval; keep one-off corrections local.

Label outputs Draft for review. Return them to this project or specified linked thread. Provide editable document/PDF exports only when supported; otherwise disclose the limitation and return the draft here.

Do not approve decisions, change commitments, edit source systems, alter permissions, or contact others without explicit confirmation.

Identify missing sources or connections and show the guidance for approval before applying it.

Review the source rules, audience, and review requirements. After approval, follow Save and reuse instructions in a Glass space.

Prompt instructions do not restrict a connected account's permissions; review Glass access to connected apps separately.

Request your next brief in Glass

Replace the bracketed fields with the meeting, audience, date, timezone, and source cutoff. Request exports only if needed.

Act as my chief of staff and get me ready using this project's approved context. Read the saved workflow and source-rule files: [File names].

What I am preparing for: [Meeting, decision or review]
My priorities: [Focus, or use my saved priorities]
Audience: [Me and any intended reviewers]
Brief date: [Date]
Timezone: [Timezone]
Source cutoff: [Date and time]
Output: Concise brief for me, editable document/PDF if supported and needed, and an action reconciliation register

Tell me what needs my attention, what has changed, what I need to decide and what needs follow-up. Recommend next steps where the evidence supports them, but separate your recommendations from approved decisions. Reconcile the sources for me, preserve original due dates, and keep missing owners, missing completion evidence and unresolved conflicts visible. Do not make decisions, assign owners or contact people on my behalf.

Use reference examples for structure and style only. Keep the result labeled Draft for review and return it to this project or the specified linked thread. Ask for missing required intake before drafting. If a single fact remains unresolved, prepare the uncontested draft and ask one focused question; do not invent the answer or finalize the brief. If an export is unavailable, state the limitation and return the draft content here.

For a Slack-based request, first check how to message Glass and link the intended channel. Check the project audience before using a channel. The Slack app and a personal Slack plugin connection are separate; do not assume connecting your personal account installs the app.

Review the Glass brief and decide what to do

Keep the result as a draft until you have checked it against the approved sources. Ask Glass to make gaps and conflicts explicit instead of filling them in, and review any requested follow-up before it changes records or reaches another audience.

• Check that later approved decisions replace older plans only when the evidence explicitly supports that change. Keep proposals and recommendations distinct from approvals.
• Confirm that after-cutoff updates are excluded, original deadlines are preserved, duplicate actions are reconciled, and completion is supported by evidence. A related metric reaching its target is not proof that an action is complete.
• Leave missing owners unassigned. Keep unresolved conflicts and missing completion evidence visible, and retain completed actions in the reconciliation register rather than presenting them as open follow-ups.
• Review the sources and decide what to do next yourself. A briefing request is not your approval for Glass to contact people, approve decisions, change commitments, or edit source systems; keep those actions separate from drafting.

All starter workflows