Feature Request: Pre-pull and scope actuals to proposal
Summary:
Enable proposal owners to pre-pull and store a curated list of relevant actuals (articles) from a project directly into a BOE Pro proposal. Estimators will then query and preview only from this preloaded subset, ensuring they see a focused, project-specific list of applicable actuals.
Problem Statement:
Estimators often do not know which actuals apply to a given project and must search across a large, unfocused dataset. This leads to confusion, slower estimating workflows, and a higher risk of selecting incorrect or inconsistent actuals. Proposal owners, who better understand project scope, currently have no way to predefine or constrain the set of available actuals for a specific proposal.
Proposed Solution:
Allow proposal owners to:
Pre-pull the entire list (or a selected subset) of actuals/articles from a project into a specific BOE Pro proposal.
Store this preloaded list locally within the proposal as the authoritative set of applicable actuals.
For estimators:
When querying for data in the BOE, limit search and selection to the preloaded actuals associated with that proposal.
Provide a preview UI to view and browse the full preloaded list of actuals before making selections.
Additional behaviors and constraints:
Support updating or refreshing the preloaded list if project-level actuals change, with clear indications of added/removed items.
Ensure appropriate permissions so only authorized proposal owners can modify the preloaded list.
Log or track which actuals are preloaded for auditability and consistency across proposals.
Benefits:
Reduces estimator confusion by scoping choices to relevant, proposal-specific actuals.
Speeds up estimating by minimizing time spent searching through large, unfocused datasets.
Improves accuracy and consistency of selected actuals across similar proposals.
Empowers proposal owners to control data applicability upfront, aligning estimates more closely with project scope.