Hire an AI construction defect handover planner

Everything it can hand back

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

• A defect register: ID, location, priority, owner, due date, evidence needed and status
• A list of the closure evidence still missing for each open defect
• A handover note for the contractor or facilities team, with access rules and dependencies
• A list of signoffs still outstanding
• A flag at the top for any record that mentions an immediate danger

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

• Closing a defect because the contractor said it was done.
• Rating a defect's priority yourself.
• Judging whether something is safe.
• Putting a defect in the register that was never accepted.
• 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 building or fit-out is near handover and the snag list is long.

• Danger flags. Any record that mentions an immediate danger, listed first with the person to pass it to.
• Defect register. Each defect with ID, location, priority, owner, due date, evidence needed, status and source ID.
• Open items. Defects still open, the closure evidence missing for each and who must sign.
• Handover note. Open items by area with access rules, dependencies and contacts, for the person taking over.
• Signoffs. Each approval still needed and from whom, and which are given.
• MISSING and CHECKS MISSED. Gaps such as an undefined priority, and any check that could not run.

How the work is checked

• A defect closes only with the required evidence and an authorized signoff. This is not an engineering or safety certification.
• Every register row traces to an inspection source ID.
• Priority comes only from the user's definitions.
• Every fact, figure and date traces to a source or is labeled as an assumption.
• 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

• Executive action register keeper. Reads the inspection records and lists each accepted defect with its inspection source ID, location, owner, due date and the evidence needed to close it. Uses only your priority definitions. Hands step 2 the open defects and the signoffs still missing. Check before moving on: no defect is closed without evidence and a named signoff.
• Handover note writer. Writes the handover note for the contractor or facilities team: where each open item is, access rules, what depends on what and the signoffs not yet given. A promised date is not treated as proof the work is done. Hand-back check: every open item in the note appears in the register.

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 prepare-a-construction-defects-handover 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/prepare-a-construction-defects-handover/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

• Inspection records with defect IDs (from the inspector's report or your snag list)
• Photos for each defect, if you have them
• Your approved priority definitions, such as what counts as high or low
• The remedial work the contractor accepted, with owners and promised dates
• The handover date and who receives the building

Helpful context (optional)

• A named person who gives final signoff.
• The contractor's own list, so you can match IDs.

Tools and access

• A chat AI that reads files: It can read inspection reports and a photo list, so each row cites its source ID.
• A spreadsheet: The register is a table. Paste it into a sheet for the contractor to update.
• Any good chat AI: A one-message note works in any strong chat AI.

Functions and deliverables

• Construction defect handover planner: Share inspection records, defect photos and accepted repair actions. Get a defect register, repair handover and missing signoff list.
  • A defect register: ID, location, priority, owner, due date, evidence needed and status
  • A list of the closure evidence still missing for each open defect
  • A handover note for the contractor or facilities team, with access rules and dependencies
  • A list of signoffs still outstanding
  • A flag at the top for any record that mentions an immediate danger
• Action item tracker: Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.
  • action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id
  • clarifications.md
  • proposed-task-changes.md
• Handover note writer: Turn a brain dump into a handover note. The person covering your work sees what breaks first and what is due, and can act on day one.
  • Time bombs first, each with a date and an action
  • What is due, live work with next steps, and where things live
  • The people and how to deal with them, what to leave alone, how to reach you
• 90-day action plan builder: Share an approved decision, owners and start date. Get a 12-week action plan with milestones, check-ins, dependencies and risks.
  • A 12-week milestone table
  • A named owner for each stream
  • A check-in schedule
  • A dependency list
  • A risk list with fixes
  Source: Alireza Rezvani.
• 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 building or fit-out is near handover and the snag list is long.
• A contractor says defects are fixed and you need proof, not a promise.
• Facilities is taking over and needs to know what is still open and where.
• Inspection notes, photos and emails sit in different places and nobody has one list.

Limits to check before starting

• You need a safety inspection or a certificate. Use the engineer's signed report. This workflow tracks and does not certify.
• A defect needs a price or a change to the contract. Use the Construction change decision brief writer workflow.
• You only want actions pulled from meeting notes. Use the Action item tracker.
• The building is already running and you are handing over maintenance. Use the Property maintenance handover and action tracker workflow.
• The contractor's own register already tracks closure evidence. Use that one.

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.

• Open Claude, ChatGPT or Gemini. Pick one that can read files, since inspection reports and photo lists are often attachments.
• Add the workflow pack. Attach the inspection records, your priority definitions, the accepted remedial commitments and the handover date.
• After step 1, check that each defect ID matches the inspection report. Check that no row is marked closed without evidence and a named signoff.
• After step 2, read the handover note as the person who receives the keys. Check the access rules and which items depend on others.
• Fill every MISSING line before you hand over. A qualified person must sign off safety items. Pass any danger flag to the site manager first.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/prepare-a-construction-defects-handover 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.