Skip to main content
The company profile is Tender’s internal source of truth. It is used to compare opportunity requirements with your capabilities, suggest Go / No-Go decisions, and prepare proposal sections. Missing data is treated as a gap for review, not as a fact.

​
Profile sections

Never place a password, API token, or OTP in onboarding fields or notes. Save authorized portal credentials through Credentials on the Sources page. Stored values are encrypted and are not displayed again.

​
Write usable evidence

​
Past project

Instead of “we delivered several technology projects,” record the client type, year, duration, scope, measurable outcome, and attached evidence.

​
Commercial rule

Write a testable rule, for example: “Any bid bond above 2% requires finance approval. Payment terms longer than 90 days require commercial escalation.” Record the condition, result, and authority: “Unlimited liability is a preliminary blocker. Legal must review it, and Go requires a written executive exception.”

​
Updating the profile safely

1

Update the source record

Correct the certificate, project, team member, or rule and attach current evidence.
2

Return to affected opportunities

Do not assume an open proposal changed automatically when the profile changed.
3

Reassess the affected area

Refresh the requirement or regenerate only the relevant section, then review the differences.
4

Create a new proposal revision

Preserve version history instead of silently replacing an approved version.
The readiness percentage is a guide, not an approval. A completed field with an expired certificate or unsupported claim remains a real gap.

Next: manage sources

Enable the sources that match your business and disable the rest.