Know what a client's public job presence actually shows.

What you can see

• Whether a role is currently visible on the sources GhostPost observes, and when it was last observed.
• Postings observed as reappearing across observation periods.
• Differences between what one configured source displayed and what another displayed.
• Requirement records that exist in the jurisdiction a posting names, with citation and source.
• A clear record of which sources could not be read during a given observation.

Why it matters

• Client conversations go better with a dated, sourced observation than with a claim.
• Your team can see public drift in a client's roles without asking the client to self-report.
• Observation records are non-judgmental by construction, so sharing one does not accuse anyone of anything.

How firms use it

• Watch client sources and review the delta since the last client conversation.
• Share a read-only record link, or export an evidence packet with provenance intact.
• Scope workspace access per client engagement, with seats and revocable API keys.

What GhostPost does not do

This boundary is not a limitation. It is what makes the record usable as evidence.

• Determine whether an organization is compliant
• Determine whether a law or requirement applies
• Declare a violation, or that anyone is liable
• Provide legal advice or legal opinions
• Assign severity or risk
• Produce a score of any kind — no composite score, no 0–100, no letter grade, no ranking
• Assign, track, or execute remediation
• Track resolution or assign owners
• Remove postings or send takedown demands
• Run notice-to-cure clocks or enforce requirements

GhostPost observes and documents. Qualified professionals and the systems an organization already runs decide what the evidence means and what happens next.