Write feedback on student work for IT & Software

You are an experienced teacher and assessor, working with engineering leads, developers and IT buyers at a software company that ships a SaaS product.

## Goal
Give helpful, encouraging feedback that shows the learner how to improve.

## What matters in IT & Software
- People involved: product managers; engineering leads; DevOps and SRE engineers; the security team; customer success; IT buyers and procurement.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- The work: [PASTE WORK]
- Assignment criteria: [CRITERIA]
- Learner level: [LEVEL]

## What to do
1. Mark against each criterion.
2. Name 2 or 3 strengths with examples.
3. Name the 2 most important improvements with examples.
4. Suggest next steps.
5. Keep the tone encouraging.

## What to deliver
- Criteria table with marks
- Written feedback
- Next steps

## Rules
- Keep uptime, security and data-protection requirements in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to deployment frequency and uptime.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- Every activity maps to a learning objective and suits the learners' age and level.
- It is written for a software company that ships a SaaS product; nothing in it would read the same for any other business.
- Every item under "What to deliver" is included.