Legal Issue: Whether a Ride-Hailing Platform (SakayNa, Inc.) Qualifies as a Common Carrier Under Philippine Law

Summary

The central legal issue is whether SakayNa, Inc.—a corporation that merely connects passengers to independent drivers through an online platform—can be classified as a "common carrier" under Article 1732 of the Civil Code, making it liable for breach of contract of carriage. The prevailing jurisprudence strongly suggests that SakayNa, Inc. is NOT a common carrier, and therefore cannot be held liable under that theory, though other liability theories may still apply.

Backgrounder

Sarah was matched by SakayNa, Inc.'s platform with Manny, who used his own vehicle to drive her. An accident occurred, and Sarah now seeks to hold SakayNa liable as a common carrier. The question turns on the legal characterization of platform-based transportation network companies (TNCs), a relatively novel issue that the Supreme Court has recently addressed.

Structured Analysis

1. Statutory Definition: Article 1732 of the Civil Code

Article 1732 defines common carriers as:

"Persons, corporations, firms, or associations engaged in the business of carrying or transporting passengers or goods or both, by land, water, or air, for compensation, offering their services to the public."

The key elements are: - Engaged in the business of transporting - For compensation - Holding out services to the public

2. Jurisprudential Framework: The "Holding Out" Test

The Supreme Court has consistently held that to be a common carrier, the entity must itself be engaged in transporting passengers/goods, not merely facilitating such transport. In Pangasinan Transportation Co., Inc. v. Cabalu (G.R. No. L-17318, March 16, 1979), the Court emphasized that common carriers must hold themselves out as willing to undertake the transportation.

3. Controlling Case: Grab Philippines, Inc. v. Field Investigation Bureau

The most directly applicable precedent is Grab Philippines, Inc. v. Field Investigation Bureau, G.R. No. 246429, December 7, 2021.

In this case, the Supreme Court ruled that Grab is NOT a common carrier because:

The Court held that Grab is engaged in the business of providing an "online-enabled platform" connecting drivers and passengers, not in the business of transportation itself.

4. Application to SakayNa, Inc.

Applying Grab to the facts:

• SakayNa does not own vehicles — Drivers use their own vehicles
• SakayNa does not employ drivers — Manny is an independent service provider
• SakayNa does not physically transport — Manny drives Sarah
• SakayNa merely provides the platform — It facilitates the connection for a fee

Therefore, SakayNa does not fit the definition under Article 1732 and cannot be treated as a common carrier.

5. Who is the Common Carrier Here?

Manny, the driver, is more likely the common carrier in this scenario because: - He operates his own vehicle for hire - He transports passengers for compensation - Even single-vehicle operators may qualify under broad interpretations (cf. De Guzman v. Court of Appeals, G.R. No. L-39955, July 19, 1985)

Possible Counterarguments Sarah May Raise

1. "Holding Out" Argument: SakayNa advertises transportation services to the public, holding itself out as offering rides.

Response: The Court in Grab rejected this argument, distinguishing between offering transport services directly versus offering a platform that enables others to transport.

1. Control Argument: SakayNa sets fares, quality standards, and routing through its app, exercising significant control.

Response: Such control relates to the platform's service terms, not to actual physical transportation, which remains the driver's responsibility.

Alternative Theories of Liability

While SakayNa is likely not liable as a common carrier, Sarah may still pursue claims under:

• Negligence (Article 2176, Civil Code) — If SakayNa failed to exercise reasonable care in vetting drivers or maintaining platform safety
• Quasi-delict through negligent platform operation
• Breach of implied warranty of safety (if a contractual relationship is established)
• Apparent authority/agency by estoppel — If the public reasonably believes drivers are SakayNa's agents

Follow-Up Questions for Critical Thinking

1. What if SakayNa required drivers to use only SakayNa-branded vehicles? Would this change the analysis?

2. What if SakayNa set fixed fares and routes, removing driver discretion entirely? Does the degree of platform control determine common carrier status?

3. Should regulatory policy evolve to treat platforms like SakayNa as common carriers for consumer protection reasons? Note that the DOTr has issued regulations for TNCs under DOTr Department Order No. 2015-11 (and later issuances), but this is regulatory, not civil liability classification.

4. How would the result differ if Manny was a regular employee of SakayNa rather than an independent contractor? (Under Grab, the Court suggested employment relationship would change the analysis.)

5. Does the rider's reasonable expectation matter? When Sarah books through SakayNa, does she reasonably believe she is contracting with SakayNa?

Conclusion and Actionable Takeaways

Conclusion

SakayNa, Inc. is most likely NOT liable for breach of contract of carriage as a common carrier under Article 1732 of the Civil Code, following the doctrine in Grab Philippines, Inc. v. Field Investigation Bureau (G.R. No. 246429, December 7, 2021). SakayNa is a technology platform, not a transporter. Manny, the driver, would more properly be considered the common carrier in this transaction.

Recommended Study Points

1. Memorize Article 1732 and its elements
2. Study the Grab case carefully — it is the leading authority on TNCs
3. Compare with Ermita-Malate Hotel v. CA (G.R. No. L-40202, July 18, 1984) — to understand when entities that appear to offer services may not be common carriers
4. Examine DOTr regulations on Transportation Network Companies (TNCs) — Department Order No. 2015-11 and subsequent issuances, for the regulatory (not civil) classification
5. Explore the distinction between contractual liability (common carrier) and quasi-delict liability (negligence)
6. Review dissents in Grab — Justice Caguioa's concurring opinion provides additional analytical framework worth studying

Practical Implication

For aspiring lawyers, this area illustrates how technological disruption challenges traditional legal categories. The common carrier doctrine predates digital platforms by decades, requiring creative statutory interpretation. Always consider whether older doctrines remain fit for modern commercial realities—and whether alternative liability theories may better serve your client's interests.