Hub
The Hub is the central repository for all your company information. It’s the foundation that powers every other feature in Forgent—the better your Hub, the better the AI performs.Why the Hub Matters
Powers Writer
Writer uses Hub data to research facts about your company, certifications, team qualifications, and past projects.
Enables Eligibility
Eligibility checks compare tender requirements against your Hub data to identify matches and gaps.
Improves Checklist
Checklist answers draw from Hub information to pre-fill responses accurately.
Consistent Results
Once data is in the Hub, it’s available across all projects—no need to re-enter information.
What Goes in the Hub
| Category | Examples | Used For |
|---|---|---|
| Company Info | Name, industry, capabilities, locations | General context, eligibility matching |
| Certifications | ISO 9001, ISO 27001, industry-specific | Eligibility checks, Writer facts |
| Team Profiles | Qualifications, experience, CVs | Proposal team sections, eligibility |
| Project References | Past projects, case studies, metrics | Writer evidence, credibility |
| Writer Rules | Style guidelines, terminology, templates | Consistent proposal writing |
Getting Started with the Hub
1
Add Company Basics
Start with your company name, industry, and core capabilities. This provides essential context for the AI.
2
Upload Key Certifications
Add your most important certifications with validity dates. These are frequently required for eligibility.
3
Create Team Profiles
Add key team members who appear in proposals—their qualifications and relevant experience.
4
Add Project References
Include 5-10 strong project references with outcomes and metrics.
5
Define Writer Rules
Set up company-specific writing guidelines to ensure consistent proposal style.
Hub Data Categories
Company Information
Basic company details and capabilities
Certifications
Compliance documents and quality certificates
Team Profiles
Employee qualifications and experience
Project References
Past projects and case studies
Writer Rules
Company-specific writing guidelines
Best Practices
Keep data current
Keep data current
Regularly update certifications (especially expiry dates), team profiles, and recent projects. Outdated data leads to incorrect proposals.
Be specific
Be specific
Instead of “IT services”, specify “Cloud migration, DevOps consulting, managed Kubernetes”. Specific data yields specific, relevant results.
Include metrics
Include metrics
For project references, include measurable outcomes: “Reduced processing time by 40%” is more compelling than “Improved efficiency”.
Start with common requirements
Start with common requirements
Focus first on data that appears frequently in your tenders—certifications, key team members, signature projects.