Showing posts with label Attendance management. Show all posts
Showing posts with label Attendance management. Show all posts

For a business system that is used every day, it is very important for users whether the input interface (input screen) is easy to understand and whether it is easy to use.

Relating a Workflow system, I often hear people saying such as;

  •  "I don't know what to input."
  • "It could be easier if there were examples or templates."
  • "I entered all the way, but it ended up as an error."
  • "The way of input varies depending on individuals."

And when I look back at our day-to-day operations, such as "Report of hours worked", "Request for approval", "Report of order receipt", "Answer to inquiries", etc., many of the occurrences of delays and reworks are mostly caused by erroneous or inappropriate input at upstream Steps.

"Improvement of work" tends to be a grandiose story such as standardization of business flow and optimal placement of resources, but as the content to be tackled becomes bigger, it takes time to get the effect. On the other hand, it can be said that "devising the input screen to reduce inputs that is erroneous and inappropriate" is a small "business improvement" that can be addressed immediately in daily work. Iterating small improvements will lead to major achievements.

In this workflow sample, I would like to introduce you the devising of "input example button" on an input screen, which allows input by clicking on it.


[Test flow for Input form]



[Test flow for Input form: "1. Input Test" screen]



When designing the input screen, it is basically necessary to set a "Data Item name" that is easy to understand, and to describe sentences and examples (Input hint) that explain how to input. Furthermore, by making it possible to select by option instead of typing, or by setting the initial value of data, the burden of inputting for a user is reduced and it also leads to suppression of variations in input data.

In addition to these means, it is also a good idea to consider using scripts such as arranging buttons for input assistance or performing input checking or setting data to other Data Items.

Even though you can set arbitrary HTML/JavaScript in [Input hint] of Questetra, in some cases it may be a trouble such as "it will destroy the layout of the whole input form". It must be set by staff members who have knowledge and experiences of HTML/JavaScript at their own risk within the range of their capability of maintenance.

▼[Input Hint] Setting Example (HTML/JavaScript):"Service Item"
E.g.: <button type="button" id="btnConsultant_1">Monthly advisory fee</button>、
<button type="button" id="btnInstruct_1">Workshop instructor fee (Diem)</button>、
<button type="button" id="btnDoc_1">Documentation fee</button>

<script type="text/javascript">
jQuery('#btnConsultant_1').on('click',function(){
jQuery('input[name="data\\[1\\].input"]').val( "Monthly advisory fee" );
});
jQuery('#btnInstruct_1').on('click',function(){
jQuery('input[name="data\\[1\\].input"]').val( "Workshop instructor fee (Diem)" );
});
jQuery('#btnDoc_1').on('click',function(){
jQuery('input[name="data\\[1\\].input"]').val( "Documentation fee" );
});
</script>
▼[Input Hint] Setting Example (HTML/JavaScript):"Quotation price"
E.g.: <button type="button" id="btnS_2">(15 years career) 820,000</button>、
<button type="button" id="btnA_2">(5 years career) 452,000</button>、
<button type="button" id="btnB_2">(Less than 15 years) 339,000</button>

<script type="text/javascript">
jQuery('#btnS_2').on('click',function(){
jQuery('input[name="data\\[2\\].input"]').val( "820000" );
});
jQuery('#btnA_2').on('click',function(){
jQuery('input[name="data\\[2\\].input"]').val( "452000" );
});
jQuery('#btnB_2').on('click',function(){
jQuery('input[name="data\\[2\\].input"]').val( "339000" );
});
jQuery('input[name="data\\[2\\].input"]').parent().parent().css("background-color","#FFC0CB");
</script>
▼[Input Hint] Setting Example (HTML/JavaScript):"Reason for Leave"
E.g.: <button type="button" id="btn1_5">Leisure and Home matter: Private</button>、
<button type="button" id="btn2_5">Local volunteer: Private (Local volunteer)</button>、
<button type="button" id="btn3_5">Got abdominal pain in the morning: Illness (abdominal pain)</button>、
<button type="button" id="btn4_5">Child's fever: Child care</button>

