# Scoping – Kleiner Auftrag

> What belongs in a job description so the quote is accurate.

- [How to Brief a Developer: Template for Small Jobs](https://kleinerauftrag.de/en/scoping/how-to-brief-a-developer/): To brief a developer, write one page covering the goal, the current setup with system and version, the result you want, one or two testable acceptance criteria, what is out of scope, available access, deadline, budget range and who signs off. Send the same brief to every developer you ask, so the quotes you get back can actually be compared.
- [How to Write a Bug Report Your Developer Can Fix](https://kleinerauftrag.de/en/scoping/how-to-write-a-bug-report/): Write one report per bug with a short title, the exact URL, numbered steps to reproduce, what you expected, what actually happened, your device and browser with version, the time it happened and a screenshot or short video. That lets the developer reproduce the problem straight away instead of hunting for it on your bill.
- [Acceptance Criteria Examples for Small Software Jobs](https://kleinerauftrag.de/en/scoping/acceptance-criteria-examples/): Acceptance criteria are testable statements that define when a job is done. Good ones describe a starting situation, an action and an observable result with concrete values, for example: after submitting the form, the enquiry arrives in the sales inbox within five minutes. For a small software job, three to seven criteria are usually enough.

About this site: https://kleinerauftrag.de/en/about/