1. Introduction (0:00 – 0:13)
Greetings, everyone! Dominic here for another ‘How I Solved It With Klient’! I wanted to do a few minutes here on Agile and how we did epics and we’re doing epics and sprint management, in the workspace and how we slightly personalized based on some requests from customers. I thought it was interesting also to show how we can manage Agile projects within Klient.

2. Main Challenges (0:14 – 0:40)
Main challenges or requests we’re here were managing the stories and planning the sprints while we’re maintaining the story relationship with the epics. Here’s how we did that and, hopefully it spurs a few ideas to you too.

3. Workspace Flexibility (0:41 – 1:10)
Here, jumping right away into the workspace which is, very flexible. You can have several lenses, through your structure of your project, your different tasks or components of the project. If you’re looking initially to a project to scope it all the way to eventually managing it you’ll see that there are different ways we can look into it.

4. Set Project Structure (1:11 – 1:50)
So for now, really high level where I have some information for my project and also briefly mentioning here even if we’re doing Agile, there’s usually a set structure to how we like to deliver it in our business, to customers. So you might have some preset sprints for the intro and the outro of the project so for your sprint one, you’re doing your planning sales to ops, documentation review, preps and stuff like that. So usually that would be a set one that you would have every time you start a new project.

5. Utilizing Templates (1:51 – 2:20)
Outros, project closeouts, lessons learned and stuff like that… Usually you want to have those in, using templates, so that when you spin a new project, you get that set structure, it’s very efficient. You can get and spin a new project, with a few clicks. So even if you’re Agile, project structure is very important and you should leverage the template feature here.

6. Maintaining Epic Relationships (2:21 – 3:00)
So back to our main topic here, the epics and how we can relate the stories. So as you’d be building your project you’d build your epics, maybe having a rough sketch or, rough estimate of the effort that are required for each of those epics. As you’re detailing further you’ll create your stories. And as we’re going to eventually use those stories into sprints, the request was ‘I want to keep and maintain that relationship, a meta red relationship between the stories and my epics’.

7. Task Management (3:01 – 3:30)
So it’s the tiny detail but just adding a field here, which is a lookup to an epic task and leveraging the task type field that we have here, we can now have that relationship created so that if I take and drag a story within an epic or create a new one, you see that the epic gets related and stamped. So I’m gonna bring that back right here, just so that I keep the information where it should be.

8. Planning Sprints (3:31 – 4:00)
So here I’m related to my project management which brings me to whenever we get to a point where we need to start planning our sprint. The same would remain here, but react slightly differently, meaning that now if I have a sprint, in this case my task is set to a sprint, if I drag and drop it here you’re just using simple record trigger and flow in the background. I did get an update on my sprint number here I’m flying that now, that story part of a sprint but I’m maintaining my epic relationship right here.

9. Developer Workflow (4:01 – 4:30)
So, a tiny change but in a meta perspective on the projects and the structure of the tasks here, I’m gonna keep those relationships so when I look back at my project I’ll still have that knowledge of where the stories are coming from. And then doing reporting, data analysis, I’ll have that information. That being said, I’d like to wrap up on how we can as a team, or dev, review those tasks and work on them. Different things or tools will be available, just different lenses to look at the data.

