On this page
You do not have to rebuild your workweek from memory every Friday. OGAD (Off Grid AI Desktop) can use retained work context to prepare a report draft on a weekly schedule in God, its Pro assistant workspace.
The automatic part starts after you enable the relevant capture and configure the routine. The draft is only as complete as the sources the app can retrieve. Review it before you share it with a manager or client.
| Download OGAD | Desktop beta 122 release notes |
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to [email protected], join our Slack community, or talk to us on Reddit.
Decide what the report needs to show
Choose a small structure that matches the reader’s decision: completed work, unresolved work, blockers, and next week’s priorities. Ask for source references beside important claims. A chronological list of everything you opened is usually less useful than a report tied to outcomes.
For example, a project lead may need to know which client requests were completed and which decisions still need an owner. The report should separate “discussed,” “started,” and “completed.” A meeting about a deliverable is not evidence that it shipped.
Choose the reporting dates explicitly. “This week” can be ambiguous near midnight or when you run the task on a different day.
Prepare a week’s worth of evidence
Set up OGAD and enable the capture features you want to use. Check the visible capture state and retention settings. Connect relevant notes or accounts only if the report needs them.
Saved screen activity is sampled context, not a continuous video recording of every action. A disconnected account, a private window that was not captured, or deleted history can leave gaps. The report must say when the evidence does not cover a period.
Before scheduling, ask God for a small summary of one known day. Open its cited sources. This tells you whether the data needed for the report is present before you automate the larger job.
Write a report instruction with boundaries
Use this as a starting point, then replace the project and scope:
Prepare my weekly report for Project Cedar. Use saved activity and connected project notes from Monday 00:00 through Friday 17:00 in my local time. Group the result into completed outcomes, work in progress, blockers, and next actions. Include a source and date for each material claim. Do not infer completion from discussion. Mark missing coverage and conflicting evidence. Draft only; do not send it.
Ask for a short opening paragraph followed by a table. The table can contain outcome, evidence date, status, and next action. If the model cannot establish a status, “needs review” is a valid result.
Keep the report scoped to the intended audience. A client report should not accidentally include another client’s work just because it appeared on your screen that week.
Schedule the Friday draft
Open God settings, expand Scheduled tasks, and choose Add a scheduled task. Enter a name such as “Friday Cedar report,” put the instruction in What to do, and choose the weekly day and local time under When.
Choose Add, leave the routine enabled, and use Run now for a first check. The immediate run tests the task with the evidence currently available; it does not create future activity for the rest of the week.
Keep the computer awake and OGAD running at the scheduled time. Local sources can be processed by a local model after setup. Live account reads still need internet, and model work can wait in the local queue.
Review the draft before sharing
Check one claim in each section against its source. For a completed outcome, look for a completion record, accepted change, delivered file, or another concrete confirmation. For a blocker, check whether a later record already resolved it.
Pay attention to names and dates. Two projects may use the same short label. A request made this week may refer to work completed last week. Ask the model to keep the event date separate from the date on which you read about it.
Edit the final report for the audience, then send it through your normal process. Creating the draft in God does not prove that an email or document was published anywhere else.
Fix weak reports at the source
| Problem | Better next step |
|---|---|
| The report is generic | Name the project and ask for dated evidence |
| Too much unrelated work | Restrict the accounts, terms, and date range |
| Finished work appears open | Ask for later evidence that changes the status |
| An entire day is absent | Check capture and retention coverage |
| A claim has no source | Remove it or verify it before sharing |
Do not solve missing evidence by asking the model to sound more certain. Keep an explicit gap list. It tells you what to add manually and what to improve in the next week’s setup.
Make the next report easier
After the first report, use Edit and Save to keep the format that worked. Preserve the source requirement and the draft-only boundary. Change the reporting dates if your workweek differs from the example.
Set up one weekly report in OGAD and compare its first draft with your own notes. Once that check is useful, the routine can prepare the same structured starting point each week.