Vetting a Philippine DMC as a Trade Buyer: Six Things That Leave Evidence Behind

Trade vetting and consumer vetting are not checking the same things

On this page: Concurrent capacity ｜ Insurance and incident chain ｜ Wholesale subcontracting ｜ Operating evidence ｜ One basis, and stop signals

A consumer verifies that the company is real. A trade buyer verifies that it can carry your volume, sit inside your accounting, and still be standing when something goes wrong. The first is a minimum threshold; only the second is a partnership threshold.

The minimum set — a verifiable registration whose name matches the contracting entity and the receiving account, a physical office you can walk into, the ability to issue a properly addressed corporate invoice, contract and bank account in the same name, and a named person with an escalation chain when something breaks — applies to every kind of buyer. It is covered in full in the five checks you can run yourself and is not repeated here. Clear that, and the six trade-specific items below begin.

Item one: corporate settlement and invoicing capability. This determines whether the company can become a supplier you place repeat orders with, rather than a one-off cash counterparty. Pin down the specifics: which type of corporate invoice or official receipt it can issue and whether it can be addressed to the entity you nominate; whether the entire relationship can run through a corporate bank account; how payment terms evolve — a first programme is normally prepaid, but can it move to batch or monthly settlement once volume exists; the settlement currency, which day's exchange rate applies, and which side absorbs conversion loss and cross-border charges; the issuing deadline and the rules for a reissue after the programme has run.

Test it rather than ask it. Three moves. First, request a sample proforma invoice and look at the addressee field, the entity name and the tax fields — formatting tells you whether books are actually being kept. Second, route a small first payment through the corporate account and check that the receiving name matches the contracting entity. Third, ask for a redacted statement of account from a comparable past programme and see whether it is itemised and whether pass-through items sit in their own block.

Three answers that should stop you: "pay my personal account, the company account is slow"; "we will see about the invoice after the trip"; and "the invoice has to be issued in another company's name". The last one usually means the entity you are signing with is not the entity taking your money, which is a far more serious problem than price. How the money itself breaks down and how to align two quotes is a separate question, covered in what sits inside a ground quote.

If the company you sign with is not the name on the receiving account, none of the other five checks matter. Want a properly formatted proforma? Send us the programme type →

Capacity: stop asking whether they have vehicles, start asking how many groups they can run on one day

What separates operators is not whether vehicles exist but how many programmes they are already carrying on your dates and how much redundancy is left. Whether the fleet is owned or subcontracted, and whether vehicles exist at all in peak weeks, is the baseline layer covered in vetting a ground operator. This section is about the number trade buyers actually need: concurrency.

Four specifics to extract. One: how many programmes it is already holding in your week and across which destinations, because that determines whether the senior drivers and escorts will be pulled elsewhere. Two: how many same-class vehicles it can dispatch simultaneously, and what happens beyond that number — a downgraded class, a split into staggered batches, or an external hire; and if external, whose vehicle and whose driver, and who is named as the performing party in the contract. Three: whether inter-island seats and domestic sectors come from its own allocation or are bought on the open market only after you confirm — in peak weeks the difference is not price, it is availability. Four: whether it can actually describe an overflow plan, such as substituting within the same area, splitting one group into two staggered batches, or shifting the whole day sequence back by a day.

Testing beats asking. Give a concrete date, a concrete headcount and a concrete day sequence, and require the reply to be one of three words — can take it, needs external hire, cannot do it — each with one line of reasoning. An operator willing to classify honestly has usually checked; one that answers "no problem" to every condition is taking the booking first and solving it later. Add one more move: require booking confirmations for the core resources within 48 hours — room and seat confirmation numbers, not the phrase "it is arranged". Without confirmations, nothing is held.

Study programmes, incentive groups and corporate inspection tours need one extra question: has it run a scenario where several vehicles must reach the same assembly point at the same moment and depart together, and if so, how many vehicles and how many escorts. Time synchronisation for this kind of group is far more demanding than for a standard leisure itinerary; the organisational differences are set out in how study programmes are organised.

One sequencing point: it can only verify capacity once you have supplied the name list, flights and rooming. What you owe and by when is in what each side must hand over before work starts — a day late and the operator can only soft-hold, which feels like a booking and is not one.

The operator that says "no problem" to every date and headcount is not strong, it simply has not checked yet. Send dates and headcount and we will answer can-take or cannot-do →

Insurance and the incident chain: whose name is on the policy, and who is standing there in the first half hour