<script type="text/javascript">
jQuery('#btn1_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Private" );
});
jQuery('#btn2_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Private (Local volunteer)" );
});
jQuery('#btn3_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Illness (abdominal pain)" );
});
jQuery('#btn4_5').on('click',function(){
jQuery('input[name="data\\[5\\].input"]').val( "Child care" );
});
</script>
▼[Input Hint] Setting Example (HTML/JavaScript):"Approval request overview" "Budget classification"
Frequent: <button type="button" id="btnExhibit_78">(Exhibitions within budget)</button>、
<button type="button" id="btnProcurement_78">(Unexpected procurement)</button>

<script type="text/javascript">
jQuery('#btnExhibit_78').on('click',function(){
jQuery('input[name="data\\[7\\].input"]').val( "Outsourcing related to the Cloud Expo" );
jQuery('input[name="data\\[8\\].selects"][value="1"]').prop('checked', true);
});
jQuery('#btnProcurement_78').on('click',function(){
jQuery('input[name="data\\[7\\].input"]').val( "Purchase of personal computers due to breakdown" );
jQuery('input[name="data\\[8\\].selects"][value="3"]').prop('checked', true);
});
</script>
▼[Input Hint] Setting Example (HTML/JavaScript):"Reason of request"
<span style='color:#ff0000;'>* Brief in Bullet</span><br>
E.g.: <button type="button" id="btnReasonA_9">(P.C. breakdown)</button>、
<button type="button" id="btnReasonB_9">(Abrupt procurement due to the increase of personnel)</button>、
<script type="text/javascript">
jQuery('#btnReasonA_9').on('click',function(){
var myReason = "";
myReason += "External Monitor output is corrupted by the dropping in transportation (Dec. 2015)\n";
myReason += "Hindrance to the operation of the latest OS, past more than three years since the purchase of January 2013.\n";
myReason += "Choose a familiar conventional series machine, even though D Company is not the lowest price, but the difference is small.";
jQuery('textarea[name="data\\[9\\].input"]').val( myReason );
});

jQuery('#btnReasonB_9').on('click',function(){
var myReason = "";
myReason += "Increase 30 part-timers to correspond due to receiving order of more than assumed.\n";
myReason += "20 spare PC. Need 10 more.\n";
myReason += "(D company is the cheapest and fastest.)";
jQuery('textarea[name="data\\[9\\].input"]').val( myReason );
});
</script>
▼[Input Hint] Setting Example (HTML/JavaScript):"Service start"
<button type="button" id="btnThisMon_11">This month</button>、
<button type="button" id="btnNextMon_11">Next month</button>

<script type="text/javascript">
jQuery('#btnThisMon_11').on('click',function(){
var myToday = new Date();
var y = myToday.getFullYear();
var m = myToday.getMonth() + 1; // Jan: 0
if (m < 10) { m = '0' + m; }
jQuery('input[name="data\\[11\\].input"]').val( y + "-" + m );
});
jQuery('#btnNextMon_11').on('click',function(){
var myToday2 = new Date();
myToday2.setDate(1);
myToday2.setMonth(myToday2.getMonth() + 1);
var y2 = myToday2.getFullYear();
var m2 = myToday2.getMonth() + 1; // Jan: 0
if (m2 < 10) { m2 = '0' + m2; }
jQuery('input[name="data\\[11\\].input"]').val( y2 + "-" + m2 );
});
</script>
▼[Input Hint] Setting Example (HTML/JavaScript):"Service end"
<button type="button" id="btnOneYear_12">→1 year cintract</button>、
<button type="button" id="btnTwoYear_12">→2 years contract</button>

