Tasks with accountability
Instructions passed on verbally are easy to lose or assign to the wrong crew.
A task has a scope, a deadline and a responsible person within the project.
WHY IT MATTERS
Information from site is valuable when it quickly reaches the right person.
A defect, a missing material or a decision needed on site can stop work. Record tasks and reports against the project instead of reconstructing their context from many conversations.
PROBLEMSOLUTIONRESULT
Reports you can come back to
A problem described in a private message creates no shared history and may go unanswered.
The report and documentation are assigned to the object and the site.Record of work on site
Without a record of attendance and time, it is hard to establish how the work actually went.
Information about the team's work helps complete the picture of project progress.
USE IN YOUR COMPANY
For site managers, foremen and teams working on site.
Information about tasks, attendance, time and defects should reach the people running the project, not get lost in private conversations.
Does the office know the state of the site without phoning the whole crew?
When reports and progress are not recorded against the project, only the people present in a given conversation know the context.
WHAT THE SYSTEM CHANGES
- 01Tasks, reports and documents kept on the project.
- 02Attendance and time records linked to the team's work.
- 03The office and the team work from the same, up-to-date data.
HOW THE MODULE WORKS IN PRACTICE
Information from the object leads to further action.
Example: a crew reports a defect during the works. The manager needs more than a message: an assignee, a deadline and a record of how it was resolved.
DATAWORKDECISION
-
01
Assign a crew and tasks
Lay out the work plan and deadlines. Assigning people and crews shows who is to carry out a task on a given project.
-
02
Record attendance and how the work went
The team records clock-ins, time, completed tasks and diary entries. The office sees the information without waiting for the end of the week.
-
03
Add a report with a photo
Assign a defect, shortage or obstacle to the object and the project. Name the person responsible, the follow-up task and the documentation.
-
04
Close the report
Once the work is done, mark the task as closed. Photos, notes and decisions stay in the object’s history.
EIGHT AREAS OF WORK
Each of them is part of the project.
EVERYTHINGFOR THESAMEPRICE
Tasks
The scope of work and the person responsible are assigned to the site.
Schedule
The crew sees what is planned and what the deadlines are.
Work diary
Progress and important events are recorded against the project.
Attendance
You see who worked on a given object.
Working time
Team hours are part of the site picture.
Reports and defects
Problems from the field go onto a shared action list.
Photos and documents
Materials from the object stay with the relevant task.
Crews
You can organise the assignments and work of several teams.
MIVARE SITESEIGHT AREAS OF WORK
WHY IT MATTERS
Field work is part of the site. Not a separate flow of information.
The most important information often arises away from the office: a stage completed, a missing material, a defect or a decision needed from the customer.
When you record them against the project, the next person knows the context at once and can act.
Every record has an owner.
A task, report or document goes to the right site. You don't have to look for them in private messages.
START WITH ONE TEAM
Your first crew. A shared picture of the work.
Add a site, tasks and a crew. See how information from the object builds into a clear history.
You don't need a separate flow for field work.
- Is field work a separate module? Field work is part of the system.
- A payment card? You don't need to provide one at all.
- What happens after the trial? Either you carry on, or you do nothing.