Methodology

How PSICph is built and verified

This page explains what the site uses as source material, how the page templates are assembled, and where the editorial boundaries are. The goal is a usable reference, not a thin copy of the official sources.

PSA overview page lists 519 classes, while the BSP practical workbook layer used here resolves to 520 distinct four-digit prefixes. PSA overview page lists 1360 subclasses, while the official BSP workbook used as the site's operational dataset currently exposes 1272 five-digit rows.

Source stack

What the site relies on

PSICph treats official Philippines source layers as the starting point. The PSA publication layer defines the classification structure, the practical workbook layer powers lookup and hierarchy reconstruction, and the BIR layer adds registration context where that context is useful to users.

Companion classifiers such as PSOC, PSCC and PSGC are handled the same way: official source first, practical navigation second, and no invented certainty where the source data is incomplete.

Page generation

How pages are assembled

Pages are built at compile time from checked data files. The templates combine hierarchy, code titles, summary explanations, related codes, FAQ, source notes and trust blocks. The site does not depend on a live database to answer standard lookups.

  • Only verified fields are rendered
  • Missing data causes the relevant block to disappear
  • Source-backed numbers are not replaced with estimates
  • Titles and descriptions are written to be useful to users first
Verification rules

What counts as verified

A page is considered verified when its code, title, hierarchy position and source note are supported by the current official layer used in the build. Crosswalks, risk score, professions and related code blocks are only shown when the corresponding data file contains real evidence.

The dedicated risk-score page documents the 7-factor model used on leaf pages. If the evidence file is missing or incomplete, the score block is omitted rather than guessed.

Open risk-score methodology

Correction policy

How updates are handled

If a source changes or a page is found to be unclear, the fix is to update the underlying data and rebuild the affected pages. The site prefers explicit source notes and correction paths over silent edits.

When a source conflict exists, the page should explain the conflict, not smooth it away. That is important for a regulated reference site where users need to know what is official, what is editorial, and what is only a navigational aid.

FAQ

Methodology questions

What sources does PSICph use first?

The site starts with the official PSA publication layer and the practical workbook layer, then adds BIR context and companion classifier pages where they improve lookup.

Why do some counts differ between pages?

Some source layers count sections and subclasses differently. The site shows that difference instead of hiding it, so users can see which layer powers search and which layer defines the official overview.

What happens when a field is missing?

If a page does not have enough verified data for a block, that block is omitted. The site does not invent a placeholder explanation or a fake number.

Contact us

Questions about the method or a source gap?

If you spot a missing source note, a stale title, or a data mismatch, send the page URL plus the source link you want checked. That makes the review much faster.

Email: kiber0101@gmail.com
Telegram: @Dondimonn