Rigi24 The Rigi24 learning book · Stories and practice
The Rigi24 learning book · Stories and practice

Chapter Eleven: The Shift That Didn’t Make It into the Report

Learn technology and business through stories

Chapter 11Educational fiction with dramatized characters and clients Rigi24

Before you begin

This story-led series teaches practical concepts in attendance tracking, school management, and business software. Each chapter presents a relatable situation, followed by takeaways and links to explore the tools further.

Important note: Characters, dialogue, and the names of individuals or client businesses in these scenarios—apart from explicitly identified real brands—are fictional or dramatized for educational purposes. This is not a factual account of a real case or an allegation against any person or company. NetCity, Rigi24, Kadrebi and SkolaPlus are real brands and services; their features may evolve.

Read the story ↓Tools and further reading ↗

Chapter Eleven: The Shift That Didn’t Make It into the Report

A Manager with Thirty Years of Experience Who Didn't Want to Learn Thirty Buttons

Nine Twenty — Eight Hours and Five Minutes

خاتونا و بادری ساعت Log in و Log out شیفت شب را بررسی می‌کنند
خاتونا و بادری ساعت Log in و Log out شیفت شب را بررسی می‌کنند

Khatuna checked the attendance report for the second time.

She was in charge of human resources at a service company in Tbilisi—a company with more than sixty employees that provided cleaning and preparation services for workplaces and commercial spaces.

The day before, an employee had come to the human resources department.

He said he had worked the entire night shift, but his reported hours were lower than he expected.

After an initial review that same day, Khatuna had contacted NetCity support.

Now she had the findings of their investigation.

The employee's clock-in had been recorded at 21:58.

His clock-out was at 06:03 the following morning.

Neither record was missing.

The issue lay in how the reporting period had been selected.

Some of the working hours fell on the next calendar date, and the report Khatuna had been using did not display the whole shift together.

She checked the settings and the shift report again.

This time, both events were visible.

Khatuna breathed a sigh of relief.

Just then, the office door opened.

A man of about sixty-five walked in, with white hair and glasses that always hung from his shirt pocket.

Badri, the owner of the company.

“Good morning, Khatuna. Is the problem with the hours sorted out?”

“Good morning. Yes. The records were correct. We needed to review the report using the right time range for the shift.”

Badri asked,

“So our employee was telling the truth?”

“Yes. His clock-in and clock-out records were there.”

Badri nodded.

“Good. I just don't want anyone shortchanged because of an incorrect report.”

Khatuna said,

“I'll complete the report, and we'll let the relevant department know the outcome.”

Badri was about to leave the room when his phone rang.

He looked at the number.

His expression changed.

“Hello, Mr. Levan. What can I do for you?”

He listened for a few seconds.

Then he asked,

“For tomorrow?”

Khatuna looked up.

Badri walked over to the window.

“How many people do you need?”

He paused.

“Six?”

His expression grew more serious.

“Let me check the staff schedule. I'll give you a definite answer by noon.”

He ended the call.

Khatuna asked,

“What's happened?”

Badri put on his glasses.

“A longtime client needs six service staff for tomorrow morning. They have an important event, and they can't change the time.”

Khatuna said,

“We'll have to see who's available.”

Badri sighed.

“We already have several people on leave.”

Khatuna replied,

“We'll need to check the report.”

Badri looked at the monitor.

“The report again?”

Nine Forty-Five — Thirty Years of Experience

Badri had been in the service business for thirty years.

Years ago, he had started his company with three employees.

Now more than sixty people worked for him.

He knew his longtime clients by name.

He knew which supervisor performed best when things got busy.

Within a few minutes of conversation, he could work out what a client was unhappy about.

But he had no interest in learning complicated software.

Khatuna opened the staff management page.

“First, we need to look at tomorrow's schedule.”

Badri sat down beside the desk.

“Where do we start?”

“In the human resources section.”

“Then?”

“The shift schedule.”

“Then?”

“We need to select the date and the work group.”

