Find generated files in GuroAssist

Get ready

Check the starting point

These are the minimum conditions for the workflow to make sense.

Steps

Complete the task in order

Review choice points, save or preview behavior, and any stop condition before continuing.

1. View full size

   Step 1

   Open Files and let the history load

   Choose Files in the main navigation. Confirm the workspace shows local generated-output history for this device before searching or filtering.

   Expected result: Files is the device-local index for generated outputs.

2. View full size

   Step 2

   Search and filter without assuming a missing file was deleted

   Use the search box and available type, source, class, or date filters. Clear filters when nothing appears, because an empty filtered result is not proof that the local file is gone.

   Expected result: Search and filters narrow the local history before selection.

3. View full size

   Step 3

   Select the exact output and read its details

   Select one row and verify its name, output type, source tool, class or subject context, created time, and local path. Similar filenames can represent different classes, terms, versions, or drafts.

   Expected result: The detail pane distinguishes the intended file from similarly named outputs.

4. View full size

   Step 4

   Resolve a file that is missing from disk

   If the selected row says Missing from disk, do not keep retrying Open or Preview. Check the displayed filename and saved location, use the source tool to regenerate when appropriate, or restore the file from a trusted backup; the local history row can remain after an external move or deletion.

   Expected result: The health state explains why the history row exists but the actual file cannot be opened.

5. View full size

   Step 5

   Inspect content and formatting before use

   Review every PDF page, Word page, spreadsheet sheet, slide, image, or packet member that will be used. Check learner and class identity, dates, official-readiness labels, page breaks, formulas, answer leakage, and clipping.

   Expected result: Opening the actual file reveals page flow and formatting that the Files row alone cannot prove.

6. View full size

   Step 6

   Inspect packet members and regenerate from the source

   For a bundle or packet, open every member rather than checking only the first file. If identity, layout, content, or answer separation is wrong, return to the source named in Files, correct the source, and generate a new output; do not rename an incorrect file to make it appear current.

   Expected result: Packet review includes every included document before the teacher returns to the source tool to correct it.

File status

Understand what each output label means

The label describes readiness inside GuroAssist; it does not create outside approval.

Local

Saved on this device for teacher use.

Draft

Still needs teacher review or editing.

Final

The teacher marked the local work final after review.

Official-ready

GuroAssist readiness checks passed; this is not DepEd approval or submission.

Review-only

Useful for checking, but not an official-ready output.

Blocked

Stop and resolve the displayed readiness issue first.

Finish

Verify the result

Do not treat a saved screen or generated filename as proof that the work is ready.