Skip to main content
Build Support for Digital Preservation in Five WeeksDigital Preservation
5 min readFor Archivists and Digital Preservation Specialists

Build Support for Digital Preservation in Five Weeks

Digital preservation programs often fail not because the technology doesn't work, but because you can't secure budget approval, executive sign-off, or cross-departmental buy-in. You're maintaining bit-level fixity while leadership questions the need for another storage tier. This gap between technical necessity and organizational understanding undermines more preservation initiatives than format obsolescence ever will.

The Digital Preservation Coalition's new Advocacy Toolkit, now in member preview, offers a structured approach to closing that gap. Here's how to use it to build internal support for your digital preservation program.

The Problem: Technical Competence Doesn't Equal Organizational Support

You understand ISO 14721. You've implemented proper Submission Information Package workflows. Your fixity checks run on schedule. None of that matters if your program gets defunded because no one outside your department understands what you do or why it costs what it costs.

Most digital preservation professionals are trained in archival theory and technical standards, not in stakeholder management or internal communications strategy. You're expected to advocate for multi-year preservation commitments to executives who think "backup" and "archive" mean the same thing. The DPC toolkit evolved from their Executive Guide on Digital Preservation into a flexible resource you can adapt to your organization's specific context.

What You Need Before Starting

Access the toolkit. If you're a DPC member, log in to the DPC website. The member preview runs for five weeks, giving you time to test the materials before the public launch in June.

Identify your advocacy target. Are you building the case for initial funding? Defending an existing program during budget review? Seeking cross-departmental cooperation for records transfer? The toolkit is designed for modular use, so you'll pull different sections depending on your goal.

Map your stakeholders. List who controls budget, who influences technical decisions, and who will be affected by preservation failures. For each stakeholder, note what they care about: compliance risk, operational efficiency, research access, or legal defensibility. Your pitch to the general counsel looks nothing like your pitch to the CIO.

Gather your program's current metrics. How many terabytes under management? How many Archival Information Packages accessioned last year? What's your cost per gigabyte for long-term storage versus your organization's backup storage cost? You'll need these numbers to translate technical work into business value.

Document a concrete failure scenario. Find one case where inadequate digital preservation caused real problems for your organization or a peer institution. Did a department lose access to project files after a system migration? Did legal discovery fail because email archives weren't properly maintained? Specific examples beat abstract warnings every time.

Step-by-Step Implementation

Week 1: Frame the value proposition. Use the toolkit's guidance to translate digital preservation into terms your stakeholders already care about. If you're talking to legal, frame it as litigation readiness and compliance with records retention requirements under your Records Control Schedule. If you're talking to finance, frame it as cost avoidance; the expense of reconstructing lost data far exceeds preservation costs. If you're talking to research leadership, frame it as enabling future scholarship and meeting funder mandates for data availability.

Don't lead with OAIS reference models. Lead with what happens when preservation fails: inaccessible research data, regulatory penalties, inability to respond to legal holds, or lost institutional memory.

Week 2: Build your core presentation. Create a 15-minute presentation with three sections: what digital preservation is (in plain language), why it matters to this specific audience, and what you need from them. Include your documented failure scenario from the preparation phase. Show the gap between your current capabilities and organizational needs, using your actual metrics.

The toolkit provides examples from other practitioners. Adapt their language, but use your own data. If your organization manages 200TB of digital records and your current preservation infrastructure only covers 40TB, that 160TB gap is your vulnerability. Quantify it.

Week 3: Test your message. Schedule informal conversations with three allies in different departments. Walk them through your presentation. Ask what resonates and what confuses them. Listen for the questions they ask; those questions reveal what your actual stakeholders will care about. Revise based on this feedback.

Pay attention to terminology confusion. If your test audience doesn't understand "Archival Information Package," replace it with "properly packaged digital records with complete metadata." You're not dumbing down; you're communicating.

Week 4: Deploy your advocacy campaign. Schedule meetings with decision-makers. Send your presentation deck in advance with a one-paragraph summary of what you're asking for. In the meeting, focus on dialogue, not lecture. Ask stakeholders what concerns them about digital records and preservation. Frame your program as solving their problems, not as a technical requirement you're imposing.

If you're seeking budget approval, come with three options: a minimal viable program, a recommended approach, and an ideal state. Show what each level of investment enables and what risks remain unaddressed at each tier.

Week 5: Document commitments and follow up. After each stakeholder conversation, send a brief email summarizing what you heard and what the next steps are. If someone committed to reviewing your budget proposal, note the timeline. If someone raised concerns about storage costs, acknowledge that you'll provide a cost comparison.

The toolkit emphasizes that advocacy isn't a one-time pitch. Build ongoing communication into your program. Send quarterly updates showing what you've preserved, what you've made accessible, and how you've supported organizational needs.

Validation: How to Verify It Works

You've succeeded when you get the resources or authority you need. But measure intermediate progress too. Track how many stakeholder meetings you've held, how many departments now understand what digital preservation means, and whether you're getting invited to relevant planning discussions.

If your advocacy isn't working, revisit your value framing. Are you speaking to what stakeholders actually care about, or what you think they should care about? The toolkit's community-sourced examples show what resonates across different organizational contexts. Use them to recalibrate your approach.

Maintenance: Ongoing Tasks

Advocacy doesn't end when you get budget approval. Continue stakeholder communication quarterly. When you successfully preserve and provide access to records that support a major project, document it and share it. When format migrations succeed, explain what would have happened without proper preservation planning.

Update your failure scenarios. As new digital preservation challenges emerge, your advocacy messaging needs to evolve. The toolkit is designed for adaptation, so revisit it as your organizational context changes.

If you're a DPC member, provide feedback during this preview phase. The toolkit's strength comes from practitioner experience across different institutions. Your input shapes what becomes a community resource in June.

You Might Also Like