Sales CRM · Feature guide

Submit and revise your revenue forecast

Record your expected revenue and assumptions, retain pipeline evidence and submit a new version when expectations change.

Audience: authorised staffPermission: Active staff member with Sales CRM viewing accessReviewed 30 October 2026

Where to goSales CRM → Forecast & targets → Submissions & review → Select period → Submit my forecast

Before you start

Use your own authorised staff account in the intended Britixo workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.

Follow these steps

Choose the correct period and read its dates, currency and scope.
Expand Your current pipeline evidence to inspect won, eligible open, weighted open, commit, best-case and omitted values.
Select Submit my forecast or Submit a new version.
Enter your total expected revenue for the period, including revenue already won, and explain the expected closes, timing and risks.
Select Submit for review. The application records the submission and measures current pipeline evidence again at save time.
To revise it, refresh the period and submit a new version. Read the review reason first if the previous version was rejected.

Behavior and limits

You can submit only your own forecast, even if you are an administrator or can view all deals. Viewing access is sufficient; editing opportunities is not required.
The period must be Open. Amounts are non-negative, support two decimal places and may be zero, up to 99,999,999,999.99. Reasoning is required and supports 2,000 characters.
Each person can submit up to 100 versions in one period. Versions remain available in history.
A new version supersedes a previous pending version. A previously approved amount remains effective until a replacement is approved, including when a replacement is rejected.
Submitted amounts are estimates, not predictions, invoice payments or changes to the underlying opportunity values.
A retry of the same submission reference and content returns the existing version; reusing the reference with different content is rejected.

Check it worked

Confirm your latest amount, version and Pending state.
Open View history and check the recorded reasoning and pipeline evidence.

Troubleshooting

If the period or latest submission changed, refresh before submitting again. This protects another session’s changes.
If there is no submit button, check whether the period is Locked or Closed.
A missing second reviewer does not authorise self-approval; an administrator must configure a different eligible reviewer.