[Developers]

Summarisation Domain

An investigation has been running for four months and a new analyst is taking it over. Rather than spending two days reading every document, she asks the Summarisation domain for a detailed case summary. Within minutes s

Category: Api DomainsLast Updated: Feb 5, 2026
api-domainsai

Overview#

An investigation has been running for four months and a new analyst is taking it over. Rather than spending two days reading every document, she asks the Summarisation domain for a detailed case summary. Within minutes she has a comprehensive narrative covering the key entities, the timeline of events, the evidence gathered so far, and the open questions. Her colleague preparing for a court hearing requests a different output: a briefing document formatted for legal proceedings, with evidence citations and professional language. The same investigation, two different audiences, two different summary types, both generated from the same underlying data.

Key Features#

  • Multiple Summary Types: Generate summaries in various formats including executive overviews, detailed analyses, chronological timelines, entity profiles, evidence summaries, and court-ready briefings.

  • Investigation Summarisation: Synthesise all available investigation data including evidence, timelines, entity profiles, and analyst notes into coherent narrative summaries.

  • AI-Powered Analysis: Use AI-powered analysis to identify key themes, important findings, and critical connections across multiple documents and data sources.

  • Configurable Detail Levels: Control the depth and focus of generated summaries to match the needs of different audiences, from brief executive overviews to comprehensive detailed analyses.

  • Court-Ready Output: Generate briefing documents formatted for legal proceedings with appropriate citations, evidence references, and professional language.

  • Entity-Focused Summaries: Create summaries centred on specific entities of interest, aggregating all relevant information about a person, organisation, or asset.

Summary Types#

TypeDescriptionAudience
ExecutiveHigh-level overview of key findingsLeadership and stakeholders
DetailedComprehensive analysis with full contextAnalysts and investigators
TimelineChronological sequence of eventsCase reviewers
Entity ProfileAll information about a specific entityInvestigators
EvidenceSummary focused on evidence itemsLegal teams
BriefingCourt-ready briefing documentAttorneys and courts

Use Cases#

AI-assisted multi-document summarisation reduces the time analysts and legal teams spend reading large case files. Primary industries include law enforcement and criminal justice, financial crime investigation, and defence and intelligence.

  • Case Status Updates: Generate executive summaries of investigation progress for leadership briefings and stakeholder communications.

  • Legal Preparation: Create court-ready briefing documents that synthesise investigation findings into professional legal documentation.

  • Analyst Handoff: Produce detailed case summaries when transferring investigations between analysts to ensure continuity.

  • Multi-Source Synthesis: Combine information from multiple documents, evidence items, and data sources into a unified narrative summary.

Integration#

The Summarisation domain connects with investigative workflows across the platform:

  • Investigation Management: Summaries are generated from and linked to investigation data
  • Evidence Management: Evidence items are referenced and synthesised in summaries
  • Timeline: Chronological summaries draw from investigation timelines
  • Reporting: Generated summaries feed into formal report packages

Open Standards#

  • GraphQL (June 2018 specification): All summarisation queries and mutations are exposed over a typed GraphQL API, enabling clients to request exactly the summary fields they need in a single round-trip.
  • JSON (RFC 8259): Every AI-generated summary is produced and persisted as structured JSON; the AI client is explicitly invoked in JSON mode and all summary payloads are stored as JSONB in PostgreSQL.
  • JSON Web Token (RFC 7519) and JSON Web Key Sets (RFC 7517): Requests to the summarisation API are authorised using RS256-signed JWTs verified against a published JWKS endpoint; unauthenticated calls are rejected with HTTP 401.
  • OAuth 2.0 (RFC 6749): The platform's Bearer-token authentication layer, on which the IsAuthenticated GraphQL permission class operates, follows the OAuth 2.0 authorisation framework.
  • ISO 8601: All temporal metadata on generated summaries (generated_at, created_at) are stored and returned as UTC-anchored ISO 8601 datetime strings.
  • UUID (RFC 4122): Primary keys for summaries, investigations, users, and organisations are version-4 UUIDs, ensuring globally unique, collision-resistant identifiers across tenant boundaries.
  • W3C Web Content Accessibility Guidelines (WCAG) 2.2: The web interface through which analysts and legal staff access generated summaries targets WCAG 2.2 conformance, including appropriate ARIA landmark and live-region markup for dynamically loaded summary content.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14

Ready to Build?

Get started with our APIs or contact our integration team for support.