10. Kanban View and Conclusion (4:31 – 5:00)
Clicking on the pencil here, I will have access to my descriptions, which is probably the story descriptions maybe my acceptance criteria, how we’re defining that, so that we can agree with the customer what it should be looking like. And we’ll see that we have other fields that are available right from here for quick review. We can, directly interact with the data from here, obviously. Maybe if we’re more of a developer and we want to be heads down working on a task ‘I wanna concentrate on that’, obviously we can pop that task open and really have a full page just working on that story specifically. So same information, obviously but then I can be focusing on the proposed solution, detailing what other custom fields I want maybe, so anything you might need, leveraging the flexibility of the page layout in Salesforce, makes it very efficient. Also, maybe having different checklists, brain dump, that I need to have for that story. Here I could be leveraging that for different reasons. An also an interesting aspect is the issues. As we’re doing the UATs, we can relate our issues to our different stories and eventually, look at it as a holistic view on our project by epics and all those type of things, neat things that we can do in Salesforce, so issues here could be also related and highly visible within our story. Last thing, I promise, is the Kanban view. So often we wanna look at our project when it’s Agile using Kanban boards. Obviously we can do that here and then if I just wrap up, being consistent with the epic and story relationship, here I have a view where I’m looking at only my stories within my project. So looking at only those four tasks that I had now, maybe I want to tell my team that I’m actually working on that task and I just want to mention that that task is in progress. So we can move those cards around but I could also be wanting to look into our stories, but by epics. We can also use those lookup fields to group our cards right on our Kanban board and kind of have that neat view of all the stories, but by epics here. So hopefully that helps, spurs a few ideas. Let us know if you have any questions, it’s always a pleasure to get in, in touch with you and discuss further on how we can help your business drive and be more efficient. Thanks. Have a great day!

1. Introduction (0:00 – 0:13)
Greeting everyone! Dominic here for another ‘How I Solved It With Klient’, focusing today on resources onboarding, and structure to get better.

2. Challenges in Onboarding (0:14 – 0:45)
Obviously, there are a few challenges when onboarding, focusing on those five for now: The information overload on day 1, so improper schedule of expected material to be consumed by our new onboardee. Not setting clear expectations and goals which may lead to a lack of employee engagement. If they don’t see what’s upcoming, what level they should be performing at a certain point, it might disengage them. Improper way of providing or grabbing the feedback so that we can do continuous improvement and eventually also inconsistent onboarding across different managers. So we don’t have one way of doing, so we are not able to reproduce and get better and improve on the process.

3. Importance of a Project Template (0:46 – 1:15)
So to me, this feels a lot like a solution to these issues are to have a project structure, to have a project template that we can leverage every time that we have a new employee onboarding with the business so that we have a structured way of onboarding the employees either by providing set goals or expectations by definition and by timing so that we can have a certain project plan for those employees so that we have clear visibility on when they should be completing those components of onboarding.

4. Using a Project Plan (1:16 – 1:45)
Using the project plan here to visualize and eventually even to have a certain scheduling and have them already from day one under your scheduling board so that you can see what their occupation will be from the beginning. Using that project here also is a good way of getting some details of things that they need to cover while they’re doing their onboarding. Either through a certain definition or different checklists items they need to mark as complete to set the status and the progress of each of those tasks on their project. It’s a very good way of structuring what they are expected to do.

5. Providing Training Material (1:46 – 2:10)
Providing some external links to trailheads or expert sites for their training material or to your LMS software, why not? So that you have different items that they need to cover and complete for their training. Or why not leverage those QR codes here where you can have some additional information that might be consumed on a cell phone or some other external screens, so take a look at that one, you might be interested into this one.

6. Feedback and Continuous Improvement (2:11 – 2:45)
So that structured approach here, using a project template that can be leveraged and assigned to a new onboardee every time they come in, is a good way also to gather, and a good container to get the feedbacks and then continuously improve as you will be able on your project closeout lessons learned. When you’re complete, you’re done with that onboarding project to get that feedback into that template so next time some other manager needs to onboard an employee, they will benefit from your experience and you will be able as a business to develop a good onboarding experience.

7. Conclusion (2:46 – 2:55)
Hopefully that helps and spur some ideas for you. Let us know if you have any questions, it will be a pleasure to have a discussion. Thanks! Have a great day!

1. Introduction (0:00 – 0:13)
Hello everyone. Dominic for another ‘How I Solved It With Klient’, talking about how we can add value to a project closure using surveys amongst other things.

2. Challenges in Project Closure (0:14 – 0:35)
Challenges we’re all facing here: getting better at what we do. As I always say, life is a project, but how can we prevent repeating the same mistakes over and over? How can we do in the context of a project for implementation? How can we do a better transition planning to the rest of the team that will need to interact with our customer after. Recording and reporting customer feedback.

3. Importance of Project Closure (0:36 – 0:55)
How can we do that within the context of one system or our project so that we can have better visibility on that. Making the project closure as an added value activity. How can we convey to the rest of the team that this step is key for us to get better?

