A person enters the municipal holding cells on a Friday at 11:40 p.m. for disturbing the peace on a public street. The civic judge does not arrive until Saturday at noon and imposes a 24-hour arrest. On Sunday, with a different custody shift, nobody knows for sure when the person should be released: the intake sheet is in one folder, the ruling in another, and the officer who received the person has gone home.
In the end, the person walks out early Monday, when someone reviews the list. Nobody acted in bad faith. But that person spent more time in the cell than the Constitution allows, and the municipality has no way to prove otherwise.
Administrative arrest is the most serious sanction a civic court can impose, because it is the only one that takes away a person's liberty. That is why its limit is not an operational guideline. It is a constitutional limit that is either met or breached hour by hour, and it can only be demonstrated with a record that counts those hours.
What Article 21 says
Article 21 of Mexico's Constitution is clear about what an administrative authority can do when someone violates a police regulation. Sanctions may only consist of a fine, arrest for up to thirty-six hours, or community service.
The same article adds two rules that matter for daily operations. First, if the person does not pay the fine, it is exchanged for the corresponding arrest, which may in no case exceed thirty-six hours. Second, if the offender is a day laborer, factory worker or employee, the fine cannot exceed one day's wage; if the offender is self-employed, it cannot exceed the equivalent of one day's income.
Read together, these rules require the civic court to know four things about every sanctioned person:
- When they were deprived of their liberty.
- What sanction was imposed, in hours or in pesos, and on what legal basis.
- Whether they were offered the option of paying the fine instead of serving the arrest, and what they chose.
- When they were released.
Without those four facts, there is no way to claim that an arrest respected the constitutional limit. And without a reliable record, the municipality cannot answer when a human rights body, an amparo judge or the person's own family asks how long someone was held.
Mexico's National Mechanism for the Prevention of Torture, part of the National Human Rights Commission (CNDH), visited the public safety holding cells of 27 municipalities in the state of Yucatán in September 2021. Its Supervision Report 03/2021 documents precisely how control over time is lost.
Of the 27 municipalities visited, only seven kept logbooks of people deprived of liberty. Of those seven, only five recorded the time people entered and left the holding area. In the other 22 municipalities, there was no documentary way to know how long any arrest lasted.
The report identifies other problems that compound the first. In 44% of the municipalities visited there were no civic judges, and sanctions were imposed by public safety directors, justices of the peace or booking desk staff who had no authority to do so. Only in four municipalities was it shown that the person was given a hearing before being sanctioned.
Interviews with detained people were even more revealing. None had been told they had the right to legal assistance. Only three had been told the reason for their arrest. And every single one said nobody had explained that they could exchange the arrest for a fine.
The Mechanism also stated that delaying an arrest sanction, which cannot exceed 36 hours, by more than 12 hours because no civic judge is available is unlawful. In other words, the time a person spends waiting for someone to rule on their case also counts.
Finally, the report documented detentions under the label of "family request," in which police take a person away at the request of relatives and the detention ends, in most cases, in a 36-hour arrest. That label does not exist as an administrative offense in any municipal code, and the report classifies it as arbitrary detention.
It would be easy to read these findings as a training or ethics problem. In part they are. But the most common operational cause is simpler: the detained person's time is scattered across documents that nobody adds up.
The officer records the time of arrest in their report. The booking desk records the intake time. The judge issues the sanction in a ruling. The custody officer records the release time, if they record it at all. When those four moments sit on four different pieces of paper, calculating the correct release time requires someone to gather the papers, do the math and pass it on to the next shift.
That calculation fails at peak load: weekends, shift changes, nights with many bookings. And it fails silently. Nobody gets an alert when a person has been in the cell for 37 hours. They simply stay there until someone checks.
The Mechanism's report puts it another way: records are one of the basic tools for giving the person legal certainty from the moment of detention, through the hearing before the judge, to the completion of the arrest hours imposed. The record is not the paperwork that follows operations. It is how operations are controlled.
Controlling arrest time does not require sophisticated technology. It requires a case file built to answer the question "when does this person leave?" without anyone having to reconstruct it. An arrest under control has, at a minimum, these characteristics:
- A single case file from the moment of detention. The event, the booking, the medical certificate and the judge's ruling live in the same record, not in folders kept by different areas.
- Hours as data, not text. The intake time and the sanction in hours are captured in fields, so the release time can be checked without doing math by hand.
- Visible statuses. Any authorized person can see whether a case is pending a ruling, already sentenced, or whether the person has been released.
- A list of upcoming releases. The custody officer on each shift knows who must leave in the coming hours without relying on what the previous shift said.
- Documented conversion. If the sanction is a fine, the case file shows whether it was paid or exchanged for arrest, with the amount in pesos and the corresponding hours.
- An audit log of every change. It is clear who issued the ruling, who recorded the release and whether anyone changed a field afterward.
- Measured waiting time. The municipality can know how long, on average, a person waits to be ruled on, and spot the shifts or days when that wait grows.
That last point is often overlooked. The delay between intake and ruling is not an administrative detail: it is time deprived of liberty that, as the Mechanism noted, cannot be extended for lack of a judge. If the municipality does not measure it, it cannot fix it.
Tribuna organizes municipal civic justice around a single case file, and the full arrest cycle takes place inside that file.
The booking desk records the event and the booking in a guided flow: offenses, the detained person's details, belongings and assigned judge. The physician certifies on the same record. The judge rules with all the information at hand (offenses, certificate, belongings and evidence) and issues the sentence as arrest in hours or a fine in pesos.
Each case moves through clear statuses: pending, assigned, sentenced and released. Each role has its own queue of pending and recently resolved cases, so an unruled case does not get lost between shifts. When the judge rules, the release is recorded and moves to Upcoming releases, so the release does not depend on what the previous shift remembers.
Control is built into operations. Every read and every change is logged, with a complete timeline per case file, and role-based permissions define who can see or change each part. The intelligence map includes average resolution time, which lets leadership track how long cases take to be resolved. And official documents, from the detention PDF to the complete case file, are generated from the same record.
It is the same logic we explain in A booking log is not detention management and in A glance is not a medical certificate: a record that moves between areas without being rewritten and leaves evidence of every step.
Before buying equipment or hiring staff, the civic justice office should answer these questions with data:
- For every person in the holding cells today, can you say when they entered and when they must leave?
- How much time passes, on average, between a person's intake and the judge's ruling? And on weekends?
- How many people were released last month after serving more hours than they were sentenced to?
- Is there a record that the person was offered the option to pay the fine instead of serving the arrest?
- Does the night-shift custody officer know who must be released before dawn without asking anyone?
- Are there detentions on record with no administrative offense to support them?
- If someone changes the intake time or the sentence, is there a trace of the change?
If several answers require searching through notebooks or calling another area, the problem is not willingness. It is that the detained person's time is not yet part of the case file.
A cell is not a clock. The 36-hour limit set by the Constitution is only met if someone counts the hours, and it can only be proven if that count was recorded in the same case file as the detention and the ruling.
That record protects the arrested person, who leaves when they should. It protects the judge, whose ruling is carried out as issued. It protects custody staff, who no longer depend on the previous shift's memory. And it protects the municipality, which can answer with evidence when someone asks how long a person was held.
If your institution is reviewing how it runs its booking desk, civic court and holding cells, explore Tribuna, see how Agora organizes the municipality's citizen services, or request a demo.