Which PQRS response deadline applies in Colombia?
First, identify who received the request and what the person is asking for. Article 14 of Colombia's Law 1755 of 2015 sets general deadlines for authorities, unless a special rule applies.
| Recipient or case | Deadline | What to check |
|---|---|---|
| Authority: general petition | 15 business days | Check whether a special rule applies. |
| Authority: documents or information | 10 business days | Check that the request asks for documents or information. |
| Authority: consultation about its functions | 30 business days | Check that the consultation concerns a matter within the authority's remit. |
| Telecommunications provider | 15 business days | Colombia's CRC Resolution 7811 of 2025 allows additional time for gathering evidence under certain conditions. |
| EAPB or IPS: healthcare complaints | 72, 48, or 24 consecutive hours | Colombia's health oversight agency, Supersalud, distinguishes between standard, priority, and life-threatening risk. |
| Provider participating in SIC Facilita | 15 business days | The SIC Facilita terms count from the business day after the request is filed. |
In healthcare, the maximum deadline doesn't justify waiting when a situation requires immediate attention. For other companies or industries, check the applicable rule before using the general deadline.
When does the clock start, and what if information is missing?
Keep the date and proof of receipt. Also identify the channel used and the authority responsible. The sending and receipt dates don't always match.
As an institutional reference, Article 24 of Colombia's SENA Resolution 1365 of 2022 starts the clock the day after the responsible authority receives the request. Don't apply that rule to every company, channel, or industry without checking.
To count business days, check the applicable calendar and holidays. If an entity receives a general petition on a business Monday, the reference count starts Tuesday. Confirm the channel's conditions and the applicable rule before setting the deadline.
An incomplete petition needs different handling from a request that's ready for a response. Article 17 of Colombia's Law 1755 of 2015 governs when an authority must ask the person to provide missing information. A system shouldn't close the case without recording that request and checking its effect on the deadline.
What happens if you don't get a response on time?
An authority may need more time in exceptional circumstances. The proviso to Article 14 of Colombia's Law 1755 of 2015 requires it to give notice before the deadline and explain the delay. It must also give a reasonable deadline no longer than twice the original period. The extension isn't automatic.
If an authority misses the deadline for a request for documents or information, Article 14 provides that the request is deemed accepted. The copies must be delivered within the following three days. That specific consequence doesn't apply to every PQRS by default.
A response must be clear, precise, and complete, and address what the person requested. Colombia's Constitutional Court ruling T-500 of 2025 also requires the authority to communicate its decision. A substantive response doesn't necessarily mean granting the request.
If the deadline has passed, keep the request and proof of receipt. Ask for a status update and keep a record of your follow-up. You can also contact the local Personería or ask about filing a tutela action. The right option depends on the recipient and the case.
In telecommunications, the rule cited in the table provides for approval by administrative silence under certain conditions. Don't assume every missed response has that result. Check the applicable rules and circumstances.
How do you track deadlines?
A PQRS queue needs clear rules and someone responsible for reviewing exceptions. Your team can follow these steps:
- Record receipt. Keep the request, receipt date, channel, and contact details. Assign a tracking number and check that the case isn't a duplicate.
- Classify before calculating. Identify the recipient, what the person is requesting, and the industry. If there's doubt about the rule or responsible authority, send the case for human review.
- Calculate and alert. Record the applicable deadline, calendar, and due date. Set alerts before the due date and flag cases without an owner.
- Review and communicate. Check that the response addresses every point in the request. Keep the response, the sending method, and proof that it was communicated.
What tool should you use to manage a PQRS queue?
Here's a hypothetical example, not a client case. A municipal government receives an email requesting a copy of a certificate. The person in charge records receipt and classifies it as a request for documents.
The system calculates the due date using its configured calendar, assigns the request to the responsible department, and sends an alert before the deadline. The department prepares the response. A person checks that it includes the certificate or explains the situation as appropriate. The team then records that it was sent.
If your current tool can assign cases, calculate dates, and store evidence, start by configuring those features. A shared spreadsheet can work for a small queue, as long as someone reviews changes and dates.
An automation platform can help when you need to connect email to the case queue and generate alerts. Custom software development may make sense if you have your own rules or systems that are difficult to connect.
Cost and delivery time depend on the channels, integrations, and quality of existing records. Who maintains the rules when they change also matters. Before choosing, review your PQRS help desk options.
AI can suggest a classification or flag parts of a response that need review. To see whether it helps, we measure its suggestions against cases reviewed by people. We check for errors that could assign the wrong deadline and compare results before and after.