How to Turn a Maintenance Ticket Export Into a Daily Worklist With AI

An open-ticket list is not the same thing as a worklist. Most exports are too noisy to hand directly to a maintenance lead. They include duplicates, stale notes, missing priorities, and a mixture of urgent, routine, and waiting-on-vendor tasks. This workflow is for property managers and maintenance coordinators who already export their ticket list and need a cleaner daily action sheet.

Warning: This workflow creates drafts, summaries, checklists, and briefing documents for review. Double-check unit numbers, dates, conditions, vendor scope, resident details, owner details, and any promised next steps before you use any output. Do not use AI output as the final signed inspection record, an official notice, a legal document, or the only record of property condition.

Problem this solves and who it is for

Use this when your property management system can export open maintenance requests, but the raw export is too messy to use as the team's daily plan. The goal is not to replace your system. The goal is to produce a shorter, more useful worklist for today's coordination.

Prerequisites

• Access to your maintenance ticket export
• Gemini on desktop or mobile
• A spreadsheet file in CSV or XLSX format
• A basic understanding of your internal priority rules
• Permission to handle the ticket data you upload

How to capture or gather the source material

Export only the fields you actually need. A strong starting export usually includes:

• ticket ID
• property or building
• unit
• issue title or short description
• created date
• current status
• assigned person or vendor
• priority if available
• category or trade if available
• last update

If your system exports much more than that, trim it before upload. Remove columns that do not help today's plan. This reduces noise and also limits how much sensitive resident information enters the workflow.

If unit access notes or phone numbers are included, consider removing those before upload and handling them separately in your normal system.

Step-by-step workflow

1. Clean the export once before you upload it

Open the CSV or spreadsheet and do one quick pass:

• remove closed tickets
• remove obvious duplicates
• keep the header row clear
• convert long internal notes into shorter summary text if needed
• make sure created dates are consistent

This is not a deep spreadsheet cleanup project. You are just making the file usable for prioritization.

2. Upload the file to Gemini

Gemini can analyze spreadsheet uploads and is a good fit for a daily triage pass.

Desktop web app path

1. Open Gemini in your browser.
2. Click Add files and upload the CSV or XLSX.
3. Paste the JSON prompt below.
4. Ask for a daily worklist view rather than a broad summary.

Mobile app path

1. Save the export locally on your phone.
2. Open the Gemini mobile app.
3. Tap Add files and choose Files to attach the export.
4. On iPhone, if the file started as a Google file inside the Files app, Gemini may convert it to PDF for analysis, so it is usually cleaner to export the sheet as CSV first.
5. Submit the same prompt and review the result on the phone, then save the final version where your team can use it.

{
  "task": "Turn this maintenance ticket export into a daily worklist for property operations.",
  "date_context": "[today's date or target work date]",
  "sorting_logic": [
    "Urgent health or active damage issues first",
    "Tasks that can be bundled by building or unit cluster next",
    "Routine tasks after urgent tasks",
    "Tickets waiting on vendor, parts, or resident access should be listed separately"
  ],
  "required_columns_to_use_if_present": [
    "ticket_id",
    "property",
    "unit",
    "issue_title",
    "created_date",
    "priority",
    "status",
    "assigned_to",
    "category"
  ],
  "rules": [
    "Use only the uploaded file.",
    "Do not invent missing priorities.",
    "If priority is missing, infer only a tentative working priority from the ticket text and label it tentative.",
    "Group tasks by urgency and then by building or unit when practical.",
    "Create a separate section for blocked or waiting items."
  ],
  "output_request": "Return a clean daily worklist with sections for Do Today, Bundle If Nearby, Waiting or Blocked, and Needs Manager Review."
}

3. Tighten the output for real-world use

The first pass is usually too verbose. Ask for a cleaner operational version.

{
  "task": "Rewrite the draft into a shorter daily worklist for a maintenance lead.",
  "requirements": [
    "Use one line per task.",
    "Keep each line concise.",
    "Include ticket ID, unit, issue, and next action.",
    "Do not repeat long notes.",
    "Mark any tentative priority clearly."
  ],
  "output_request": "Return a shorter version that can be pasted into email, chat, or a shared daily planning doc."
}

4. Add the missing human context

This is where you correct anything AI cannot know well from the export alone:

• actual resident access constraints
• whether a waiting item suddenly became urgent
• whether a vendor is already onsite
• whether two units can be bundled because they are in the same building
• whether a manager wants one unit handled before another for leasing reasons

5. Save the final worklist as a dated artifact

Save the worklist with the date in the filename. Do not overwrite yesterday's plan. That makes it easier to review what was planned versus what actually moved.

Tool-specific instructions

Desktop is usually the best path for spreadsheet uploads because you can quickly inspect the export, trim columns, and compare the AI output with the original file side by side. Mobile is still usable when you already have the export on your phone and need a fast plan away from your desk.

Quality checks

Before you send the worklist, verify:

• urgent tickets are still actually urgent
• blocked items are not mixed into today's execution list
• no one-line task dropped the core issue description
• unit numbers and ticket IDs match the file
• tentative priorities are marked as tentative

Common failure modes and fixes

The worklist is still too long
Ask for a version capped to today's top items only.

The model over-prioritizes old routine tickets
Tell it to separate age from actual urgency.

Blocked tickets are cluttering the list
Create a separate waiting section and remove them from active work.

The uploaded spreadsheet is hard to parse
Re-export as CSV and simplify the header names.

The list includes too much private resident detail
Trim those columns before upload and regenerate the worklist.

Sources Checked

• Google Gemini Apps Help, "Upload & analyze files in Gemini Apps - Computer." Accessed 2026-03-21. https://support.google.com/gemini/answer/14903178?co=GENIE.Platform%3DDesktop&hl=en
• Google Gemini Apps Help, "Upload & analyze files in Gemini Apps - iPhone & iPad." Accessed 2026-03-21. https://support.google.com/gemini/answer/14903178?co=GENIE.Platform%3DiOS&hl=en
• Unsplash License. Accessed 2026-03-21. https://unsplash.com/license
• Unsplash Help Center, "Can I use Unsplash images for personal or commercial projects?" Accessed 2026-03-21. https://help.unsplash.com/en/articles/2612315-can-i-use-unsplash-images-for-personal-or-commercial-projects

Quarterly Refresh Flag

Review by 2026-06-19 to confirm Gemini spreadsheet upload behavior, iPhone local-file handling, and any changes to spreadsheet analysis support in Gemini.