Overview
The Library is your organization's knowledge base of reusable implementation components. By importing historical Statements of Work (SOWs), Glossa extracts the categories and capabilities that make up your typical projects — complete with scope items, assumptions, complexity drivers, and typical hours. Over time, the Library becomes a canonical reference for what "standard" looks like across your engagements.
The Library lives at the organization level (accessible via Library in the main navigation) and is shared across all projects. When you create a new project and generate requirements, Glossa automatically compares those requirements against your Library to identify what's standard, what's new, and what needs attention. See the Capability Review article for details on that project-level workflow.
Key Concepts
Categories and Capabilities
The Library uses a two-level hierarchy:
Categories are the top-level groupings representing major functional areas of work. Examples: "Data Migration," "Training & Change Management," "System Integration," "Automation & AI."
Capabilities are the specific components nested under a category. Examples: under "Automation & AI," you might have "Prospect Research & Intelligence" and "Automated Outreach, Engagement, and Payment Processing."
This two-level structure mirrors how implementation work is often organized: broad sections containing specific groups of deliverables.
What Makes Up a Capability
Each capability in the Library includes:
Description — What this capability involves
Scope Items — The specific deliverables or work items typically included (e.g., "Configure Agentforce Prospect Research for gift officers and the development team")
Assumptions — Delivery assumptions and constraints (e.g., "Company uses Slack," "Company defines engagement signals")
Complexity Drivers — Factors that can increase implementation effort or variability (e.g., "Existing prospect research storage locations," "Integration with backend systems for real-time status updates")
Default Questions — Discovery question templates that get seeded onto a project's Questions page when this category or capability is selected
Typical Hours — Hour range based on historical SOWs (e.g., "10.0h – 35.0h")
Projects Using — How many Glossa projects are using this capability, with mapped requirements count
Referencing Requirements — Total requirements across projects mapped to this capability
Source Files — Which imported SOWs contributed to this capability
Originating Sources — Full audit trail of changes, including what was updated, by whom, and when
Target Products
Categories can optionally be tagged with Target Products — the software systems or platforms the category applies to (e.g., "Salesforce - Sales Cloud," "NetSuite"). When you tag a category with one or more target products, Glossa uses that tag to scope Capability Review matching: the category will only be suggested as a match for projects whose target system is one of the tagged products. Categories with no target products tagged are treated as generic and can match any project.
To tag target products, pick from your organization's existing systems or add a new one inline while creating or editing a category. See the Capability Review article for how this affects matching.
How Categories and Capabilities Get Created
There are two ways to populate your Library:
Import historical SOWs — Glossa parses the SOW and extracts categories and capabilities automatically.
Create manually — You can also create categories and capabilities by hand, though you'll need to manually add scope items, assumptions, and complexity drivers.
The Library Interface
Navigating to the Library
Click Library in the main navigation. You'll see:
Summary stats at the top: total Categories, total Capabilities, number of Imported SOWs, and your Most Used Category
Two tabs: Categories and Imported SOWs
Import SOWs button in the top right
Categories Tab
The Categories tab is the main view of your Library. It shows a table with:
Category — Name of the category (click the expand arrow to see nested capabilities)
Description — What the category or capability covers
Source File — Which imported SOW(s) contributed to this entry
Hours — Typical hours (when available)
Projects — Number of projects currently using this category/capability
Requirements — Number of requirements mapped to this category/capability
Created At — When the entry was created
You can search across categories, capabilities, and descriptions using the search bar, and filter by source file using the dropdown.
Categories with nested capabilities show an expand arrow (›) on the left. Click it to see the capabilities underneath.
Capability Detail View
Click on Open next to any capability to see its full detail page, which includes:
Parent Category shown at the top, with a link back to the parent
Capability name and description
Action buttons: Edit, Move to Category, Delete
Stats bar: Typical Hours, Projects Using, Referencing Requirements, Scope Items count, Source Files count
Scope Items — Ordered, reusable scope bullets extracted from SOWs
Projects Using This Category/Capability — List of Glossa projects with mapped requirements count
Assumptions — Delivery assumptions and constraints
Complexity Drivers — Factors that affect effort and variability
Default Questions — The Discovery Question templates seeded for projects that use this category/capability; add, edit, or delete templates from here
Originating Sources — Full audit trail showing all changes, who made them, what type of action (manual edit, SOW import, capability review update), and old vs. new values
Imported SOWs Tab
The Imported SOWs tab shows all SOWs you've uploaded to build the Library. Each row shows:
SOW Name — File name
Status — Processing status (e.g., "Succeeded")
Uploaded By — Who uploaded it
Uploaded At — Date
File Size
Categories — How many categories were extracted from this SOW
Capabilities — How many capabilities were extracted
Importing SOWs
How to Import
Click Import SOWs (top right of the Library page)
Upload one or more SOW files (Word documents and PDFs are supported)
Glossa processes each SOW and extracts categories and capabilities
What Glossa Extracts
From each SOW, Glossa identifies:
Major sections as Categories (L1)
Specific deliverables or components as Capabilities (L2) nested under categories
Scope items for each capability
Assumptions mentioned in the SOW
Complexity drivers implied or stated in the SOW
Typical hours when explicitly stated in the SOW
What Happens After Import
After processing, extracted categories and capabilities are added to your Library. If Glossa identifies that an extracted capability overlaps with an existing one in the Library, it will merge them — enriching the existing entry with additional scope items, assumptions, or hours data from the new SOW.
You can verify what was extracted by checking the Imported SOWs tab (Categories and Capabilities columns) and reviewing the entries in the Categories tab.
Tips for Best Results
Use real, executed SOWs — These produce the most complete and realistic capability data
Import multiple SOWs — The Library gets richer as more SOWs contribute to the same categories and capabilities. Hours ranges become more accurate, scope items become more comprehensive, and complexity drivers accumulate real-world insight.
Review after import — Check extracted categories for duplicates or entries that should be merged. You can edit, move, or delete entries as needed.
Managing the Library
Editing Categories and Capabilities
Click on a category or capability to open the detail view
Click Edit
Update the name, description, scope items, assumptions, complexity drivers, or hours
Save changes
All edits are tracked in the Originating Sources audit trail.
Moving a Capability to a Different Category
Open the capability detail view
Click Move to Category
Select the new parent category
Confirm
Deleting Entries
Open the category or capability detail view
Click Delete
Confirm deletion
Deleting a category also removes its nested capabilities. Deleting a capability does not affect the parent category.
Managing Default Questions
Each category and capability can have its own set of default questions — these seed onto a project's Questions page when that category or capability is selected for the project.
To add a default question:
Open the category or capability detail view
Find the Default Questions section
Click Add Question
Enter the question text and save
To edit or delete a default question:
Open the category or capability detail view
Find the question in the Default Questions section
Click Edit or Delete
Changes to default questions only affect projects added after the change — they don't retroactively update questions already seeded on existing projects.
Creating Entries Manually
You can create categories and capabilities manually without importing a SOW. This is useful for adding components you know are standard but haven't yet appeared in an imported SOW.
How the Library Connects to Projects
The Library's primary value is realized at the project level through Capability Review. When you generate requirements in a project, Glossa automatically compares each requirement against your Library and suggests matches. You then review and approve these matches, which populates the project's Categories tab with the relevant library categories and capabilities.
See the Capability Review article for the full workflow.
Categories tagged with Target Products are only matched against projects targeting those same systems, so tagging accurately keeps Capability Review suggestions relevant as your Library grows to cover multiple platforms.
Best Practices
Building Your Library
Start with 3–5 representative SOWs from recent, typical projects. This gives you a solid foundation without overwhelming you with cleanup.
Review and clean up after each import. Check for duplicate categories, merge overlapping capabilities, and correct any extraction errors.
Add to the Library over time. Each new SOW import and each Capability Review enriches the Library. It's designed to grow with your practice.
Maintaining Library Quality
Keep category names generic and reusable. "Data Migration" is better than "Acme Corp Data Migration" - the Library is meant to capture patterns that repeat across clients.
Use the audit trail to understand how capabilities evolved. If a scope item was added from a specific SOW, you can trace it back.
Periodically review underused entries. If a capability has 0 projects and 0 requirements, consider whether it belongs in the Library or was an extraction artifact.
Organizational Considerations
The Library is organization-wide — all team members can view and edit it.
Changes to a library capability (name, description, scope items) are reflected wherever that capability is referenced.
Imported SOWs may contain sensitive client information. Keep in mind that all organization members can see the Library, including imported SOWs and extracted content.