Back to Policy Scan

    Example · L1 Policy Scan report

    What an L1 reading looks like in practice.

    This is a fictional example report. It shows the structure, tone and scope of an L1 deliverable — not a real customer assessment. The example contains no personal data.

    Document type
    HSE handbook (excerpt)
    Sector
    Professional services · 250 employees (fictional)
    Analysed as
    Governance text — not individual case
    Reviewed by
    A person — L1
    Scope
    One document · three findings · one suggested rewrite
    Version
    Example · not customer data

    Sydera reviews bounded governance documents and makes visible what the text documents, what is unclear, and what the organisation must validate. Sydera does not assess people, rank organisations, or establish actual practice, legal compliance, certification, or validity.

    Three prioritised findings

    01Work environment

    Reactive accommodation dominates

    Finding
    The accommodation chapter starts with «when an employee reports a need». There are few descriptions of systematic, predefined measures that work without the individual having to ask.
    Impact
    The organisation leans on individual reporting to meet its prevention duty — a weakness for both work environment and privacy.
    Recommendation
    Define at least three pre-established, always-available measures per identified risk area, and link them to a line of responsibility without requiring individual documentation.
    02Privacy (GDPR art. 9)

    Indirect prompting for health data

    Finding
    The routine asks managers to document «reason for accommodation» in a shared case-management system. The phrasing may pull managers toward registering health or diagnosis data the organisation has no basis to process.
    Impact
    Risk of processing special categories of personal data without a legal basis.
    Recommendation
    Replace «reason» with «category of adjustment» and remove free-text fields. Needs are documented at system level, not per person.
    03Universal design

    Solutions described as exceptions, not design

    Finding
    Low-threshold resources are consistently referred to as «special measures» and «individual support» rather than part of default access.
    Impact
    Reinforces stigma and makes it harder to demonstrate systematic universal design in audit or ESRS S1 reporting.
    Recommendation
    Refactor the language: «standard available resource» instead of «individual accommodation». Move selected measures from the exceptions chapter into the main chapter on workplace design.

    Suggested rewrite — for finding 02

    As written
    “The manager documents the reason for accommodation in the case-management system.”
    Suggestion
    “The manager records the category of adjustment (working hours, tasks, equipment, premises) — not the reason. No free text. Needs beyond the categories are solved in the arrangement, not in the file.”

    One suggestion per document. You decide whether it fits, and whether it matches practice.

    Recommended next steps

    What organisations typically do after L1.

    1. 01Update language and structure in the policy's first three chapters.
    2. 02Remove free-text fields for health-related documentation.
    3. 03Define two–four standard measures per identified risk area.
    4. 04Consider an L2 engagement to review the updated policy against the routines. Whether practice follows the text is for you to validate.
    Start your own L1

    Example · no actual customer, no personal data. L1 is not legal advice and does not replace internal HSE, HR or legal processes.