Industries · Property and construction

Faster property and construction admin, with valuation, legal and safety calls left to people

If your property, lettings, development or construction business is buried in documents, enquiries and reports, I pilot one bounded administrative workflow, such as enquiry triage, document extraction or site-report drafting, with source provenance on every output and a named person approving anything that leaves the business. Valuations, legal interpretation and safety decisions stay outside the AI's remit.

This is a good fit if…

  • Your team re-keys data from leases, tenancy agreements, contractor quotes, requests for information or site reports into your systems.
  • Enquiry inboxes for lettings, sales, maintenance or tenders are slow, and most answers already exist in your documents.
  • Monthly portfolio, project or client reporting takes days of manual collation.
  • You want AI used, but with firm red lines on valuations, legal interpretation and health-and-safety decisions.

Look elsewhere if…

  • You want automated valuations, pricing, tenant screening or contractor selection. I do not build those.
  • You are a property-technology company adding AI to your product. Use AI product delivery for B2B SaaS instead.
  • You need a general document-processing system across the business rather than one workflow pilot. Use document processing and reviewed reporting workflows.

What you get

Bounded administrative workflow pilot, document provenance and human decision gates

  • One administrative workflow piloted end to end with the staff who run it.
  • Every extracted field and drafted sentence traced to its source document and page.
  • Human decision gates at each point where judgement, money, legal meaning or safety is involved.
  • Cycle time and correction rate measured against the current process.
  • A runbook, a written list of red lines and a named internal owner.

How it runs

  1. 01

    Workflow and red lines

    We choose one workflow with clear volume and pain, and write down the decisions AI must never make in it, before any build.

  2. 02

    Provenance and gates design

    I design how each output links to its source, where a person must approve, and how personal data about tenants, occupiers or workers is handled.

  3. 03

    Pilot with staff

    The workflow runs on real documents in your environment, connected to your property or project management system where agreed, with corrections recorded.

  4. 04

    Decision and handover

    Results against the baseline, a go, revise or stop recommendation, and handover to the operations owner.

What needs to be in place

  • An operations owner for the workflow who can commit staff time to the pilot.
  • A representative sample of the documents or enquiries involved.
  • Access to the system of record, or an agreed export, for the workflow's data.
  • An agreed basis for handling personal data about tenants, occupiers, buyers or workers.

Not included

  • Valuations, pricing or investment advice.
  • Legal interpretation of leases, contracts, planning or building regulations.
  • Health-and-safety, building-safety or design decisions.
  • Automated decisions about tenants, applicants, buyers or contractors.
  • Regulated property advice of any kind.

The situation

Property and construction businesses run on documents. Leases, tenancy agreements, service-charge budgets, contractor quotes, variations, requests for information, site diaries, inspection reports and compliance certificates arrive in every format, and much of the administrative day is spent reading them, re-keying what matters and answering questions about them.

That makes the sector a strong candidate for AI-assisted administration, and a risky one. The same documents carry decisions with legal, financial and safety consequences: what a break clause means, what a building is worth, whether a defect is dangerous. A tool that drafts helpful answers will, if left unbounded, start drifting into those decisions.

The answer is to choose one administrative workflow, draw the red lines before building, and make every output traceable to its source.

What the work involves

Choosing the workflow. Good first candidates are high-volume, rule-bound and currently manual:

  • Extracting key dates and obligations from leases or contracts into your property management system, for a person to check.
  • Triage and draft replies for lettings, maintenance or tender enquiries, approved before sending.
  • Compiling monthly portfolio or project reports from site reports, budgets and trackers.
  • Logging and chasing requests for information and their responses on construction projects.

Writing the red lines. Before building, we list the decisions the workflow must never make: valuations, legal meaning, safety judgements, decisions about individual tenants or contractors. The system is designed so those questions are routed to a person, not answered.

Provenance. Every extracted field and every drafted sentence links back to the document, page and passage it came from. Checkers verify by clicking through, not by re-reading the whole file. Where the source is unclear or the scan unreadable, the field is flagged, not guessed.

Decision gates. Wherever an output could create a commitment, a cost or a safety consequence, a named person approves it, and the approval is recorded. Anything that mentions a hazard, defect or complaint is routed to the responsible manager.