4. Best Practices for Project Closure (0:56 – 1:30)
So, two best practices here, there could be a longer list but focusing on those two. First is to make project closure part of your delivery recipe. So it needs to be there so that we build that habit and then getting the feedback from the customer, but especially take action on that and on the results that you’re getting from those probings.

5. Incorporating Project Closure in Templates (1:31 – 1:50)
So first thing is that it needs to be part of your recipe, it needs to be part of your project templates. When you spin a new project for an engagement with a customer, the project closure step should be there so that we have visibility on that, we can foresee it, we can plan it, and we can make sure that we have visibility as a team on those steps.

6. Using Checklists for Project Closure (1:51 – 2:20)
So making it as a milestone most likely on our project, makes a lot of sense so that you can include it as a task as part of your project template, have some key information descriptions, maybe guidance of what you’re expecting to be done and how we want to do that as a business, when we’re doing that project closure, so key information here on the task that can be brought over when we’re spinning that new template.

7. Sending Surveys from Project Context (2:21 – 3:00)
The checklist is also quite interesting because the checklist is really “don’t forget to do this” so there’s a certain list here connecting and sending the survey, sharing the lessons learned through a Slack channel maybe, so just providing guidance to your team of what you’re expecting to make this project closure process complete. As they are going through those steps, they’ll be able to mark complete and we’ll have an assessment of what was done in this stage here.

8. Analyzing and Using Survey Results (3:01 – 3:30)
A bit more on the send project closure, an interesting aspect here is that sending the project right from the project context, makes it quite interesting. It is a step, it’s something that will be within your system so you can easily select here ‘Send survey’ right from your project that you’re completing, which is going to use the contact information from the account of that project. You can simply select who were the contacts within that engagement you completed, sending them through a pre-built survey, it’s an email survey that they will receive and then selecting which survey that you might have.

9. Leveraging Survey Feedback for Improvement (3:31 – 4:00)
Based on context, in this case here the post go live, but selecting the right survey that they will receive that and the result, as you’ll see, will be back right into contacts in that project. The customer, as we’re sending that will receive an email from using your template where they can directly into an email take action and start filling that survey. So a combination of NPS, CSAT, star-style type of questions, open topic questions… We also have multi checklists and radio button, so all possibilities here to build a detailed survey, with whatever information that you feel are required to complete that.

10. Conclusion (4:01 – 4:30)
Submitting the response, the customer will send the information back into our project. So right in context, we will have information available to see the responses. Maybe with some high level information reports here, and dashboard report components right on our record to show NPS results, maybe or having a full detailed list of all answers per customer that we can see right from our project. Providing visibility to the team on that feedback that you’re getting from the customer will be key for the business to improve. And then feedback that knowledge within your templates to keep on improving your delivery methodology and procedure and documentation. That’s gonna be very important to get better, but leveraging that information also will be key. Thanks! If there’s any questions, it’s always a pleasure. Reach out to us and we can continue the discussion.

1. Introduction (0:00 – 0:12)
Greetings! We all know that running a professional service team smoothly requires handling customer relationships efficiently.

2. Challenges in Customer Relationships (0:13 – 0:50)
But as challenges arise, it will increase risk of hindering service quality. Whether it’s difficulty accessing all customer data at once due to disconnected systems, inconsistent interactions between customers and your team. Difficulty in gathering feedback to guide improvements, irregular contact points with your customers or slow responses to their demands. This can all significantly impact customer satisfaction and business financial results.

3. How Klient PSA Solves These Issues (0:51 – 1:20)
Klient PSA ensures easy access to up-to-date customer data, combining accounting contacts to project delivery information, proposals, projects, invoices, survey results are all on one page for easy access. Yes, that’s right! Klient PSA comes out-of-the-box with survey mechanics allowing you to capture and analyze customer feedback efficiently from any touchpoint.

4. Leveraging Customer Feedback (1:21 – 1:40)
Customer feedback is crucial for continuous improvement, obviously. Why not leverage disinformation to update how we’re delivering our next implementations, by updating our project templates.

