The compliance mindset.
Compliance is unglamorous, occasionally frustrating, and necessary. Cohort default approach: get the paperwork right early and keep it current; treat compliance as a recurring rhythm rather than an afterthought. Alumni who establish good standing in their first year operate freely afterwards; graduates who skip steps end up dealing with bigger problems later, often when they least want to.
The four compliance principles:
What "good standing" looks like
An alumna in good compliance standing has, at any moment:
- Current CAAP drone registration with valid expiration date.
- Current pilot certification matching operations tier.
- Valid business registration (DTI for sole proprietor, SEC for incorporated) with renewals current.
- BIR registration with TIN, books of accounts, current tax filings.
- Mayor's permit and barangay clearance current for the operations base.
- Per-mission documentation retained — flight logs, contracts, receipts.
- Maintenance and incident records retained per cohort default schedule.
This list of artifacts produces the operational confidence that "if anyone asks, I can show them." Most graduates rarely need to produce these documents — but the few moments when they do (CAAP inspection, BIR audit, cooperative dispute, insurance claim) determine whether the operations continue or are disrupted. Compliance is insurance you maintain regardless of whether you ever need to use it.
The honest reality of bureaucracy: Philippine government offices are slow. CAAP processing can take 4-8 weeks; BIR registration 2-3 weeks; LGU permits 1-2 weeks. This is the system; plan around it. Trying to expedite via informal channels usually creates more problems than it solves.
Cohort defaults that work well with bureaucratic timelines:
- Start setup 6-8 weeks before first paid mission: gives time for delays, document corrections, and any unexpected requirements.
- Bring everything plus extra copies: photocopies, originals, secondary IDs. Office staff often request additional documents on the spot.
- Visit offices early in the morning: queues are shorter; staff is fresher; processing is faster.
- Track everything: which office, which person, which date, what was filed. Lost paperwork is frustrating; tracked paperwork is recoverable.
- Build relationships with office staff: be polite, learn names, follow up patiently. Repeat visitors are generally helped faster.
The graduates Slack workspace has a "compliance" channel where graduates share current Davao-specific procedures, office hours, helpful staff, and recent regulatory changes. The collective experience accelerates individual setups significantly.
Pre-operational paperwork.
Before commercial operations, several registrations and permits need to be in place. The order matters — some registrations require others as prerequisites. Cohort default sequence below works for most graduates starting commercial drone work in Davao; adjustments may be needed for specific business structures or operations outside Davao City proper.
The cohort default pre-operational sequence:
The Davao One-Stop-Shop
Davao City has a centralised "Business One-Stop Shop" (BOSS) at City Hall that consolidates several pre-operational steps:
- Mayor's permit application
- Sanitary permit
- Fire safety inspection
- Engineering office clearance
- Some BIR coordination
The BOSS is meaningfully faster than visiting each office individually. Cohort experience: ~5-7 working days for typical sole-proprietor setup vs ~3-4 weeks doing offices separately. The trade-off is that BOSS is busy in the mornings and queues can be long; arrive early.
For graduates operating outside Davao City proper (e.g., Tagum, Digos, neighboring municipalities): equivalent services exist at municipal level but are typically less consolidated. Budget more time and visit offices individually. Local barangay captain or neighborhood association can advise on specific procedures.
Sole proprietor vs. corporation: most cohort graduates start as sole proprietors. The trade-offs:
- Sole proprietor (DTI): simpler setup, lower fees, simpler taxation. Personal liability is your responsibility — operations issues affect personal finances.
- One Person Corporation (OPC) — SEC: separates business and personal liability. ~₱5,000-10,000 setup; more complex annual filings; better for higher-revenue operations or partner-org formal structures.
Cohort default starting structure: sole proprietor for first 1-2 years, then evaluate transition to OPC if revenue exceeds ~₱500K/year or if liability exposure becomes significant. The transition is doable but requires planning; consult an accountant for the specific timing and procedure.
Tax classification: most cohort graduates qualify as 8% gross-income earners or under graduated income tax depending on total annual revenue. The 8% option is simpler if revenue is below the VAT threshold (~₱3M/year). An accountant can advise on the optimal choice for specific situations; the wrong choice can cost meaningful amounts annually.
Partner-org operations: typically operate as corporations or formal partnerships. Pre-operational paperwork is more involved (SEC registration, separate accounting, board structure). Lumipad engineering can advise partner orgs on the structure but specific setup needs Philippine-licensed legal counsel.
Per-mission documentation.
Each commercial mission produces records that need to be created, retained, and sometimes shared. The documentation exists at three points: before (cooperative agreement, mission notification), during (flight log), and after (delivery confirmation, official receipt). Most cohort default missions produce ~10-15 documents; the discipline is creating them at the time, not reconstructing them later.
The per-mission documentation lifecycle:
The cooperative contract template essentials
Cohort default cooperative agreement covers, at minimum:
- Parties: alumna business name (DTI-registered) and cooperative full name.
- Scope: what survey work, AOI description, expected outputs.
- Deliverables: format (NDVI map, GeoTIFF, report), timeline (X days after mission).
- Pricing: total amount, payment schedule, currency (PHP).
- Mission timing: planned date, weather contingency, postponement handling.
- Property and access: cooperative grants access to AOI; alumna accesses for survey purposes only.
- Privacy and data: imagery use is for cooperative purposes; not redistributed without consent.
- Liability and disputes: basic statement of responsibility; resolution approach (typically: good-faith discussion first, escalation to barangay or LGU mediation if needed).
- Termination: how either party can end the agreement.
- Signatures and dates.
~1-2 pages total in the cohort default template. Both parties sign; both retain copy. The relationship matters more than the contract — but the contract clarifies expectations and provides reference if disagreements arise. Most cohort missions never need to refer back to the contract; the few that do appreciate having one.
Per-mission documentation in practice: cohort default workflow is to create most documents as part of the mission rhythm rather than as a separate paperwork session.
- Pre-mission: cooperative agreement signed (first mission only); mission notification filed if required; field log opened.
- Mission day: field log entries during; quick photo of any cooperative leadership signed acknowledgment after.
- Post-mission (within 48 hours): delivery via agreed channel (email, USB, printed); delivery confirmation requested; OR issued upon payment.
- Weekly review: file all per-mission documents into operational records; verify completeness; transfer to long-term retention.
The discipline is contemporaneous — created at the time, not retrofitted later. program graduates who maintain this discipline report ~10-15 minutes per mission in paperwork time; graduates who try to reconstruct later report 60+ minutes per mission and incomplete records. Building paperwork into the mission rhythm is much cheaper than treating it as separate work.
Periodic obligations.
Once registered, ongoing obligations follow a calendar rhythm — quarterly tax filings, annual renewals, periodic compliance items. Missing periodic obligations is one of the most common ways graduates drift out of compliance; the cure is treating them as scheduled work, not as something to remember. Cohort default approach: tax calendar on the workshop wall, automated reminders 2 weeks before each deadline.
The cohort default tax and renewal calendar:
The tax calendar discipline
Quarterly tax deadlines are the most-missed compliance item. Cohort defaults that prevent this:
- Calendar reminders: 30 days before, 14 days before, 7 days before each tax deadline. Phone calendar, paper calendar, graduates Slack — whichever is reliable for you.
- Records-current discipline: monthly review ensures records are current, so quarterly filing is "consolidate the month"s, not "reconstruct three months."
- eBIRForms account: registered and tested well before first filing. The system has occasional issues; testing during deadline week causes problems.
- Bank arrangements: tested payment workflow with your bank well before first deadline. Payment via authorized agent banks (AABs) is more reliable than newer online channels for first-time filings.
- Buffer in mission scheduling: don't plan paid missions during the week before a tax deadline. Save that week for paperwork; missions can be other weeks.
Late filing produces penalties — typically ~25% surcharge plus 12% annual interest on unpaid amounts. Avoidable; the calendar discipline above prevents 95%+ of missed deadlines for cohort graduates.
The annual review happens around the time of the 1701 annual filing (April). Cohort default annual review covers:
- Total revenue and expense reconciliation: quarterly filings consolidated; corrections if needed.
- Tax option review: still on optimal tax structure (8% vs graduated)? Consult accountant if revenue trajectory has changed.
- Business structure review: still appropriately sole-proprietor, or is OPC transition warranted? Threshold typically ~₱500K-1M annual revenue.
- Renewal calendar update: which registrations expire in the coming year; budget for renewals.
- Insurance review: coverage adequate for operations volume? Is rate competitive?
~3-4 hours of work for sole proprietor; longer for OPC. ~₱2,000-5,000 for accountant consultation if needed. Cohort default: most graduates handle quarterly filings themselves and use accountant for annual review only. The hybrid balances cost with rigor.
Record retention.
Records aren't just for current operations — they need to be retained for periods set by various regulators. BIR is the most demanding: 10 years for financial records. CAAP requires 3 years for flight logs. Cooperative agreements should be retained as long as the relationship continues plus several years after. The cohort default approach: structured retention from day one; periodic review to clear out records past their retention period.
The cohort default retention schedule:
Digital vs paper records
The cohort default is hybrid: digital primary for ease of access, physical originals for legal validity where required. Specifically:
- Originals required physical: signed cooperative contracts (with cooperative's wet signature), official receipts (BIR-issued booklet), barangay clearances and other LGU stamped documents.
- Digital primary: flight logs (entries directly digital), email correspondence, maintenance spreadsheets, photos and incident documentation.
- Hybrid (both): anything that needs to be both legally valid (physical) and easily accessible (digital). Most permits and key documents fall here.
Digital backup discipline: cloud storage (Google Drive, Dropbox) with automatic backup; periodic local backup to external drive; cohort engineering recommends 3-2-1 strategy (3 copies, 2 different media, 1 offsite). For most cohort graduates, original drive + cloud + occasional external HDD backup is sufficient.
Specific regulatory note: BIR audits typically accept digital records with proper backup, but require original paper books and original ORs. Don't discard physical originals even after scanning.
The "I can find it within 5 minutes" test: cohort default for record organization. If asked for any specific document — last quarter's tax filing, the contract with cooperative X, the field log from June 15 — you should be able to produce it within 5 minutes.
Not having an instant retrieval system creates two problems:
- Audit anxiety: BIR or CAAP requests trigger panic if records can't be found.
- Operational drag: routine questions about past missions take longer than they should.
The cohort default retrieval system is folder-based: top-level by year (2024, 2025); within year by category (taxes, missions, registrations, maintenance); within category by date or cooperative. Spreadsheet index of significant documents. ~30-60 minutes initial setup; ongoing discipline of filing as documents are created. Total annual time investment: ~5-10 hours; total benefit: never having to scramble for documents under pressure.
Disposal after retention period: documents past their retention period can be disposed of, but cohort default is to err on the side of keeping. Storage costs are minimal; the once-in-a-decade scenario where an old document matters justifies the storage. Disposal isn't saving you much; retention isn't costing you much. Mark old records "post-retention" and box them; clear them every 5+ years if storage becomes an issue.
Incident-triggered paperwork.
Some paperwork is triggered by specific events — incidents, claims, disputes, regulatory follow-up. Most graduates operate for years without needing this; the few moments when something does happen, having the right paperwork produces the difference between contained problem and major operational disruption. emergencies.html Section 6 introduces incident reporting; this section covers the paperwork side in detail.
Common incident-triggered filings:
The CAAP self-reporting principle
For incidents that are CAAP-reportable, self-reporting before CAAP discovers via other means typically receives more favorable treatment than discovery via complaint or pattern. The cohort default approach:
- When in doubt, report. Over-reporting is administrative burden; under-reporting can be a serious regulatory issue.
- Report promptly. The 72-hour window for most incidents is a maximum, not a target. Same-day for serious situations.
- Honest factual report. Don't minimize; don't exaggerate; describe what happened and what was done. CAAP staff can usually identify reports that aren't straightforward.
- Document for your records. Keep copies of what was reported, when, and any CAAP response.
- Cooperate with follow-up. CAAP may request additional information or schedule a review. Respond promptly and completely.
A later cohort had two reportable incidents in the first 18 months across graduates. Both were handled with prompt self-reporting; no significant regulatory consequences resulted. The discipline of self-reporting is part of operating in good standing.
Cooperative dispute handling: most disputes resolve through honest communication. The cohort default escalation path:
- Direct communication: discuss the issue with cooperative leadership. Most disputes are misunderstandings or unmet expectations; clarification resolves them.
- Written summary: if discussion doesn't resolve, document the issue in writing — what each party understood, what was actually delivered, what each party wants. Often the writing process clarifies the actual disagreement.
- Barangay mediation: barangay captain or council can mediate informally. Common practice for community-level disputes; non-formal but effective.
- Mediation through cohort or partner-org: if structural issues, cohort engineering can sometimes help facilitate (especially for cooperative relationships originally introduced via cohort).
- Formal legal action: rare for cohort default operations; reserved for substantial disputes involving real money or material breaches. Consult lawyer before escalating.
Cohort experience: most disputes in the first 4 years across graduates were resolved at step 1 or 2. Steps 3-5 are rare; step 5 is rarer still. The relationship is the foundation; preserving it is usually possible if both parties want to.
Insurance claims: if you carry liability insurance and an incident occurs that might trigger a claim:
- Notify insurer promptly: most policies require notification within specified window (typically 7-30 days); delays can void coverage.
- Document thoroughly: photos, witness statements, incident report (per emergencies.html Section 6).
- Don't admit liability informally: any admission outside the formal claim process can complicate the insurer's response. Acknowledge that something happened; defer "fault" determination to the formal process.
- Cooperate with investigator: insurer typically conducts review; respond promptly and honestly.
- Document the resolution: claim outcome, any payments, lessons. Adds to your incident records.
Most cohort default operations never make insurance claims. The few that do typically involve property damage rather than personal injury. Maintaining insurance is for the rare significant incident; the routine incidents are self-funded from the cohort default repair reserve.
The bigger picture: paperwork during incidents is most useful when it builds on paperwork that was always being kept. Alumni with strong contemporaneous record-keeping (Section 3) and disciplined retention (Section 5) handle incident-triggered paperwork as extension of routine documentation. Alumni without that foundation scramble during incidents to create records that should have existed already.
Routine paperwork discipline is what makes incident-triggered paperwork manageable. It's also what makes BIR audits, CAAP inspections, and cooperative reviews go smoothly when they happen. The unglamorous routine pays off in the few high-stakes moments when documents matter most.