Badri laughed.

“Khatuna, how many computer tests do I have to pass just to find six employees?”

Khatuna smiled.

“None. We just need to find the right information.”

Badri said,

“I want the information, not to learn every menu in the program.”

Then he added mischievously,

“And every time you bring in new software, there are more buttons!”

Khatuna remembered her earlier conversation with Mari.

“Actually, we do have an easier way.”

Badri asked,

“What way?”

“Rigi24's AI.”

Badri took off his glasses.

“Is that the thing everyone's talking about these days?”

“Yes. But this one is inside our own company management system.”

Badri asked skeptically,

“So it's going to teach me how to manage my employees?”

Khatuna laughed.

“No. It can help you find information and carry out certain tasks.”

Badri said,

“All right, let's try it.”

Ten Oh Five — The First Conversation

Khatuna opened the AI assistant.

Badri looked at the screen.

There was a box for typing a request.

He asked:

“Do I have to write in English?”

“No. You can ask in your own language.”

“You mean Georgian?”

“Yes.”

Badri smiled.

“I like this one.”

He leaned a little closer to the screen and typed his first question:

“How many of our employees are on leave tomorrow?”

A few moments later, the assistant checked the information available to the management account and provided a report on recorded leave and the status of requests awaiting approval.

Surprised, Badri asked:

“That’s it?”

Khatuna said:

“That’s it.”

“I didn’t have to go into the leave section?”

“No. You asked the question directly.”

Badri typed his second question:

“Which employees in the service department are scheduled to work tomorrow?”

The assistant displayed the work schedule information.

Badri recognized several names.

Then he asked:

“Has anyone requested leave that hasn’t been approved yet?”

The information on requests awaiting review appeared.

Badri looked at Khatuna.

“So it doesn’t just give canned answers from the internet?”

Khatuna replied:

“No. When the necessary access is granted and the relevant tool is enabled, it uses this company’s actual information.”

Badri thought for a moment.

“So if I ask which of our customers owe us money today, it can tell me that too?”

Khatuna said:

“If the information has been recorded in the relevant module, that module is active, and your account has permission to access it, it can help within the limits of its supported capabilities.”

Badri laughed.

“Then I’ll have to be more careful about my questions from now on!”

Ten Twenty — One Person Short

Khatuna checked the staffing situation for the next day.

Several people were on assignments scheduled in advance.

Two had approved leave.

Fewer employees were available for the customer’s new request than Badri had expected.

Khatuna said:

“For that assignment, we have five suitable people available at the moment.”

Badri asked:

“What about the sixth?”

“We’ll have to check the other teams’ schedules.”

Badri tapped the desk lightly.

“Levan needs an answer by noon.”

Khatuna said:

“I know.”

Badri turned to the assistant again.

“We need six people for tomorrow’s assignment. Who in the other teams might have time available?”

Based on the recorded information, the assistant displayed several candidates for consideration and indicated that their final availability would need to be confirmed by the person responsible for HR.

Badri looked at the list.

“I know this one. They used to work on the special services team.”

Khatuna replied:

“Yes, but they’re on a different team now.”

Badri said:

“We could ask them to help tomorrow.”

Khatuna said:

“First we need to coordinate with their supervisor and make sure we won’t disrupt their existing schedule.”

Badri nodded.

“That’s right.”

Then he addressed the screen:

“Then change tomorrow’s schedule yourself.”

Khatuna explained:

“If schedule changes are enabled in the AI tool and your account is authorized to make them, it can prepare the change and obtain the necessary approval. But for now, we shouldn’t change anyone’s shift without reviewing it first.”

Badri asked:

“So it can’t just do whatever it wants?”

“No. It follows the same system restrictions and permissions.”

Badri said with satisfaction:

“Good. I wouldn’t want anyone changing my employees’ schedules without permission either.”

Ten Forty-Seven — Leave That Must Not Be Sacrificed

