A trip notice, a sports reminder, and a class update can each contain a small task. Together, they become easy to lose track of.

OGAD (Off Grid AI Desktop) can help you turn saved school notices into a checklist on your computer. Use a local text model to extract dates, requested items, and actions, then verify them against the notices. After setup, the review can run offline without uploading the documents to a cloud AI provider.

Download OGAD

Desktop releases

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 support@offgridmobileai.co, join our Slack community, or talk to us on Reddit.

The useful result is a short list your family can check: what needs doing, which notice it came from, and what is still unclear. It should reduce the work of collecting details while keeping you responsible for confirming them.

What should a family checklist contain?

Keep the action, the child or class it applies to, the stated date, and the source. A notice may describe an event date and a separate response deadline. Those need different checklist entries.

Suppose one notice asks for a trip response by Monday and another asks children to bring sports shoes on Thursday. A third describes an activity for one year group only.

A useful table would include:

Field	What to record
Action	Return a form, prepare an item, or confirm information
Applies to	The child, class, or year group stated in the notice
Due date	The date for the action, if stated
Event date	The date the activity happens
Source	The notice or message behind the entry

If a date is absent, leave it absent. A model should not guess that “next week” means a particular date without the message date and context.

What do you need before starting?

Install OGAD and download a local text model that fits your computer. Save the notices as readable local files or copy their text into a document. Complete app and model downloads before working without internet.

The procedure uses the free core desktop app on supported Mac and Windows computers. Linux packages are available in release 0.0.54-beta.108 as a beta.

Use TXT, Markdown, DOCX, or text PDFs. If a notice is a scanned image, prepare checked text first. Keep the original notice for dates, tables, and details that extraction may miss.

You can use neutral labels such as “Year 4” in a working copy when a child’s full name is unnecessary. Include only the information needed to understand the requested action.

How do you create the first list?

Start with a few current notices. Attach them to a new chat, check the extracted text, and ask the model to separate actions from general information.

1. Select a downloaded local model in Models > Text.
2. Open a new chat and choose + > Attach files.
3. Add the saved notices.
4. Wait for processing and inspect the text previews.
5. Check the dates and group labels against the originals.

The file-processing implementation extracts document text for the model. It does not connect automatically to a school app, verify a timetable, or know whether your family already completed an action.

Ask:

Make a family checklist from these notices. Separate requested actions from information only. Include who each item applies to, the stated response deadline, the event date, and the source filename. Preserve dates exactly as written. Mark missing or ambiguous details instead of guessing.

How do you check dates and overlapping notices?

Read every date in the output against its source. Check whether it refers to the event, a payment request, a form response, or a preparation step. Similar dates can belong to different actions.

If a later notice changes an earlier one, keep the revision visible. Ask the model to show both passages rather than silently choosing a date.

For example:

Do any notices appear to update the same event? Show the source dates and the wording that changed. Do not assume the latest file is an official correction unless the text establishes that.

Then confirm the current detail from the school’s notice or normal communication channel. The model cannot know that an event was cancelled elsewhere unless that information is in the material you supplied.

How should you divide tasks within the family?

Assign tasks yourself after reviewing the list. The model can format a blank owner column, but it does not know who is available or who agreed to do something.

You might divide the checked list into:

• Responses to send.
• Items to prepare.
• Dates to add to your own calendar.
• Questions to ask the school.

Keep completed items marked in the document or task tool your family already uses. If you later ask OGAD for an updated list, supply those status changes rather than expecting it to know what happened offline.

The workflow produces text. It does not send forms, make payments, add calendar events, or confirm attendance.

What if the notices contain detailed instructions?

Preserve important wording and read the original. A checklist should point you to the instruction when shortening it could remove a condition.

For a trip notice, the useful entry may be “Read the equipment list and prepare the specified items,” with the source beside it. Ask the model to quote any passage whose exact wording matters instead of paraphrasing everything.

If the notice contains health, safety, or permission information, use the school’s actual guidance and contact the relevant person for clarification. The checklist is an organising aid, not an authority on what your child should do.

How do you keep the list manageable?

Work with the current period and archive old notices separately. A large mixed collection makes it easier for a past event to appear relevant again.

For repeated lookup, create a project with Projects > New project, then add current checked files under Knowledge & settings > Knowledge base > Add files. Wait for indexing and open Chats > New chat inside the project.

Project search retrieves selected passages. Use a direct checked checklist for deadline tracking rather than relying on a broad question to recover every action each time.

Problem	Next check
The wrong class appears	Compare the group label with the source
A relative date becomes a guessed date	Keep the original wording and confirm it
An old notice returns	Check the source date and current file set
An action is marked complete	Check whether you supplied that status
The list omits a form	Review each notice once against the final checklist

Try this week’s notices

Download OGAD and add a small set of current notices. Create the list, verify the dates, and mark the tasks your family actually needs to do.

Keep the model local for processing after setup. Sharing the checklist or using school services has separate network requirements. The first useful result is a checked list you can use without rereading every message.