Archaeological Excavation Services · Planning conditions, WSIs, and heritage consent

AI HER Search and Monument Record Consultation for Archaeologists

AI-assisted HER and monument record consultation integrates planning data streams to streamline heritage approvals and mitigate risks across the site lifecycle.

By Suhas BhairavUpdated 4 min read

AssetGeophysical survey, remote sensing, and prospection
AssetTrenches, sections, features, and excavation methods
AssetContext sheets, plans, survey, and photogrammetry
AssetFinds, environmental samples, and on-site processing
AssetPlant, spoil, shoring, and site equipment
AssetSite welfare, fencing, dewatering, and set-up
AssetTrench safety, buried services, contamination, and UXO
BusinessPlanning conditions, WSIs, and heritage consent
BusinessPost-excavation analysis, reporting, and archiving
BusinessTendering, clients, and project delivery
BusinessField teams, training, and professional standards
1Context sheet binder2Single context recording form3Harris matrix board4Consultation log binder5Georeferenced map overlay6Archive deposition folder

The short answer

HER search and monument record consultation for archaeologists uses AI to read HER searches, monument records, event records, and grey literature, decides on consultation scope and mapping constraints, and stays with people through final reporting, and archive deposition. It also records decision rationales, timestamps actions, and flags upcoming consent deadlines for sign-off by the planning archaeologist.

Who it's for: Project managers, planning archaeologists, heritage consultants, and site supervisors.

Why it matters

Without AI, inconsistencies in records and missed consultation requirements create delays, conflicting guidance, and backlogs in post-excavation analysis and archive deposition.

From design to safety

  1. Design

    AI scopes planning condition checks

    The AI reads HER entries, monument records, event records, and grey literature to flag required consultations, identify restrictions, and suggest mapping layers for the WSI and trench designs.

    • Context sheet binder
    • Single context recording form
    • Harris matrix board
  2. Build

    Mapping and consultation integration

    During build, it cross-references site plans with HER overlays and monument data, updating mapping and flagging areas needing roadside notices or specific liaison with stakeholders' input and approvals.

    • Georeferenced map overlay
    • Consultation log binder
    • Archive deposition folder
  3. Operation

    Dynamic discovery tracking

    In operation, AI monitors new event records and finds-based updates, adjusting watch lists and notifying the team of emerging conditions in real time promptly.

    • Context sheet binder
    • Georeferenced map overlay
    • Consultation log binder
  4. Maintenance

    Record maintenance and retrieval

    AI ensures post-excavation assessments align with HER data, updates the archive with new citations, and maintains versioned monument record mappings, and facilitates future reliability checks.

    • Archive deposition folder
    • Harris matrix board
    • Single context recording form
  5. Safety

    Regulatory compliance checks

    It validates that every design and site change adheres to planning conditions and CIfA standards, generating compliance reports for sign-off by the qualified person and audit trails.

    • Consultation log binder
    • Archive deposition folder
    • Georeferenced map overlay

Part by part

  1. 1

    Context sheet binder

    Watch for
    Missing context identifiers or mismatched context numbers across sheets and plans.
    AI action
    Detect numbering conflicts and trigger reconciliation workflow automatically to records.
  2. 2

    Single context recording form

    Watch for
    Inconsistent context types or missing date stamps on forms during field capture.
    AI action
    Flag anomalies and auto-append validation notes to records in the form.
  3. 3

    Harris matrix board

    Watch for
    Discrepancies between plotted context relationships and planned trench sections and sections.
    AI action
    Suggest corrections to stratigraphic linking within the matrix.
  4. 4

    Consultation log binder

    Watch for
    Unlogged stakeholder contact or unanswered consultation requests.
    AI action
    Generate unresolved-item alerts and assign follow-up tasks to planning archaeologist.
  5. 5

    Georeferenced map overlay

    Watch for
    Outdated layer versus current grid coordinates or control points.
    AI action
    Prompt update with latest geospatial fixes to maps and plans.
  6. 6

    Archive deposition folder

    Watch for
    Missing provenance data or incomplete archive metadata.
    AI action
    Trigger completeness check and metadata prompts to archive records.

Worked example

HER and Monument Record Integration at 12.7 ha coastal development

Illustrative scenario with sample data.

A coastal development on scrubland triggers planning consent; AI integrates HER searches, monument records, event data, and grey literature to map constraints and inform liaison scheduling with the planning authority and curator.

Signal in

HerSearchDate: 2026-05-01; MonumentRecordID: MR-085; EventRecords: ER-23, ER-27; GreyLiteratureLinks: GL-112; ConsultationRequests: CR-46; GridRef: NZ123405; WSI: draft; DesignNotes: coastal risk; ExistingSiteContext: shoreline retreat

System out

AI-generated consultation scope and mapping plan with condition dependencies; mapping layers added to the WSI plan; liaison schedule proposed; upcoming consent deadlines logged.

Human sign-off: Project manager reviews the AI-produced consultation scope and mapping plan, verifies with the HER adviser, and signs off before planning authority submission.

How to roll it out

  1. Phase 1

    Weeks 1 to 2: Baseline

    Establish data feeds, schema, and AI thresholds; align with HER and monument record databases; prepare initial mapping overlays.

  2. Phase 2

    Weeks 3 to 6: Integration

    Integrate AI outputs with WSI and risk assessments; implement consultation tracking and document versioning.

  3. Phase 3

    Weeks 7 and beyond: Operational

    Maintain live monitoring, automate reporting to HER, and support post-excavation archive deposition.

Where people stay in charge

  • All planning-condition decisions remain with a qualified person or planning archaeologist responsible for sign-off and evidence trail.
  • AI recommendations must be reviewed against the Written Scheme of Investigation and HER guidance before submission to regulators.
  • Any conflict with statutory consent must trigger escalation to the client’s heritage consultant and local authority.

Questions owners and crews ask

What records does AI use to inform HER search outcomes?

AI reads HER databases, monument records, event records, and grey literature to identify relevant constraints, so human sign-off confirms the interpretation and scope.

How does AI handle conflicting records from different sources?

AI flags conflicts, aggregates notes, and routes them to the planning archaeologist for reconciliation with the WSI and planning conditions.

Who signs off the consultation plan generated by AI?

The project manager or planning archaeologist signs off after reviewing the evidence trail and compliance with the Written Scheme of Investigation.

Can AI update the monument record mapping during excavation?

Yes, AI proposes updates and logs changes; the qualified person signs off embodied amendments and archive records.

Sources and further reading

  1. CIfA: Standards and GuidanceStandards and guidance for archaeological excavation, evaluation, watching briefs, finds, and archives.
  2. Archaeology Data ServiceDigital archive deposition standards, grey literature guidance, and OASIS records for archaeological projects.

Work with Suhas Bhairav

Let's find where AI pays back on your excavation sites.

Archaeology units, heritage consultants, and developers bring me the problem that keeps costing them programme delays, post-excavation backlogs, or curator queries. We map it to one system you can ship.

  • A 30-minute working call, not a pitch
  • You leave knowing the first system worth building
  • Built around the systems, records, and people you already have