Why event certificates in the Philippines are always late, and how to issue them in 72 hours
What CPD providers, professional societies and universities in the Philippines actually owe attendees after an event, why certificates slip by weeks, and the close-out workflow that ships them in 72 hours.
- By
- Viron Gil Estrada
- Published
- Read
- 7 min
If you have ever run a conference, a CPD seminar or an alumni forum in the Philippines, you know the pattern. The event goes well. Everyone goes home. Then the emails start: "Where is my certificate?" Three weeks later, the most senior person on the committee is still in Canva at 11 pm, retyping names from a sign-in sheet.
I have been an event director six times across four institutions in seven years, from a children's science workshop to a 795-registrant AI summit at UP Diliman, and the close-out was late every single time. This article is about why that happens, what you actually owe people after an event, and the workflow I now use to get certificates, the attendance record and the sponsor report out within 72 hours.
What an organiser owes after the event
Three constituencies are waiting the moment the last talk ends.
- Attendees want a certificate, spelled the way they spelled their own name, in their inbox.
- The board or the accrediting body wants an attendance record that survives an audit: who registered, who actually showed up, when, and in which sessions.
- Sponsors want proof that every deliverable they paid for was delivered: the logo on four emails, the booth, the two social posts, the speaking slot.
For PRC-accredited CPD providers none of this is optional. Under PRC Resolution No. 1948, s. 2025, effective 1 March 2025, applications for accreditation of a CPD program must be filed at least 30 working days before the activity through the CPDAS portal, and providers must issue certificates of attendance and keep the records that back them. The question is never whether the close-out gets done. It is only how many of your senior people it eats every time.
Why certificates are always late
Late certificates are not a discipline problem. They are a data problem that lands on the wrong person at the wrong time.
- Registration and attendance live in different places. Registration is in a form export. Attendance is on a paper sign-in sheet, a QR scan log, or someone's memory. Reconciling the two is the first job, and nobody scoped it.
- Names arrive dirty. "Ma. Cristina", "Maria Cristina" and "MA CRISTINA" are the same person, and she will notice if the certificate gets it wrong. Manual spelling checks are where the weekends go.
- The people who can approve are the people who are exhausted. Certificates need a sign-off. The sign-off sits with the chair, who just ran the event.
- The sponsor report is a different document with the same inputs. It gets done last, or not at all, which is why sponsors do not renew.
At Gen AI to Z in March 2026 we had 795 registrations and 341 people checked in, a 42.9 percent show rate. Most Philippine organisers do not know their own show rate because nobody reconciles registration against the door. That number alone changes the catering budget for the next event.
What a 72-hour close-out looks like
The fix is to treat the close-out as a pipeline that starts the moment the event ends, with the machine doing the reconciliation and a human doing only the decisions.
| Step | Owner |
|---|---|
| Ingest registration exports, sign-in sheets, QR scan logs and the photo dump | System |
| Reconcile attendance, deduplicate, flag mismatches and unreadable names | System |
| Generate certificates from the organiser's own template, one per qualified attendee | System |
| Deliver by email, track bounces, run the re-issue queue for corrections | System |
| Compile the close-out report and tick off the sponsor deliverable checklist | System |
| Draft the recap post, select photos, cut a 30-second vertical | System |
| Approve the name list before a single certificate goes out | Human |
| Decide what belongs in the sponsor report | Human |
| Own the 72-hour promise | Human |
The certificate system behind this was first built for Vibe Coders PH and is now part of Takits, the events platform I am building in public. Each certificate has a unique human-readable code, a public verification page anyone can open, a revocation flag that stops a withdrawn certificate from verifying, a PDF drawn from the record rather than a pre-rendered image, and a native LinkedIn "Add to Profile" link.
What the manual version actually costs
For a 300-attendee event, a manual close-out is realistically 40 to 60 hours of work: reconciling lists, generating and checking 300 certificates, emailing them, chasing corrections and building the report. Philippine event agencies bill a median of roughly USD 25 an hour, about PHP 1,450, according to the agency listings on Clutch and GoodFirms. That puts the manual close-out at PHP 58,000 to 87,000 of billable time, before the cost of the senior person doing it instead of their real job.
That arithmetic is what sets the price of my Event Close-Out offer: PHP 55,000 for a single event up to 300 attendees, PHP 85,000 up to 1,000, or a PHP 35,000 monthly retainer for organisations running four or more events a year. The full list is in pricing.md.
What this is not
A scope is only real if it says where it stops.
- It is not on-site event management, production, venue, suppliers or food.
- It is not camera work on the day. We work from your footage, or bring a shooter in at cost.
- It is not paid advertising.
- It is not PRC or CPD filing. The records are prepared in the shape the filing needs. The accredited provider files them. That line stays on the page, not in the fine print.
If your calendar has the same events on it every year and the certificates are always late, tell me about the next one. Fifteen minutes. If it is not useful, I will say so.