A pre-start check is the list an operator ticks before starting a machine. One check can cover a tractor, bar and air cart, or a truck and its trailers, and a problem it finds can become a repair job. When a machine must not be used, tag it out so nobody starts it by mistake.
Before you start
Checks are in More → Daily work → Machinery → Checks: Templates, History and Problems.
Building, editing and deleting checklists needs permission to edit the farm: owners, co-owners, admins, and staff unless their access was narrowed.
Doing checks, making jobs from problems, resolving problems and tagging out need access to record work. Owners, co-owners, admins and staff always have it. Advisers and view-only logins don't.
Build a checklist for a machine and its implements
Open Checks → Templates and select Checklist, or use New work → Build a pre-start checklist.
Type a Name, for example "Seeding rig daily pre-start".
Under Machines, choose the main machine, or leave Any machine.
For a combination, select Add implement or machine for each one working with it, such as the bar and the air cart. Each shows under the main machine with × to take it off.
Under Checklist items, type a Section name, for example "Engine", then the first check, for example "Check engine oil level". Select Add check for each one after it.
Tick Require note or Require photo where the operator must add one, and Allow N/A where an item doesn't always apply. Reference photo shows them what good looks like.
Select Add section for the next group, then Save checklist.
Any machine can join a combination, whatever its type, and it needs no name. Type part of a name to search. Combinations saved earlier sit at the top of the list marked "Saved combination"; choosing one fills in its machines.
Do a pre-start check
On Checks → Templates, select Begin. You can also use Pre-start check on the Notice board widget on Overview, New work → Do a pre-start check, or Pre-start check on a machine's scanned Phase tag. A checklist that names its machines fills them all in.
Check Machine at the top. One checklist can serve several machines of the same kind, such as three headers: choose the one you're checking here. The checklist itself doesn't change.
Select OK or Problem for each item, or N/A on an item set to Allow N/A. Remaining items OK ticks everything you haven't answered. N/A counts as answered, is not a problem, and asks for no note or photo.
For a problem, choose Which machine? (shown when the check covers more than one) and the Severity, then Fixed it if you fixed it on the spot, or Still to fix.
Describe the problem under What needs attention? (What was wrong, and what did you do? when you fixed it). Add photo attaches a photo.
Type the reading in Current hours (or Current km) if you like. It belongs to the main machine and only ever moves its meter forward.
Select Complete check, or Save draft to finish later from History with Resume.
A check of several machines is one record, shown on each machine's Work and Checks tabs. A problem goes on its own machine only: a fault on the air cart puts the air cart in for repair, not the tractor.
What a problem does to the machine. Minor: needs attention and Moderate: needs assessment put it In for maintenance. Critical: do not operate and Unsafe: do not operate mark it Needs repair and alert everyone who works the farm, except whoever found it. It stays flagged until the problem is resolved. A retired machine, or one already Needs repair, keeps its status.
Fixed it on the spot. A problem marked Fixed it stays on the machine's record as found and fixed, with your note saying what was done. It isn't left open, doesn't put the machine in for repair or Do not operate, sends no alert and asks for no job. The check counts it as, for example, "1 fixed on the spot".
Turn a problem into a repair job
During the check. Marking Problem asks, for example, "Make a job for Air cart's problems when this check is saved?" Yes, make a job makes it when the check is saved; Not now leaves it.
After the check. Problems you didn't answer about are offered in Make a job for these?, critical and unsafe ones ticked. Select Make a job (Make 2 jobs when the problems are on two machines), or Not now. The check is saved either way.
Later. Make a job sits on each open problem in Checks → Problems, on the machine's Checks tab, on its scanned Phase tag, and in Needs attention on the Machinery Overview tab. It opens the job form filled in; select Plan work.
Problems on one machine share a job, which goes to Tasks with nobody assigned. It's a repair on that machine named after the item, for example "Hoses and lines: Air cart", Urgent for a critical or unsafe fault and High for a moderate one, with the operator's note and photos.
The problem then shows Job: with the job's title and status, and the job shows From a pre-start check: with the item and date. Each opens the other. Marking the job done offers Resolve the problem too (ticked), and the completion notes become the corrective action. Resolving the problem first never changes the job.
Resolve a problem
Open Checks → Problems. Open problems come first.
Select Resolve on the problem.
Describe the fix under Corrective action, and add Resolution photos if you like.
Select Resolve.
With nothing else open on it and no open service or repair job, the machine goes back to Operational.
The next check shows what's still open. Once the machines are picked, the next pre-start lists their open problems, for example "2 unresolved problems on Air cart", with each item, severity, date and who reported it. If any is critical or unsafe, the heading reads "Do not operate" instead.
An item with the same name as an open problem says, for example, "Reported 3 Oct, still open", with Still a problem (noted as seen again, not reported twice) and Resolve. A new check never resolves an earlier problem by itself.
See past checks
History shows the latest 12 checks and who did each, then Show all (for example Show all 40 checks). View result opens a finished check read only: when, who, the meter reading, each problem with its severity, notes and photos, the check's notes, and every item marked OK, Problem or Not checked. Checks from the older combination screen are under Earlier combination checks, and an unfinished one can still be resumed.
Tag a machine out of service
Tag out a machine or implement that must not be used, because parts are off it or something is unsafe. Anyone who can record work can do it: owners, co-owners, admins and staff.
Select Tag out at the bottom of the machine's page, on its card in Machines, or on its scanned Phase tag.
Under Why is it tagged out?, say why, for example "Wheel nuts off the left wheel". This is required.
Add a photo with Add a photo if you like, then select Tag out.
Phase records who and when, and tells everyone who works the farm straight away, you included: "Hay rake TAGGED OUT by Jack", with the reason. This alert comes at any hour, even overnight. If someone has already tagged it out, Add to the tag adds your reason.
While it's tagged out it reads TAGGED OUT with a padlock:
across the machine's page and its scanned tag, with the reason, who and when;
with the reason on its card in Machines;
first in Needs attention on the Machinery Overview tab;
on any job that uses it, and beside its name when you pick a machine for a job;
at the top of a pre-start.
The machine also reads Needs repair. Starting a pre-start on it, completing a check that includes it, or marking a job that uses it done stops at "This machine is TAGGED OUT". Going ahead needs I know it's tagged out, … anyway, which puts your name on the tag-out's history. A repair or service job on it isn't stopped, but says finishing it does not clear the tag.
Clear a tag-out
Only the person who tagged it, or an owner, co-owner or admin, can clear a tag.
Select Clear tag-out on the machine's page, its card, its scanned tag, or in Checks → Problems.
Under What was done?, say what was fixed, for example "Wheel back on, nuts torqued".
Select Clear and return to service.
Everyone is told it's back in service; overnight, phones wait until 6 am for this one. The machine returns to its earlier status, Operational or In for maintenance, unless another open problem or repair still holds it. One that was already Needs repair when tagged stays that way. Finishing a job made for a tag-out never clears the tag.
Good to know
A check shows exactly the items in your checklist. Editing a checklist changes the next check, not past ones.
A checklist that has been used can't be deleted, so past checks stay readable.
Changing the main machine part-way through a check starts its answers again. Adding or removing an implement keeps them.
Every tag-out stays on the machine's Checks tab and in Problems: who tagged it, anyone who started work anyway, and who cleared it and how.
Phase Agent answers "is the hay rake tagged out?" and "what's tagged out?" with the reason, who and when. It can't tag out or clear a tag.
The alerts are A machine is tagged out and A tagged-out machine is back in service, in More → Settings → Notifications, under Jobs and machinery. Both start on. A tag-out doesn't also send A machine is flagged unsafe or critical.
If something doesn't look right
Complete check won't save. The check needs a machine, every item needs OK, Problem or N/A, every problem needs a note, and items set to Require note or Require photo need one.
No Checklist, Edit or Delete button. You need permission to edit the farm.
No Tag out button. It needs access to record work, and isn't offered on a retired machine or one that is already tagged out.
No Clear tag-out button. Only the person who tagged it, or an owner, co-owner or admin, can clear it.
A check asks you to confirm before it starts. A machine on it is tagged out. Select Don't start and read why.