5. Sharing Project Progress (1:41 – 2:00)
Klient also makes it easy for project managers to share project progress and budget updates with their customers in a sleek and intuitive format. With one click, updates can be sent from anywhere, anytime! It simplifies communication and will surely strengthen relationships.

6. Transparency and Monitoring (2:01 – 2:30)
Nowadays transparency is key. Klient allows customers to monitor progress live, by sharing selected information on Klient customer community. Information such as deliverable statuses, information from projects, giving customers call to action by assigning them tasks that they need to complete. Listing all sent invoices for historical review of data by the customer. Or interacting with your staff using the Salesforce platform chatter option.

7. Encouraging Engagement and Loyalty (2:31 – 2:50)
It will surely encourage engagement and loyalty. Klient is definitely a partner in elevating your customer satisfaction and business efficiency, as it helps you streamline communication, enhance and boost customer interactions, reveal insightful and actionable feedback data, enrich customer trust and optimize your project progress sharing in the snap of a finger.

8. Conclusion (2:51 – 3:10)
So yes, Klient can help you bring your professional service team to new heights, ensuring business growth is just around the corner. So next, let’s connect and discuss how we can help your business. Thanks!

1. Introduction (0:00 – 0:13)
Hi everyone! This is Yanick for another ‘How I Solved It With Klient’. In this episode, we’re going to be looking at how we can prevent budget disaster before it happens.

2. Importance of Budget Control (0:14 – 0:35)
So as a project manager, I don’t want to go over budget. Budget is precious. I want to keep it in my project. I want to be notified and alarmed if ever I’m going to go over budget and if it’s the case, I want to be able to easily dig in and find the root cause. And at that point, I want to be able to stop everything or course correct, so I can deliver my project successfully.

3. Introduction to Klient (0:36 – 0:50)
So with this in mind, let’s go see it in Klient.

4. Daily Routine of a Project Manager (0:51 – 1:10)
So as a Project Manager, at the beginning of my day, after looking at my release note in Klient, I would go in my ‘Global Workspace’ where I would see a detailed list of my projects with the different attributes and surprise, surprise here! We do have some red showing. It wasn’t the case yesterday.

5. Identifying At-Risk Projects (1:11 – 1:30)
So, we have this project that has become at risk and we definitely need to take care of it. As a Project Manager, I want to be able to simply investigate.

6. Investigating the Problem (1:31 – 2:00)
So let me go in my Workspace, switch my preset to another set of columns where I’m going to be able to see in detail that this is the main problem we have, the design phase of this project, where we had 29 hours estimated, 21 hours have been logged so far, and only 25% has been completed. And we can see with this specific field, and this is the key here, is that 84 hours is estimated at completion if we keep this course.

7. Course Correcting the Project (2:01 – 2:50)
So as a good Project Manager, I want to be able to go in and course correct like we said. So let me open up that specific task and go see its details of what it entails. So a design task could always be tricky. In this case, we’re building a customer community page for our customer. So, there’s a design that’s been proposed. We can see the team, you have myself and also have Jim and Ben Gray, my Developer and our Business Analyst. And this is the main problem here is that if we stay on course at 25% complete, with that number of hours logged and the estimation, we’re going to end up at 84 hours. So this is unacceptable.

8. Resolving the Issue (2:51 – 3:30)
So let me go in and see more of the details. On the left side, I can see my checklist, where only one out of four items, for 25%, has been complete. So we need to tackle the other tasks if we want to get unblocked and unstuck. And we can really go in the details here and because everything lives under one roof, one roof, one system, all that communication is also following and we can see that there’s been a lot of communication between the Developer and the Business Analyst not agreeing on the design. This happens quite often. This is how you go over budget.

9. Making the Final Decision (3:31 – 4:00)
So now I can simply and easily stop this madness and say ‘I got it, first design is good enough!’ and then communicating with my team, we can unstuck this task and I’ll handle Jim and the way he handled this task in his one-on-one. But now I can come back here in my checklist, define that the ‘Develop design’ is good. As a Project Manager, I do approve that design. And just like that my task is now completed.

