Why “calendar days” matters in procurement disputes

In Philippine government procurement, remedies are deadline-driven. A supplier that misses a filing period—even by a day—can lose the right to challenge an award, disqualification, eligibility ruling, or other procurement action. The phrase you will repeatedly encounter in the procurement rules is “calendar days.” It sounds simple, but it is often miscounted because bidders instinctively default to “working days,” exclude weekends/holidays, or assume extensions for courier delays or internal approvals.

This article focuses on how to count “calendar days” for protests and related procurement challenges under the Philippine procurement framework, with practical counting rules, common traps, and scenario-based guidance.

Core legal framework (Philippine context)

The procurement system that uses “calendar days”

Philippine public procurement is governed principally by:

Republic Act No. 9184 (Government Procurement Reform Act), and
its Implementing Rules and Regulations (IRR), as supplemented by Government Procurement Policy Board (GPPB) issuances and procurement documents (bidding documents, instructions to bidders, BAC notices).

Within this framework, “calendar days” is used frequently—especially in time periods tied to:

requests for reconsideration (e.g., of eligibility/disqualification decisions),
filing of protests (as an administrative remedy),
BAC processes (posting, evaluation windows, notices),
and sometimes in contract administration and sanctions timelines.

Remedies to distinguish (because the counting can attach to different triggers)

Request for Reconsideration (RfR) A first, usually mandatory, step before a formal protest in many situations. It challenges a BAC/BAC Secretariat decision (e.g., disqualification, ineligibility, post-qualification failure). The RfR has its own short “calendar day” period counted from receipt of notice.
Protest A formal administrative remedy filed with the procuring entity’s head (HOPE) against BAC decisions (commonly the decision to award, disqualify, declare failure of bidding, etc.), after complying with prerequisites (often including an RfR), and typically requiring payment of a protest fee.
Judicial remedies Separate from “protest” in procurement rules; generally involve court actions (e.g., petitions for certiorari) subject to different procedural rules. Even where judicial relief is sought, parties are commonly expected to respect and exhaust procurement administrative remedies unless exceptions apply.

This article is about counting calendar days for filing these procurement administrative remedies (especially protests), and how to avoid miscounting.

What “calendar days” means in Philippine procurement practice

Definition in plain terms

Calendar days = every day on the calendar, including:

Saturdays and Sundays,
regular holidays,
special non-working days,
and other non-business days.

You do not automatically skip weekends or holidays when the rule says “calendar days.”

Contrast with “working days”

When a procurement rule uses “working days,” you generally count only days when offices are open for business (excluding weekends/holidays). But if the rule says calendar days, you count continuously.

The single most important takeaway

If the rule states X calendar days from receipt of notice, then:

you start counting using the date you received the notice as the reference point, and
you count consecutive dates on the calendar until you reach the deadline date.

The remaining questions are about (a) when Day 1 starts, (b) what counts as receipt, (c) what happens if the last day falls on a day when filing is impossible, and (d) how electronic transmission affects receipt and deadlines.

Step-by-step: How to count “calendar days” correctly

Step 1: Identify the triggering event (“from what date?”)

Procurement deadlines are usually tied to one of these triggers:

Receipt of BAC notice (e.g., notice of disqualification, notice of post-qualification result, notice of award, notice of denial of reconsideration).
Knowledge of an act/decision (sometimes framed as “from receipt of notice” rather than mere knowledge).
Posting/publication date (less common for protests; more common for bid opportunities and notices).

Always use the exact trigger stated in the relevant rule or notice. If it says “from receipt,” do not substitute “from date of issuance,” “from date on the letter,” or “from posting date,” unless the applicable rule explicitly equates them.

Step 2: Determine the date of “receipt”

“Receipt” in procurement disputes can occur through:

personal service to a bidder’s representative,
courier delivery with proof of delivery,
registered mail (often with presumptions in general rules),
electronic mail or e-procurement portal notification (depending on the procurement mode and the terms in the bidding documents).

Practical rule: the safest stance is to treat the earliest provable moment you received the notice as the receipt date and count from there.

Step 3: Decide whether Day 1 is the day of receipt or the day after

In Philippine legal time computation, the common convention is:

Exclude the day of the act/event that triggers the period, and
start counting on the next day, unless the governing rule expressly includes the first day.

In procurement documents, the phrase “within X calendar days from receipt” is typically treated as counting starting the day after receipt. That said, bidders sometimes lose disputes by assuming a more generous interpretation when the procuring entity counts more strictly.