خاتونا و بادری نیروی جایگزین را بدون لغو مرخصی نینو هماهنگ می‌کنند
خاتونا و بادری نیروی جایگزین را بدون لغو مرخصی نینو هماهنگ می‌کنند

Khatuna reviewed the list of requests again.

One experienced employee’s name appeared.

Nino, the supervisor of one of the service teams.

She had submitted a leave request for the next day.

Badri noticed her name.

“Nino wants leave for tomorrow?”

Khatuna said:

“Yes. Her request is still awaiting review.”

Badri thought for a moment.

“Nino could solve tomorrow’s scheduling problem.”

Khatuna said nothing.

Badri asked:

“What’s the reason for her leave?”

Khatuna checked the request details she was authorized to view.

“A family matter.”

Badri leaned back in his chair.

“How many years has Nino been working with us?”

“Nearly seven years.”

“How many times has she helped us when we needed her?”

Khatuna smiled.

“A great many.”

Badri was silent for a few moments.

Then he said:

“Then it’s our turn to help her when she needs us.”

Khatuna looked at him.

“Does that mean you approve her leave?”

“Yes. Subject to the rules and her leave balance, of course. Let’s do the final check first.”

Khatuna said:

“Everything’s ready.”

Badri looked at the AI assistant again.

“I want us to record and approve Nino’s leave for tomorrow.”

Khatuna said:

“Write the request precisely.”

Badri typed:

“Review Nino’s leave request for tomorrow and, if it meets the regulations, prepare it for approval.”

The assistant checked the request details, the date, and the type of leave.

Then it displayed a summary of the proposed action.

The change had not yet been carried out.

Badri read the details.

“What’s this step for?”

Khatuna replied:

“So that before any important change, it’s clear exactly what is going to happen.”

Badri said:

“Good.”

After reviewing the information and making sure he had the necessary authorization, he submitted his approval.

The supported action was completed, and the result remained in the relevant record.

Badri smiled.

“So it’s recorded now?”

Khatuna checked the status again.

“Yes. The result has been recorded in the system.”

Badri said:

“Very good. Now let’s find our sixth person.”

Khatuna laughed.

“I thought you might hold off on Nino’s leave until tomorrow’s schedule was sorted out.”

Badri replied:

“No. If I’ve spent thirty years managing people and still haven’t learned that employees have lives too, what were those thirty years good for?”

Eleven ten — An Important Customer

Badri’s phone rang again.

It was Levan.

“Hello, Mr. Badri. Have you had a chance to review tomorrow’s schedule?”

Badri replied:

“We’re coordinating things. I’ll give you a definite answer by noon.”

Levan said:

“We really do need six people. Our event has a fixed schedule.”

“I understand. I don’t want to make a promise we can’t keep.”

When the call ended, Khatuna said:

“We should look at this customer’s request history too.”

Badri asked:

“Why?”

“There might already be an agreement on record about the timing, the number of staff, or the terms of service.”

She opened the customer relations section.

The customer’s information was in CRM.

Previous calls and requests had been recorded.

Badri said:

“Can we ask the AI about this customer too?”

Khatuna replied:

“Yes, within the information and tools enabled and authorized for your account.”

Badri typed:

“Show me this customer’s latest requests in CRM.”

The assistant reviewed the available information.

Khatuna also went through the file’s details with him.

It turned out that the customer needed six people for tomorrow’s event, but the service start time differed from what Badri had understood during the first call.

Badri asked:

“So all six don’t need to be there first thing in the morning?”

Khatuna replied:

“According to the recorded request, two people start earlier for setup, and four are needed later. Of course, we need to confirm that with the customer.”

Badri said quietly:

“So we were looking for six people to start at the same time, when the actual schedule was different.”

Khatuna said:

“Yes. We need to read the request carefully.”

Badri laughed.

“Well, would you look at that! For thirty years I’ve told my employees to understand the customer’s requirements properly before accepting a job. Today I nearly forgot that myself.”

Eleven twenty-eight — A Decision the Software Would Not Make

Khatuna called one of the team supervisors.

