From 1st January 2026, new jobs will be created for all Hourly and Dedicated engagements.

Action required from JC/PCs:

• Ensure your project team member does NOT log hours in any old jobs after 31st December 2025
• From 1st January 2026 onward, hours must be logged only in the newly created 2026 jobs
• Please verify that new jobs are created for your team by 31st December 2025

Job creation update:

• Nidhi will start creating the new jobs today
• This is expected to be completed by tomorrow before lunch
• If you do not see the new job after that, please raise a support ticket in Everest for the missing job and assign it to Nidhi

This is required for clean yearly tracking, billing, and reporting.

Thanks for your cooperation.

We’ve added Bucket Jobs for prepaid, flexible work models.

✨ What is a Bucket Job?

A prepaid engagement where the client purchases a fixed amount and number of hours upfront through one-time billing.

✨ How it works

• Hours can be consumed flexibly

• Valid only until the defined expiry (end) date

• Bucket jobs cannot be extended

Additional work requires creating a new bucket job with fresh hours and billing

✨ Best suited for

• Support work

• Maintenance

• Marketing & branding

• On-demand or ad-hoc engagements

This keeps scope clear, billing upfront, and usage fully controlled 💼

We’ve introduced Recurring Jobs to support ongoing work with predictable billing cycles.

✨ What is a Recurring Job?

A job with a fixed duration and a recurring billing cycle, where the client is billed automatically at a defined frequency — weekly, monthly, yearly, or a custom interval.

✨ How it works

• Billing runs automatically as per the selected schedule

• Continues throughout the job’s active period

• Stops immediately once the job is closed

✨ Best suited for

• Managed services

• Domain renewals

• Subscriptions

-Any long-term, recurring engagement

This removes manual billing effort and keeps recurring work consistent and hassle-free 🔁

All pre-sales activities must now follow the updated process in Everest. This applies to Sales, Estimation, and Delivery teams.

Where to Log

• Project: Sales Enablement Workflow
• Job: Pre-Sales Activity

The Quote Generation job and the Elite milestone are now closed. Every pre-sales lead will have its own dedicated milestone.

All pre-sales work must be logged only against the lead-specific milestone under Pre-Sales Activity.

Mandatory Milestone Rule

• Job-level logging is disabled for Pre-Sales Activity
• Hours can be logged only against milestones
• Each pre-sales lead must have one milestone
• If a milestone is missing, Sales must create it from Sahara

Ownership & Reviews

Sales

• Create a milestone for each pre-sales lead
• Assign a Milestone Coordinator (MC) at creation time (confirm with the relevant FPOC)

Milestone Coordinator (MC)

• Acts as the Estimation Lead
• Reviews and approves all logged hours for that milestone

Note: Hem will no longer review pre-sales hours. Reviews will be done only by the assigned MC.

Why This Change

• Accurate effort-to-lead tracking
• Better estimations
• Clear ownership and audit trail

Action RequiredIf you are working on an active pre-sales lead without a milestone, reply to this message and tag your Sales person. Logging will not be possible until the milestone is created.

More flexibility and better data handling across modules.

✨ What’s new?

Jobs

• Updated job cell layout for Job Extension listings

Bookmark

• Enabled bookmark creation for JC users

Case study

• Added Date Created field in Case Studies

• Replaced select fields with combo-boxes for Tool & Tech Stack selection

• Enabled tool and tech stack selection based on the selected type
• Add industry and sub industry inputs

More control, less manual effort ✨

Reporting just got more insightful.

✨ What’s new?

• Overview Report

• Added total unreviewed hours

• Introduced color indicators

• In-Review Report: Added logged hours field

• Updated PC Dashboard

• Added User ID filtering for Underrun & Overrun reports in PC

• Adjusted total limits in JC–PC unreviewed reports

Better insights, faster decisions 📊

We’ve shipped major improvements across billing and contract workflows.

✨ What’s new?

• Added Start Date and End Date support for billables (live in production)

• Billables now pull dates directly from Collections

• Merged Contract Extension and Scope Expansion into a single flow for: Job Extensions, Billables

• Removed job management from Contract CRUD

• Added Contract selection during Job creation

• Launched Contracts listing and detail pages

• Added Contract Revenue Sidebar for better financial visibility

This should make contract and billing workflows much smoother 🚀

The Performance module just got simpler and more focused.

✨ What’s new?

• Added Performance Reports under the Performance root tab

• Updated Performance Quadrimester:

• Shows only ongoing items within 15 days

• Removed global quadrant filter for easier usage

We’ve rolled out a set of UI improvements to make navigation smoother and layouts more readable.

✨ What’s improved?

• Restructured application tabs for better flow

• Multiple views upgraded from card layout to table layout

• Enhanced project sidebar indexing

• Updated contract sidebar and breadcrumbs to align with job navigation

• Renamed Needs Attention → Overview with better text formatting

• Improved flag font sizing for Jobs

Cleaner UI, faster navigation, less friction 🔥

To improve billing accuracy and avoid missed client invoicing, we’ve introduced an important update to how timesheet logging works in Everest.

What Was Happening Earlier

Until now:

• Employees could log hours as long as the job date range was valid.
• In multiple cases, billables were not created or were created without proper coverage.
• This resulted in projects turning inactive via automation, or missed or delayed client billing

What’s Changed (Effective Immediately)

From now on, both conditions must be met to log hours:

1. The date must fall within the job’s defined date range
2. A billable must exist AND cover that same date range

If a billable is missing or does not cover the required period, hour logging will be blocked, even if the job dates are valid.

What Employees Should Do If They Can’t Log Hours

If you’re unable to log hours for a valid job period:

1. Reach out to your JC (Job Coordinator)
2. Inform them that the billable is missing or not covering the required date range
3. The JC will coordinate with the PC and Finance team to get the billable updated
4. Once the billable date range is corrected, hour logging will be enabled

Finance - Billable Creation Responsibility (Important)

From now on:

• The finance team will be responsible for adding the Start Date and End Date to every billable
• Billables must always have a defined date range
• Finance should not assume billing date = billable end date

How Start & End Dates Should Be Decided

• Finance must discuss with JC and/or PC to confirm when work actually starts and when work is expected to end
• This is critical because, in cases of advance payments, the billing date may be earlier, and the billable period must still cover the actual delivery timeline

📌 Key Rule:

Billable Start & End Dates should reflect the delivery period, not just the invoice or payment date.

Why This Change?

• Prevents billable work from going un-invoiced
• Avoids projects from becoming inactive unintentionally
• Improves coordination between Delivery, Sales, and Finance
• Ensures accurate timesheets, billing, and revenue tracking

We appreciate your cooperation in following this updated process. This change is essential for smoother operations and financial accuracy.