The project changed direction. You need to know when and why.
OGAD (Off Grid AI Desktop) helps you search past recorded meetings and compare what was agreed at each stage. On Mac with Pro, use local transcripts and meeting citations to build a decision history you can check. You supply the project question; the saved meetings provide the evidence.
Follow one decision across the project
Choose a specific subject: launch date, rollout scope, hosting choice or an approval requirement. “How did this project change?” is too broad for a useful first pass. A narrower question gives you a sequence you can verify.
For example:
Search my recorded meetings about the Cedar rollout scope. Find statements about what belongs in the first release. Give a dated sequence, cite each meeting, and distinguish an agreed change from a suggestion.
Replace Cedar with your project name. The output you want is a timeline of supported statements, not a confident story that fills the gaps between calls.
Find the meetings before comparing them
Use OGAD Pro with completed meeting transcripts and a local text model. In Chat, select a model that supports tools, turn Tools on and ask the meeting question. Check that the answer actually searched recorded meetings and includes source citations.
You can also open Search, enter the project and decision topic, and narrow Sources to Meeting. Use Recent to inspect newer discussions. Open each relevant result in Meetings and record its date.
The tool returns a limited set of matches and bounded excerpts. It is not an automatic, exhaustive audit of every call. If the project has many meetings, search again with narrower terms and different phases of the decision.
Build a decision history you can defend
Use a small table in your own notes:
| Field | What to record |
|---|---|
| Meeting and date | Where the statement came from |
| Position at that time | The actual choice or proposal |
| Status | Agreed, conditional, proposed or unresolved |
| Reason stated | Only a reason present in the source |
| What changed | The difference from the previous supported position |
Read the surrounding transcript before entering a row. Replay the retained recording when a name, condition or deadline is unclear. A citation opens the meeting; it does not guarantee a jump to the exact spoken second.
For instance, “start with two regions” and “consider a third region” are not necessarily conflicting decisions. The second statement may be an option for later. Ask the model to preserve that difference.
Use AI for the comparison after checking the sources
Once you have verified the relevant passages, paste those passages with their meeting dates into a local chat and ask:
Compare only these dated statements. List confirmed changes, conditions that stayed the same and unresolved questions. Do not invent a reason for a change. Keep the meeting label with each point.
This gives you a useful project note: what changed, what remains open and what you need to confirm next. It also makes the source scope clear when you share the note with someone else.
Long meetings need a closer look
The checked automatic summary uses the first 12,000 characters of a transcript. A later reversal may not appear there. Read the full stored transcript for the decision topic rather than assuming the summary covers the closing discussion.
A missing recording, incomplete transcript or call that was never recorded leaves a gap in the history. Mark the gap. Do not let the model infer that the last visible statement is necessarily the latest real-world decision.
The guide uses Mac Pro meeting search associated with OGAD 0.0.51. Prepare local models and licence setup before offline work. New recordings need the visible recording state and participant agreement.
Recover the history of one open question
Download OGAD for Mac, search one project topic and compare two relevant meetings. Check both sources, then write a short “changed / unchanged / unresolved” note. Go into the next discussion with the history in front of you.
Top comments (0)