A backup is not an archive: why operational data needs to survive a change of administration

It is January 2 and the new municipal administration is installing its team. The handover record has a line that reads "backup of the booking desk system, external hard drive, 1 unit." The passwords come in a sealed envelope.

The new director plugs in the drive. There is a database file several gigabytes in size and a folder of PDFs with no apparent order. No document explains which table holds what, what the statuses mean, or which version of the system is needed to open it. The vendor that installed it no longer has a contract. The IT person who ran it left with the previous administration.

Technically, the information was handed over. In practice, nobody can answer a question as simple as how many people went through the civic court last year, or rebuild a case file that the human rights commission is now requesting.

A backup is not an archive. A backup is a copy of bytes. An archive is information that is organized, described and carries enough context for someone who did not produce it to find it, understand it and show that it was not altered. The difference rarely matters in daily operations. It matters the day the administration changes.

What the handover requires, line by line

Municipal handover is not an informal procedure. In Veracruz, where city governments changed on January 1, 2026, the state's Organic Law of the Free Municipality lists the documents that must be delivered. Among them, in article 187, section XII, is "the inventory of the software programs in use and the electronic backup of the information and the databases." Article 115 of the same law requires public servants to inventory "the printed and electronic documents, archives or case files" they receive or hand over.

The guide issued by the state Congress and the Superior Audit Body (ORFIS) for the 2022-2025 process turns that obligation into forms. Two of them deserve a close read:

• List of electronic files. It asks for the backed-up information, the medium where it was stored (the form itself gives external hard drive, server, CD or DVD as examples), an identification code, the number of media and remarks.
• List of access credentials. It asks for the systems, equipment, official email accounts and digital environments, the unit that operates them and whether the credential was delivered. Credentials go in a closed, sealed envelope, and the guide states they should be changed afterwards.

The guide also schedules a handover rehearsal in October of the final year, to assess progress before closing. It is a good practice: it forces the handover to be tested before it becomes final.

The design makes sense. It ensures that a copy exists and that the new administration can log into the systems. But neither form asks what the director in our example needed to know: what the backup contains, how its records relate to each other and who changed them.

The answer to that question is in another law.

What the General Archives Law says

Mexico's General Archives Law, in force since 2019 and binding on the federal government, the states and the municipalities, treats electronic documents as archival records, with the same obligations as paper.

Its article 7 requires institutions to produce, record, organize and preserve documents on every act arising from their functions. A booking at the municipal holding desk, a medical certificate, a ruling of administrative arrest or a work order to fix a streetlight are acts of that kind, even if they live in a system and not in a folder.

Article 10 is more direct about changes of administration: a public servant who leaves office "must guarantee the delivery of the archives to whoever replaces them, organized and described" according to the archival control and reference instruments. Article 17 adds that, during the handover, those instruments must also be delivered and kept up to date. Article 13 lists the minimum ones: the general classification chart, the records retention schedule and the document inventories.

The chapter on electronic records is even clearer:

• Article 41 requires electronic records management to cover intake, access assignment, security, storage, use and traceability.
• Article 44 requires institutions to guarantee the recovery and preservation of electronic records held in management systems, "databases and email throughout their life cycle."
• Article 46 calls for guidelines on automated systems that, at a minimum, ensure the long-term accessibility and intelligibility of records, preserve the data describing their content and structure, and record the traceability of updates, backups or any other process that affects their content.

Read together, the two laws tell a coherent story. The handover ensures that the information exists and can be opened. The archives law requires that it also be intelligible, described and carry the record of what was done with it. A hard drive meets the first part. It rarely meets the second.

What is lost when only the backup is handed over

In an operational system, records are not worth much on their own. Their value comes from context. When the handover is reduced to a copy, context is the first thing to go:

• The meaning of statuses. A field with the value "3" might mean "sentenced" or "released." The rule lived in the system's code or in the head of whoever used it.
• Relationships. The booking, the medical certificate, the property receipt and the ruling for the same person sit in different tables. Without the data model, rebuilding a complete case file is archaeology.
• The history of each record. If the copy only keeps the final value, it loses who captured it, who corrected it, when and why. That is exactly what a complaint, an audit or a lawsuit two years later will ask for.
• Access rules. A backup without roles is a file that anyone with the password can read in full, including sensitive personal data about detained people or residents who reported a problem.
• The ability to open it. A proprietary format without the software, the license or the vendor that understands it can become unreadable within a few years. This is the technological obsolescence that article 49 of the archives law refers to.

