Enter Project Proposal
Entering a project proposal in ProjectStream 365 captures the scope of work, pricing, milestones, terms, and customer requirements needed to present a formal offering to a prospective customer. Proposal records help sales and project teams manage the estimating process, maintain consistency across submissions, and track opportunities from initial pricing through customer acceptance. Based on the structure of the ProjectStream 365 help article Enter an Opportunity.
β Goal
Create a project proposal by entering project, customer, location, and sales information. Proposal records provide a central location for estimating, budgeting, scheduling, document management, and proposal development before work begins.
π When to Use
Enter a project proposal when a customer has requested pricing, a project opportunity has moved into the estimating phase, or a formal proposal is required before contract negotiations begin.
Use proposals to:
- Develop project pricing and estimates
- Define project scope and deliverables
- Document assumptions and exclusions
- Present formal pricing to prospects and customers
- Track proposal revisions and approvals
- Support opportunity management and forecasting
- Convert approved proposals into agreements or projects
πΆββ‘οΈ Step-By-Step Guide
π Procedure
1. Navigate to Projects

2. Change the screen view to "Open Proposals"

3. Click +New

4. Enter Proposal Header Info

| Name | The name used to identify the proposal or prospective project. |
| Project Type | Identifies the type of project record being created. For this process, the Project Type is Proposal. |
| Project Class | The classification that determines the type of project or proposal being created and drives the applicable Project Proposal form and related configuration. |
5. Note: The selected project class will determine the fields on the full Proposal entry screen.

6. Enter the remaining Proposal General Information:

| Site | The ProjectStream 365 site associated with the proposal. |
| Account | The customer or account associated with the proposal. |
| Address | The customer address associated with the proposal. |
| Contact | The customer contact associated with the proposal. |
| Payment Terms | The payment terms associated with the proposal and customer account. |
| Contract | The contract associated with the proposal, when applicable. |
| PO Number | The customer's purchase order number associated with the proposed work. |
| Start Date | The anticipated start date for the proposed project. |
| Finish Date | The anticipated finish date for the proposed project. |
| Target Completion Date | The targeted date for completion of the proposed project. |
| Price List | The price list associated with the proposal and used as the pricing reference for applicable items. |
| Rate List | The rate list associated with the proposal for applicable resource rates. |
| Partner | The partner associated with the proposal, when applicable. |
7. Enter Project Description and Address Info

| Description | General information about the proposed project, including its purpose, scope, requirements, or other relevant proposal details. |
Project Address
| Street 1 | The primary street address of the proposed project location. |
| Street 2 | Additional project address information, such as a suite, unit, building, or secondary address line. |
| City | The city associated with the project location. |
| State/Province | The state or province associated with the project location. |
| Postal Code | The ZIP or postal code associated with the project location. |
| Building Type | The classification of the building associated with the proposed project. |
| Phone | The phone number associated with the project location. |
| Validated Address | Indicates whether the project address has been validated. |
| Map | The map/location reference associated with the project address. |
Sites
| Site | An additional project site associated with the proposal. |
| Distance | The distance associated with the project site. |
8. Click Save

β Result
After saving the configuration:
- Project scopes are established for the project.
- Estimates can be organized by scope.
- Budgets and costs can be tracked at the scope level.
- Resources and production activities can be planned using the defined scope structure.
- Project reporting can be summarized by scope and phase.
π‘ Tips
- Create scopes that reflect how the project will be estimated and managed.
- Keep scope names clear and standardized across projects.
- Avoid creating unnecessary scope levels that add complexity.
- Use consistent scope structures for similar project types to improve reporting.
- Review scopes before beginning estimating activities to ensure all work is represented.
- Update scope definitions early in the project lifecycle to minimize downstream rework.
π Related Actions
π§ What Happens Next?
Once project scopes have been configured, estimators can begin developing project estimates, budgets can be established for each scope, and project teams can use the scope structure to support scheduling, resource planning, production management, and project reporting.