Skip to content
Browse docsFirst review

Documentation First review

Leave the first review with an answer you can inspect.

Start with one question engineering and finance already need to answer. This guide is for invited partners after their workspace, source scope and client setup have been accepted during onboarding.

Updated October 6, 2026

Bring a question and the right people

  1. Name the decision and the person who needs the answer. For example: which reported project costs need investigation before the next budget review?
  2. Identify the workspace owner or administrator who can authorize access and a finance reviewer who can check the result.
  3. Agree sources, account IDs, currency and inclusive UTC dates with your onboarding contact. Record the latest available data and any missing days.
  4. Have comparable source records ready for the same period. Do not paste provider keys, browser cookies or credentials into an AI conversation.

A connection is only the starting point

Use the client and setup path agreed during onboarding. For hosted MCP, follow the connection guide, inspect the app and workspace on the consent screen, and confirm that all four tools appear. A founder weekly review in ChatGPT Work has been demonstrated; acceptance of your own workspace and client remains a separate step.

Read how consent, expiry and removal work.

Keep the scope beside the answer

Example review request
Review my workspace for the agreed UTC start and end dates.
Name the included accounts, currency, freshness and missing coverage.
Show supported spend and available project detail, summarize the briefing,
and list budget settings separately. Do not treat settings as enforcement.
Keep estimates and shared activity separate from provider-reported costs.
Identify one question to investigate; do not infer ROI or individual spend.
  1. Spend: check the period and accounts before interpreting the total. Identify incomplete or unavailable coverage.
  2. Projects: inspect the available provider project groups. Unattributed amounts stay unattributed; repository activity is separate evidence.
  3. Briefing: check the evidence behind a suggested investigation. A spike is not automatically waste.
  4. Budget settings: read configured amounts and settings. These reports do not enforce limits or report every budget evaluation.

Compare the same thing twice

Compare the report with Workspace and the available source records using the same dates, accounts and currency. Keep credits, taxes, timing and missing records in view when an invoice differs. Do not combine overlapping history or silently shorten the requested period to produce a complete-looking answer.

Record what was useful and what remains open

Write down the answered question, remaining uncertainty, next investigation and review effort, including hands-on assistance. Agree whether a second review would be useful and check the access expiry before it. Connection alone is not a successful review.

If the question is about return, an assisted AI Value Pilot can help define one outcome baseline. Current cost reports do not automatically measure productivity, useful outputs or ROI.