A rebuilt interface, not just a redesign
The most visible change in version 4.0 is on the surface: new icons, an updated color scheme, and a workspace built for modern screens. But the redesign only holds up because of what changed underneath it, and that's where the rest of this article spends most of its time.
New workspace, new foundation underneath
Version 4.0 rebuilt how data relationships function inside the platform, not just how they're displayed. That's what makes the redesigned interface stay stable as a project's task list, budget lines, and related records grow more complex, instead of slowing down or becoming harder to navigate the way older interfaces tend to under the same load.
Inline editing cuts the clicks
Task details, statuses, due dates, and assignees can now be updated without opening the task. Hover over a field, use the edit icon that appears, and change the information directly from whatever view you're already in: a task list, a calendar, a board. Screens stop getting toggled back and forth for small updates that used to require opening a full record.
Faster previews without leaving the page
Hovering over a task now surfaces more of its data directly on the screen, without a click: status, dates, notes, related budget lines. The full picture of a task is visible without leaving the current view, which matters most when scanning a long project list looking for the one item that needs attention.
Crystal-clear project context
Selecting a project narrows the entire system down to that project's information only: tasks, budgets, documents, related records. Menus, filters, and lists stop surfacing data from every other project in the account. Fewer distractions, and less scrolling past information that has nothing to do with the task at hand.
Forms built around how the work actually happens
That same underlying rebuild carries into the forms themselves. This is where the version 4.0 changes show up most in daily use, since forms are what a project manager or field lead touches dozens of times a day.
Configurable, card-based forms
Data fields can be grouped into cards, reordered, and displayed in one or two-column layouts, so a form matches how a specific role actually works through it. Fields from related objects, a client's billing terms, a task's parent project, can be pulled directly into the form being worked on, so the context needed to make a decision stays visible without switching screens to look it up.
Formulas built into the form itself
Custom properties now support formula logic. Calculations, decimal precision, and math run automatically as data is entered, covering markups, unit conversions, and budget totals without exporting anything to a separate spreadsheet to do the math and re-entering the result.
Project names that build themselves
Naming rules are set once, and the project title updates automatically as details, client, site, and service type are entered. That removes manual assembly at project creation, and it removes the inconsistencies that come from different people naming similar projects slightly differently across a project list.
A form that used to send someone to a spreadsheet on the side now does the math itself, as the data is entered, not after.
Templates that carry more than a task list
Forms handle how data enters the platform. Templates now determine what happens to that data the moment a project exists, which is a bigger shift than it sounds.
Full budget structure travels with the template
Project templates now include budgeted expenses linked to specific tasks, not just a task list with no financial structure behind it. Creating a project from a template brings that budget structure with it, already connected to the right tasks and ready for the proposal stage, instead of being built manually after the project is already underway.
Conditional workflows adjust automatically
Templates can define conditions that determine which task workflows run, based on how the project is set up. Selecting Phase II ESA as a project type, for example, can trigger the correct task sets automatically, without someone manually assembling them. One template can produce several different, correct outcomes depending on what's selected, instead of needing a separate template for every variation.
Project-level data populates every task
Task details now populate automatically from project-level properties. Site dates, location codes, and client identifiers get entered once at the project header and carry into every task that needs them, instead of living in two places at once and drifting out of sync when one gets updated and the other doesn't.
One template can now produce several different task workflows automatically, depending on the project type selected, without separate setup for each one.
Billing and financial tracking tighten up
Templates set the financial foundation of a project before work starts. What happens to that foundation once billing actually begins is where version 4.0 makes its next set of changes, and it's also where a mismatch between field data and financial data tends to cost the most time to untangle.
Fixed fee work tracks itself
Time entries logged under fixed fee tasks are now labeled as fixed fee work automatically, with no separate step to flag them. They still appear as billable in utilization and labor reports, so the firm can see the real cost of the work, but they aren't billed directly to the client the way hourly time is. When a parent task is set as fixed fee, every child task underneath it inherits that status automatically.
QuickBooks Online sync expands to real time
This is not a new integration; EVX Software has synced with QuickBooks Online before. What changed is the scope and the timing: vendors and projects now sync in real time alongside the existing client sync, the moment they're created in EVX Software. Both systems stay aligned automatically, without a manual reconciliation pass at the end of the month to catch whatever drifted out of sync in between.
Proposals start with the numbers already in place
Proposals can now launch directly from templates that already include task structures and expense estimates, so scope and pricing stay consistent from one proposal to the next instead of varying based on who happens to be building it. The financial foundation of the project is set the moment it's created, before the first invoice goes out, not reconstructed after the fact once work is already underway.
One connected platform
Individually, these changes touch forms, templates, billing, and proposals as separate parts of the platform. Together, they close the gap between the work happening in the field and the numbers that come out of it at the end of a project, so less time gets spent reconciling the two after the fact and less budget risk sits undetected until an invoice finally surfaces it. EVX Software 4.0 is the version built to hold that connection together.