None of these losses shows up in the handover record. The record says "1 unit" and it is signed. The problem appears months later, when the information is there but cannot be used.

This connects to what we argued in A number is not an indicator: if the definition of an indicator lives in a personal spreadsheet, it leaves with whoever built it. The same happens to the meaning of data when it lives only in the system that gets switched off.

The three-day test

There is a practical way to know whether an institution has an archive or only a backup. Imagine the current team disappears tomorrow and, in the first three days, someone from the new administration has to answer five questions with the information that was handed over:

1. How many cases were handled last year, by type and by status?
2. What happened in a specific case, step by step, and who intervened at each step?
3. Which records were modified after they were closed, and by whom?
4. Which information is confidential and who is allowed to see it?
5. Which case files must be kept, and for how long?

If the answers depend on the previous vendor picking up the phone, the institution has a backup. If they can be answered from the information and its documentation, it has an archive.

The Veracruz guide already schedules a handover rehearsal in October. That rehearsal is the ideal moment to run this test on the systems, and not only on the inventories of furniture and bank accounts.

How continuity is designed from day one

Continuity is not built in December of the final year. It is decided when the system is chosen and configured. Four conditions make the difference:

• Every record with explicit statuses. A case file that moves through pending, assigned, sentenced and released can be explained to anyone. A free-text field that each department fills in its own way cannot.
• History inside the record itself. The timeline of each case, with who did what and when, must live next to the data, not in a technical log that nobody exports.
• Official documents generated from the record. If the certificate, the ruling or the report is generated from the system, the document and the data cannot contradict each other.
• Documented catalogs and rules. Offenses, report types, statuses and roles need written definitions. This is what the law calls control and reference instruments, applied to the system.

With those conditions in place, the backup stops being a black box. It becomes a copy of an archive that was already organized.

How this connects to Tribuna and Agora

In Tribuna, Intello's platform for public safety and civic justice, police, physicians and judges work on the same case file, with clear statuses: pending, assigned, sentenced and released. The audit module logs every read and every change, keeps the complete timeline of each case file and requires a reason to open sensitive files. Official documents are generated from the same record: PDFs of the detention, personal property, medical certificate, crash report and full case file. In the crash investigation module, a report approved by the supervisor is locked. And search results are filtered by the role of the person searching. All of that is context that travels with the data instead of staying in someone's memory.

A Tribuna implementation starts with an assessment that documents workflows, actors, catalogs, documents and rules, followed by an institutional configuration where roles, permissions, forms and naming conventions are defined. That is the documentation a handover needs and that rarely exists. Tribuna can also import historical records and coexist with systems already in place, which helps when information from previous administrations sits in other tools.

In Agora, the citizen services platform, reports from every channel arrive in a single system and traceability keeps the full history of each case: who did what, when and with what result. Work orders for in-house crews and external contractors live on the same platform, with the case information. When the administration changes, the new team does not receive a spreadsheet of pending items, but cases with their history.

No platform replaces an institution's archival work: the classification chart, the retention schedule and records appraisal remain the responsibility of the archives coordinating unit. What a well-designed system does is give that work something to stand on.

The institutional lesson

Municipal administrations last three years. The case file of a detained person, a citizen complaint or a traffic crash may be needed long after that. That gap in timescales is why the law treats public information as an archive and not as the property of whoever captured it.

The question for leadership teams is not whether they have a backup. Almost all of them do. It is whether the next administration could use that backup without calling anyone.

If your institution wants its operations to reach the next team intact, see how Tribuna organizes public safety and civic justice in a single auditable case file, how Agora keeps the history of every citizen case, or request a demo.

Sources

• General Archives Law (Ley General de Archivos), current text with the latest amendment published in the Official Gazette on January 19, 2023 (Supreme Court of Justice of the Nation version)
• Congress of the State of Veracruz and ORFIS, Guía para el Proceso de Entrega y Recepción de la Administración Pública Municipal 2022-2025 (2025)