Release Notes | July 2025

Integrations 

• We released an off-the-shelf integration with Zoho. Users can easily connect to their Zoho account and configure the trigger to create or edit a scope in SCOPE Better from the Opportunity/Deal in Zoho. Special feature – users can include as many custom fields from Opportunity/Deal as they need, they will be automatically created in SCOPE metadata, visible on UI and editable directly in SCOPE or through re-triggered push from Zoho.

Application settings page 

• Reviewed and removed some outdated settings
• Replaced the on/off buttons with the toggle for a consistent experience throughout the platform
• Added tooltips to the settings
• Removed the legacy “Custom fields” form as it is now fully replaced by the new feature Scope Dynamic Fields and located in Manage -> Data

Scenario pricing 

• Custom fee/discount prompt that is configured in the questionnaire is now possible to edit and resubmit the questionnaire for recalculation on both scope and deliverable level

UX improvements 

• Added “loaders” to the scope approval flow. When processing large scopes, the loaders keep users informed that the process is underway and prevent confusion and excessive clicking 

Output editor 

• We now have a new output editor content block “Cover page” which is configured differently from the rest of the document: it doesn’t contain header, footer, or page margins.  Users can add a background image to cover the entire page
• New variable “Total scope fees” that the users can filter to exclude or include scope, component or deliverable level fees
• We added ability to edit or completely disable page margins in Document (Word, PDF) output templates
• Enhanced output variable options for Third Party costs now include Margin and Markup values for one or all TPCs inside the deliverable
• Total Stage price variable now has a filter: users can include or exclude the Fees, Third Party Costs or Overtime values
• Output Editor for Document and Spreadsheet outputs - “Office Location” name

Additional Description Fields

• Components and Deliverables in scopes by work, as well as Tasks in scopes by role, now have a second Descriptions field. Users can create boiler plate descriptions for their library items, or fill them out directly in a scope
• Use in outputs: This separation of descriptions into two fields gives users flexibility while building their output documents. For example, users can surface different parts of component descriptions in different sections of their proposals, or show different descriptions for different audiences of the outputs

Scope by Role

• Users can now reorder Tasks by using drag&drop
• We introduced Stages: users can group the Tasks into Stages that have their own start/end date, descriptions and can be reorderd by drag&drop. Tasks can be moved in/out/between the Stages

Dashboards

• We refactored the code for Dashboard Filters which now load fully and much faster

 Bugs and improvements

• Components with no roles added to them are included in the Component export file
• Folders page: users can create Scope by Scenario from inside the Folder
• Cover page: users can select the A4 and Letter size of the cover page image automatically
• Scenario pricing bug where the default values were not showing on the configuration forms (questionnaires) is now fixed.
• Legacy custom fields bug where the users couldn’t delete or edit them.
• Scope by Role reordering of Tasks within the same Phase wasn’t working smoothly.
• We fixed a bug where users couldn’t delete the highlighted text from their output templates when exporting the Word and PDF files
• We fixed the dynamic fields with external dropdown lists for Netsuite integration where they were not possible to edit in existing scopes or when duplicating existing scopes
• Fixed the deliverable entries prices that were not updating on the Deliverable overview page
• Output editor bugs: images added to the Headers used to cut off when aligned to the left of the page
• Output editor bugs: some output variables were added with extra padding, which is now removed
• Scenario pricing bug where the default values were not showing on the configuration forms (questionnaires) is now fixed.