<script type="text/javascript">
jQuery('#btnOneYear_12').on('click',function(){
var myDateStr = jQuery('input[name="data\\[11\\].input"]').val();
var myStartMon = new Date( myDateStr + "-01");
var myEndMon = new Date();
myEndMon.setMonth( myStartMon.getMonth() + 11 );
var y = myEndMon.getFullYear();
var m = myEndMon.getMonth() + 1; // Jan: 0
if (m < 10) { m = '0' + m; }
jQuery('input[name="data\\[12\\].input"]').val( y + "-" + m );
});
jQuery('#btnTwoYear_12').on('click',function(){
var myDateStr = jQuery('input[name="data\\[11\\].input"]').val();
var myStartMon = new Date( myDateStr + "-01");
var myEndMon = new Date();
myEndMon.setMonth( myStartMon.getMonth() + 23 );
var y = myEndMon.getFullYear();
var m = myEndMon.getMonth() + 1; // Jan: 0
if (m < 10) { m = '0' + m; }
jQuery('input[name="data\\[12\\].input"]').val( y + "-" + m );
});
</script>
[Data Item list]

Similar Models

Related Articles


Free download Business Template : Test flow for Input form

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

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]


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]

Start small

"How can I get used to the system?"

Considering only the investment effect, it is effective to systemize "existing inefficient work". If there is a work being done on "paper base", you should consider systematization of that work. If systemization is applied to "core business" such as order receiving, shipping and billing, "effect" will be more than "investment" relatively easily.

However, there are also risks that you can not get "effects" at all, if in a situation which is 1) administrator: insufficient system setting skill, 2) general worker: insufficient computer literacy. It is like forcing computer graphic to an oil painting artist.

"I may worsen business efficiency introducing a system." If you have such anxiety, it may be better to start a trial run first with "a small operation" (a work to be done every day if possible).

Habit of continuing to improve

When promoting paperless and teleworking, introduction of "workflow system" will be considered.

It is a very annoying question that to which operation to apply for the first, but for example, the following small workflow called "work time report" could be a powerful candidate. It is definitely good because "inevitably to use every day".

Naturally you will understand what you need and what you can omit, by actually trying "entering data", and "approving on it". And various ideas will be born through the usage.
  • Administrator: Will be Increased the skill of designing workflow
  • General worker: Understand the basic usage of handling Steps

[Hours Worked Report]

Utilization of programming knowledge

"Script Step" is a kind of "automated Step" within a Business Process.

These are Steps for automatically executing "program processing", such as, for example;
  • with reference to "attendance time" and "leaving time" entered in the upstream process,
  • automatically calculates "working time" ({leaving time} - {attendance time}).
Conversely, if you incorporated such a Script Step into the Daily report flow, employees do not have to fill in "hours worked " each time.

What can be done?

Automatic processing performed on the Workflow platform is so-called "Server side processing".

In other words, when an Issue flowing through a Business Process reaches the "Script step", data are automatically referenced and updated. All processing is executed while human beings are not aware or concerned.

The program code to be set there will be a configuration like;
  • starting with "to reference business data",
  • via "various arithmetic processing",
  • end with "updating business data".

What kinds of "operations" are possible?

For example, in the case of "Questetra BPM Suite" which is a cloud based Workflow product, it is given the specification as "(*) capable of setting Server-side JavaScript (ECMA Script)". And the following operations are available.
  • Basic numerical data operation (four arithmetic operations, square root, exponent, round-off, random number...)
  • Basic character string data manipulation (join, split, reshape, extract, replace, search ...)
  • Basic date and time data operation (addition, subtraction, progress calculation, day of week judgement, Japanese calendar conversion ...)
  • Generation and analysis of JSON data
  • Generation and analysis of XML data
  • Sending HTTP request (data GET, data POST, OAuth2 communication, Basic authentication ...)
  • Send SMTP request (send email, attachment file generation, convert character code ...)
* You can also use Java methods that can be handled by the Rhino engine, and Questetra extension methods. [R2300]
※ The details are HERE and THERE.

[Hours-worked report-Hours and minutes]