10. Conclusion (4:01 – 4:18)
And then the number of hours… I’ve ended up at 21 hours. So we are even under budget because I’ve been able to see and interact very rapidly with my team to prevent that budget overrun. So at the end, with Klient as a Project Manager, I never go over budget because I always find out before it happens and I can then course correct effectively. So with this, I say thank you and see you in another episode!

0:01 – Introduction
Greetings everyone! Dominic for another ‘How I Solved It With Klient’. Today, on how we can ensure project accuracy with contextual timesheets approval. First, not doing an approval process for your timesheets will generate some challenges. It will reduce the accountability of your team against the information they put on the projects. It will also reduce the accuracy of your project remaining budget so that you can have project overruns or poor reactions to changes on the project. It will obviously potentially generate errors on the billing, which could cause disputes or dissatisfaction of your customer, and ultimately reduce the efficiency of your operational process with back and forth between Project Management and the accounting part of your projects.

0:56 – Best Practices
So just to name a few best practices here related on that topic, which would help in using Klient is the real-time project tracking. Log time as often as possible, daily, worst case weekly, so that your information is as valid as possible. Launching your timesheets within an automated approval process, which can be contextualized based on types of projects and other business rules. Including your team members to validate the data, so the right person at the right time. If the PM is the best person, then we have the PM. If in some other context it should be Functional Manager, have that person validate the information. Operate within an integrated system so that you use the same information for project management, time tracking, and eventually invoicing. And as for any other processes, keeping an eye on dashboards is always a big plus.

1:58 – Timesheet Approval Process
So without further ado, let’s show how to achieve a few of those items within the Klient system. This all starts on My Timesheet where a consultant will be able to commit on their time, hitting the Submit button. Once this is clicked, it will launch into the approval processes as set by the system admin. The approval process can be easily configured by reaching Setup, and then getting on the configuration side into the Approval Processes section. That approval process will define what are the conditions, we could think of having several approvals for maybe billable projects, where timesheets might go to a Project Manager, then to accounting. Or a non-billable project, let’s say for training or any overheads that you might want to track so that it goes to Functional Managers in those cases. Each of the actions, approval, rejections, or recall, can be set to have email templates to automatically notify users that an action is required from them.

3:00 – Mass Approval UI
As an approver, I will have mass approval UI to help me look over all timesheets that are pending my action. I can look at those timesheets grouped by projects, project resource, role, or even account, based on the context that I’m in. The high-level information will provide more information of what I’m looking at. I can also eventually look into further details, hovering over this to look into all the comments or digging into a timesheet for further details. Once I’m done, I can mass select any timesheets that are okay and ready for the next step, and then I can simply select what is the status and then hitting Submit. This will launch the next step of our approval if it’s a multi-step approach.

3:43 – Dashboards and Reports
As for any other processes within our business, we should leverage the dashboards and reports to review the information based on different segmentations or grouping that we want to have. That information can eventually be used so that we create personalized flows to notify our users, if a timesheet is not submitted for example. We can also use the reports to have a global overview of all our comments or time entered, so that it’s another tool that can support the timesheet approval process.

4:14 – Conclusion
All in all, Klient will help you improve the quality of information by easily setting up contextualize approval process. Simplifying the review of your timesheets with the mass timesheet approval UI. Using the available data for personalized notification. Improve the data quality and review using the dashboards and reports. And ultimately reducing your invoicing cycle. Hopefully, you’ve seen a few tricks that will help in your business. Let us know if you have any questions or comments. Always a pleasure to help! Reach out to [email protected], it’ll be a pleasure. Thanks, have a great day!

Introduction (0:00 – 0:14)
Greetings, everyone! Dominic for another ‘How I Solved It With Klient’. Today a quick tip related to a question from Billy Blue on “How can we highlight key related records on a Klient page?” and we’ll use dynamic related lists for this.

Overview of Page Layout (0:14 – 0:37)
So here’s how my page layout looks like on my environment here where I have some subtabs showing open milestones and uninvoiced items. This case, maybe when we’re logging onto a project, we just want to have a quick snippet on key items.