Best practice: Compute two calendars immediately:

Conservative count (treat the day after receipt as Day 1), and
Ultra-conservative internal cutoff (prepare to file as if the receipt day is Day 1). Then aim to file by the earlier internal cutoff. In real operations, this removes ambiguity risk.

Step 4: Count consecutively, including weekends/holidays

Once Day 1 is fixed, count every calendar date. Do not stop for:

weekends,
holidays,
typhoons,
suspension of work (unless it affects actual filing ability—see Step 5).

Step 5: What if the last day falls on a non-working day or filing is impossible?

This is where general legal principles on computation of time matter. If the last day falls on a day when:

the office required for filing is closed, or
filing is not possible due to officially declared suspension/closure,

the deadline is commonly treated as moving to the next working day (a principle recognized across Philippine procedural settings).

However, procurement practice can be unforgiving, and procuring entities may argue strictness where the filing channel was still available (e.g., an electronic submission system or email accepted filings), or where the bidder could have filed earlier.

Best practice: never rely on “next working day” unless you have no choice—and if you must rely on it, preserve proof:

announcements of suspension/closure,
screenshots of unavailable filing portals,
email bounce-backs,
sworn statements of attempted filing,
and any BAC/HOPE guidance issued.

Where “calendar days” shows up in protest-related remedies

A. Request for Reconsideration (RfR) periods

Many procurement disputes begin with an RfR because procurement rules often require a bidder to seek reconsideration before escalating to a protest. The RfR period is usually very short and stated in calendar days.

Counting risks:

The notice is received late in the day; bidders assume the next business day is Day 1.
Weekends/holidays occur mid-period; bidders pause counting.
Internal approvals (board resolution, signatories) consume the limited window.

Practice tip: Treat the RfR as an emergency filing. Submit a compliant RfR immediately and supplement within allowed rules if necessary (but do not assume supplementation is allowed unless your procurement documents permit it).

B. Protest filing periods

A protest often must be filed within a short number of calendar days after:

a bidder receives the BAC decision being protested, or
receives the denial of reconsideration (if RfR was required/availed).

It is common for the protest period to be triggered by receipt of a BAC resolution or notice (e.g., notice of award, notice of disqualification, notice of post-qualification failure, or denial of RfR).

Common trap: Counting from the wrong notice. For example, counting from the “date of BAC resolution” rather than “date of receipt by bidder.”

C. Protest fee and “perfection” of the protest

A protest is typically not treated as properly filed unless accompanied by the required protest fee (or paid within the specified period/manner). If the rules or procurement documents say the protest must be filed “within X calendar days,” and fee payment is a condition, then:

a protest submitted on time without the fee may be treated as not perfected,
or as defective and dismissible.

Counting implication: if payment takes time (e.g., government cashier schedule), you must factor that into the same calendar-day period. Do not assume you can file the pleading first and pay later unless the applicable rule explicitly allows it.

“Receipt” problems: service, email, portals, and bidders with multiple addresses

1) Physical delivery: who received it?

If the procuring entity serves notice to the bidder’s office and a receptionist receives it, the procuring entity will usually treat that as receipt by the bidder. Internal handoff delays do not extend deadlines.

Mitigation: Train front-desk staff and messenger logs to escalate BAC/Procurement mail immediately and record the exact date/time of receipt.

2) Email service: which inbox counts?

Bidding documents often require the bidder to state an official email address for communications. If the procuring entity sends the notice to that address, the bidder may be deemed to have received it even if:

it went to spam,
the responsible employee was on leave,
the inbox was full.

Mitigation: Use a monitored group inbox, enable alerts, whitelist the procuring entity’s domain, and keep server logs.

3) E-procurement portals: the timestamp issue

Where portals are used, the “receipt” might be equated with:

the time the notice is posted to the bidder’s account, or
the time an email notification is sent, or
the time the bidder downloads/views it.

Different systems and bidding documents define this differently.

Mitigation: Assume the earliest system timestamp is your receipt time. Take screenshots and keep audit logs.

Counting examples (with timelines)

These examples assume the common convention: exclude the day of receipt, start Day 1 the next day, and count every calendar day.

Example 1: 3 calendar days from receipt, received on a Wednesday

Received: Wednesday, March 4
Day 1: Thursday, March 5
Day 2: Friday, March 6
Day 3: Saturday, March 7 Deadline: Saturday, March 7

