DRAFT WEBSITE PREVIEW · Subject to Sam’s review · Not a final website
CLEARER EVIDENCE FOR SCHOOL DECISIONS

HOW WE WORK

Agree on the question.
Test the evidence.
Make the next step clear.

  1. Define the decision together.

    Agree on the question, the people or periods included, and who will use the answer. Clarify terms such as new, enrolled and retained before comparing totals.

  2. Start with existing systems.

    Review the relevant reports and supported options in your SIS and other approved sources. Check date meanings, historical coverage and counting rules.

  3. Reconcile and explain.

    Test the result against available independent evidence. Make differences and limitations visible, then explain what the analysis supports and what remains unknown.

  4. Deliver a process your staff can use.

    Agree on the format, documentation, training and ongoing responsibilities. More development is a separate decision based on the evidence and your priorities.

Enrollment Measurement Feasibility Assessment

One question. An agreed scope. A fixed price.

This starting service establishes whether your existing records can support a defined enrollment measure. You receive:

  • A clear definition and map of the relevant sources and historical coverage.
  • A bounded, reproducible reporting test or a precise explanation of the missing evidence.
  • A recommendation: use an existing report, request a supported vendor query, undertake separately scoped implementation, improve future collection or stop.
  • A review with your team and usable documentation.

The scope, price and delivery dates are agreed in writing before work. Implementation and any paid vendor services require separate approval. A finding that current evidence cannot support the requested historical answer is a valid assessment result.

Handle school information deliberately.

Begin with the question and aggregate examples where possible. Any record-level work uses agreed fields and school-approved access and storage. Shared reporting and identifying reconciliation serve different audiences and should be kept separate.

Implementation scopes specify documentation, source files and usage rights, account ownership, backups, staff training and any continuing software or support costs.

Start with a manageable scope.

Discuss an assessment