Hire an AI property repair and access reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A maintenance handover for the incoming lead, with overdue and time-critical tickets first
• Access limits for each ticket: the approved window, who approved it and what is still unconfirmed
• A list of overdue decisions, each with what must be decided and who decides
• A closure check for every ticket marked complete: closed with proof, or still open
• MISSING lines for anything your sources do not say, and a short record to start the next review from

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Repeating last review's list as if it were new.
• Treating a confident ticket note or a closed status as proof.
• Keeping tenant details you do not need.
• Describing installation as a running automation.
• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.

What a good result looks like

An example, not your task: A property manager goes on leave and a colleague takes over the open repairs.

• Handover. The note for the incoming lead. Urgent items and overdue tickets come first, then every open ticket with its status and owner.
• Access limits. For each visit, the approved window, who approved it and what is not yet confirmed. No entry is shown as allowed without a named approval.
• Overdue decisions. Each decision that was due, what must be decided, who decides and how long it has been open.
• Closure checks. For each ticket marked complete, what the contractor report or sign-off proves. Tickets without proof stay open.
• Changes since the last review. New tickets, changed tickets, tickets closed with proof and tickets missing from the export.
• MISSING lines and CHECKS MISSED. Every fact the sources did not give, and every check that could not run.

How the work is checked

• No ticket is closed without a closure record, and no entry is allowed without a recorded approval.
• Nothing in any file says a repair is done or a space is safe unless a source says so.
• No tenant name, phone number or access code appears in any file.
• Danger items are on the first line and point to the user's own rule.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read the last review. Loads the saved record if it belongs to this property group. On a first run it builds a baseline with you: the review date, who takes over and which emergency rule applies.
• Look for danger first. Scans tickets and notes for danger to a person or the building. If it finds any, the first line of the handover points to your emergency rule. It does not judge how serious the problem is.
• Sort the tickets. Marks each ticket new, changed, unchanged, closed with proof or missing from the export. A ticket missing from the export is unknown, not closed.
• Check access and closure. Lists the approved entry window and approver for each visit. For tickets marked complete, the Source note summariser reads the contractor report or sign-off and says what it proves.
• Write the handover. The Prepare a property maintenance handover workflow runs the Handover note writer, then the Executive action register keeper. Overdue decisions go first.
• Check and save. Checks that no entry permission, repair or safety clearance is invented. Saves the files, a run log and the new record, and keeps the old record.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id property-maintenance-evidence-review-assistant only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/property-maintenance-evidence-review-assistant/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Open maintenance tickets, each with an ID, a short location, a status and a date (from your ticket tool or a spreadsheet export)
• Access approvals and appointment windows (from tenant messages, contractor bookings or your calendar)
• The contractor and the owner for each ticket
• Your approved emergency escalation rule, with contact roles (from your handbook or lease pack)
• The name of the incoming property lead and the review date
• Closure records for tickets marked complete, such as a contractor report or sign-off (optional)
• Last review's record (optional, from the second run on)

Helpful context (optional)

• Your ticket tool export, as a spreadsheet or pasted list.
• Contractor reports and sign-offs for finished work.
• Your access rules, saying who may approve entry.

Tools and access

• A capable chat AI with file support: Keeps the record between reviews. In a plain chat tool you paste the record in each time.
• A chat AI that reads files: It reads a ticket export and your notes together. Nothing is booked or closed for you.
• Any good chat AI: Claude, ChatGPT and Gemini all handle a long source in one message. Claude takes the longest texts.

Functions and deliverables

• Property repair and access reviewer: Review open property repairs and planned visits. Get a handover with access gaps, late decisions and work still to verify.
  • A maintenance handover for the incoming lead, with overdue and time-critical tickets first
  • Access limits for each ticket: the approved window, who approved it and what is still unconfirmed
  • A list of overdue decisions, each with what must be decided and who decides
  • A closure check for every ticket marked complete: closed with proof, or still open
  • MISSING lines for anything your sources do not say, and a short record to start the next review from
• Property maintenance handover and action tracker: Share open repair tickets, access rules and appointments. Get a team handover, confirmed actions and overdue decisions.
  • Urgent jobs first, with who to call
  • Each live job with status, next step, contractor and appointment
  • Access notes for each property, with gaps marked
  • Overdue decisions and unresolved approvals, each with a ticket ID
  • Proposed changes kept as drafts, and a list of gaps
• Source note summariser: Paste an article, talk or chapter into this source note summariser. You get each claim, how well it is backed, the gaps and three quotes to keep.
  • Every claim with a quote and location, and the evidence behind each rated
  • The gaps and assumptions
  • What it adds to your question, three quotes to keep, and an 80-word summary
• Gorgias shift handover writer: Write a Gorgias shift handover note from your open tickets and those closed in the last four hours. You get urgent tickets, waiting replies, work in progress, recent fixes and blockers for the next agent.
  • A handover note with urgent tickets, waiting replies, work in progress and recent fixes
  • The last action and next step for each ticket
  • A list of blockers and open questions for a manager
  • Background notes so the next agent can start fast
  Source: Composio.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• A property manager goes on leave and a colleague takes over the open repairs.
• The ticket system says "complete" but nothing shows the contractor finished.
• A contractor visit needs tenant access that was agreed for a window that has now moved.
• It is review day and you want to know what changed since the last review.

Limits to check before starting

• A gas smell, fire, flooding, exposed wiring or anyone at risk right now. Follow your approved emergency rule and call the emergency contact in it. Use this agent afterwards to write it up.
• You want one quick note for the next person and no tracking. Use the Handover note writer.
• You want the agreed actions from a meeting turned into a list. Use the Action item tracker keeper.
• You need to know who covers a team while people are away. Use the Team absence coverage reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the agent to Claude, ChatGPT or Gemini with its helpers, the Prepare a property maintenance handover workflow and the Source note summariser. Or download the pack and attach it.
• Paste your ticket list and access notes. Say the review date and who is taking over. From the second review, paste last review's record too.
• Read the first section. Check that no ticket is marked done without a closure record, and that no entry is shown as allowed without a named approval.
• Fill in each MISSING line yourself, or ask the person who knows.
• Next, have the incoming lead sign off the handover. Then decide which overdue decisions go to the responsible role before any message or booking is made.
• Send any message and book any visit yourself. The agent only drafts.
• In a chat-only tool, copy the record it gives you and paste it in at the next review. With file access, it saves the record for you. Installing sets up no schedule, so you start each run.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/property-maintenance-evidence-review-assistant for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.