"We are fully insured" carries no information. What matters is whose name is printed on the policy and who is moving in the first two hours after an incident. The three-layer structure — carrier cover, operator liability cover, traveller policies — is explained in who is liable when something happens. This section is about turning it into something verifiable.

Request the policy copy and read five fields. One: the named insured — is it the entity you are contracting with, or its upstream transport company or boat owner? A policy in someone else's name has no relationship to your counterparty. Two: whether the policy period covers every date of your programme, including arrival and departure days. Three: scope and exclusions — island hopping, water activities, diving and elevated-height activities frequently sit inside the exclusions, and those are precisely the moments groups get hurt. Four: whether limits are expressed per person or per occurrence, because the two behave very differently once headcount rises. Five: the claims contact and the notification deadline, since late notification is routinely refused.

Ask about the incident chain in minutes, not adjectives. Who reaches the scene first — the escort already with the group, or a duty manager dispatched from the office, and how long does that take? Who accompanies the traveller to a facility, who fronts costs, who speaks to the medical staff? Who speaks to the traveller and the family, who notifies your side and at what frequency? Who produces a written incident record, and on the same day or later? Any link in that chain without a name attached becomes a group of people waiting for each other on the day.

Night duty is the other half of the same chain, and it must be tested. Do not settle for "24-hour line". Ask for three things: a duty roster with names, time bands and languages; a written response commitment expressed in minutes for night and for day; and the waiting and re-dispatch rules for flight delays. Then call late at night in local time yourself, record how long the response took, and note whether the person could pull up your file immediately. That single action tells you more than any brochure.

Clarify whether "standby vehicle" means redundancy or improvisation. Holding a vehicle and a few rooms in reserve is redundancy; going to the market after something breaks is luck. Ask whether reserve resources were actually deployed during last year's peak and how the dispatch worked. If it comes to formal recourse, the evidence and complaint route is in how to escalate and pursue a claim.

Call the duty line once at midnight and time the answer — the cheapest and most accurate step in the whole exercise. Want to see our duty roster and escalation chain? Just ask →

Will your programme be handed wholesale to someone else, and how to nail the performing party into the contract

The real damage from wholesale subcontracting is not diluted service — it is that your counterparty is not present. It holds no vehicle, no policy and no person on the pier where the incident happens, and your contract lets you pursue only a messenger. So this has to be solved in the clauses before signature, not through trust afterwards.

Five clauses to write in. First, a named performing party clause: state segment by segment who executes — ground transport, inter-island sectors, guiding and escorting, water activities — with any change requiring prior written consent. Second, disclosure and joint responsibility: if subcontracting is permitted, require written disclosure of the subcontractor's name and make it explicit that the contracting party remains fully responsible to the travellers and cannot plead that the work was passed on. Third, personnel notification: driver names and plate numbers, guide and escort names and credential numbers submitted before departure, with advance notice of substitutions. Fourth, no onward assignment by the subcontractor. Fifth, consequences written as executable actions — replacement of the performing party, suspension of the next payment milestone, settlement limited to what was delivered — rather than a vague undertaking to bear responsibility.

Five signals that only surface on the day. Vehicle markings or operating details that do not match the contracted company; a driver or guide who cannot name the company you signed with; an unfamiliar third-party coordinator suddenly appearing in the group chat; a confirmation sheet addressed differently from the quotation; and an entirely new team appearing on the second island with no advance notice. If any of these occurs, record it in writing that day and require the contracting party to explain — do not save it for the post-trip reckoning.

Distinguish subcontracting from a lead-plus-local structure. A multi-destination programme coordinated by one operator and executed locally by partners is normal and efficient. The difference comes down to two things: the local partners are disclosed in writing beforehand, and responsibility remains entirely with the lead operator. With both, it is division of labour; without either, it is abdication. Who owns which leg of the chain is set out in which company owns which segment.

A direct probe: table the clause requiring written consent for any change of performing party, and watch the reaction. Operators that genuinely run their own programmes agree and volunteer the crew list; those that habitually pass work on begin explaining that this is how the industry works. The explanation is the answer.

Table the written-consent clause and watch: agreement or explanation — the explanation is the answer. Want terms that name the performing party? We will draft to your programme type →

How to ask for operating evidence instead of accepting "we have handled many groups"

You are not after a case-study deck; you are after operating traces that tie to a date, a place and a person. An operator that has genuinely run programmes keeps all four of the items below. One that has only passed work along usually cannot produce a single one.

