In the "Hours Worked Report flow" which I showed the other day, it has been designed that the working status becomes "Vacation" when the deadline passed without reporting one's attendance. Does it mean that it is possible for the person him/herself or the boss or the management to confirm the days when the vacations were taken just by looking at the processing record of the "Attendance Report flow", which is actually the attendance record?

No, Wait a minute... There could be a possibility of a case where it has been recorded as vacation despite worked, because forgotten reporting. In the first place, a "vacation" should be given only after you apply in advance and your boss approves it.

The management department checks the monthly service record by matching "Leave application" and "Attendance record (record of Hours-worked reports)". In case if an employee is recorded as on vacation on the attendance record, but the corresponding application has not been submitted, you need a correction of attendance record (reapplication) or to ask submission of leave application (Post-application). In order to reduce the extra labor in the management department, it is desirable to correctly make attendance reports and leave applications, and to confirm oneself whether there are omissions at the end of the month.


[Leave Request Flow]


In Japan, half a month has passed since a new fiscal year started, so I guess the new hires are getting used to their new environment.

In the past two weeks, we introduced workflows for "Attendance report flow" and "Daily report flow" oriented (not necessarily) for new employees. If you've "reported" properly every day, I suppose you thoroughly got used to operations of the Workflow platform.
When you compare these two Workflows, you will recognize that they are very similar
  • It is automatically started and appears in [My Tasks] of all employees every morning
  • An employee reports, the boss (a leader) confirms.
  • The deadline has been set and if it is not finished until, it automatically terminates

Even though the contents to be reported are different as "work time" and "work contents" depending on the Workflows, their outlines are almost the same. Then, why don't you put these together?

[Attendance-Work Report]

Based on the "Hours Worked Report" in Episode 581, I made some improvements to make it capable of reporting "work content" as well. With this, it is now possible to report/check "work time" and "work content" of that day in one Workflow! It is now convenient, isn't it?

You can complete a new Workflow in ten minutes or less since the changes are few. It is not a good idea to include too much of this and that in one Workflow definition, but by integrating similar flows, users can complete their reporting with fewer operations. Even though the changes are few, the effect of the improvement will be great if the Workflow is used by many people every day.
(On the other hand, splitting a grand Workflow that is too complicated will lead to big business improvement.)

As you use and operate Workflows every day, it is very important to keep improving them continuously. It is often happening to become easy for the user to use just by changing a Data Item name or adding an explanation. In addition, it is also important to instantly reflect it in the Workflow definition when the business rule changes. Always try to be flexible for modification/improvement according to your organization and users.

<Operating screen: "2. Enter leaving time/work content">

<Data Items list>


[Free download]
Business Template: Daily Report



<Similar Models>


<<Related Articles>>



[Japanese Entry (ε’Œζ–‡θ¨˜δΊ‹)]

In the previous post, I introduced you the "Hours-worked report" which even new hires make every day. It has been designed considering input effort to be reduced by devising of initial value and input screen so that reports are made properly every day. Speaking everyday report, the daily report is one of them. Whether it is during the training period or after being assigned, it is an important task for new recruits to report the "works done" and "matters learned" to the superiors or to seniors.

Through the daily report, new hires can learn business etiquette and how to work, and also help them communicate with their boss, seniors or other employees. Above all, the opportunity to look back on the day and organize what you learned or noticed is particularly important to be in the new environment.

[Daily Report]

In Japan, spring is the season of cherry blossom and the starting of a new life.

Another new fiscal year begins today, so an employment ceremony is held in many companies. Once a new employee is assigned, the superiors, senior employees, or HR staffs will instruct this and that of company life. Among them, it supposedly includes "how to make work report".

Recently, "Workstyle reformation" and "Discretionary working time system (Exempt employee)" are topics frequently discussed, so it is very important to be able to record and to recognize the hours worked properly. (Attendance management)
Reporting and recording of attendance and leave time has been managed in various ways, such as by filling in paper or stamping on time cards when it used to be, or now with IC cards or in a dedicated system, etc. Also, to use a general-purpose Workflow system is one of the ways.

Sometimes "Attendance report flow" is referred to as "the four major Workflow Apps", together with "Work request flow", "Procurement request flow" and "Out-of-pocket expenses claim flow" which I introduced you before as "the Starter templates pack". By managing attendance using cloud-based Workflow, you can take advantages of the following.
  • Teleworkers/Remote workers or staffs with frequent outings can also be recorded in the workplace or on the go
  • Daily processing allows new members to become accustomed to Workflow operations
  • Possible to improve ease-of-use for the organization continuously (would lead to reform of work style)

[Hours Worked Report]

Continuing the past two weeks, I will introduce you the operation of "Starter Template" which has been pre-installed in the cloud-based Workflow, "Questetra BPM Suite".

The third one is "Out-of-pocket Expenses reimbursement claim".
Episode 464: Out-of-pocket Expenses Reimbursement Claim (Starter Template) (2016-01-04)

It is a business flow to make an application for claiming with email attachment of images of receipts taken with a mobile camera. And there is a focus on making it easier to manage receipt images by applying sequentially. Therefore, this will be a business process which is on the premise that "regulation that allows discarding the original paper receipt by taking a receipt image with a mobile camera".

[Out-of-pocket Expenses claim]


Continuing from the last week, I will introduce you the operation of "Starter Template" which has been pre-installed in the cloud-based Workflow, "Questetra BPM Suite".

The second one is "Procurement Request".
Episode 463: Procurement Request (Starter Template) (2015-12-28)

It is a business flow that allows anyone to make requests for purchasing from consumables to equipment as long as they are employees. Since status management such as "Decision pending " or "Delivery waiting" is automated, you can check progress at any time.

[Procurement Request flow]


In the article of "Episode 577: Work Request Flow is the Basic of Workflow", I introduced you the "Work Request flow" as an operation that I can recommend for any organization. It is one of the business flows (applications) pre-installed in the cloud-based Workflow "Questetra BPM Suite", and there three other business flows are pre-installed. I will introduce you the operation of "Starter Template pack" in three articles in series from this one.

The first installment is "Approval flow".
Episode 462: Planning - Approval (Starter Template) (2015-12-21)

It is a simple business flow in which an employee "applies" a request for approval and the superior of the applicant "approves" it. The flow has been configured that if the external payment amount is 1 million JPY or more, it goes also to the "Approval" by the officer. (Automatically be approved after neglected for 24 hours)


[Planning-Approval flow]