Release Notes | February 2026

Change request

A brand-new feature that allows users to extend the lifecycle of their scopes past the client acceptance stage. Now, with the enabled Change Request feature, the users can bring their scope all the way to “Client accepted” status and from their select to create “Change request” - but not one, multiple change requests in parallel. Not every one of them will have to accepted by the client and will end up being merged to the main scope, some might get closed or abandoned, and it will not impact other change requests in progress.  
 
The feature will allow:

1.  Initiate and put through approval multiple change requests in parallel 
2. Track changes between the latest client accepted version of scope and the change request consolidated scope version 
3. Track and output “net changes” only  
4. Merge the client approved changes back to the original scope and retain the access to the merged or dismissed change requests 
    
   

Dynamic fields

• Dynamic fields now retain the line spacing all the way to the output documents
• The association of dynamic fields with scope type: users can select which dynamic fields can be shown only in certain scope types
• Users can make dynamic fields “uneditable” from the UI, which is useful when these dynamic fields are updated by API from the external system (such as Project IDs, Opportunity IDs etc)

• Scope type selector is moved to the first page of “Create scope” form so the dynamic fields are selected and displayed to the user by the time they get to the third step of scope creation

Scope building UX

• Add a new column “Rate” to the scope overview page, which is a unit price of a single component before quantity value is applied
• Add a new column “TPC unit price” to the scope overview page
• Created a feature to make “client” field uneditable in “create a scope” form, when the scope is created inside a folder and inherits “client” value from folder

• Added “Value” column to scopes list table in a Folder

Scope duplication and building from scope template

• Created a feature to restrict the duplication of scopes and using templates in a different rate card

  

Component sizes

• Created a feature to hide the sizes (complexities) of the components when the company uses only one level of complexity

Outputs

• Folder name variable is added to Scope outputs
• TPC quantity variable
• Filter on Deliverable content to either show all scope deliverables on a loop, or only the deliverables with 1) zero value, or, 2) zero quantity
• 

Scenario pricing

• Scope traffic: add the scenario name to the payload
• Added scenario name to the header of the scope overview
• Added “trafficker” email to the payload

Safari compatibility

• Fixed some UX issues that prevented users from fully using the platform in Safari browsers

Admin

• Enhanced the “Application settings” page and surfaces some settings previously not available to company admins like showing/hiding Collaborators in scope overview, and “Enable fixed cost component and deliverable editing”
• Created a new setting to hide FF components with roles entries when scoping in a different rate card to these entries 
  
• Created a new setting to hide a checkbox in the “Add deliverable” modal to show deliverables in all rate cards. This is useful for the companies that don’t allow users to use deliverables cross rate cards