# Project proposal: [specific question or process]

Draft date: [date] · Version: [number]

Organization and department: [name and unit]

Partner contact: [name, role, email]

Faculty lead: [name]

Proposed arrangement: [faculty-led semester project / full-time industry placement / preparatory review]

## Purpose

[Describe the current process and the specific difficulty. State who will use the result and what task or decision it supports. Identify whether this need was stated by the partner or is still a proposal for discussion.]

## Agreed scope

[Define the business unit, users, records, period and question covered. Identify the minimum useful deliverable. State a small number of explicit exclusions where needed to avoid ambiguity.]

## Available information and access

| Item | Agreed detail |
|---|---|
| Sources | [Files, systems, documents or interfaces] |
| Definitions and coverage | [Fields, record meaning, date range, known gaps] |
| Authorization | [Responsible data owner and permission status] |
| Working environment | [Where information and code will be held] |
| Conditions | [Permitted uses, confidentiality, retention and access removal as applicable] |

## Work and deliverables

| Work | Deliverable | Review or completion measure |
|---|---|---|
| [Initial review] | [Data or workflow assessment] | [What must be established to proceed] |
| [Development or analysis] | [Specific report, code, dataset or prototype] | [Agreed reconciliation, user tasks, comparison or evaluation] |
| [Handover] | [Files, documentation and demonstration] | [Recipient can locate and use the agreed output] |

Assessment measures describe how the work will be judged. Do not guarantee a model accuracy, cost saving or business improvement before it has been evaluated.

## Schedule and responsibilities

Start and end dates: [dates, including dependency on access]

Milestones: [sample review, confirmed scope, initial output, interim review, handover]

Partner responsibilities: [process explanation, access arrangements, review time, day-to-day supervision for a placement]

Program responsibilities: [faculty review, student assignment if confirmed, academic supervision and scheduled reviews]

Student responsibilities: [agreed work, progress records, questions and delivery]

## Costs and practical arrangements

[Specify compensation for a placement, if applicable; software, hosting, purchased data, travel or other costs; and who is responsible. State which items remain unresolved. Do not infer that faculty-led work is automatically free.]

## Ownership, use and support

[Record the applicable agreement for code, data and deliverables. Specify whether a student may show any part in a portfolio or presentation. Identify prototype versus operational status, the intended maintainer and the agreed extent of support after the end date.]

## Dependencies and scope changes

[List the few dependencies that materially affect delivery. Identify who agrees to changes. If required data is unavailable, specify whether to pause, complete an agreed preparatory output or revise the project.]

## Confirmation

Partner scope reviewer: [name and date]

Faculty scope reviewer: [name and date]

Outstanding institutional or administrative arrangements: [items or none]

Student assignment and start confirmed: [status and date]

This scope document records the intended work. It does not replace any institutional agreement required for the arrangement.