First: a redacted operations sheet or confirmed itinerary from a comparable programme. Names removed, but dates, headcount, the full day sequence, vehicle configuration and crew assignments retained. Ask for the same route in the same season. Two things reveal themselves: whether the day sequence is sensible — a zigzag suggests it was never run — and whether vehicle and crew configuration actually match the headcount.

Second: a crew roster for one real week. This single document answers two questions at once — how many programmes genuinely ran concurrently that week, and how stable the team is. The same names recurring across different weeks means in-house staff; a completely fresh cast every week means people are recruited once a booking lands. It also cross-checks the concurrency claim: an operator that says it can field five vehicles at once but cannot produce a roster for any week has misstated one of the two.

Third: genuine on-the-ground photographs rather than marketing imagery. The test is simple. Operational photographs contain that day's people, a plate number, real weather, food on the table, ticket gates, an actual hotel lobby — and they are usually not beautiful. Marketing images are official site photography, empty of people, perfectly lit, and the same frame turns up in several companies' materials. Make the request specific: "three on-site photographs from the same route last season, showing the vehicle and the crew." Whoever can supply them has run it.

Fourth: a trade referee willing to take a call. The question is not whether they were good but what happened operationally: how many travellers over how many days, whether anything changed mid-programme, how many hours it took to produce an alternative, and whether settlement and documentation went smoothly. Only a referee who can answer at that level carries weight. Incentive and reward programmes, where presentation and timing matter more, deserve an extra question about on-site supervision levels — see what incentive programmes demand operationally.

Last move: a trial booking. Run one transfer or one small group through the entire cycle — enquiry, confirmation sheet, payment milestones, pre-departure briefing, on-site execution, post-trip settlement — and watch whether each stage follows what was agreed. That single run tells you more than any amount of desk diligence.

An operator with no dated operating trace and only beautiful imagery is usually selling someone else's vehicles. Want to start with a trial group? We will run the full process →

Forcing a like-for-like reply, and the sentences that should stop the conversation

Send the ten headings below to every operator verbatim and require a written point-by-point reply. Comparison only exists once two same-format replies are in hand — and an operator that declines to answer point by point has already given you a conclusion.

• Entity and account. Contracting company name, receiving account name, whether they match, whether the whole relationship can run corporate-to-corporate.
• Documentation. Which invoice types can be issued, whether the addressee can be nominated, issuing deadlines and reissue rules.
• Settlement. Currency, which day's exchange rate applies, who absorbs conversion loss and charges, terms for the first programme and thereafter.
• Concurrent capacity. For a stated date and headcount: can take it, needs external hire, or cannot do it — and if external, who is named as performing party.
• Proof of hold. How many hours until booking confirmations for core resources arrive, and in what form the room and seat confirmation numbers come.
• Insurance. Policy copy showing named insured, policy period, scope and exclusions, limit basis, notification deadline.
• Incident chain. Who attends the scene and within what time, who accompanies to treatment and fronts costs, who is notified and how often, who issues the written record.
• Duty cover. Roster with names and time bands, written response times for night and day, waiting and re-dispatch rules for flight delays.
• Performing party. Segment-by-segment execution names, acceptance of the written-consent clause, crew list filed before departure.
• Operating evidence. Redacted operations sheet, one week's crew roster, three on-site photographs, one contactable referee.

Stop and re-verify if you hear any of these. "Pay my personal account, the company one is slow." "We will sort the invoice after the trip." "Any date is fine" with a refusal to write "needs external hire" anywhere. "We are fully insured" with no policy copy forthcoming. An inability to say who reaches the scene and within what time. A refusal to name the performing party in the contract, or the reassurance that "the people we send are all the same anyway". No dated operating trace of any kind. A habit of steering every detailed question back to price and answering with a discount. And most dangerous of all, emphasis on connections and on leaving everything to them — language that supplies no verifiable information and simply asks you to substitute trust for evidence.

Keep the order: entity and account first, capacity and insurance second, price last. Buyers who reverse it usually discover on arrival day that they were comparing two things that were never comparable. Once the engagement actually starts, how the enquiry, confirmation sheet, payment milestones and pre-departure briefing run is covered in the full working cycle and liability split; what each side must hand over and carry before work begins is in the document list and liability boundaries.

Send us the programme type, dates, headcount and destination combination and our team will reply against those ten headings in writing — then put the same sheet to another operator and let the answers separate themselves. This article is general industry information, not legal or commercial advice; the binding terms are those in your signed contract.

Entity and account first, capacity and insurance second, price last — reverse it and you compare the wrong things. Send the ten headings and we will reply in writing within 48 hours →