What this guide helps with
Different answers come from different evidence. Aggregate counts describe the whole filtered inventory; sampled listings describe visible or inspected listings; job-source facts come from the individual listing.
Decision guides
What partner feeds, sampled listings, aggregate counts, and job-source facts mean on puntWork pages.
Different answers come from different evidence. Aggregate counts describe the whole filtered inventory; sampled listings describe visible or inspected listings; job-source facts come from the individual listing.
Full-scope counts are strongest for market size, city alternatives, and category mix. Sampled text is useful for requirements like language, shifts, licences, remote work, and training, but should stay labeled as sampled.
When a field is missing, treat it as unknown rather than bad. On puntWork, sampled signals should stay labeled, and missing source fields should stay visible instead of being hidden behind confident wording.
These labels are the bridge between job listings and the decision guides. They tell you how strong the underlying evidence is before you act on it.
How to read source pay values, salary ranges, missing pay, and sampled salary coverage without over-trusting a single listing.
How to use inventory deltas between nearby cities and regions when the current page is too narrow.
A practical checklist for checking known, missing, and stale job facts before leaving puntWork for a partner application page.
How puntWork uses feed refreshes, dateModified, datePosted, and validThrough signals to keep Belgian job pages current.
How to interpret Dutch, French, English, and bilingual signals in Belgian job listings without over-reading sampled text.
How to compare interim, temporary, fixed-term, permanent, and recruitment-agency listings on puntWork.
How puntWork reads remote, hybrid, and telework wording in Belgian job listings.
What happens when a candidate clicks Apply, why puntWork uses a redirect, and what to verify on the partner page.