What goes in the library?
The library lives at Account → Bid library and is scoped to your workspace — every team member sees the same entries. Five categories cover most repeatable bid content:
The five categories
Win themes
One-paragraph hooks you've found land with buyers — drop them into executive summaries; refine as you learn what resonates.
PQQ answers
Section 1 (supplier identity), Section 2 (insurance, ISO, financials), Section 3 (modern slavery, environment, equality) — write once, reuse forever.
Case studies
Past performance evidence — keep them in polished, droppable form rather than rewriting from scratch each time.
Capability statements
Short descriptions of what you do in each service area. Useful when a bid asks "describe your capability to deliver X".
Compliance
Modern Slavery Act statements, Equality Act policies, environmental commitments, data-protection postures. Anything you keep retyping from the same Word doc lives here instead.
Tagging convention
Each entry can carry an arbitrary set of tags (comma-separated at create time). Lowercase, kebab-case is the convention. Examples:
The list page filters by category + tag + free-text search across title and body.
Editing vs archiving
Any workspace member can edit any entry — the library is a shared asset, not personal notes. The author is recorded for attribution but doesn't gate edits.
Archive
When an entry is no longer the right answer but you want the audit trail. Hidden from the default list; surface with the "Show archived" toggle.
Delete
Only after archiving, and only when you're sure. Permanent. For sensitive entries (financial figures, personal data), archive-then-delete leaves a clear paper trail.
Workflow patterns that work
-
1
Bid manager curates, team contributes
One person owns the library; others suggest entries via the bid Discussion thread, the curator promotes them.
-
2
Post-win review
After winning, review the answers the bid used; promote the strongest ones to the library so the next bid inherits them.
-
3
Quarterly refresh
Half a day every three months reviewing entries beats letting them rot. Archive anything untouched for 18 months — odds are it's stale.
Privacy
Library content is org-scoped — other workspaces never see your entries. We don't read or analyse your library content for any cross-org feature: it's storage, not training data.