These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Sales Forecasting
- Features
- Rep submissions
Rep submissions
Prepare the rep's category amounts and carry the submission into a documented manager decision.
OverviewMy Forecast Submissions×
Sales Forecasting · Rep submissions
New
My Forecast Submissions
Forecast submissions
| Submission number | Period | Manager | Status | Submitted at | Reviewed at | |
|---|---|---|---|---|---|---|
| FS-87860 | FP-4727 | Draft | 16 Oct | 21 Oct | ||
| FS-12866 | FP-3286 | Submitted | 06 Oct | 10 Oct | ||
| FS-45852 | FP-6321 | Manager reviewed | 23 Oct | 30 Oct | ||
| FS-17667 | FP-8607 | Locked | 27 Oct | 30 Oct | ||
| FS-72796 | FP-9121 | Reopened | 13 Oct | 15 Oct |
6 of 6 records
FP-4727Forecast submissions · FS-87860
DraftSubmitted at16 Oct
Reviewed at21 Oct
CurrencyUSD
Total commit540
Total best case790
What you can do
Make the rep's call reviewable
Sales Rep works on a submission for a specific period with an assigned manager. The submission lines retain the rep’s amount beside the system amount for the relevant category and revenue or bookings type. An override reason explains why the rep’s judgment differs from the calculated starting point.
The Forecast Submissions page lets the team filter by rep, manager, period, status, submitting or reviewing user and currency. It shows distinct submission counts by period and supports inspecting an individual call alongside the full list. The manager can start from the same submission that the rep prepared.
How the work is organized
- Prepared call. The period-opening process creates the Draft submission and seeds its category lines. Sales Rep reviews the amounts and adds commentary before submitting the forecast.
- Manager decision. Sales Manager reads a Submitted call and appends a manager note. The manager accepts it as reviewed or reopens it with an explanation for the rep to address.
- Decision evidence. Submission and review timestamps identify when the handoffs occurred. The submitting and reviewing user references support follow-up when a number or decision needs explanation.
What to agree during setup
Agree which submission-line types the business uses and how their amounts contribute to the forecast totals. Revenue and bookings should retain their own basis. Review the relationship between the rep-entered amount and the system amount so an override has an understandable meaning.
Decide what commentary belongs on the call. A rep can explain a category amount at the line and use forecast notes for the wider context. The manager should give a reopened call a reason that points to a specific correction or unresolved customer fact.
Set the submission deadline and the notification delivery connection together. The team needs a practical way to find Draft calls approaching the deadline, then confirm that a submitted call is visible to the right manager. Agree how a reopened submission returns for review and how the period lock stops further rep editing.
Check the handoff on an actual case
Prepare the pilot rep’s Draft call and compare a Commit-Revenue line with its system amount. If the rep changes the amount, record why. Submit the call and ask Sales Manager to locate it in Manager Review Inbox with the same period and currency. The manager should be able to explain the difference without asking someone to recreate the original line.
Have the manager reopen the submission with a specific note, such as a close-date assumption that needs checking. The rep follows the agreed resubmission procedure after resolving it. On approval, confirm the reviewed time and reviewer identity. Then lock the ended pilot period and verify that the rep cannot alter the final call through either the entry form or another authorized editing path.
What your team sees
- My Forecast Submissions — The current rep’s calls with period, manager, status and forecast totals.
- Manager Review Inbox — Submitted calls waiting for the responsible manager’s decision.
- Submission Board — Call progression across Draft, Submitted, reviewed, reopened and locked work.
Follow the work through
Follow Submit and review the forecast, then Lock and reconcile the period to protect the final call.
What it keeps track of
Data model- Forecast submissions
- Per rep per period forecast submission carrying the commit, best-case and pipeline call to the manager.
- Submission lines
- One line per forecast category and revenue type on a submission, holding the rep number and the system auto amount.
- Forecast notes
- Rep and manager commentary attached to a forecast submission.
- Forecast periods
- US fiscal forecast periods on a calendar-year basis (Week, Month, Quarter) with submission deadlines and open/lock/close lifecycle.
- Forecast categories
- The category taxonomy reps use to classify open opportunities: Closed, Commit, most likely, best case, Pipeline, Omitted.
- Users
- Users
Who uses it
Permissions- Sales Rep
- Prepares and submits the call.
- Sales Manager
- Reviews or reopens it.
- Sales Operations
- Follows submission progress and resolves cycle setup.
- CRO
- Oversees the final period lock.
Set up Sales Forecasting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.