Dynamic Lists for Open Milestones (0:37 – 0:54)
Open milestones might be one. So in a big project, you might have several milestones. You want to see what’s still there, put some highlights and focus on the milestones. I could have a dynamic list here, showing just open milestones right on my page layout.

Dynamic Lists for Uninvoiced Items (0:54 – 1:25)
Same concept here with ‘Uninvoiced’, where if I’m a project type ‘time and material’, then I have a certain number of lists showing, ‘Timesheet Splits’ for billable items, maybe my ‘Milestone Payments’ that I could have for specific deliverables or in some other cases, ‘Billing lines’ or ‘Expense lines’ if I have any.

Accessing Setup and Page Layout Configuration (1:25 – 1:43)
So to do just that, we just reach out to the ‘Setup’ and go into the ‘Edit Page’. This brings you on the backside of your page layout itself, where you can configure that. So if you’re a system admin, you should be able to do that.

Configuring Dynamic Related Lists (1:43 – 2:16)
So here I have my tabs that we were seeing earlier. So let me reach the ‘Uninvoiced’ one. So to add those lists, we simply need to drag the ‘Dynamic Related Lists – Single’ and then drop in on our page. And then the configuration starts for each of those lists.

Setting Up Timesheet Split List (2:16 – 2:42)
So here, how I’ve set up the timesheet split ones, where we select the related lists that we want to see, so any objects that are related to our Klient project record that we’re looking at right now. What is the label that we want to use? And then going lower here we have the related list fields that we want to see.

Defining Columns and Filters (2:42 – 3:14)
So what are the columns that you actually want to show in your related list. So you can go and select any fields from the Klient task and the timesheet split sorry, that we have here. Then we can sort by some fields and define on the order. And then we get into the filters. So in this case, for this timesheet split list, I’m showing only ‘Uninvoiced’. So where ‘Invoiced’ checkbox is equal to false. And then where the ‘Billable’ checkbox is equal to true. So only those timesheets split records are going to show here.

Additional Filter Examples (3:14 – 3:45)
We understand that it would be the same concept if we were to say only ‘Open milestones’, so where milestones equal true, and then where ‘Status’ is not equal to ‘Completed’. So you can think of several types of filters here.

Setting Component Visibility (3:45 – End)
And then the other neat aspect here is the set component visibility. So maybe timesheet split, we don’t necessarily want to have it on every type of project. Maybe we want to see it only if it’s a time & expense type of project. So we can set, based on the record that we’re looking at, so in this case the Klient project record, we can define what conditions would make this list view visible. So this is how we can use the dynamic related lists to show specific items or highlight key related records on our page layout. Obviously that can be used on any types of records. We could also find lots of other examples, maybe even on invoices or your tasks themselves. Hopefully that helps. If you have any further questions, feel free to reach out to [email protected] to continue the discussion on this. Thanks! Have a great day!

0:00 – Introduction to Exception Reports
Hey, greetings everyone! Dominic for another ‘How I Solved It With Klient’! I want to talk about exception reports now and how they are a key tool to maintain data quality in your system. So we do have access to a myriad, a notion of information these days. We are bringing everything on the same system which is great, but how do we keep focus and how do we have access to key information that needs to be addressed right now? How do we identify process blockers or things that might be an issue, so that we have a process that runs smoothly and we address or tackle potential problems with our customer before they become one? And then how do we provide visibility on critical tasks that need to be addressed? So these are just a few challenges obviously, that can eventually be addressed using exception reports.

0:52 – What are Exception Reports?
And what do I mean by the exception report? It’s really just a report that focuses on an hour type of things. In this case I’m showing the example of billable milestones. So you’re doing project management, you have some deliverables. There might be a gate or a key date that needs to be tracked, a project go-live, or some delivery approval that are attached to a payment. So here I’m looking at only milestones from our project. So it’s a subset of tasks within all my tasks that I have in my system. And I’m looking only at tasks that are overdue. So my due date is in the past, so something needs to be done about that. Or if my status is not complete. So if they are in the past and not completed, either I need to change the date and reschedule and address the issue with the customer or whomever is dependent on that milestone to be completed. Or I update the status because it was actually completed, but it was not marked as such. So that’s an exception report.

