Start here

Paste your maintenance notes where this prompt says to. Keep them as-is: equipment names, asset tags, dates, intervals (days / weeks / months / years), owner or vendor names, and any note about skipped or late service.

You do not need to organize anything first. Mixed order and rough wording are fine.

1. Copy the complete prompt below into one message.
2. Paste your raw notes directly after it, in the same message.
3. Send it to an ordinary AI chat that accepts text.

Then check the output against these points:

• One table, with the columns in the order given in the prompt (Equipment, Maintenance task, Interval stated, Last done, Next due, Basis for next due, Owner / vendor, Confidence, Needs human confirmation, Notes).
• Every next-due date has a stated interval behind it; nothing is calculated from an invented last-done date.
• Rows with conflicts or missing key fields are blank on the uncertain field and marked for human confirmation.
• A "Needs confirmation" section with one question per flagged row, and a "What I did not assume" section.

What this prompt does

This is a reusable office prompt for turning rough maintenance notes into a draft schedule table. It prepares a table for your review only.

It does not send reminders, book appointments, notify anyone, or change any calendar. Those steps stay with you.

Common household and small-business uses:

Missing inputs and how they are handled

If a note lacks a last-done date, that field stays blank. If an interval has no clear start point ("quarterly", "as needed"), the next-due date stays blank and the row is marked for confirmation.

If your notes are too thin to build any row, the prompt tells you which fields are missing instead of inventing a table.

Privacy and boundaries

The prompt keeps working only from the material you paste. Notes can contain vendor contacts and room or vehicle identifiers, so remove anything you would not want in that chat tool, and paste only what the table needs.

It does not give safety, legal, warranty or compliance advice. A safety-looking note is restated in the Notes column and flagged for confirmation. It does not recommend intervals you did not state, estimate costs, or claim any reminder was set up.

The worked example inside the prompt is labelled fictional and shows output shape only.

FAQ

Do I need to install anything? No. Paste the prompt and your notes into any AI chat that accepts text.

The output has next due blank on a row I expected a date for. That happens when the interval wording was ambiguous or the last-done date was missing or conflicting. Use the "Needs confirmation" questions to fill those from real records yourself after the review.

Verification note

Source reviewed; runtime not tested. This guide documents how to use the prompt; it makes no claim that the prompt was executed or that any reminder, calendar entry or message was created.

Complete reusable prompt

Equipment Maintenance Schedule Table Builder

You are helping me turn rough maintenance notes into a clean scheduling table. This prompt only prepares a table for my review. It does not send reminders, book appointments, notify anyone, or change any calendar.

What I will provide

Paste your raw material after this prompt. It may include, in any mix of order or wording:

• Equipment names and identifiers (for example, a room number or asset tag)
• Maintenance dates already recorded, and which task each belongs to
• Maintenance intervals stated in days, weeks, months or years
• Due dates someone mentioned, notes about skipped or late service, and whose responsibility each item is
• Contacts or vendor names if they appear in the notes

Your task

1. Read only the material I provided. Do not add equipment, dates, intervals, vendors or owners that are not present.
2. Build one table with exactly these columns, in this order:
   • Equipment
   • Maintenance task
   • Interval stated (copy the wording I used, with unit)
   • Last done (date, or blank)
   • Next due (date, or blank)
   • Basis for next due (say "calculated from last done plus stated interval" or "stated directly in the notes" or leave blank)
   • Owner / vendor (only if I named one)
   • Confidence (High, Medium or Low, using the rules below)
   • Needs human confirmation (Yes or No)
   • Notes (short, factual)
3. Group rows by equipment. If one equipment item has several tasks, give each task its own row.
4. Sort so that rows with a usable next-due date come first, earliest first. Rows with a blank next-due date go last, in the order they appear in my notes.

Rules for dates and blanks

• If I gave a last-done date and a clear interval, you may state a next-due date. Show it as an exact date if possible, and state the basis in the basis column. If the interval wording is ambiguous (for example "quarterly" without a start point, or "as needed"), leave next due blank and mark Needs human confirmation as Yes.
• Never invent a last-done date. If it is missing, leave it blank.
• Never guess month lengths or leap years silently. If your calculation depends on an assumption about month length, note it in the Notes column.
• If two dates or intervals conflict, do not pick one. Leave last done or next due blank, set Confidence to Low, set Needs human confirmation to Yes, and describe the conflict briefly in Notes.
• If the same equipment and task appears twice with different dates, merge into one row only if the dates agree. Otherwise keep one row and flag the discrepancy.

Confidence rules

• High: a last-done date and a clear interval unit are both present and the calculation is unambiguous.
• Medium: the dates are present but the interval wording is loose, or the equipment name may match another row.
• Low: any conflict, missing essential field, or unclear ownership.

Output format

1. One short paragraph: what I gave you and anything you could not use.
2. The table in Markdown, following the column order above.
3. A section called "Needs confirmation" listing every row marked Yes, with a one-line question per row.
4. A section called "What I did not assume" listing anything you deliberately left blank and why.

Worked example (fictional, for shape only)

Input notes: "Meeting room projector, bulb replaced 03 Feb 2025, change every 6 months, done by A. Patel. Kitchen fridge filter, change every 90 days, last change unknown. Van 12, oil service, every 12 months, last service 14 Nov 2024, also recorded as 14 Dec 2024 by mistake."

Illustrative output shape: three rows. The projector row shows last done 03 Feb 2025, next due calculated as 03 Aug 2025, basis "calculated from last done plus stated interval", confidence High, needs confirmation No. The fridge filter row shows last done blank, next due blank, confidence Low, needs confirmation Yes, with a question about when it was last changed. The van row shows last done blank because of the conflicting dates, next due blank, confidence Low, needs confirmation Yes, with a question about which service date is correct.

Checks to run before you answer

• Every row traces to wording in my notes. If you cannot point to the source phrase, leave the field blank.
• No next-due date appears without a stated interval or a directly stated due date.
• Every row with a missing or conflicting key field is marked Needs human confirmation = Yes and has a matching question in the "Needs confirmation" section.
• The number of rows matches the number of distinct equipment-and-task pairs you found.
• No reminders, notifications, calendar changes, purchases or messages are described as done or scheduled. Everything here is a draft table for me to review.

Boundaries

• Do not give safety, legal, warranty or compliance advice. If a note looks like a safety concern, just restate it in Notes and mark the row for confirmation.
• Do not recommend a maintenance interval I did not state.
• Do not estimate costs or lead times.
• If my notes are too thin to build any row, say so and list exactly which fields are missing instead of inventing a table.

What I will do with the result

I will review the "Needs confirmation" questions, fill the blanks from real records, and then set up any reminders in my own tools myself.

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.