Context items
The context labels, initiative versus workspace scope, and how to write context that produces better documents.
Context items are the ingredients ForceVue uses to write your documents. Each one is a labeled note: research, feedback, a competitor, a constraint, a piece of company background. The better your context, the better every draft.
Adding a context item
- Open an initiative and go to the Context tab (or use workspace context in Settings for workspace-level items).
- Click Add Context.
- Fill in:
- Label, the category (see below).
- Title, a short name.
- Content, the actual detail.
- Source URL (optional), a link back to the original.
- Save it.
Labels
Labels tell ForceVue what kind of context a note is, so it can weigh it correctly. The labels available depend on scope.
Initiative-level labels:
| Label | Use for |
|---|---|
| Target Users | Personas and customer segments |
| Competitors | Competing products and their features |
| Market Research | Industry trends and analysis |
| User Feedback | Customer requests, support tickets, quotes |
| Feature Idea | Product ideas and enhancement proposals |
| Technical Constraint | Limitations and technical requirements |
| External Link | Articles, docs, and references |
| General Note | Anything else relevant |
Workspace-level labels add company background that applies across every initiative:
| Label | Use for |
|---|---|
| Company Info | What your company does |
| Tech Stack | The technologies you build on |
| Target Market | Your overall market |
| Brand Guidelines | Voice and brand rules |
| Compliance | Regulatory and compliance requirements |
Workspace context also reuses several of the initiative labels (target users, competitors, feature ideas, links, and general notes) for things that are true across the whole workspace.
Initiative scope vs workspace scope
- Initiative context is specific to one product effort: the feedback, research, and constraints for that feature or launch.
- Workspace context is shared across every initiative in the workspace: who your company is, your tech stack, your brand voice, your compliance rules.
Put a note where it belongs. Company background belongs at the workspace level so you write it once. Effort-specific detail belongs on the initiative.
Writing context that improves output
- Be specific. "15 enterprise customers asked for SSO in Q1" beats "users want better auth."
- Use real data. Survey numbers, support-ticket counts, and direct quotes carry more weight than summaries.
- Cover both sides. Pair user needs with the technical constraints that shape the solution.
- Start with three to five solid items for a first document, then add more as the effort grows.
- Keep titles meaningful. A good title helps you find and reuse the item later, including through @mentions in the editor.
Thin context produces generic drafts. ForceVue will even warn you when a document type does not have enough context to work with. See How generation works.
Where to go next
- Goals to add the outcomes context items support.
- Uploading documents to bring in larger source files.
- Generating documents to put your context to work.