Job Cards¶
A Job Card is the record of one piece of shop-floor work on a Work Order — what was done, who did it, shift by shift, and who signed it off.
A Work Order says what has to be made. Its routing says which steps it goes through. A Job Card is where a single step actually gets carried out and recorded.
Accessing Job Cards¶
Open the Execution sidebar and select Job Cards for a list of every job card you're involved in, or open a Work Order and use its Job Cards card to see just that order's.
Note
The Job Cards list shows the cards you are assigned to — as maker, checker, approver, shift supervisor, or as someone rostered onto one of its shifts. If the list looks emptier than you expect, that usually means the remaining cards belong to other teams, not that they don't exist. Engineers see every card in the organisation.
Finding what's waiting on you¶
Being on a card isn't the same as the card waiting on you — you might be the approver on something that's still being filled in. The For Me column says what, if anything, each card needs from you right now:
| Badge | Meaning |
|---|---|
| To fill | You're the maker and the card is yours to record and submit |
| To check | You're the checker and it's been submitted for your review |
| To approve | You're the approver and it's been checked, waiting on your final sign-off |
| — | Nothing for you to do on this card at the moment |
Use the Needs me filter to narrow the list to just those. A card shows a dash when it's someone else's turn, when it's finished, or when it's been rejected and is waiting to be reopened.
Shifts awaiting your sign-off are counted separately, under Shift Entries — select the awaiting sign-off note to jump to Shift Sign-offs.
Where Job Cards come from¶
There are two ways a Job Card appears:
- Automatically, from the routing. If a Work Order's routing has a step configured to generate a job card, the card is created the moment the routing reaches that step. This is the normal path for production work — see Workflow Templates.
- By hand. From a Work Order's detail page, click New Job Card. Use this for one-off work that isn't part of the standard routing.
Maintenance Work Orders raised from a Maintenance Plan get their job card automatically, using the form attached to that plan.
Creating a Job Card by hand¶
From a Work Order's detail page, click New Job Card and fill in:
| Field | Description |
|---|---|
| Name | Required |
| Checklist Template | Optional — the form to be filled in on this card. Leave it as None for a card that only records shift work, with no form |
| Maker | Required — the user group responsible for carrying out and submitting the card |
| Checker | Optional — a user group that reviews the submitted card |
| Approver | Optional — a user group that gives final sign-off |
Each card is given its own number, based on the Work Order it belongs to.
Recording work, shift by shift¶
This is the heart of a Job Card. A single step can run for days across many shifts, so the work is recorded as one shift entry per shift.
Open a Job Card and use the Shift Entries card:
- Fill from roster creates entries automatically from the shift assignments already planned against this Work Order — see Shift Assignments. Safe to use again later as more shifts are planned; it won't duplicate what's already there.
- Record Shift adds or updates a single shift by hand.
For each shift you can record:
| Field | Description |
|---|---|
| Date and Shift | Required — which shift this entry is for |
| Performed By | The person who did the work. This can be a contractor as well as an employee |
| Shift Supervisor Group | Optional — who may sign this shift off. Leave blank to use the card's Maker group |
| Start / End | When the work actually started and finished |
| Produced Qty | Everything the step turned out this shift, including anything later rejected or scrapped |
| Rejected Quantity | Pieces that failed inspection. These are part of Produced Qty, not counted on top of it |
| Of which: to Rework / to Scrap | How many of those rejected pieces are going to be reworked, and how many scrapped. Fill these in when inspection has decided — they can be left blank and completed later |
| Downtime (min) | How long the step was stopped during this shift. Only used if nobody logged the stoppages properly — see below |
| Downtime Reason | Chosen from your organisation's standard list of downtime reasons |
| Downtime Note | Optional — anything about the stoppage the standard reason doesn't capture |
| Remarks | Anything worth noting about the shift |
Note
Downtime Reason is picked from the same standard list used when logging downtime against a machine, so everyone classifies stoppages the same way. If the list is empty, an engineer can add reasons under OEE ▸ Reason Codes. The list shows reasons set up for the card's machine plus those that apply across the whole organisation.
There is one entry per shift per day on a card. Recording the same shift again updates it rather than adding a second row.
Who fills each shift¶
Each shift on a card can be assigned to one person, so it is clear who is responsible for recording it. The Assigned To column shows who holds each shift.
- Unassigned — anyone in the card's group can fill it, and one person can start a shift and another finish it. This is the normal state, not a gap.
- Assigned — only that person can enter or change the shift's numbers. Everyone else in the group can still see the shift and who holds it; they just cannot type into it.
Claim takes an unassigned shift for yourself. If two people claim at the same moment, only one gets it and the other is told who did — nobody's work is quietly overwritten.
Assign and Reassign are available to engineers and to the shift's supervisor. Anyone rostered for that shift is listed first and marked on shift, so the obvious choice is the quick one. If the person already holding the shift has started filling it, you are warned and can confirm — their work is kept either way.
Assigned To is not the same as Performed By
Performed By is the worker whose output the shift records — often someone who has no login at all, such as contract labour. Assigned To is the person responsible for entering the record. The two are frequently different people, and only one of them needs a platform account.
Only people in the card's group can be assigned
The list of people you can assign comes from the group named on the routing step, not from the shift roster. Somebody rostered for the shift but outside that group cannot open the card at all, so assigning them would leave the shift stuck with nobody able to fill it. If the person you want is missing from the list, add them to the group first.
Above the table, Enture shows how many shifts still have nobody assigned, so gaps are visible before they become a problem. Anyone in the group can pick those up.
The roster line under Performed By lists everyone else rostered for that shift on this job, so a supervisor can see the whole crew and not just the one name on the record.
How a step is measured
Not every step is measured the same way, and an engineer sets this on the routing step (or on an individual Job Card). There are three choices:
- Full OEE — repetitive work with a cycle time standard. Availability, Performance and Quality all apply. This is the default.
- Availability and Quality only — steps that run for days or weeks on engineered, one-off work, where a "pieces per minute" figure means nothing. The machine's uptime and quality still count, and the card shows a Schedule Adherence panel instead of Performance.
- Not shopfloor work — desk work such as design, drawing or GTP preparation. These cards are left out of OEE entirely and show Schedule Adherence only.
Why the last one matters. Desk work has planned hours but no machine, so no stoppages are ever logged against it — which would make it look like a machine that ran perfectly, all day, every day. Counted into the Work Order, that would quietly lift the whole order's Availability. Marking those steps as not shopfloor work keeps them out of the figure altogether.
Schedule Adherence compares planned duration against actual, and shows whether the step is running ahead of or behind its plan. A step still in progress shows the time elapsed so far, so you can see it slipping before it finishes. If the card has no planned start and end dates, set those first: adherence is measured against them.
Downtime is taken from logged stoppages
If stoppages were logged against this Work Order and machine — using OEE ▸ Downtime Log, with its start and stop times — the shift entry shows that total instead of whatever was typed in Downtime (min), marked with how many stoppages it came from. A stoppage still running counts up to the current time rather than as zero. The typed figure is only used for a shift where nobody logged the stoppages, and it won't appear in downtime reports, because it has no start, end or reason attached to it. Logging stoppages properly is what gets them into those reports.
Rejected pieces waiting on a decision
Until you say where rejected pieces went, the row shows "N rejects awaiting disposition". Those pieces are left out of the OEE figures entirely rather than being guessed at, which means the Quality figure reads slightly high while they are outstanding. Filling in to Rework and to Scrap — whenever inspection decides, even days later — settles them against the shift they came from.
Note
Performed By and sign-off are deliberately separate. The person who does the work may be a contractor without an Enture login; sign-off always belongs to a user group. A supervisor records a contractor's shift on their behalf.
The Job Card's own totals — produced, rejected, downtime, and actual start/end — are added up from its shift entries automatically. The card's Actual End stays blank while any shift is still in progress.
Signing off a shift¶
Each shift entry can be signed off on its own, by whoever is named in its Shift Supervisor Group (or the card's Maker group if none is set). Use the Sign-off action on the row.
A shift that has started but not yet ended can't be signed off — finish it first.
Once signed off, a shift entry is locked. If something needs correcting, the card's Maker can Reopen it, make the change, and it can be signed off again.
Finding the shifts waiting on you¶
You don't have to open Job Cards one by one to find shifts that need your sign-off. Execution ▸ Shift Sign-offs lists every shift entry across every Job Card that is waiting on your attestation, newest date first, with the Job Card, Work Order, who performed the work, and the shift's produced quantity and downtime.
Sign off directly from the list — the row disappears once it's done. Shifts that have started but not yet finished are listed too, marked In progress, so you can see what's coming; they can't be signed off until the shift ends.
If the page is empty, nothing is currently waiting on you.
Tip
Per-shift sign-off is optional and off by default. It's for cases where each shift's supervisor should attest their own shift's numbers — for example on a card that runs for a fortnight across three rotating shifts. When it's switched on for a card, every shift entry must be signed off before the card itself can be submitted.
Filling in the form¶
If the Job Card has a Checklist Template, its form appears below the shift entries. Fill it in the same way as any checklist in Enture — see the Checklist reference for how the individual field types behave.
Save keeps your progress without submitting. Submit hands the card on to the next stage.
A card can't be submitted while:
- any shift entry is still in progress (started, not ended), or
- per-shift sign-off is required and some shift hasn't been signed off yet.
The reason is shown if you try.
Checking and approving¶
Once submitted, the card moves to its Checker (if one is set), then its Approver (if one is set). If neither is set, submitting completes the card outright.
At each stage the responsible group sees Check / Approve and Reject actions, with a remarks field.
Rejecting sends the card back with a reason. Its Maker can then Reopen it, correct the work, and submit again.
Rejections and rework¶
If a rejected Job Card belongs to a routing step with a Rework Target Seq configured (see Workflow Templates), the Work Order's routing automatically loops back to that step for another pass — no separate action needed. Once the configured number of attempts is used up, the routing carries on as normal instead of looping again. Rejecting a card with no rework configured on its step is a plain rejection with no effect on the routing.
Job Card statuses¶
| Status | Meaning |
|---|---|
| Pending | Created, nobody rostered onto it yet |
| Assigned | Someone is rostered on a shift entry, work hasn't started |
| In progress | At least one shift has started |
| Submitted | The Maker has submitted it; waiting on the Checker |
| Checked | The Checker has passed it; waiting on the Approver |
| Approved | Complete |
| Rejected | Sent back — the Maker can reopen and resubmit |
| Cancelled | No longer to be carried out |
Opening a Job Card at the machine¶
If the Work Order has a Planned Line or Machine set, opening one of its Job Cards from the Work Order page first prompts a QR scan, to confirm you're at the right equipment. See QR-Scan Reconciliation.
Opening a card from the Job Cards list doesn't prompt a scan — that list isn't tied to a particular work order's planned equipment.
Seeing shift work on the roster¶
The Shift Assignments calendar shows job card work alongside the roster: days with job card entries are marked, and selecting a day lists each entry with its shift, who performed it, its Work Order, and whether it's been signed off. See Shift Assignments.