# Your software project brief

Blank planning template from Culvion Technologies. A rough description is enough to begin. This is not an order or a quotation. No information is sent by downloading it.

## The problem

What happens today? Where is the difficulty? What information or examples support that description?

Your notes:

## Users and tasks

Who will use the software? What does each person need to complete? Who can make decisions about the workflow?

Your notes:

## First release and exclusions

Essential journeys for the first version. Later ideas and work that should remain outside scope.

Your notes:

## Existing systems and data

Current products, editions, records, files and connections. Who owns each source? What access and permissions need checking?

Your notes:

## Failure and approval paths

What happens when information is missing, a system is unavailable or a decision needs approval?

Your notes:

## Acceptance

What observable checks will show that the agreed work is ready? Include access boundaries, devices, keyboard use and error handling as relevant.

Your notes:

## Budget and timing

Range and currency if known; why a deadline matters; which assumptions need assessment.

Your notes:

## Handover and ongoing ownership

Source code, accounts, hosting, documentation, training, monitoring and support responsibilities to agree.

Your notes:

## Open questions

What needs discovery before a reliable proposal can be prepared?

Your notes: