> 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/cvs-and-project-experience.md).

# CVs and project experience

Keep your firm's experience ready for tenders: a sheet for each project worth showing, a CV for each person, and capability statements you can reuse.

Every tender asks the same three things: what you've done that's like this job, who would do the work, and why you. tiny+ keeps the answers where your work already lives. A **project sheet** describes a project the way a client should read it. A **CV** describes a person the same way. A **capability statement** is a page in your own words that you can reuse from one tender to the next.

Once they're in tiny+, a [submission pack](https://docs.tiny.plus/guides/everyday/submission-packs.md) picks the ones that fit a tender and lays them out in your firm's look, as a PDF or a Word file.

{% hint style="warning" %}
CVs, capability statements and submission packs are invite only for now. Accounts we've invited see them under **Submissions**; other accounts see only project sheets there. 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 %}

## Turning it on

An Account Admin turns on **Project sheets** and then **Submission packs** under [Account Settings -> Submissions](https://crm.tiny.plus/account/submissions). That adds a **Submissions** menu with your project sheets, CVs, capability statements and packs. [Set up submissions](https://crm.tiny.plus/submissions/setup) then walks through everything a firm needs before its first pack, one step at a time. See [Submission packs](https://docs.tiny.plus/guides/everyday/submission-packs.md#setting-up).

## Project sheets

A project sheet belongs to a project. Open the project, find its **Project Sheets** panel, and click **+ New project sheet**. The sheet starts with the project's name, client and pictures, and you write the rest: a summary of a sentence or two, the description, the completion year, the value band, the location and size, and any awards.

One sheet can cover several projects: the stages of one job kept as separate projects, say, or a run of schools for the same client. Edit the sheet and add them under **Other projects**, below its main project. The sheet then shows in each of those projects' **Project Sheets** panels, none of them is listed as still needing a sheet, and their pictures are offered to the sheet alongside the main project's. The sheet still takes its client and location from the main project. While you edit the sheet, the small arrow beside the main project and beside each other project opens that project in a new tab. A project you had already linked to a sheet under its Relationships shows in **Other projects** too: they are the same links.

Tag each sheet with its **sector**, the **services** you provided and the **expertise** it shows. Those tags are what a pack matches a tender against, so a sheet without them is hard to find. [Tag project sheets](https://crm.tiny.plus/submissions/sheet_tagging), under the Submissions menu, sets them for every sheet on one page.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-e82d4cbfe4f7419c36708e697bd064f271c157a1%2Fsheet-tagging.png?alt=media" alt="Tag project sheets: one row per sheet with its sector, services, expertise, value band, completion year and whether it is approved for external use, each changed in place" width="979"><figcaption></figcaption></figure>

Only a sheet **approved for external use** can go into a pack. A Records Admin ticks it once the sheet reads right. Until then the sheet still shows in a pack's list, greyed out with the reason.

### Asking someone to write a sheet

Whoever ran the project usually knows it best. On a project with no sheet yet, the **Project Sheets** panel has **Request a sheet**. Choose the person, add a line if you like, and click **Ask them to write the sheet**.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-c1a0388d4bdf9aa777a7a298c06d215fcda480b2%2Fsheets-panel-ask.png?alt=media" alt="The Project Sheets panel on a project with no sheet: Request a sheet, with the person to ask, a box for a note, Ask them to write the sheet, and a line saying they get an email with the note and a link to the sheet form, and a task due in two weeks" width="814"><figcaption></figcaption></figure>

They get an email from you with your note and a link straight to the sheet form for that project, and a task on their list, due in two weeks. The task's reminders chase it the way any task's do.

## CVs

A CV belongs to a team member and lives on their page. Open the person under Team Members, find the **CVs** box, and click **+ New CV**.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-82fbb15df088c00392033f3fe13fdedf46090324%2Fcv-page.png?alt=media" alt="A CV being edited beside its page: the team member, the name and variant, the title, the summary, the notable projects with a role for each, years in practice and at the firm, registrations, education and memberships" width="979"><figcaption></figcaption></figure>

* **Variant** sets one CV apart from the person's others, such as *Health* or *Short*. A person can keep as many as they need. **Default CV** is the one a pack picks first.
* **Summary** is what a pack prints: up to 150 words.
* **Notable projects** are the jobs worth naming, in order, each with a one-line role. Pick a tiny+ project, or click **One from elsewhere** to type one from a previous firm with its client and year.
* **Expertise** and **sector** are tags, as on a sheet. A pack uses them, and the notable projects, to pick the right people. If the expertise you need isn't listed, type it under the Expertise tags and click **Add**: it joins the firm's list and is ticked on your CV. Tags in every other category are managed by Account Admins.

The page beside the form shows the CV as a pack will print it, in your firm's look, and **PDF** and **Word** download it on its own.

Everyone in the firm can read every CV. The person, Records Admins and people with the **Submissions** role can change one.

### Asking someone for a CV

On another person's page, the CVs box ends with **Request a CV**. Add a line if you like and click **Ask** with their name.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-f8195f939d9aeb35f79261b6f6d9ca948f482b5a%2Fcv-panel-ask.png?alt=media" alt="The CVs box on Sam Whitfield&#x27;s page: his CV with its title and status, then Request a CV with a box for a note, Ask Sam for a CV, and a line saying he gets an email with the note and a link to his CV form, and a task due in two weeks" width="543"><figcaption></figcaption></figure>

They get an email from you with a link to a new CV already set to them, and a task due in two weeks. The box then says who asked and when. [Set up submissions](https://docs.tiny.plus/guides/everyday/submission-packs.md#setting-up) can ask several people at once.

## Capability statements

A capability statement is a page about your firm for a kind of client: health, education, workplace. Keep the ones you reuse under **Submissions -> Capability statements**, each with the audience it's for.

<figure><img src="https://1957838173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnoXYnzHXoSKmkXmIHw%2Fuploads%2Fgit-blob-fcddad949cda11a853f8bdc7d6b21629dd21bc7b%2Fstatements-list.png?alt=media" alt="The capability statements list: Health, Education and civic, and Workplace and interiors approved, and Industrial and logistics still a draft" width="979"><figcaption></figcaption></figure>

A statement starts as a draft. Someone with the Submissions role or a Records Admin approves it, and only approved statements are offered when a pack is written. Changing an approved statement's text puts it back to draft until it's approved again.

## Keeping it current

**Data Health** counts the CVs not updated in twelve months, so stale ones are easy to find, and each CV's page says when it was last saved.

## Through the API

Project sheets, CVs and capability statements are records like any other: see [CVs](https://docs.tiny.plus/api/endpoints/cvs.md), [Capability statements](https://docs.tiny.plus/api/endpoints/capability-statements.md) and [Records](https://docs.tiny.plus/api/endpoints/records.md).

## Who can do what

|                            | Read                                                                 | Write and change                                        | Approve                              |
| -------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------ |
| Project sheets             | Everyone who sees the project                                        | The sheet's owner, Records Admins, the Submissions role | Records Admins (for external use)    |
| CVs                        | Everyone                                                             | The person, Records Admins, the Submissions role        |                                      |
| Capability statements      | Records Admins, the Submissions role and the person it's assigned to | Records Admins, the Submissions role                    | Records Admins, the Submissions role |
| Asking for a sheet or a CV |                                                                      | Account Admins, Records Admins, the Submissions role    |                                      |
