A folder can look complete while a required deliverable is missing, outdated, or impossible to open. A Gemini-assisted audit should compare an approved brief with a verified file inventory. Its output is a deliverable inventory that distinguishes missing work from work that the reviewer simply cannot access.
Primary product documentation checked on 8 October 2026. The worked examples are fictional editorial examples, not claims of hands-on testing inside Gemini or Perplexity.
Turn the brief into acceptance records
Start with the approved brief, not with the folder contents. Extract each promised deliverable into a separate requirement: seven listing images, one mobile layout, editable source files, a final copy document, or a localization package. Include the required format, language, dimensions, version, and approval state. If the brief says “all campaign assets,” ask the owner to define that phrase before deciding what is missing.
Use stable requirement IDs. Two files with different names may satisfy the same requirement, while one combined PDF may contain several required deliverables. A simple filename comparison therefore produces false alarms. The requirement record should explain what acceptable evidence looks like, such as a final approved Spanish image exported at the specified dimensions. Preserve the brief section that establishes the obligation.
Verify the inventory before asking Gemini
Record every file in the agreed folder scope, including nested folders, shortcuts, and files shared from another owner. Google documents that Gemini responses for folders may omit files. A generated folder summary is therefore not a complete inventory. Compare it with the visible file list or an authorized exported manifest. Note inaccessible files instead of treating them as absent.
Attach or select the approved brief and the inventory as explicit sources. If a source cannot be read, record that failure. Ask Gemini to report which requirements it assessed and which files supported each assessment. Do not rely on a statement that it reviewed “the folder” when the output gives no coverage list. The audit concerns a defined set of records at a defined time.
Map requirements to evidence
Prompt Gemini to create one row per requirement, with requirement ID, expected deliverable, candidate file, evidence location, format check, approval evidence, and status. Useful statuses include satisfied, missing candidate, wrong version, wrong format, approval missing, and access unresolved. Keep the candidate match separate from the final judgment. A plausible file title does not prove that its content meets the brief.
Inspect grouped outputs carefully. If seven images are requested and one PDF is supplied, count the relevant pages and inspect what each page represents. If editable files are required, flattened exports alone are insufficient. If the same asset is required in two languages, an English original does not satisfy the second-language requirement. Explain the specific mismatch so the owner can fix it without interpreting a vague “incomplete” label.
Work through a fictional campaign audit
Imagine a brief requiring six product images, a brand-story panel, and layered source files. The folder contains six PNGs, an old brand-story PDF, and a ZIP that the reviewer cannot open. Gemini initially identifies eight files and calls the folder complete. The corrected inventory records the six images as candidate matches, the brand-story panel as wrong version, and the ZIP as access unresolved.
The next actions differ. The designer should provide the approved brand-story revision. The reviewer should obtain access to the ZIP and inspect whether it contains the layered sources. Neither task should be described as “create missing files” yet. That distinction prevents unnecessary rework and keeps access problems from becoming accusations that a colleague failed to deliver.
Publish an actionable discrepancy list
Sort the final inventory by delivery risk rather than by filename. Put missing contractual deliverables and unusable formats first. Include the affected requirement, the evidence checked, the precise correction, the responsible owner if documented, and the next review date. Keep unresolved ownership explicit. Gemini may suggest a likely owner, but that suggestion is not an approved assignment.
Save the reviewed inventory beside the brief and the source manifest. If files arrive later, update only the affected requirement records and preserve the original audit date. A folder audit is a snapshot, not a permanent guarantee of completeness. Repeat the format and approval checks for replacement files instead of marking a row satisfied merely because its filename now exists.
Validate the evidence and hand over the result
Run the review in two passes. First, check the source records without reading the generated conclusions. Select a small but representative sample: a clear record, a contradictory record, an incomplete record, and a record that changed after the review began. Write down the expected treatment of each. This gives you a reference for judging the output instead of accepting a plausible narrative because it looks organized.
Then inspect the generated result against those expectations. Open every source supporting a consequential conclusion. Check the surrounding paragraph, the relevant table heading, and any qualifying note. A link to the correct document is only the beginning of verification. The document may support a narrower claim, describe a different version, or use a different unit. Record a correction beside the affected item rather than quietly changing its meaning.
Count the inputs and outputs where a one-to-one relationship is expected. Explain every omitted record and every merged record. When several source items become one conclusion, retain the individual references so the reviewer can reverse that grouping. When one source item produces several actions, preserve the connection so a later source correction can update all affected actions. Never interpret an empty output as evidence that there are no problems until you have checked source coverage.
Keep proposed wording separate from approved wording. An AI system can suggest how to express a finding, but the source owner still needs to confirm the underlying facts when records disagree. Use explicit states such as supported, disputed, missing evidence, and awaiting owner confirmation. Avoid a single confidence score that disguises those different reasons for uncertainty. A disputed statement with two strong sources needs a different next step from a statement with no accessible source.
Before handover, ask a colleague to use the result without your explanation. Can they locate the original evidence, identify unresolved items, and understand what changed since the last version? Fix the places where they need to guess. Save the source manifest, the prompt, the reviewed result, and the correction history together. A useful deliverable should remain understandable after the conversation that produced it has ended, and it should make the next review cheaper because the evidence trail is still intact.
Frequently asked questions
Can Gemini prove a folder is complete?
Not from a summary alone. Verify the file inventory independently, then inspect the evidence for each requirement. Folder coverage and content compliance are separate checks.
Does an inaccessible file count as missing?
Use access unresolved. A file may exist and satisfy the requirement, but the reviewer cannot establish that until authorized access is restored and its content is inspected.
Should similarly named files be merged?
Only after examining their content, language, format, and version. Similar names can hide different deliverables or obsolete copies, so retain the original file references during matching.
What if the brief is ambiguous?
Create a clarification item with the exact phrase and the acceptance detail needed. Do not let Gemini invent dimensions, languages, file counts, or approval requirements.
When should the audit be repeated?
Repeat affected checks after additions, replacements, or brief changes. Preserve the earlier findings so the team can distinguish newly delivered work from corrected requirements.
