Why it matters
Without AI, mismatches between acquisitions criteria and holdings checks produce overstocked or undersold catalogues, misaligned curator briefs, delayed invoicing, and fragmented provenance trails, increasing risk of misdescriptions and client dissatisfaction. Errors escalate when multiple entities contribute notes.
From design to safety
Design
AI shapes proposal design and standards
The system reads acquisition criteria, holdings checks, and curator briefs to draft a template proposal that aligns with catalogue standards and ESTC/ICS metadata requirements, ensuring consistent scope, pricing anchors, and archival references across formats.
- catalogue entry ledger
- provenance label
- condition report form
- curator brief
Build
Data harmonization from acquisitions to invoicing
The AI ingests data from acquisition criteria, holdings checks, and curator briefs, applying standardised fields and issue points to generate ready-to-send proposals and quotes, with version control and audit trails and explicit edition point tagging.
- catalogue entry ledger
- provenance folder
- curator brief
- condition report form
Operation
Proposal generation and negotiation workflow
During listings and client outreach, the AI assembles proposals, compares pricing against market notes, and flags negotiation-ready terms for human sign-off, while tracking approvals, rejected offers, and version histories for revisions.
- invoice
- curatorial dossier
- packing slip
- condition report form
Maintenance
Ongoing accuracy with stock and terms audits
The system performs periodic checks of holdings against catalogue records, validates curator updates, reconciles invoices with terms amendments, and flags drift between physical stock and digital records, triggering re-cataloguing as needed.
- catalogue entry ledger
- provenance folder
- curatorial dossier
- invoice
Safety
Provenance diligence and regulatory alignment
AI flags missing provenance documentation, monitors compliance with library access policies, and routes significant provenance concerns for review and sign-off by a qualified librarian or curator, with escalation to legal when required.
- catalogue entry ledger
- provenance label
- curator brief
- curatorial dossier
Part by part
- 1
catalogue entry ledger
- Watch for
- Mismatch between catalogue notes and holdings; missing edition points or ESTC references.
- AI action
- Flag discrepancies; suggest corrected cataloguing fields and proposed price range.
- 2
provenance label
- Watch for
- Incomplete provenance chain; gaps in ownership or sale history.
- AI action
- Highlight gaps; trigger curator briefing and archival request.
- 3
condition report form
- Watch for
- Unrecorded repairs or foxing patterns; deteriorated bindings.
- AI action
- Suggest preventive conservation notes and condition grading update.
- 4
curator brief
- Watch for
- Unclear curatorial priorities or missing scope for a sale.
- AI action
- Propose clarifying questions and scope of collection emphasis.
- 5
invoice
- Watch for
- Unmatched terms between proposal and payment schedule.
- AI action
- Flag for accounting review; auto-fill standard payment terms.
- 6
packing slip
- Watch for
- Inaccurate item counts or incorrect shipping details.
- AI action
- Trigger packing checklist and shipping label verification.
Worked example
Creating a Proposals Pipeline for a 3,500-item Special Collection
Illustrative scenario with sample data.
A mid-size dealer builds proposals for libraries, aligning acquisitions criteria with holdings and curator briefs.
Signal in
stockSize: 3500; acquisitionCriteria: {minEditionPoints: 4, regions: [Europe, Americas], priceBand: 200-2500}; holdings: {catalogued: 3100, missingPoints: 120}; curatorBrief: {focus:
System out
Human sign-off:
How to roll it out
Phase 1
Weeks 1 to 4: Baseline
Establish data feeds from acquisitions, holdings, and curator briefs; validate catalogue fields and pricing anchors against ESTC and ICS metadata.
Phase 2
Weeks 5 to 8: Integration
Implement version control, audit trails, and standardised proposal templates; test negotiation workflows and sign-off routing.
Phase 3
Weeks 9 to 12: Optimization
Refine alerting rules, containment of drift, and provenance checks; validate invoicing integration with accounts payable and client tracking.
Where people stay in charge
- Only the senior cataloguer or librarian may approve final proposals and price bands when within the defined cataloguing rules and ESTC references.
- AI may propose terms but cannot finalize payment schedules or client terms without explicit human sign-off by the responsible dealer or curator.
- Sensitive provenance concerns and restricted-access holdings require escalation to the legal/compliance officer before any outgoing proposal or invoice is released.
Questions owners and crews ask
How does AI help ensure acquisitions criteria align with holdings during proposal creation?
AI analyzes criterion fields and holdings metadata, cross-checking edition points, provenance, and region fits; it then suggests cohesive proposal scopes and price anchors for curator review.
What signals trigger a curator alert during proposal drafting?
Gaps in collection emphasis, missing establishment of edition points, or conflicting curatorial briefs trigger alerts; a summary of questions is prepared for curator input before finalising the draft.
How are invoicing terms reconciled with proposed terms in client proposals?
The system compares proposal terms with established payment schedules, flags mismatches, and auto-fills standard terms; final terms require approval by the dealer and accounting head.
Who signs off on provenance-related flags before proposal submission?
A designated librarian or curator signs off on flagged provenance concerns; if needed, a legal/compliance officer reviews high-risk provenance issues prior to release.