Find project dependencies nobody has agreed to own
A reviewed draft of dependency ownership exceptions with affected milestones, checked against the original inputs.
Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
ChatGPT: drafts the table and exceptions, you check both
ChatGPT builds the coverage table and drafts the exceptions in one chat. You check both against the originals.
You
You: Get inputs ready
ChatGPT
ChatGPT: Build coverage table
You
You: Check the table
ChatGPT
ChatGPT: Draft exceptions
You
You: Check and decide
Get the inputs ready
Use:You
Have ready: the dependency register, ownership map and milestone dates. Paste the set into one new ChatGPT chat.
Check
Check your plan terms allow this data, and every source ID matches the originals.
Build the coverage table
Use:ChatGPT
Ask ChatGPT to build the dependency-to-owner coverage table from the pasted inputs, flagging ambiguous items as unresolved.
Details
What to paste into the tool
From the pasted dependency register, ownership map and milestone dates, build dependency-to-owner coverage table. Output a structured table. Keep every source identifier, relevant date and explicit uncertainty exactly as supplied; mark anything ambiguous as unresolved rather than guessing; use only the supplied operating rules, do not invent policy; minimise personal and personnel data in the output.
Check the table against the originals
Use:You
Compare the table with the original register, map and dates; ask ChatGPT for corrections in the same chat.
Check
Check each source ID, date and uncertainty marker against the originals.
Draft the ownership exceptions
Use:ChatGPT
Ask ChatGPT to draft the ownership exceptions with affected milestones from the checked table, listing unresolved questions.
Details
What to paste into the tool
Using the corrected dependency-to-owner coverage table and the supplied rules, prepare draft dependency ownership exceptions with affected milestones. Keep every source reference visible, keep disputed or uncertain items explicitly marked, and list unresolved questions with their source references. Draft wording only: do not add facts that are not in the corrected table or the supplied inputs. Do not assign anyone or commit to any action.
Check the exceptions and decide
Use:You
Check the draft exceptions and unresolved questions against the original inputs; the workflow ends at this checked draft.
Check
Check each unresolved dependency without assigning anyone. Decide any next action separately.
Gemini: builds the coverage table and drafts exceptions
Gemini builds the coverage table and drafts the exceptions. You check both and keep the final call.
You
You: Get inputs ready
Gemini
Gemini: Build coverage table
You
You: Check the table
Gemini
Gemini: Draft exceptions
You
You: Check and approve
Get the inputs ready
Use:You
Have ready: the dependency register, ownership map and milestone dates.
Check
Check your plan terms allow pasting the inputs into Gemini.
Build the coverage table
Use:Gemini
Ask Gemini to build the dependency-to-owner coverage table: one row per dependency with source ID, date and uncertainty marker.
Details
What to paste into the tool
Build the dependency-to-owner coverage table from the inputs pasted below. One row per dependency, each with its source ID, relevant date and an uncertainty marker where the input is unclear. Use only the supplied inputs: do not add facts, sources or decisions. Keep every source reference visible.
Check the table against the inputs
Use:You
Check the table against the original register, map and dates; ask for fixes in the same chat.
Check
Compare identifiers, dates and ambiguous claims against the original inputs.
Draft the ownership exceptions
Use:Gemini
Ask Gemini to draft the ownership exceptions from the checked table and supplied rules, listing unresolved questions with their references.
Details
What to paste into the tool
Draft the dependency ownership exceptions with affected milestones from the checked dependency-to-owner coverage table pasted below and the supplied rules. Wording only: do not add facts, sources or decisions that are not in the checked table. Keep every source reference visible and list unresolved questions with their source references. Do not assign anyone or commit to any action.
Check the exceptions and approve
Use:You
Read the draft against the requirements, resolve or keep each open question, and approve only when facts and source references are right.
Check
Check each unresolved dependency without assigning anyone. Decide any next action separately.
Gemini Notebook: builds the cited table and drafts exceptions
Gemini Notebook builds the cited table and writes the exceptions from it. You check both and approve.
You
You: Set up notebook
Gemini Notebook
Gemini Notebook: Build cited table
You
You: Check the table
Gemini Notebook
Gemini Notebook: Write exceptions
You
You: Check and decide
Set up the notebook and sources
Use:You
Have ready: the dependency register, ownership map and milestone dates. Upload them to a new notebook in Gemini Notebook as named sources, so citations stay attributable.
Check
Check your plan terms allow the upload and the set is complete; free notebooks allow up to 50 sources.
Build and export the cited table
Use:Gemini Notebook
Ask Gemini Notebook to build the cited coverage table, then export it to Google Sheets; citations land on the second tab.
Details
What to paste into the tool
Using only the uploaded sources, build the dependency-to-owner coverage table. Produce it as a data table; describe the rows and columns so each row keeps its source citation, relevant date and any uncertainty. Mark anything ambiguous as unresolved rather than guessing; use only the supplied operating rules. Nothing is sent or published.
Check the exported table
Use:You
Check the exported table against the original inputs and correct it. Mark anything you cannot settle as unresolved.
Check
Check each row has a source reference; check missing ones directly against the originals.
Write the exceptions from the notebook
Use:Gemini Notebook
Ask Gemini Notebook to write the ownership exceptions from the checked table and uploaded sources, with a source reference next to each item.
Details
What to paste into the tool
Using only the uploaded sources and the checked dependency-to-owner coverage table below, draft the dependency ownership exceptions with affected milestones. Keep one source reference next to each item. Mark anything ambiguous as unresolved rather than guessing; list unresolved questions with their source references. Use only the supplied operating rules; do not invent policy, facts or names. Nothing is sent or published. Checked table: [paste the checked table].
Check the exceptions and decide
Use:You
Check the draft wording against the checked table and originals; do not add unsupported facts or settle ambiguity by inference.
Check
Check each unresolved dependency without assigning anyone. Decide any next action separately.
Compare the three approaches
Option A: ChatGPT: drafts the table and exceptions, you check both
Best when: You want one ChatGPT chat to structure and draft both artefacts
What it does: ChatGPT builds the table and drafts; you check both
Strong at: One chat holds both stages; no re-explaining
Limit: Source IDs may not survive; re-check every identifier against originals
Free plan: Yes, limited (uploads and analysis capped)
Option B: Gemini: builds the coverage table and drafts exceptions
Best when: You want Gemini to do the extraction and the drafting
What it does: Gemini builds and drafts; you check and decide
Strong at: Your time goes to checking, not typing
Limit: Vendor states LLM outputs can invent inaccuracies; check every row
Free plan: Yes
Option C: Gemini Notebook: builds the cited table and drafts exceptions
Best when: You want cited answers grounded only in your uploaded sources
What it does: Gemini Notebook builds the table and writes; you check
Strong at: Citations are direct quotes; the table exports to Sheets
Limit: Citations point to uploaded files, not your own source IDs
Free plan: Yes
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Compare the source identifiers, definitions, dates and ambiguous claims against the original inputs; correct the dependency-to-owner coverage table before handoff.
Lead verifies each unresolved dependency without automatically assigning anyone. Confirm any next action separately; this workflow ends at a reviewed draft.
Suggestions and draft artefacts only. Do not send, publish, update records, assign people, reserve resources, buy goods or authorise work.
Any safety, legal or employment requirement needs the responsible qualified human; this output is not certification.
Check the result against your original inputs. Approve it before sharing or acting.
What still needs checking
Whether the supplied inputs already carry stable source IDs or the reviewer must assign them during preparation.
No option assigns an owner for any dependency still to confirm; naming owners stays with the lead, outside this workflow.