If filing can only be done at an office closed on weekends, you might argue next working day (Monday, March 9). But do not rely on that—file before the weekend if possible.

Example 2: 5 calendar days from receipt, received on a Friday before a Monday holiday

Received: Friday, April 3
Day 1: Saturday, April 4
Day 2: Sunday, April 5
Day 3: Monday, April 6 (holiday)
Day 4: Tuesday, April 7
Day 5: Wednesday, April 8 Deadline: Wednesday, April 8

The holiday did not pause the count.

Example 3: Received by email late at night

Email received: Tuesday, 11:50 PM For counting, the procuring entity may treat “receipt” as Tuesday (the date stamp), not Wednesday.

Practical approach: Treat Tuesday as receipt; start Day 1 on Wednesday; and file as early as possible.

Interplay with internal procurement steps (and why bidders get squeezed)

Even if you count calendar days correctly, bidders often miss deadlines because procurement timelines are designed for speed and finality. Common squeeze points:

Decision chain: legal review → management approval → signature authority.
Document assembly: annexes, bid documents, notices, proof of receipt, affidavits.
Payment process: protest fee payment often requires in-person processing during limited hours.
Geography: procuring entity location vs bidder location; courier time is not part of the period.

Operational rule: Your deadline is not “end of the last day”—your deadline is “the latest hour the receiving office or allowed channel accepts filings.” If the HOPE’s office accepts filings only until 5:00 PM, a submission at 5:30 PM may be treated as late even if the calendar date is correct.

Practical filing mechanics: how “calendar days” interacts with time of day

Office-hour cutoffs

Procurement rules may not state a specific time-of-day cutoff, but the receiving office’s business hours effectively impose one.

Best practice: Aim to file during business hours on or before the computed deadline date, and earlier if the final day falls on a weekend/holiday.

Electronic filing

If electronic filing is permitted:

confirm whether a time-stamped email or portal submission outside business hours is accepted, and
keep proof (sent email headers, portal confirmation screens).

If electronic filing is not explicitly allowed, do not assume it will be honored for protests; it may be accepted for communications but rejected for formal filing requirements.

Common misconceptions and how they lose cases

“Calendar days means working days.” Wrong. Calendar days includes weekends and holidays.
“We can extend because the office was closed on the last day.” Sometimes arguable, but risky—especially if you could have filed earlier or another channel was available.
“Courier delays excuse late filing.” Generally no. Deadlines attach to filing/receipt by the procuring entity, not when you dispatched the document—unless rules explicitly say otherwise.
“We filed the protest on time; we can pay the fee later.” Often fatal if the fee is a perfection requirement within the same period.
“We counted from the BAC resolution date.” Deadlines usually run from receipt of notice by the bidder, not from internal BAC dates.
“We didn’t see the email so we didn’t receive it.” If it was sent to the declared email and not bounced, you may still be treated as having received it.

Documentation checklist for deadline-proofing

To defend timeliness, preserve:

Proof of date/time of receipt of the triggering notice:
- signed receiving copy, courier POD, registry return card, email headers, portal timestamp screenshots.
The notice itself (complete pages, attachments).
Your computation sheet/calendar showing Day 1 and deadline.
Proof of filing:
- receiving stamp, acknowledgment email, portal confirmation.
Proof of payment of protest fee (official receipt, transaction record) and the date/time paid.
If relying on closure/suspension:
- official memoranda, public advisories, screenshots, and evidence that filing channels were inaccessible.

Strategy: file early, file complete, preserve proof

Because “calendar days” compresses time:

treat every receipt of a BAC notice as a countdown,
prepare templates for RfR and protest pleadings,
pre-authorize signatories when participating in major bids,
set up same-day payment capability for protest fees,
and implement an internal “procurement disputes” mailbox and tracking log.

A disciplined approach to counting and proof-building is often more decisive than the substantive arguments—because an otherwise strong protest can be dismissed outright for being late or unperfected.

Quick reference: counting rules you can apply immediately

Calendar days: count every day, no skipping weekends/holidays.
Use the rule’s stated trigger—commonly receipt of notice.
Compute Day 1 conservatively (typically the day after receipt), and file earlier than the computed deadline.
Do not rely on “next working day” unless filing was genuinely impossible; preserve proof if you must.
Confirm whether fee payment is required within the same period to perfect the protest.
Preserve evidence of receipt, filing, and payment with timestamps.