How to budget for a digital catalogue raisonné
A digital catalogue raisonné requires more than a publication budget. It needs a plan for research, data preparation, images, rights, technology, editorial review, and long-term access. This guide helps project leads create a preliminary multi-year budget, identify commonly overlooked costs, and compare technical proposals on the same basis.
Akseli Gallen-Kallela, Lakeside Landscape, 1911, oil on canvas, 42.5 × 33.5 cm, Ateneum Art Museum. Image courtesy of the Ateneum Art Museum/Finnish National Gallery and Jenni Nurminen.
What does a digital catalogue raisonné cost?
There is no standard price for producing a digital catalogue raisonné. The cost depends on the scope of the research, the condition of the existing records, the number and type of images, the publication requirements, the technology selected, and how long the project must remain available.
Digital publication also changes where costs occur. It may avoid printing, physical storage, and distribution expenses, but it introduces continuing responsibilities for hosting, maintenance, accessibility, preservation, and future migration.
A useful preliminary budget should therefore provide four figures:
The cost of preparing and publishing the first release
The expected annual cost after publication
A reserve for periodic upgrades or migration
A contingency for work that cannot yet be estimated
Calculate these figures over a defined period, such as five, ten, or twenty years. A low launch price does not necessarily indicate a low long-term cost.
Start by defining the scope
A budget will remain unreliable until the project team agrees on what it is budgeting for.
Begin by recording:
The estimated number of works
The number and condition of existing records
The location and format of existing information
The amount of research still required
The number and type of images
The languages in which the catalogue will be published
The intended public and restricted content
The number of people who will create, edit, and approve records
Any connections required with archives or institutional systems
Whether the catalogue will be published at once or in stages
The period for which the publication must be maintained
The number of works alone does not determine the scale of the project. Five hundred records assembled from several databases, spreadsheets, paper files, and image folders may require more preparation than several thousand consistently structured records.
Create at least three versions of the scope:
Minimum: The smallest publication that would still meet the project’s scholarly purpose
Expected: The publication the team reasonably anticipates producing
Expanded: Additional content or functions that could be included if resources permit
This distinction makes it easier to protect the essential scholarship when costs change.
Which scholarly costs should be included?
Technology does not conduct the research or establish the authority of a catalogue raisonné. Budget first for the people responsible for producing and reviewing the scholarship.
Depending on the project, these costs may include:
Research
Allow for archival research, provenance research, object examination, bibliography development, correspondence, travel, and consultation with external specialists.
Research time should be included even when it is contributed by salaried staff or volunteers. Record unpaid and internally funded labor as an in-kind contribution so the budget reflects the project’s actual resource requirements.
Editorial review
Budget for reviewing attribution decisions, object histories, provenance, exhibition histories, bibliographies, inscriptions, and catalogue entries.
Also include copyediting, proofreading, fact-checking, citation review, and final approval. If the catalogue will continue to change after publication, some editorial work will remain a recurring cost.
Project management
Someone must coordinate researchers, editors, photographers, rights holders, technical specialists, and institutional decision-makers.
Project management includes scheduling, documenting decisions, monitoring budgets, managing permissions, preparing meetings, and maintaining communication across the team. These responsibilities should not be treated as incidental additions to another role.
Photography and digitization
Include new object photography, archival scanning, image processing, color correction, file naming, metadata creation, and quality review.
The budget should distinguish between preservation files and the smaller versions delivered through the public website. It should also account for any physical preparation needed before an object or document can be photographed.
Rights and permissions
Budget for researching copyright status, locating rights holders, obtaining permissions, recording license terms, and preparing required credit lines.
Fees are only one part of this work. Correspondence, negotiation, documentation, and later renewals can also require substantial staff time.
Translation and language review
If the catalogue is multilingual, budget for translation, specialist review, terminology management, and later updates in every published language.
A translation is not complete when the initial text is delivered. Changes to the source content may require corresponding revisions throughout the life of the publication.
Which costs occur before publication?
Some technical and production costs are concentrated around setup and the first release.
These may include:
Requirements analysis and technical planning
Audit of existing records, files, and systems
Data cleaning and restructuring
Development of the catalogue’s data model
Configuration or development of the research workspace
Data and image migration
Design of the public website
Search, filtering, and browsing functions
Connections with other institutional systems
Mobile and browser testing
Accessibility review and remediation
Security and privacy review
Staff training
Workflow documentation
Publication testing and quality assurance
Domain registration and launch preparation
Some of these costs can recur. For example, accessibility should be tested before publication, but later changes to the website may require further review. The Web Content Accessibility Guidelines provide a stable standard that can be included in requirements, contracts, and testing plans.
If the team has not yet selected a technical approach, compare the responsibilities associated with purpose-built platforms, assembled systems, and custom development before requesting estimates.
Which costs continue after launch?
Publication is a change in project stage, not the end of the project.
A long-term budget may need to cover:
Hosting or annual platform fees
Domain renewal
Data and image storage
Image delivery
Software maintenance
Security updates and review
Technical support
Backups and restoration testing
Monitoring of broken links and other errors
Browser and device compatibility
Accessibility testing
New research and record updates
Editorial and scholarly review
Additional photography or digitization
Rights renewals
Staff training and transitions
Documentation updates
Data exports and preservation copies
Future migration to another system
The Digital Preservation Coalition’s guidance on lifecycle costs emphasizes that digital costs extend from creation and ingest through preservation and access. It also cautions that cost models are approximations because technology and institutional requirements change.
A budget should therefore state its assumptions. Note whether annual figures are fixed, expected to increase, or subject to storage, traffic, record, or user limits.
Which costs are commonly overlooked?
Existing data preparation
A migration estimate may cover moving records without covering the work required to understand, clean, and reconcile them.
Before requesting a migration estimate, determine:
How many sources contain relevant information
Whether the same work appears in several sources
Whether fields are used consistently
Whether stable identifiers exist
Whether dates, dimensions, and names follow consistent formats
Whether images can be reliably connected to records
Whether rights information is complete
Whether any sensitive information must be excluded
Internal staff time
A supplier’s estimate may cover only external work. Add the hours that institutional staff will spend preparing data, answering questions, testing records, attending meetings, reviewing designs, and approving the publication.
Change during migration
Research often continues while records are being prepared for a new system. Budget for deciding where new information will be entered, reconciling parallel changes, and confirming which version of each record is authoritative.
Complex records
Testing only the simplest records can produce an unrealistically low estimate. A pilot should include difficult cases, such as:
Uncertain or changing attributions
Multiple titles and languages
Complex edition or casting histories
Interrupted provenance
Lost or destroyed works
Works known only through documentation
Extensive exhibition and publication histories
Restricted images or records
Relationships between artwork and archival material
Custom changes
A small custom feature can create continuing responsibilities for testing, maintenance, documentation, and future compatibility.
Ask whether each proposed change is essential to the scholarship, useful but optional, or primarily presentational.
Exit and migration costs
Every technical arrangement will eventually change. Include the cost of exporting records and images, documenting their structure, checking the export, and moving them elsewhere if necessary.
The National Endowment for the Humanities recommends planning for the management and sustainability of project assets as part of project design, rather than treating sustainability as a question to address after funding ends.
How should technical proposals be compared?
Give every prospective provider or development team the same description of the project. Otherwise, differences between estimates may reflect different assumptions rather than different prices.
Ask each provider:
What work is included in the setup estimate?
What must our team prepare or complete?
Is data cleaning included?
How many records, images, users, or languages are included?
Which functions are included, and which require custom work?
Are design, accessibility, testing, and training included?
Which costs recur annually?
Can recurring prices increase, and on what basis?
Are storage, data transfer, support, or usage limits applied?
Who maintains the system and its integrations?
How are security updates and backups managed?
What happens when an underlying component changes?
Can we export all records, relationships, images, and metadata?
What would an export or migration cost?
What happens when active research pauses or concludes?
Which parts of the estimate remain uncertain?
Ask providers to identify exclusions explicitly. An apparently comprehensive proposal may omit data preparation, image processing, content entry, accessibility testing, support, or long-term preservation.
Calculate the total lifecycle cost
Use the same formula for every technical approach:
Total lifecycle cost = scholarly and editorial labor + data, image, and rights preparation + technical setup + recurring annual costs + periodic costs + contingency
For each budget line, record:
The amount
Whether it is one-time, annual, or periodic
The number of years covered
Who is responsible
How the estimate was calculated
Whether it is confirmed or provisional
What is excluded
Do not combine all technical expenses into a single “website” line. Separating them reveals which responsibilities continue and which costs might change.
How can costs be controlled without weakening the scholarship?
Cost control should remove unnecessary repetition and uncertainty, not reduce research quality or transparency.
Useful measures include:
Audit the records and images before selecting technology.
Establish the minimum scholarly scope.
Test representative records before committing to a full migration.
Publish in defined stages when appropriate.
Record information in reusable, structured forms.
Reuse shared records for people, institutions, publications, and exhibitions instead of maintaining separate copies.
Limit custom development to requirements with a clear scholarly purpose.
Adopt an existing accessible design system where possible.
Establish an image and rights strategy early.
Document editorial and technical decisions.
Confirm that data and images can be exported.
Reserve funds for unexpected work.
Staged publication can distribute costs across several years, but it does not make unfinished work free. Each release still requires review, documentation, technical support, and a clear explanation of its scope.
Preliminary digital catalogue raisonné budget
Use the following checklist to prepare an initial budget or compare estimates.
Project assumptions
Number of works:
Number of existing records:
Number of images and files:
Number of publication languages:
Number of internal users:
Intended first publication date:
Expected years of active research:
Total budgeting period:
Planned publication stages:
Public and restricted content:
Existing systems or integrations:
Scholarly and editorial costs
Research:
Provenance research:
Object examination:
External specialists:
Travel:
Project management:
Editorial review:
Copyediting and proofreading:
Translation and language review:
Ongoing scholarly updates:
Data, image, and rights costs
Data audit:
Data cleaning:
Data restructuring:
Photography:
Digitization:
Image processing:
Metadata creation:
Rights research:
Licensing fees:
Rights documentation and renewals:
Initial technical costs
Requirements analysis:
System configuration or development:
Data migration:
Image migration:
Public website design:
Search and browsing functions:
Integrations:
Accessibility review:
Security and privacy review:
Testing and quality assurance:
Training:
Documentation:
Launch:
Recurring annual costs
Hosting or platform:
Domain:
Data storage:
Image storage and delivery:
Maintenance:
Security:
Backups:
Technical support:
Accessibility testing:
Editorial updates:
Staff training:
Periodic and future costs
Major upgrades:
Additional migration:
Data and image export:
Preservation copies:
Staff transition:
Redesign:
Rights renewals:
Contingency:
Budget summary
One-time preparation and publication costs:
Annual recurring costs:
Number of years:
Periodic costs:
Contingency:
In-kind contributions:
Estimated total lifecycle cost:
Record the date on which the budget was prepared and review it at least annually. Update the assumptions whenever the scope, schedule, staffing, or technical approach changes. A sustainable budget does not promise the lowest possible cost. It shows what the project requires, who will be responsible for each part, and how the publication will remain credible and available after its first release.
