> 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/guides/everyday/submission-packs.md).

# Submission packs

An EOI or tender pack in an hour: the project sheets and CVs that fit, a capability statement, and a fee proposal, built in your firm's look.

A submission pack is what you send 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. tiny+ ranks your sheets and CVs against what the tender asks for, you choose and order them, and the pack is built as a PDF, a Word file or both, in your firm's own look. A **fee proposal** is the same idea for the price: a letter, the scope, the fee by stage and the terms, with the sheets and CVs you choose.

Both start from the project, and the files land on the project when they're built.

{% hint style="warning" %}
Submission packs, CVs, capability statements and fee proposals are invite only for now. Accounts we've invited see them under **Submissions**; other accounts don't see them yet. If you'd like to try them, [get in touch](https://crm.tiny.plus/help).
{% endhint %}

{% hint style="success" %}
This is a Pro plan feature, which an Account Admin turns on.
{% endhint %}

## Setting up

An Account Admin turns on **Project sheets** and **Submission packs** under [Account Settings -> Submissions](https://crm.tiny.plus/account/submissions), where every setting for them lives (see [Submissions settings](https://docs.tiny.plus/guides/everyday/document-templates.md)). [Set up submissions](https://crm.tiny.plus/submissions/setup), in the Submissions menu, then goes through the rest in order. Each step saves as you go and ticks itself off when it's done, so you can leave and come back. A step you're happy to leave as it stands, such as the plain look or the Standard cover, has **Mark this step as done** under it; **Not done yet** takes that back.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-a76a895862d7588bfa2b31fc524b4a326d713aa9%2Fsubmissions-setup.png?alt=media" alt="Set up submissions: a row of steps from Turn it on to Done, each with a tick when done, then the Turn it on step with the Project sheets and Submission packs cards, then Your look with the five layouts" width="979"><figcaption></figcaption></figure>

1. **Turn it on**: project sheets and submission packs.
2. **Your look**: a layout, your colours, a font and your logo. See [Submissions settings](https://docs.tiny.plus/guides/everyday/document-templates.md#look).
3. **Your cover**: the front page every pack starts with.
4. **Your fees**: fee templates and rate cards, for fee proposals.
5. **Sectors and services**: the tags your sheets and CVs are matched on.
6. **People**: who has the Submissions role, who has a CV, and asking the rest for one.
7. **Project sheets**: the projects won or delivered recently that have no sheet, with the person to ask for each.

Give the **Submissions** role to the people who write your bids, under Account Settings -> Users. They can change any sheet, CV and statement and build packs, as Records Admins can.

## Writing a pack

Open the project and click **Submission pack** at the top, or **Start a pack** in its Submission Pack panel. The pack opens with the project's client, sector, services, value band and due date filled in, and the best five sheets and three CVs already ticked.

### The ask

Say what the tender wants under **Brief**: the job, what they want to see, anything that decides it. Its words are matched on your sheets. Check the client, sector, services and value band, choose the layout (when your admin has offered more than one), the cover and its picture, and the sections the pack should have.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-3c7de693e7693668fb24466bf506c79ab3fcce81%2Fpack-ask.png?alt=media" alt="The pack&#x27;s first step: the title, what the tender asks for, the client, sector, services, value band, due date, the output, the sections, the contact on the last page, and the cover and its picture" width="915"><figcaption></figcaption></figure>

**Rank the sheets and CVs from the ask** ranks them again after a change, and keeps anything you ticked by hand.

### The project sheets and CVs

Each sheet and CV is listed best first, with its score and why it's there: the same client, the sector, a service, the value band, a recent year, an award, words from the ask. Tick what goes in and drag to change the order. A sheet not approved for external use, or the CV of someone who has left, is greyed out with the reason.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-56da9f3c65fca9840e86d299e854ed7037e7745f%2Fpack-candidates.png?alt=media" alt="The project sheets step: ten sheets best first, the top five ticked, each with its client, year, value band, the reasons it scored and its score; a sheet not approved for external use greyed out; and Order with AI" width="915"><figcaption></figcaption></figure>

**Order with AI** has the tiny+ AI engine read the ask and every sheet and CV, put them in the order that fits best, and tick the best. Its reason comes first on each one, and it says what the tender wants that none of your records shows, such as *no aquatic projects*.

### The capability statement

Choose an approved statement from your library to start from, or write one here. A blank line starts a paragraph and a line starting with `-` is a bullet. **Save to the library** keeps a good one for next time.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-54f0edfc09a10acb27f01cf1813103e8381ead21%2Fpack-statement.png?alt=media" alt="The capability statement step: an approved statement to start from, Save to the library, Draft from the chosen records, the statement, and the line saying which sheets and CVs it was drawn from" width="915"><figcaption></figcaption></figure>

**Draft from the chosen records** has the tiny+ AI engine write the statement from the sheets and CVs you ticked, in your firm's voice, using the tone of your nearest approved statement. Under it:

* **Drawn from** names the records it used.
* A yellow box lists anything it wrote that isn't in those records: a figure, a year, a name or an award. Check each one. Nothing is taken out for you.
* It also says what the tender asked for that your records don't show.

Once you type in the statement, it's yours, and the box goes.

### Building it

**Build the pack** checks it first: nothing chosen, a sheet without a picture, a statement left empty. The build runs on its own and takes a minute or so; you can leave the page. The side column shows how far it is, then **PDF** and **Word**. The files are added to the project's documents, and a post on the project says who built which version.

Change anything after a build and the pack says it's out of date until you build it again. Each build is a new version, and the earlier files stay on the project.

## On the project

The project's **Submission Pack** panel shows the pack and the fee proposal: their state, their files, and when and by whom they were last built.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-050f1e5c9b6203ecd67c04c4711febf1d5d0d360%2Fpack-panel.png?alt=media" alt="The Submission Pack panel on the Penrith day surgery: the pack built, with its files, and a Write a fee proposal link" width="780"><figcaption></figcaption></figure>

Every pack and fee proposal is listed under **Submissions -> Packs**, newest first, with its state and, for a proposal, its total.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-354b76bdd13d90b8c726b32a033b042775ccaca9%2Fpacks-list.png?alt=media" alt="The packs list: each pack and fee proposal with its project, kind, state, due date and when it was built" width="979"><figcaption></figcaption></figure>

The **Submissions due** dashboard item lists the proposals due in the next 30 days that have no pack, or whose pack is out of date.

## Fee proposals

A fee proposal is a priced proposal for a project: a letter, our understanding of the job, the scope of services by stage, the fee, the programme and the terms, with the sheets and CVs you choose and a schedule of rates when it charges time. It starts from one of your [fee templates](https://docs.tiny.plus/guides/everyday/document-templates.md#fee-templates).

Open the project and click **Fee proposal** at the top, or **Write a fee proposal** in its Submission Pack panel.

A fee proposal comes in two styles:

* **Full proposal**: a cover, then the letter, the proposal's sections and the sheets and CVs, each part on its own pages.
* **Fee letter**: a less formal letter on your letterhead, with no cover. Our understanding, the scope, the fee and the terms run on under the letter, and you sign at the end. Sheets, CVs and the capability statement are left out unless you **enclose** them; enclosed, they follow the letter on their own pages and are listed under your signature.

### Starting from the brief

Before a new fee proposal opens, tiny+ asks for the client's brief: the email or document asking for the fee. Drop in a PDF, a Word file or a saved email (.eml, or .msg from Outlook), or paste the email's text, and click **Save and start the proposal**. The brief is kept with the project under Documents, and the proposal lists it. There's no need to have one: **Skip** starts the proposal from your default template.

Where your default template sets the fee as a percentage of the construction value, the same screen shows that percentage under **The fee**. Change it there to start this proposal at another figure; the template keeps its own. When a brief is read, the percentage is on the review screen instead, beside the fee template it belongs to.

With an AI Assistants seat and [AI drafting](#ai-drafting) turned on, you can click **Read the brief and suggest a proposal** instead. The tiny+ AI engine reads the brief and suggests:

* a full proposal or a fee letter, and which fee template suits;
* the title, the client and when the proposal is due;
* the scope for each stage, and any stages the brief doesn't ask for;
* our understanding, and assumptions and exclusions the brief gives rise to;
* which of project sheets, CVs, a statement and a programme the client wants;
* the construction value, where the brief states one, and notes such as key dates and who to send it to.

Each suggestion is shown with the words of the brief it came from. Change any of them, untick the ones you don't want, then click **Start the proposal**; or **Start without these** to begin from the template alone. It never suggests a fee, and it changes only the proposal: the project record stays as it is. A stage you leave out has no scope and no fee lines.

A PDF or Word file attached to an email is read with it. Old Word files (.doc) are kept with the project but can't be read: save them as .docx or PDF. A confidential project's brief is never read.

### The proposal

Choose the style, the fee template, the bid team the proposal is for (on a project with [bid teams](https://docs.tiny.plus/guides/everyday/bid-teams.md)), who signs it, the rate card for time charges, the output and the sections. For a fee letter, the sections are split into what goes **in the letter** and what to **enclose**. Changing the style keeps the fee and the words; switching to a fee letter takes the sheets, CVs and statement out until you enclose them again. **Start again from this template** copies the template's stages, lines and words afresh, and keeps everything else, the style included.

### The fee

The fee is laid out by stage, the way the document prints it. Each line is a **lump sum**, a **percentage** (see below), a **time charge** (hours at a role's rate from the rate card), a **provisional** allowance, or an **exclusion**. Each change is worked out at once: the stage subtotals, the professional fee, provisional allowances, disbursements, tax and the total. **A percentage is of** says what percentage lines are worked on: the fee as a percentage of the construction value (4.5% of a $10m building is a $450,000 fee, and a 15% line is $67,500), the fee set on the project when the proposal was started, the construction value itself, or a figure you type. The template sets it, and you can change it, and the percentage or figure beside it, on each proposal. On a project with stages, each stage's heading shows when it starts and finishes. Changing those dates changes the stage itself, and they're the dates the programme page draws.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-7e0d4277288b08aa3753977c63900a38f0b53f4e%2Ffee-proposal-fee-step.png?alt=media" alt="The fee step: lines grouped by stage, each with its basis and figure, a time charge of 12 hours at the Associate rate and a provisional physical model, the stage subtotal, then the professional fee, provisional allowances, disbursements at 5%, GST and the total including GST" width="915"><figcaption></figcaption></figure>

**Add an option** makes a second fee for the same job, such as *Option B: reduced scope*, starting as a copy of the first. The primary option is the one written to the project.

### The words

The letter, our understanding, the scope of each stage and the terms (assumptions, exclusions, payment, variations and how long the proposal stands) come from the template with the project's name, client and figures filled in. Change them freely.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-db28f78df55f7db9e96a196d666b473f74b0b586%2Ffee-proposal-words.png?alt=media" alt="The words step: the letter, our understanding, the scope by stage and the terms" width="915"><figcaption></figcaption></figure>

### Building it, and the project's fee

A fee proposal is built as a pack is. The first build of each version also sets the fee where it belongs:

* on a project with [bid teams](https://docs.tiny.plus/guides/everyday/bid-teams.md), the fee of the team the proposal is for;
* on a project with stages, each stage's fee, and the project's fee from them;
* otherwise the project's fee, or new stages from the fee's groups when you ticked that.

The figure written is the professional fee, before disbursements and tax. The project's status and chance are never changed.

## AI drafting

**Order with AI** and **Draft from the chosen records** need an AI Assistants seat and **AI drafting for submissions** turned on by an Account Admin under [Account Settings -> AI](https://crm.tiny.plus/account/ai). They send the ask and the chosen sheets' and CVs' own text to the tiny+ AI engine. The same seat and switch let you have a fee proposal's [brief read](#starting-from-the-brief): its files and text are sent only when you ask for that. On a proposal started that way, ordering and drafting also draw on what you kept from the reading: our understanding, what the client asked to see, and the notes. Nothing confidential is sent, and nothing is built until you build it. Fair use is 40 orderings, drafts and readings a day for each person.

## Through the API and AI assistants

Packs and fee proposals have their own endpoints: see [Submission packs](https://docs.tiny.plus/api/endpoints/packs.md) and [Fee templates and rate cards](https://docs.tiny.plus/api/endpoints/fee-templates.md). An [AI assistant](https://docs.tiny.plus/guides/everyday/ask-and-ai-assistants.md) connected to tiny+ can find the sheets and CVs for a tender, draft a statement, build a pack (where the account allows changes) and read a fee proposal.

## Who can do what

|                                         | Who                                                                           |
| --------------------------------------- | ----------------------------------------------------------------------------- |
| Turn submission packs on                | Account Admins                                                                |
| Write and build packs and fee proposals | Records Admins and the Submissions role                                       |
| See the built files                     | Everyone who sees the project                                                 |
| Order with AI and Draft                 | People with an AI Assistants seat who can build packs, once AI drafting is on |