1:59 – Benefits of Exception Reports
Looking across all my information just to find some key information that we need to address, that we might have an issue with, have a challenge managing it. So in this case, we can use or review that information obviously as a report itself. Another neat thing that I like to do often is to use the ‘Subscribe’ button on reports in Salesforce where you can have that scheduled, sent over to you. It could be sent only if there are actually records in there, so you just send me the report if there are records, if there is more than one. So that also serves as an alert. I love that feature, especially when we’re doing a pilot or trying to find solutions to address a process before we fully automate things. I like to use the ‘Subscribe’ on reports, to address that. And obviously, those exception reports should be used and leveraged also on dashboards. So if you want to provide that visibility and generate accountability to people, you should expose that and review them as a team.

2:52 – Practical Example: Pre-Invoicing
So here the example is pre-invoicing, so finance, accounting. They’re looking into generating new invoices, they want to make sure that everything is up to date. Overdue billable milestones is going to be key for them. So they will want to look with their PMs and make sure that there are actions taken to correct the information. So reschedule or mark as complete so that we can go on the rest of the process.

3:39 – Summary of Benefits
Benefits, obviously, just to summarize my thoughts here: We want to create team alignment and visibility by using those exception reports, bringing focus to people so that we stimulate accountability. People will tend to make sure that they maintain their information. If we keep on looking into those exception reports in the team meetings, it’s going to build some habits, doing so.

4:02 – Conclusion
So hopefully you find some value into this trick here, using exception reports to have better visibility over your information. Thanks, you have a great day!

Introduction (0:00 – 0:13)
Hey, greeting everyone! Dominic for another ‘How I Solved It With Klient’ with a customer question today on how we can prevent time entry on specific tasks.

Customer Query (0:13 – 0:17)
So thank you, Rose, for your question. I will go a bit broader than the specific task here to show you all the ways we can affect time entry.

Project Settings (0:17 – 0:44)
I’m starting on a project where I want to show you the ‘Close Time Entry’ field. First, if you are on a V48 or earlier version, you should have that available. If not, it’s most likely just not showing on your page layout. Reach out to a system admin so they can bring it back as visible.

Close Time Entry Field (0:45 – 1:55)
Here, ‘Close Time Entry’ on a project, if enabled, means that anyone from the project will not be able to log hours on that project. This can be used in the context where the project is not completed, it might be on hold for some reason, financial issues, or whatever. You want to prevent your team from logging hours on there. You might want to use that temporarily so you can control the hours being entered against that project. It is also available if you reach a Klient task where that same name field ‘Close Time Entry’ is available.

Preventing Time Entry on Klient Tasks (1:56 – 2:59)
Same kind of use, this will prevent logging hours on a specific task. You might also want to enable that temporarily or permanently depending on the need. Another way to prevent time entry is by using resource availability. Resources can be set to unavailable, meaning they won’t be able to log hours during the time they are unavailable.

Timesheet Custom Settings (3:00 – 3:36)
Next, you have timesheet custom settings. First one is ‘Disable Completed Tasks’, which states it by the name, which is if you have the task completed, it will not be available in your timesheet. The other one is ‘Display Assigned Tasks Only’, where if you want to be very prescriptive on how people are logging their hours, if you enable this, the resource would only see assigned task in their dropdown.

Custom Validation Rules (3:37 – 4:15)
And the last one I’m listing here, custom validation rules. If you want to affect time entry, you can add custom validation rules on timesheet detail object. If you have a different use case, that’s also another option, to show an error message on a line that maybe you don’t want hours to be logged for some reason. Exceeded number of estimated hours or some other business rules you might have.

Conclusion (4:16 – 4:29)
So hopefully one of those five ways will suit your need. If you have any questions, comments, feel free to reach out to [email protected]. It will be a pleasure to support you and help you in finding the right method to apply in your context. Thanks, have a great day!