This article has the improved version.

Amelioration of Excessive Work Hours

In the Japanese government, "health damage due to overwork" has been actively discussed. The rise of this discussion is not an exaggeration to say that triggered by the "new employee suicide for overwork" (2015) in a major advertising agency. And it is expected that a new rule will be added such as "at most of 60 hours of monthly average overtime work under whatever employment contract", within the next one or two years.

In companies and government agencies where work hours are over 220 hours a month persistently, it may be necessary to take various actions, such as "drastic review of business processes" and "consideration of adopting of deemed hours worked system".

Reference) Labor Standards Act of Japan
  • Employers shall not have Workers work more than 40 hours per week, excluding rest periods.
  • Employers shall not have Workers work more than 8 hours per day for each day of the week, excluding rest periods.

Learning by implicit instruction is also included to hours worked

Certainly, it is true that there are people who think "want to work more for learning and experience" (staying in the office) with a pure heart.

Today, however, "learning necessary for work" is also defined as working hours. Given the fact that the case of trying to disguise the working hours as short as possible by letting workers to report as "self-development" or "private information gathering", this guidelines may be "unavoidable".


Common recognition within the team about working hours

Hours worked is defined as "time that a worker is objectively evaluated as being placed under command of the employer".

However, taking into consideration the situation as described above, it is very effective to once again discuss the common perception of each department of each company regarding "how to measure working hours concretely".

For example, not only "preparation of materials" at home but also "learning of technology trends" should be measured as working hours. However, on the other hand, if a server administrator who is required to confirm the latest security trends, included the time for "checking the Web for information" and "subscribing to the email newsletter", all the awaking time could be the hours worked.

[Hours-worked report]

"I wish I could do my input more smoothly..."

A business system is evaluated more or less by its "Operating screen". Just try to recall your day-to-day jobs, such as "Attendance report", "Decision-making request", "Contract report", "Answer to inquiry", so on... Most of the Delays and reworks that occur on these jobs are caused by "erroneous input or Inappropriate input at upstream Steps".

The following Workflow has been devised to input by clicking on the "Input sample button".

By a button being there, the concentration of inputting personnel will be sustained. Furthermore, occurrence of careless mistakes will be reduced. Even though you won't understand the advantage of "Input sample button" unless you experience, it is another input support that is different from a method of Selecting from options or Configuration of initial value. Even though it is just a button, it helps to go piled up a "sense of doing" of operators because it is their own input!?? And (something like) "CPU load" that give to the brain of the operator will drop significantly.

[Test flow for Input form]

"Personnel evaluation" is unavoidable for a company organization .

However, "Personnel evaluation process" varies depending on each company. The "Evaluation axis", such as for example;
  • Emphasizing on Outputs?
  • Emphasizing on personal skills?
is an issue concerning with self identity of each company. In other words "Examples of other companies" cannot be nearly as a reference.
  • [Self outcome] Has outputted sufficient quality and quantity outcomes in accordance with internal rules.
  • [Organizational efficiency] Proposed a better internal rules, so that to contribute to the improvement of the internal rules.
  • [Self-ability] Always absorbing the latest knowledge related to information technology and social system.
  • [Contribution to others] Originating the latest knowledge on the information technology and social system to in-house.

Moreover, "the basic way of thinking" may differ by companies, i.e.
  • Absolute evaluation
  • Comparative evaluation
  • Absolute evaluation on primary evaluation, comparative evaluation on secondary

Also, the "frequency of evaluation implementation and the mechanism of reflecting on reward", will greatly vary depending on company size and business content.
  • Implementation of once a year
  • Implementation of once in every 3 month
  • Monthly implementation

The following Workflow is an example of personnel evaluation to be implemented monthly. An employee conducts self-evaluation (relative evaluation) for each of the evaluation axis with 0 to 5 points. In response to it, a director and an officer conducts evaluation on all personnel (relative evaluation).

[Personnel Evaluation process]