One experienced employee was available to help with the second part of tomorrow’s schedule, provided the reassignment did not conflict with their existing work.

The supervisor checked the arrangements.

A few minutes later, they replied:

“We can arrange it. It won’t make any significant difference to their existing schedule.”

Khatuna said:

“Good. Please speak to the employee as well and let us know the outcome.”

Badri waited.

Ten minutes later, the arrangements were complete.

The employee had agreed to the proposed schedule.

Khatuna recorded the necessary change through the authorized human resources process.

Badri said:

“So all six are ready?”

“Yes. With two different start times.”

“And Nino’s leave is still approved?”

“Yes.”

Badri breathed a sigh of relief.

“Very good.”

Then he looked at the AI assistant’s screen.

“You know, Khatuna, something struck me.”

“What?”

“This system didn’t decide whether Nino could take leave. It didn’t decide what we should promise the customer. It just helped us see the right information sooner.”

Khatuna said:

“Yes. The management decisions are still ours.”

Badri replied:

“And that’s very important.”

Twelve oh five — NetCity

At the NetCity office, Nika was reading the documentation for Rigi 24’s AI.

Mari asked:

“How far have you got?”

Nika said:

“Far enough to realize that AI isn’t just for answering questions.”

“All right, go on.”

“It can review information within the user’s access permissions and, if the necessary tools are available, help carry out actions too.”

Mari smiled.

“That’s right.”

Nika said:

“But I have a question.”

“Go ahead.”

“Suppose an employee at a company asks the AI how much their manager earns.”

Mari replied:

“If they don’t have permission to view that information, the AI shouldn’t show it to them either.”

“Even if they ask very politely?”

“Even if they ask in verse!”

Nika laughed.

Just then, Morteza said from the technical desk:

“AI mustn’t become a way to bypass the system’s permissions.”

Nika turned around.

“So, authorization first, then the action?”

Morteza said:

“Yes. Understanding the request is the AI’s job. But validation, authorization, execution, and logging must remain under the system’s control.”

Nika thought for a moment.

“So if I say, ‘Cut all the store’s prices in half,’ it shouldn’t just do it without checking.”

Morteza smiled.

“Exactly. Especially when the store isn’t even yours.”

Mari laughed.

Nika said:

“Well, that’s another one crossed off my list of economic master plans!”

Twelve thirty-seven — The Manager Who Asked the Questions Himself

بادری شخصاً از دستیار هوشمند منابع انسانی استفاده می‌کند
بادری شخصاً از دستیار هوشمند منابع انسانی استفاده می‌کند

Badri asked Khatuna to stay with him a few more minutes.

“I want to try it again myself.”

Khatuna said:

“Go ahead.”

Badri opened the AI assistant.

This time, he typed a question without help:

“What leave requests do we have awaiting review for next week?”

The relevant report appeared.

Then he asked:

“Show me this month’s unapproved overtime.”

The assistant reported the status of the available information.

Badri asked:

“Do these extra hours mean we have to pay for all of them?”

Khatuna replied:

“Not necessarily. Recorded extra time isn’t the same as approved overtime. It needs to be reviewed under company policy and the applicable regulations.”

Badri said:

“I see.”

He typed his next question:

“Which employees have contracts that need to be reviewed soon?”

Khatuna went over the personnel records with him and explained that, for reports like these, it was important for the contract information in the system to be complete.

Badri looked out the window at the street.

“Do you know what was bothering me?”

Khatuna asked:

“What?”

“I thought that to use new software, I had to have grown up with computers like you all did.”

Khatuna smiled.

“You don’t.”

Badri said:

“I know how to run a company. I just don’t want to open ten menus every time I have a question.”

Khatuna replied:

“That’s exactly what this assistant is for: making the system easier to use.”

Badri said:

“But now I’ve realized there’s something even more important.”

“What?”

“That I need to know what to ask of it.”

One ten — A Promise That Could Be Trusted

Badri called Levan again.

“Hello, Mr. Levan. We’ve reviewed tomorrow’s schedule.”

