> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/api/endpoints/packs.md).

# Submission packs

{% hint style="warning" %}
Submission packs are invite only for now, so these requests answer only for accounts we've invited; [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) carries `integrations.submissions`.
{% endhint %}

A submission pack is what a firm sends with an expression of interest or a tender: the project sheets most like the job, the CVs of the people who would do it and a capability statement, built as a PDF or a Word file in the firm's own template. A pack belongs to a project. tiny+ ranks the account's project sheets (a [record type](https://docs.tiny.plus/api/endpoints/records.md)) and [CVs](https://docs.tiny.plus/api/endpoints/cvs.md) against the pack's ask, the builder picks what goes in, and a build runs on its own and leaves the files on the project as documents.

A **fee proposal** is a pack of another kind: a priced proposal with a letter, the scope by stage, the fee, the programme and the terms, plus the sheets and CVs chosen as for a pack. It starts from one of the account's [fee templates](https://docs.tiny.plus/api/endpoints/fee-templates.md), and its first build writes the fee back to the project. The same endpoints serve both kinds; [Fee proposals](#fee-proposals) below says what a proposal adds.

Packs have endpoints of their own. They aren't a [record type](https://docs.tiny.plus/api/endpoints/records.md), so the list filters, search and the generic create, update and delete requests don't apply to them.

| Request                                       | What it does                                                                                                                                                             |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `GET /v2/packs?project_id={id}`               | [The packs on a project](#the-packs-on-a-project), newest first; `kind` picks packs, fee proposals or both.                                                              |
| `GET /v2/packs/{id}`                          | [One pack](#one-pack): its ask, its parts, its statement and its builds.                                                                                                 |
| `POST /v2/packs`                              | [Opens a project's pack](#open-a-pack), or its [fee proposal](#open-a-fee-proposal), making a draft when it has none.                                                    |
| `PATCH /v2/packs/{id}`                        | [Changes a pack](#change-a-pack): the ask, the parts, the statement; ranks again; queues a build. A proposal also takes [its words and its fee](#change-a-fee-proposal). |
| `GET /v2/packs/{id}/builds/{build_id}`        | [How far a build is](#how-a-build-is-going).                                                                                                                             |
| `GET /v2/packs/{id}/download?format=pdf`      | [A link to the built file](#download-a-built-pack).                                                                                                                      |
| `DELETE /v2/packs/{id}`                       | [Removes a pack](#remove-a-pack). Its files stay on the project.                                                                                                         |
| `GET /v2/fee_templates`, `GET /v2/rate_cards` | The account's [fee templates and rate cards](https://docs.tiny.plus/api/endpoints/fee-templates.md), read-only.                                                          |

As with [bid teams](https://docs.tiny.plus/api/endpoints/bid-teams.md): ids are numbers, text is plain, times are UTC (`2026-10-21T04:12:00Z`), a date with no time is `YYYY-MM-DD`, and errors are sentences, as `{"error": "That pack could not be found."}`.

## Is it switched on?

Submission packs come with the Pro plan and are off until an account admin turns them on under Account Settings → Submissions, which needs project sheets on too. [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) carries `integrations.submissions`, `true` while they're on. While they're off, every request here answers `403`:

```json
{
    "error": "Submission packs aren't available on this account."
}
```

## Who sees a pack

A pack is read through its project: the token's user sees a project's packs when they can open the project, and a [confidential](https://docs.tiny.plus/api/concepts/permissions.md#confidential-records) project they can't open answers `404`. Opening, changing and building a pack takes the Submissions role or Records admin, which `can_build` on a project's packs says; anyone else gets `403`. The built files are ordinary documents on the project, so anyone who sees the project can open them.

## The packs on a project

<mark style="color:blue;">`GET`</mark> `https://api.tiny.plus/v2/packs?project_id={{project_id}}`

`kind` is `pack` (the default, so an integration written before fee proposals sees what it always saw), `fee_proposal`, or `all` for both kinds newest first.

```bash
curl "https://api.tiny.plus/v2/packs?project_id={{project_id}}" \
  -H "Authorization: Bearer {{user_access_token}}"
```

```json
{
    "project": {
        "id": 195414,
        "name": "Tasman Health new wing",
        "record_status": "proposal",
        "proposal_due_date": "2026-11-07",
        "record_url": "https://crm.tiny.plus/project/195414"
    },
    "can_build": true,
    "records": [
        {
            "id": 1,
            "project_id": 195414,
            "kind": "pack",
            "fee": null,
            "name": "Tasman Health new wing",
            "due_date": "2026-11-07",
            "output": "both",
            "status": "built",
            "state": "stale",
            "state_display": "Out of date",
            "version": 1,
            "stale": true,
            "sheets": 2,
            "cvs": 1,
            "built_date": "2026-10-21T03:57:43Z",
            "built_by": {"id": 1, "name": "Nick Smith"},
            "files": {"pdf": {"id": 221163}, "docx": {"id": 221164}},
            "url": "/submission/195414",
            "created_date": "2026-10-21T03:55:31Z",
            "modified_date": "2026-10-21T04:12:00Z"
        }
    ]
}
```

`state` is one of `draft` (never built), `queued` and `building` (a build is on its way), `built`, `stale` (built, but a record in it, the ask or the templates changed since) and `failed`; `state_display` says it in words. `files` names the documents of the latest build, which [`GET /v2/attachments/{id}`](https://docs.tiny.plus/api/endpoints/attachments.md#open-a-document) or the [download link](#download-a-built-pack) below opens. `kind` is `pack` or `fee_proposal`; a proposal's `fee` is `{total, subtotal, currency, printed, options, written_version}`, its primary option's figures (see [the fee](#the-fee)), and `url` is the proposal's page.

## One pack

<mark style="color:blue;">`GET`</mark> `https://api.tiny.plus/v2/packs/{{id}}`

```bash
curl "https://api.tiny.plus/v2/packs/{{id}}" \
  -H "Authorization: Bearer {{user_access_token}}"
```

Everything a project's packs list, and:

| Field                                  | What it is                                                                                                                                                                                                                                                               |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `brief`                                | What the tender asks for, in the builder's words. The ranking matches its words on the sheets.                                                                                                                                                                           |
| `client`                               | `{id, name, deleted}` of the client company, or `null`.                                                                                                                                                                                                                  |
| `value_band`, `sector_tag`, `services` | The value band (`lt_1m`, `1_5m`, `5_20m`, `20_100m`, `gt_100m`), the sector tag's id and the service tags' ids the ranking matches on.                                                                                                                                   |
| `sections`                             | Which parts the document has, each `true` or `false`: `contents`, `statement`, `sheets`, `cvs` and `closing` for a pack; `letter`, `understanding`, `scope`, `fee`, `programme`, `terms`, `statement`, `sheets`, `cvs` and `closing` for a fee proposal.                 |
| `contact`                              | `{id, name}` of the team member named on the last page, or `null`.                                                                                                                                                                                                       |
| `cover`                                | `{id, name}` of the cover sheet the pack is built with (one of the account's, set up under Account Settings → Submissions → Look), or `null` when the account has none.                                                                                                  |
| `cover_image`                          | The stored path of a picture chosen for this pack's cover instead of the cover sheet's own, or `null`.                                                                                                                                                                   |
| `layout`                               | `{key, name, default}` of the layout the pack is drawn with: the account's default, or another an account admin approved for packs.                                                                                                                                      |
| `statement`                            | `text` as typed (a blank line starts a paragraph, a line starting with `-` is a bullet), `source` (`edited`, `draft`, or `library:{id}` for an approved [capability statement](https://docs.tiny.plus/api/endpoints/capability-statements.md)) and `edited`.             |
| `items`                                | The parts in order: `kind` (`sheet`, `cv` or `divider`), `record_id`, `name`, `included`, `position`, `score` and `reasons` from the ranking (such as `["same client", "2024", "mentions timber"]`), and `note` where one can't go in ("Not approved for external use"). |
| `errors`, `warnings`                   | What would stop a build, and what is worth a word before one: nothing chosen, a sheet with no picture.                                                                                                                                                                   |
| `builds`                               | Every build, newest first, as [How a build is going](#how-a-build-is-going) shows one.                                                                                                                                                                                   |
| `proposal`                             | A fee proposal's own part: its words, its scope and terms, and its fee. See [One fee proposal](#one-fee-proposal). A pack has no `proposal`.                                                                                                                             |

## Open a pack

<mark style="color:green;">`POST`</mark> `https://api.tiny.plus/v2/packs`

Answers the project's latest pack, or makes a draft when it has none: titled after the project, the client from the project's company, the due date from Proposal Due, the sector and services from the project's tags, and the best five sheets and three CVs already picked. Anything else sent with `project_id` is applied as [a change](#change-a-pack) would apply it.

```bash
curl -X POST "https://api.tiny.plus/v2/packs" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{"project_id": {{project_id}}, "brief": "Two-storey healthcare wing, timber structure, due in six weeks"}'
```

The answer is [the pack](#one-pack).

## Change a pack

<mark style="color:orange;">`PATCH`</mark> `https://api.tiny.plus/v2/packs/{{id}}`

Send any of:

| Field                                                                                                 | What it changes                                                                                                                                                                                                                                                                    |
| ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `name`, `brief`, `client_id`, `value_band`, `due_date`, `sector_tag`, `services`, `output`, `contact` | The ask. `services` is a list of tag ids; `output` is `pdf`, `docx` or `both`; `null` clears a field.                                                                                                                                                                              |
| `sections`                                                                                            | An object of the sections to turn on or off, such as `{"closing": false}`.                                                                                                                                                                                                         |
| `cover`, `cover_image`                                                                                | The cover sheet's id (one of the account's), and the stored path of one of the account's pictures to put on it for this pack; `null` goes back to the cover sheet's own.                                                                                                           |
| `layout`                                                                                              | The key of a layout approved for packs (as `layout.key` reads); `null` or `""` goes back to the account's default. A layout that isn't approved answers `400`.                                                                                                                     |
| `items`                                                                                               | The parts in the order wanted: a list of `{kind, record_id, included}`; a `{"kind": "divider", "title": "…"}` adds a page between them. Parts not named keep their place after the named ones. A sheet not approved for external use, or an archived CV, can't be included: `409`. |
| `statement_text`, `statement_source`                                                                  | The statement as typed, and where it came from (`edited` unless said).                                                                                                                                                                                                             |
| `rank`                                                                                                | `true` ranks the sheets and CVs against the ask again and picks the best; what was ticked by hand is kept.                                                                                                                                                                         |
| `build`                                                                                               | `true` queues a build of the pack as its `output` says. A build is refused (`409`) while one is queued or running, or while `errors` names something.                                                                                                                              |

```bash
curl -X PATCH "https://api.tiny.plus/v2/packs/{{id}}" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{"items": [{"kind": "sheet", "record_id": 62152, "included": true}, {"kind": "cv", "record_id": 219655, "included": true}], "build": true}'
```

The answer is [the pack](#one-pack); with `build`, it also carries `build`, the queued build.

## How a build is going

<mark style="color:blue;">`GET`</mark> `https://api.tiny.plus/v2/packs/{{id}}/builds/{{build_id}}`

A build takes ten seconds to a minute. Poll every few seconds until `status` is `built` or `failed`.

```bash
curl "https://api.tiny.plus/v2/packs/{{id}}/builds/{{build_id}}" \
  -H "Authorization: Bearer {{user_access_token}}"
```

```json
{
    "id": 2,
    "version": 1,
    "status": "built",
    "percent": 100,
    "step": "Done",
    "output": "both",
    "pages": 9,
    "bytes": 2359728,
    "warning": null,
    "error": null,
    "files": {"pdf": {"id": 221163}, "docx": {"id": 221164}},
    "queued_date": "2026-10-21T03:57:41Z",
    "started_date": "2026-10-21T03:57:41Z",
    "finished_date": "2026-10-21T03:57:43Z"
}
```

`step` says what the runner is doing ("Resizing images (4 of 9)", "Laying out the PDF"). A failed build says why in `error`, and the pack's last good version stands.

## Download a built pack

<mark style="color:blue;">`GET`</mark> `https://api.tiny.plus/v2/packs/{{id}}/download?format=pdf`

A short-lived link to the latest build's file, `format` `pdf` or `docx`, in the shape [a link to a file](https://docs.tiny.plus/api/endpoints/attachments.md#open-a-document) answers with, plus `version`. A pack not built yet, or not built in that format, answers `404`.

```bash
curl "https://api.tiny.plus/v2/packs/{{id}}/download?format=pdf" \
  -H "Authorization: Bearer {{user_access_token}}"
```

## Remove a pack

<mark style="color:red;">`DELETE`</mark> `https://api.tiny.plus/v2/packs/{{id}}`

Takes the pack off its project. The files its builds made stay on the project as documents.

```bash
curl -X DELETE "https://api.tiny.plus/v2/packs/{{id}}" \
  -H "Authorization: Bearer {{user_access_token}}"
```

```json
{
    "results": true,
    "project": {"id": 195414, "name": "Tasman Health new wing", "record_status": "proposal", "proposal_due_date": "2026-11-07", "record_url": "https://crm.tiny.plus/project/195414"}
}
```

## Fee proposals

A fee proposal is written on the web from a project's page (Fee proposal), from one of the account's [fee templates](https://docs.tiny.plus/api/endpoints/fee-templates.md): the template gives it the stages, the lines, the letter and the terms, with the project's name, client and figures filled in. The fee is one or more **options** (the primary first; an alternative is "Option B: reduced scope"), each a list of **lines** grouped by stage: a line is a lump sum, a percentage of the construction value, a time charge (hours by role, at the proposal's [rate card](https://docs.tiny.plus/api/endpoints/fee-templates.md#rate-cards)), a provisional allowance or an exclusion. Every figure comes back twice: as stored, and as the document prints it.

When a proposal is built, the primary option's professional fee (the lump, percentage and time lines, before disbursements and tax) is written to the project's fee, to its stages' fees where the lines sit on stages, or to its bid team's fee when the proposal is one team's; `written_version` on the option says which build did it. The API reads and changes a proposal's words and its primary option; alternative options are managed on the web.

### Open a fee proposal

<mark style="color:green;">`POST`</mark> `https://api.tiny.plus/v2/packs`

`kind` `fee_proposal` answers the project's latest fee proposal, or makes one when it has none. Four fields apply only when one is made: `template`, a fee template id (left out, the account's default); `bid_team`, the team the proposal is for on a project bid through [bid teams](https://docs.tiny.plus/api/endpoints/bid-teams.md); `headline`, the fee the template's shares are worked out from (left out, the team's fee, else the project's); and `percent_of_rate`, the percentage of the construction value the fee is, in place of the template's, where the template's `percent_of` is `value_rate`. Anything else sent is applied as [a change](#change-a-fee-proposal) would apply it.

```bash
curl -X POST "https://api.tiny.plus/v2/packs" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{"project_id": {{project_id}}, "kind": "fee_proposal", "headline": 240000}'
```

The answer is [the proposal](#one-fee-proposal).

### One fee proposal

<mark style="color:blue;">`GET`</mark> `https://api.tiny.plus/v2/packs/{{proposal_id}}`

```bash
curl "https://api.tiny.plus/v2/packs/{{proposal_id}}" \
  -H "Authorization: Bearer {{user_access_token}}"
```

Everything [one pack](#one-pack) carries, with `kind` `fee_proposal`, its `sections`, and `proposal`:

```json
{
    "id": 224,
    "project_id": 181651,
    "kind": "fee_proposal",
    "name": "Fee proposal: Northgate Library, Stage 2",
    "status": "built",
    "state": "built",
    "version": 1,
    "fee": {"total": 277200, "subtotal": 240000, "currency": "AUD", "printed": "$277,200", "options": 1, "written_version": 1},
    "url": "/fee_proposal/181651",
    "proposal": {
        "style": "proposal",
        "template": {"id": 73, "name": "Harbourside standard"},
        "rate_card": {"id": 58, "name": "Harbourside rates 2026", "retired": false},
        "bid_team": null,
        "signatory": {"id": 181484, "name": "Priya Natarajan"},
        "letter_text": "Thank you for asking Harbourside Studio to put forward a fee for Northgate Library, Stage 2. …",
        "understanding_text": "Northgate Council is looking for a design team for Northgate Library, Stage 2. …",
        "scope": [
            {"position": 1, "name": "Concept design", "text": "Site and brief analysis, concept options, a preferred concept and an order-of-cost estimate."},
            {"position": 2, "name": "Design development", "text": "The preferred concept developed: planning, structure, services and materials resolved to the level needed for approvals."}
        ],
        "terms": {"assumptions": "Our fee assumes the scope described above…", "exclusions": "Authority fees and charges…", "payment": "Fees are invoiced monthly…", "variations": "Work outside the scope above…", "validity_days": 30},
        "programme_on": true,
        "fee": {"total": 277200, "subtotal": 240000, "currency": "AUD", "printed": "$277,200", "options": 1, "written_version": 1},
        "fees": [
            {
                "id": 200,
                "name": "Fee",
                "is_primary": true,
                "grouping": "stages",
                "percent_of": "project_value",
                "percent_of_amount": null,
                "disbursement_kind": "percent",
                "disbursement_value": 5,
                "note": null,
                "currency": "AUD",
                "subtotal": 240000,
                "provisional_total": 3500,
                "disbursements": 12000,
                "tax": 25200,
                "total": 277200,
                "written_version": 1,
                "lines": [
                    {"id": 1401, "stage_id": null, "stage_name": "Concept design", "stage_position": 1, "position": 1, "title": "Professional fee", "basis": "lump", "percent": null, "amount": 33120, "hours": null, "role": null, "rate": null, "note": null, "amount_calc": 33120},
                    {"id": 1402, "stage_id": null, "stage_name": "Concept design", "stage_position": 1, "position": 2, "title": "Council and community workshops", "basis": "time", "percent": null, "amount": null, "hours": 12, "role": "Associate", "rate": 240, "note": null, "amount_calc": 2880},
                    {"id": 1403, "stage_id": null, "stage_name": "Concept design", "stage_position": 1, "position": 3, "title": "Physical model", "basis": "provisional", "percent": null, "amount": 3500, "hours": null, "role": null, "rate": null, "note": "A 1:200 model of the preferred concept.", "amount_calc": 3500}
                ],
                "printed": {
                    "option": "",
                    "basis_note": "",
                    "groups": [
                        {"key": "1", "stage_id": null, "name": "1. Concept design", "lines": [
                            {"i": 0, "title": "Professional fee", "basis": "", "figure": "$33,120", "note": "", "excluded": false, "provisional": false},
                            {"i": 1, "title": "Council and community workshops", "basis": "12 h × $240/hour, Associate", "figure": "$2,880", "note": "", "excluded": false, "provisional": false},
                            {"i": 2, "title": "Physical model", "basis": "", "figure": "$3,500", "note": "A 1:200 model of the preferred concept.", "excluded": false, "provisional": true}
                        ], "subtotal": "$36,000", "provisional": "$3,500"}
                    ],
                    "subtotal": "$240,000",
                    "provisional_total": "$3,500",
                    "disbursements": "$12,000",
                    "disbursement_note": "5% of the fee",
                    "tax": {"label": "GST", "rate_text": "10%", "amount": "$25,200"},
                    "total": "$277,200",
                    "currency": "AUD",
                    "note": "",
                    "warnings": []
                }
            }
        ]
    }
}
```

| Field                               | What it is                                                                                                                                                                                                                          |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `style`                             | `proposal`, a full proposal with a cover, or `letter`, a fee letter: no cover, the fee and terms running on under the letter, signed at the end, with the statement, sheets and CVs enclosed after it when their `sections` are on. |
| `template`                          | `{id, name}` of the [fee template](https://docs.tiny.plus/api/endpoints/fee-templates.md) the proposal started from, or `null`.                                                                                                     |
| `rate_card`                         | `{id, name, retired}` of the [rate card](https://docs.tiny.plus/api/endpoints/fee-templates.md#rate-cards) its time-charge lines take their rates from, or `null`.                                                                  |
| `bid_team`                          | `{id, company}` of the [bid team](https://docs.tiny.plus/api/endpoints/bid-teams.md) the proposal is for, or `null`. Its fee goes to that team when the proposal is built.                                                          |
| `signatory`                         | `{id, name}` of the team member who signs the letter and the closing page, or `null`.                                                                                                                                               |
| `letter_text`, `understanding_text` | The letter and "Our understanding", as typed: a blank line starts a paragraph, a line starting with `-` is a bullet. The template's tokens were filled in when the proposal started.                                                |
| `scope`                             | The scope of services, one entry per stage in the order printed: `{position, name, text}`.                                                                                                                                          |
| `terms`                             | `{assumptions, exclusions, payment, variations, validity_days}`: the four texts and how many days the proposal stands (`0` prints no validity line).                                                                                |
| `programme_on`                      | Whether the programme page is in, when the project's stages have expected dates.                                                                                                                                                    |
| `fee`                               | The primary option's figures: `total`, `subtotal`, `currency`, `printed` (the total as the document prints it), `options` (how many options the proposal has) and `written_version`.                                                |
| `fees`                              | Every option in order, the primary first. See [The fee](#the-fee).                                                                                                                                                                  |

#### The fee

Each entry of `fees` is one option:

| Field                                     | What it is                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id`, `name`, `is_primary`                | The option. The primary is the one written to the project.                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| `grouping`                                | `stages` (lines grouped by stage) or `flat` (one list).                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| `percent_of`, `percent_of_amount`         | What a percentage line is a percentage of: `project_value`, the project's construction value; `value_rate`, a fee that is `percent_of_rate` percent of the construction value, so each percentage line is its share of that fee; `project_fee`, the fee the project (or the bid team) had when the proposal was started, kept in `percent_of_amount`; or `typed`, the amount in `percent_of_amount`. Setting `project_fee` without an amount takes the fee the project has now.                   |
| `disbursement_kind`, `disbursement_value` | `none`, `percent` (of the fee, the value a percentage), `at_cost` or `amount` (the value an amount).                                                                                                                                                                                                                                                                                                                                                                                              |
| `note`                                    | A note printed under the fee table, or `null`.                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| `currency`                                | The project's fee currency: every figure is in it.                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| `subtotal`                                | The professional fee: the lump, percentage and time lines added up. This is what a build writes to the project.                                                                                                                                                                                                                                                                                                                                                                                   |
| `provisional_total`                       | The provisional allowances, which sit outside the fee.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| `disbursements`, `tax`, `total`           | Disbursements as worked out (`0` when at cost), tax at the account's rate (`0` when the account prints fees without tax), and the total.                                                                                                                                                                                                                                                                                                                                                          |
| `written_version`                         | The proposal version whose build wrote this option's fee to the project, or `null` while none has.                                                                                                                                                                                                                                                                                                                                                                                                |
| `lines`                                   | The lines in order: `stage_id` (one of the project's stages) or `stage_name` and `stage_position` (a stage of the proposal's own), or neither (Other services); `title`; `basis` (`lump`, `percent`, `time`, `provisional` or `excluded`); the figure that goes with the basis, `amount`, `percent` or `hours` and `role`; `rate`, the hourly rate as it was when the line was last changed (read-only: it follows the rate card); `note`; and `amount_calc`, what the line comes to (read-only). |
| `printed`                                 | The option as the document prints it: `groups` with each line's `figure` and `basis` in words ("12 h × $240/hour, Associate"), each group's `subtotal`, then `subtotal`, `provisional_total`, `disbursements` and `disbursement_note`, `tax` (`{label, rate_text, amount}` or `null`), `total`, and any `warnings` ("no construction value"). Every amount is a string with the currency's symbol.                                                                                                |

### Change a fee proposal

<mark style="color:orange;">`PATCH`</mark> `https://api.tiny.plus/v2/packs/{{proposal_id}}`

A proposal takes everything [a pack's change](#change-a-pack) takes but `brief`, `value_band`, `sector_tag`, `services` and `contact`, which it has no use for, and also:

| Field                                               | What it changes                                                                                                                                                                                                                                                                                                                                                                                              |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `style`                                             | `proposal` or `letter`. Changing it to `letter` turns the `statement`, `sheets` and `cvs` sections off, and back to `proposal` turns them on; send `sections` in the same request to choose otherwise.                                                                                                                                                                                                       |
| `signatory_user`, `rate_card_id`, `bid_team_id`     | Who signs (an active team member's id), which rate card the time-charge lines use (every line's `rate` follows), and which bid team the proposal is for; `null` clears.                                                                                                                                                                                                                                      |
| `letter_text`, `understanding_text`, `programme_on` | The words, and whether the programme page is in.                                                                                                                                                                                                                                                                                                                                                             |
| `scope`                                             | The whole scope, a list of `{position, name, text}`.                                                                                                                                                                                                                                                                                                                                                         |
| `terms`                                             | An object of any of `assumptions`, `exclusions`, `payment`, `variations` and `validity_days`.                                                                                                                                                                                                                                                                                                                |
| `fee`                                               | The primary option: any of `name`, `grouping`, `percent_of`, `percent_of_amount`, `percent_of_rate`, `disbursement_kind`, `disbursement_value`, `note`, and `lines`, the whole list of lines as [The fee](#the-fee) reads them, without `id`, `rate` or `amount_calc`. A line on one of the project's stages sends `stage_id`; one on a stage of the proposal's own sends `stage_name` and `stage_position`. |
| `restart`                                           | `true` starts the proposal again from its own template, or a fee template's id starts it from that one: the words, the scope, the terms and the fee are copied afresh; the style, the name, the client, the cover, the output, the signatory and the chosen sheets and CVs stay.                                                                                                                             |

A pack (`kind` `pack`) refuses these fields with `400`, naming them. `sections` takes a proposal's section names; `programme` on or off also sets `programme_on`.

```bash
curl -X PATCH "https://api.tiny.plus/v2/packs/{{proposal_id}}" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{"fee": {"lines": [{"stage_name": "Concept design", "stage_position": 1, "title": "Professional fee", "basis": "lump", "amount": 36000}, {"stage_name": "Documentation", "stage_position": 2, "title": "Professional fee", "basis": "lump", "amount": 84000}, {"title": "Physical model", "basis": "provisional", "amount": 3500}]}}'
```

The answer is [the proposal](#one-fee-proposal), its figures worked out again.

## Errors

| Status | When                                                                                                      |
| ------ | --------------------------------------------------------------------------------------------------------- |
| `400`  | A field is not what it should be, nothing was sent to change, or a pack was sent a fee proposal's fields. |
| `403`  | Submission packs aren't on for the account, the token is read-only, or the person may not build packs.    |
| `404`  | No such pack, or one on a project the person can't open.                                                  |
| `409`  | A build is already on its way, something stops a build, or a part can't go in.                            |