My background in the sector is platform engineering for property portals: a modular widget platform for 99Acres and database and infrastructure scaling for PropTiger. The administrative workflow patterns draw on my book on everyday AI automation, which covers research, reporting and document workflows.

The signature deliverable, illustrated

Illustrative extract from a lease-abstraction pilot design, not taken from a client:

FieldExtracted by AISource linkDecision gateRed line
Lease start and end datesYesClause and pageProperty administrator checks—
Rent review dates and basisYesClause and pageProperty manager checksNo view on likely review outcome
Break clause conditionsYes, text onlyClause and pageProperty manager checksNo interpretation of validity; refer to counsel
Repair obligationsSummaryClause and pageProperty manager checksNo assessment of dilapidations liability

How acceptance is judged

The scope fixes the baseline (current time per document or enquiry, current error rate where known) and the pilot measures: time to complete, share of outputs corrected and the nature of corrections. The red lines are tested deliberately: questions that should be refused or routed are put to the system, and every one must be. The operations owner accepts or stops the pilot on that evidence.

Ownership and handover

The operations owner keeps the workflow, the red-line list and the decision gates. Staff who ran the pilot hold the runbook. Changes to red lines go through the owner, not through prompt edits.

When to choose something else

For a broader document-processing capability, see document processing and reviewed reporting workflows. For operations-team enablement beyond one workflow, see AI enablement for operations teams. Property-technology product companies should use AI product delivery for B2B SaaS. Other sectors are on the industries overview.

Questions buyers ask

Can AI summarise a lease for us?

It can extract defined fields (parties, dates, rent review dates, break clauses, repair obligations) with a link to the clause each came from, for a person to check. It should not tell you what a clause means for a dispute or a negotiation; that is legal interpretation and stays with your solicitor or in-house counsel.

What does a decision gate look like in practice?

A point in the workflow where nothing proceeds without a named person's approval, recorded in your system. For example, a drafted reply to a maintenance enquiry is approved before sending, and anything mentioning a safety issue is routed to the responsible manager rather than answered by the drafting tool at all.

Our documents are scanned PDFs and photos from site. Is that a problem?

It affects accuracy, which is why the pilot measures correction rates on your real documents rather than clean samples. Poor scans are flagged for manual handling rather than guessed at, and the provenance link lets the checker see the original page in one click.

Do you have property sector experience?

I built a modular widget platform for 99Acres and optimised database and server infrastructure for PropTiger during high growth. That was platform engineering for property portals, not AI administration, so the workflow knowledge in a pilot comes from your staff; my part is the engineering, provenance and controls.

What if the pilot does not save time?

Then the evidence shows why: poor document quality, too many exceptions, or reviewing taking as long as doing. Stop is a valid outcome, and it is cheaper to learn on one workflow than across the business. The recommendation may also point to a fix that is not AI at all, such as a better intake form.

Related engagements

Industries · Regulated operations

Regulated operations

We need useful AI workflows in a controlled environment. How do we translate agreed policies into technical and review controls?

You get:Policy-to-workflow control mapping, evidence capture and pilot approval dependencies

Industries · Retail and marketplaces

Retail and marketplaces

Which search, merchandising and operations problems should we tackle first, and how will we measure whether the change helps?

You get:Retail-specific opportunity brief, evaluated retrieval or recommendation pilot and rollout plan

AI delivery · Document workflows

Document workflows

We need to extract and summarise documents with provenance and exception review. What should a deployable workflow include?

You get:Document pipeline, source traceability, exception queue and evaluated sample set

Department enablement · Operations

Operations teams

Our team repeatedly reconciles information between systems. How can we change this workflow without losing exception handling?

You get:Process map, reviewed reconciliation pilot and exception-handling runbook

Industries · B2B SaaS

B2B SaaS

We need an AI feature that works across customer accounts without breaking tenant isolation or unit economics. What belongs in the delivery plan?

You get:Tenant-aware feature architecture, task evaluation and per-customer cost model

Industries · Professional services

Professional-services firms

How should our firm sequence AI adoption across client confidentiality, partner review and billable delivery work?

You get:Firm-level use-case portfolio, client boundary model and governed pilot sequence

Further reading

Describe what needs to work

A short, non-confidential description is enough to start. I read every brief personally and reply within two business days, including when the answer is that I am not the right fit.

Step 1 of 2 · The basics