Levan asked:

“So, is the team ready?”

“Yes. Based on the information you sent, we’ve planned for two people to handle the initial preparations and four for the next part of the event. I’d just like to confirm the times with you once more.”

Levan went over the arrangements.

“Yes. That’s exactly what we wanted.”

Badri said:

“Very good. Then we’ll coordinate the final schedule on that basis.”

Levan laughed.

“Mr. Badri, you always say we need to understand the job properly first.”

Badri replied:

“Yes. Sometimes I need someone to remind me of that myself.”

The call ended.

Khatuna asked:

“How did it go?”

Badri replied with a smile:

“The contract is still in place. And the schedule is clear.”

Then he looked at the Rigi24 screen.

“Khatuna, from now on, I want to ask more of my management questions right here.”

Khatuna said:

“Wonderful. Just remember that the information in the system needs to be accurate and up to date.”

Badri laughed.

“That’s one lesson I’ve learned well.”

Three twenty — One Last Question

At the NetCity office, Giorgi was reviewing new requests.

Mari had prepared a report on the follow-up with the service company.

Nika asked:

“So, did they sort out the issue with their time clock?”

Mari said:

“Yes. The HR officer reviewed the report, and that cleared things up.”

“And did the company’s manager like the AI?”

“Very much, apparently.”

Nika said:

“I think it’s great for people who are just getting to know the system.”

Mari replied:

“Not just beginners. Even a manager with years of experience might not want to spend time learning how to navigate every part of the software.”

Nika thought for a moment.

“So AI isn’t supposed to replace people’s experience.”

“No. It should help them make better use of it.”

Giorgi said from behind his desk:

“As long as Nika hasn’t asked it to sign a contract with a client on his behalf, of course!”

Nika protested:

“When did I ever say that?”

Mari smiled.

“You haven’t yet. But you’ll probably ask soon.”

Everyone laughed.

Nika opened his notebook.

At the top of the page, he wrote:

“Good AI doesn’t just answer questions; it helps get things done within its authorized scope.”

Then he added underneath:

“But responsibility for the decision still rests with a human.”

Five twenty — The Responsibility Left Unassigned

Badri closed the day’s final report.

Tomorrow’s schedule was ready. Six people had been lined up, and the client had approved the timing too.

Khatuna picked up her bag.

“Mr. Badri, may I head home now?”

“Yes. Thanks for your hard work.”

Khatuna had almost reached the door when she suddenly stopped.

“By the way, who’s going to prepare the final schedule for the supervisors?”

Badri said:

“I thought you were doing it.”

“I checked the HR schedule. Irma, one of the other supervisors, was supposed to coordinate with the teams.”

Badri thought for a few moments.

“Then who’s going to let the client know the outcome?”

Khatuna shrugged.

“I don’t know. You didn’t say.”

Badri laughed.

“Well, would you look at that! We found six people for tomorrow’s job, but we still don’t know who’s supposed to tell them exactly what to do!”

Khatuna said:

“Actually, Rigi 24 has a section for that too.”

“Another module?”

“Task Desk.”

Badri took off his glasses.

“So I can specify what each employee should do, and when?”

“Yes. Employees can also record and track their own personal tasks.”

Badri smiled.

“Then teach me that first thing tomorrow morning.”

Then he paused.

“Just please make sure you record that task somewhere too, so you don’t forget!”

Khatuna laughed.

Practical articles related to this story

RIGI24 · ARTICLE Rigi24 HR RIGI24 · ARTICLE HR AI

Tools and further reading

Explore the real services and related guidance behind this chapter:

RIGI24 · INTERNALRigi24 business toolsExplore more solutions and educational stories. RIGI24 · INTERNALRigi24 articles and guidesPractical articles for additional reading. RIGI24 · INTERNALBrowse all storiesLearn technology and business through stories EXTERNAL · NetCity.ge ↗About NetCityMeet the company behind the services.

Learning note: examples are illustrative, not a substitute for reviewing real records.