In this example, it is excellent that "Total score in consideration of the weighting of each evaluation axis" will be indicated automatically in the moment when evaluation values of 0 to 5 points for each of the evaluation axis are entered.

It can be said that "Monthly report" added with simple evaluation. (* The weighting here is "Self outcome: 8, Organizational efficiency:6, Self-ability: 4, Contribution to others: 2.)

Incidentally, it might sound rather cumbersome that conducting evaluation for the personnel, director and officer each and every month. However, diligent quantification in every month could become an opportunity to brush up on "How to evaluate?" or "How to be evaluated?". If "reflecting in remuneration" was reviewed only once a year, it may be good for discussing on looking back on 12 months of the evaluated value that was recorded by everyone, month after month.

[Personnel Evaluation process:"1. Enter Self-evaluation" screen]

[Data Items list]

[Free Download]
<Similar Models>
<Related Articles>>

[Japanese Entry (ε’Œζ–‡θ¨˜δΊ‹) ]
  • My husband caught "Chickenpox"!
  • My child caught "Flu"!

Anyone wants to reduce risks of "Infectious diseases to be prevalent in the workplace" to zero. Everyone wants the company to take the "appropriate measures against infectious diseases".

Speaking "Infectious disease", it differs widely. There are severe illnesses that have defined as "Category 1 infections" in "Infectious diseases law", such as Ebola hemorrhagic fever", extremely strong infectivity. Also there are infectious diseases such as "Chickenpox" an "Seasonal flu" which have been defined as "Category 5", and the countermeasures is left to each organization. (The national authority would take countermeasure against Category 1.)


The following Workflow is a modified version of "Attendance Report flow" which I had presented in "Episode 465: Attendance Management in Cloud-based Workflow!"

It is nothing special. I Just added an input form of "Questionnaire for signs of infectious disease (optional)" beneath "Time and attendance report form" which everyone inputs daily.

  • I myself might have been infected with Seasonal flu, Rubella, Chickenpox, etc. (0/1/2/3)
  • My family member might have been infected with Seasonal flu, Rubella, Chickenpox, etc. (0/1/2/3)
    • 0: Almost no possibility of infection
    • 1: Feel like the symptoms began to appear
    • 2: I think the symptoms began to appear strongly
    • 3: Test positive of infection

[Attendance Report flow]

Want an "anonymous voting" to evaluate the supervisor!

Indeed, if we could have opportunities of "supervisor evaluation" by the staff easily online, it would be convenient in its way. To conduct evaluation not only "Annually", but "on Each quarter" or "Monthly", it will allow good occasions for a supervisor to look back on the day-to-day operations him or herself. (Is this something like a "Cabinet approval rating"?)

However, a Workflow system is a tool to record "What, when or who of the input", in the first place. It is naturally considered poor compatibility with "anonymousness".


In this Workflow, "Supervisor evaluation (Anonymous voting)" has been defined.

Specifically, it is a mechanism that Task of [1. Enter Evaluation on Supervisor] will be allocated to My Tasks of all members when it will come to the scheduled date and time. Members will cast a vote to ballot, for example, [1] Confidence, [2] No confidence, [3] Neither of them.

The excellence in this Workflow is that the entered "Evaluation data" will be automatically appended to "External file", and the data itself will be deleted. That is, even a User who has the [Data viewing authorization] is not able to see "who casted a vote, and how?". In addition as the attentive, in this example it is well-equipped with a function to shuffle the contents of the "external file" upon each appending. In other words, the vote content is surely protected unless the communication log was wiretapped and analyze it.
("Whether voted or not?" and "Voted when?" are excluded from protection.)

Even though, it is not possible to conceal "Who voted how", in cases like "Total number of votes cast was one!" or "All the votes were casted to No confidence". (scary...)

[Supervisor Evaluation Ballot]

'I can't handle approval on travel request from all these guys all alone...'

Whatever an organization chart could be, "a leader" is essential to its respective departments. Especially, the role of "leader" is important in determining "the Policy of department" and "the Goal of the department".
However, speaking about the day-to-day approval job, it is not necessary to be performed all by "one leader".

For example, if an operation such as "approval on business trip" in the "section" of about 10 to 20 personnels , you should let the "deputy manager" and "assistant manager" to do proxy approval actively. There is also meaning of clarifying the responsibilities and rank within the department. (There may be a definition in the business rules of the company, such as "Substitute on duties when there was an accident on the section chief".)

Incidentally, such a system can be seen often also in the "Operations of government" which blank period of procedures is not allowed. (e.g.:"State-Owned Articles Management Act, Institutions of surrogate officer"(Only in Japanese) The rules of surrogate (Only in Japanese))

[Travel Request]
"We are trying to do all the work on Workflow. So please make Time and attendance reports also possible on Workflow!"

Attendance management (Time and attendance report) is performed by "Time card" in many companies. (Monthly confirmation)

However, if you are doing the routine work on the Workflow, you should consider how to make possible to report of "Coming to work" and "Leaving work" on the Workflow as well. Above all, it is significant that it allows real-time confirmation on the attendance of "Persons in positions of supervision or management" (Article 41 of Labor Standards Act in Japan). (Daily confirmation)

In this Workflow, a Task of "1. Coming to work Report" will be allocated as [My Task] to all the employees at 7 o'clock in the morning of every weekday.

Each employee will register the time of start working by clicking on the [Now] button upon starting to work to finish the Task of "1. Coming to work Report". (Of course, arbitrary time can be entered manually as well.) Likewise, handle the Task of "2. Leaving work Report" at the end of the day's work. Incidentally, in case someone forgets clock-out, the regular time will be recorded automatically. (For a day of regular time work, only reporting in the morning is enough.)

It might be rather a natural mechanism for a company in which a lot of "Teleworkers", "Remote workers" or "Outside sales people", etc.

[Attendance Report flow]

In the morning, a Task in the title of "Daily Report, Nov. 4th" is added in your 'My Tasks'.

Not bad...

If it were not for this function, you would have forgotten to submit 'Daily Report' on the half of the weekdays. (I'm sure about it.) Incidentally, 'Submit by the time you leave' is its rule. Submit it on the next day, even if you forgot. Even worse, in the morning after the next, at least.

However...

Although all the members are flowing a 'Daily' on this Workflow in their own way,,, I'm aware of something wrong in this function of [Automated Start].

That is, the mechanism is that the Task is automatically added to 'my Tasks' of all in every morning of Monday to Friday, whereas it will be piled up in vain when you took a few days off.
For example;
  • Bereavement leave, major holidays, Christmas holidays, etc..
  • Childcare leave, maternity leave, nursing leave, etc..
  • (There might be irregular shift workers...)
Well, on the Reports for few days, you would have worked hard, one by one. But for amount of 30 day, 60 days, or even for one year, it is definitely impossible.


[Daily Report flow 1]

The evolution of "Remote Work platform" is awesome. Cloud-based services are evolving rapidly, for example;
  • Email
  • Calendar
  • File manager
  • Web conferencing
  • Workflow(!)
  • etc.

File sharing was achieved only on Corporate LAN when it was 5-10 years ago. But now, it can be 'Always synchronize with local' on the cloud. That means, there are no longer spatial constraints on the file sharing with coworkers, even if for translating job, for Web designing job, or support service job.

In recent, "Sqwiggle", a tool for remote work of which free use limitation has been expanded, is notable. Briefly, it is a device to share the appearance of work at home, etc. with the teammates, by 'still image of every 5 minutes'. The 'presence' of coworkers can be recognized each other in a natural way, for it is not the live broadcasting of video. After all, it provides 'motivations as if they are working seated next to each other'. Well, speaking in detail, there might be some negative opinions in various levels, such as 'possibility of information leakage from still images' or 'Load on CPU by the camera'. (Shall we federate Questetra with it?)

Anyway, the environment, in which we can experience the 'new ways of working' that we never knew, is growing.

As enterprises, they can only continue to experience "new ways of working", by incorporating the new information and communication technologies. If you do not go to experience sequentially in the trial and error, you will not be able to even experience the tools of the next. (If you are doing nothing but only feel pity for a person who attends to a computer beginner's class, you will be standing on the side to be pitied.)

The following is an Online timecard system, which also serves as a daily report.

If you provide it as one of the Workflows, the worker will be able to submit daily report, in the same way processing other tasks flowing on it. You don't need another dedicating timecard system. As the first step for "Remote working" (Telework / Telecommuting), how about experience for trial of clarifying 'Hours worked'.

[Daily Report-Timecard]


"Updating the Website" is operations that exist in most companies.
And the "Workflow" for it is shrouded in secrecy...

First of all, speaking about "site update", there are a variety of "levels".
  1. Correcting the typographical errors.
  2. Adding a blog post
  3. Adding information such as press release news, etc..
  4. Adding the introduction page of product service.
  5. Replacing the induction banner on the homepage. 
  6. Changing the site design as far as leading to advertising campaign.
  7. Changing the platform (CMS), major relocation and major modification.
  8. Outsourcing to a professional company, build a project of large-scale modification.

In the following Workflow, it aims to up to "level 5" of the above 8. In plain words, this workflow smoothes the "operations of the Web site on a daily basis". And it records adding or editing on the Web page automatically.

At any time, people who concerned will be able to see who created which content (= governance point of view), how many times a month each member makes updating (= personnel evaluation point of view), as well as the history of the Website (= governance point of view).

[Website Updating]
It is better to handle the "Attendance and leaving information" on Workflow for an Organization that handles various daily works in the Workflow (Paperless/ Digitize).

Anyhow, you manage it on Workflow, how about making attendance time and leaving time reported daily, instead of 'creating attendance record once a month'?

It seems nonsense that letting the workers create attendance records while remembering previous month. It will not work as a checking function for the supervisors, even if they handed 'attendance record data of one month' at a time. But suppose if it is a daily check on working hours confirmation, they could give approval during a little time of transportation.

[Timecard]

Business Manual within Workflow!

Monday, October 7, 2013
You need
(A)'a Manual to accelerate each processing (each step)' (micro-spective) as well as
(B)'a Manual that grows understanding about the entire business' (macro-spective).

Looking at the operating screen of the Workflow, it is possible to handle allocated tasks even for non-experience personnel. "Vacation Request", "Approve the Request", "Confirm Absence", etc. All they have to do is to input along the indicated form screen. (There may be 'a Manual to accelerate each processing'(A).)

* Sample for (A) Embed Manual to Operating Screen of Workflow with Google Drive

However...
They are not few cases that you want solutions to the questions in entire-business-spective or entire-system-spective such as ,
  • Will my salary be reduced?
  • First of all, how the leave system is defined?

The following Workflow-sample contains "The overview of the leave system" (a business manual). That is, apart from the "manual to handle each step"(A), "Manual for the entire business flow"(B) is given to see in the workflow. (New feature of Questetra [Version 9.7!!)

[Leave Request Flow-w/Manual]

There are many types of "off".
What is "Vacation"?
What is "Leave"?

Request for "leave" is an important application that concerns to salary, but in the other hand it is troublesome that you have to read-back "the work rules" or to look for the format of the "application". You want to make it smoother.

The following Workflow is "Leave Request flow" which can be used by a lot of companies.
You do not have to care such as "difference between annual leave and special leave" or "difference between compensatory day off and Substitute holiday". Except the "obvious holidays" like Saturday and Sunday, you can freely request for leave of vacation. Furthermore, every time you see the screen of application, you can learn that "Oh yeah, I can also make request from here when I request parental leave".


[Leave Request flow]