Document Designer - Job Tickets

Create bespoke PDF Job Tickets that can be printed or emailed to your customer. These can include images, service check lists and pictures taken on site.
Details

To edit Job Tickets, navigate to Settings > Document Designer > Job Tickets.

 

This guide must be read in conjunction with the general Document Designer guide Here, explaining the basics of the Document Designer module.

 

Job Tickets are the back bone of the Workforce Manager system. Each visit to site and completed using the Mobile App will result in the requirement to send your customer a Job Ticket detailing the works done. Even without sending the ticket, you will need a permanent record of the visit.

 

There are a total of 21 Job Tickets where each one can be its own unique design. More often, these tickets are all very similar to each other in design with maybe an additional page for service jobs where a second page that details all service check points can be added.

 

Each of the 21 Job Tickets can be sub divided into an unlimited number of categories, each can have its own unique Job Ticket design making the number of possible Job Ticket types infinite. Job Categories are covered in a separate How To Guide.

 

Job Ticket Designs

Workforce Manager includes a basic Job Ticket design as a default that allows you to get started immediately when first using the system. All that is required is to add your own Logo and company address to the design and you will have a working document.

 

Below is an example of this where we have added our own Logo

 

Text Editor Image

 

Our default Job Ticket designs are examples of items created within the Document Designer where we have not used the 'Letter Head' option as the background for the document, instead we chose to create the design using the option 'None' for the canvas, utilising the whole page for the Job Ticket.

 

If you would prefer to change the Default Job Ticket Design, we would recommend starting a design on an unused Job Ticket tab where this will not interfere with live jobs. 

 

 

Adding a Second Page

For some Job Tickets, it will be necessary to add a second page that would detail additional information such as 'Service Checks' which are completed on site using the Mobile App.

 

To add a second page, include the tag #PageBreak# at the bottom of your first page then begin designing your second page below the tag. Workforce Manger will automatically put all information below a #PageBreak# Hash Tag on to a second or subsequent page.

 

Below is an example of a second page added to our Service Job Ticket.

 

Text Editor Image

 

 

 

The Completed PDF

Once your design is complete and used within a Site Record when completing work on site for a Service Visit, the below example shows how the PDF may look once all of the #HashTags# contain data.

 

Page 1

Text Editor Image

 

Page 2

Text Editor Image

 

 

Including Images

Using the Mobile App (or uploading directly to a Job Ticket), pictures can be taken on site at the time of the visit, these can also be included as part of your Job Ticket design by including the Tag; #TicketImages#

 

Below is an example of images added to our second page embedded within the document.

 

Text Editor Image

 

You may of course add a third page dedicated to images with its own border and page design. If you simply want to add a new page without any other design features but simply list the pictures, the Tag #NewPageTicketImages# will do this automatically if you place it at the end of your entire design.

 

Selecting Which Images to Include

Using the #TicketImages# tag comes with the flexibility of choosing which images are going to be shown on the final PDF document.

 

You can select which images are to be included within the final PDF while of the Job Ticket page using the web UI. While on a Job Ticket after the site rep has completed work, click the 'In Ticket Images' tab shown in the LH menu.

 

Text Editor Image

 

This will open the Ticket Images Dialogue

 

Text Editor Image

 

Clicking on any of the images will toggle the image on or off as shown with a green tick. Images with a green tick will be used within your PDF design.

 

If remarks are added (click the 'Edit' button to open a remarks dialogue) these remarks are also included on your PDF design positioned above each corresponding image.

 

It is worth noting at this point that selecting images from the Ticket Images Dialogue will also automatically add the images as attachments to an email when sending the Job Ticket document. You may choose to delete these from the attachments panel at the time of emailing (deselecting them in the Ticket image dialogue is also an option) or you may choose to only include them as attachments instead of embedding into the Job Ticket PDF.

 

 

HashTags

There are a large number of Custom #HashTags# available within the Job Ticket designer. These are listed below with a brief explanation of its purpose.

 

#TagName#:

The location tag name entered within the Site Record Product Manager dialogue.

 

#CustomerOrderNumber#:

Order Number as entered in the Job Ticket order number field.

 

#CustomerName#:

Name of the Customer as shown in the address field of the Site Record.

 

#CustomerAddress#:

Name and address as shown on the Site Record.

 

#CustomerAddressNoName#:

Address excluding the name as shown on the Site Record.

 

#CustomerAddress_InLine#:

Site record name and address but in a single line instead of an address block.

 

#S_Add1#:

Site address line 1.

 

#S_Add2#:

Site address line 2.

 

#S_Town#:

Site address line 'Town'.

 

#S_County#:

Site address line 'County'.

 

#S_PostCode#:

Site address line 'Post Code'.

 

#S_LandLine1#:

Site land line number 1.

 

#S_LandLine2#:

Site land line number 2.

 

#S_Mobile1#:

Site mobile number 1.

 

#S_Mobile2#:

Site mobile number 2.

 

#S_Email#:

Site email address.

 

#CompanyName#:

Your own Company Name as shown in the address dialogue for 'My Company'.

 

#TicketTitle#:

The name of the Job Ticket as shown in the LH menu Tab.

 

#JobCategory#:

If Job Categories are used and one has been selected, the name of the category is shown.

 

#CNum#:

The Site 'C' number.

 

#SerialNumber#:

Serial number of the selected product on the site record.

 

#ProductRef#:

Our Ref field as shown on the Product Manager Dialogue.

 

#ProductMisc1#:

Misc 1 (a custom named field that may have been renamed) as shown on the Product Manager Dialogue.

 

#ProductMisc2#:

Misc 2 (a custom named field that may have been renamed) as shown on the Product Manager Dialogue.

 

#ProductMake#:

The Make name of the Product as shown on the Product Manager Dialogue.

 

#ProductModel#:

The Model name of the Product as shown on the Product Manager Dialogue.

 

#InstallationDate#:

Installation date of the Product.

 

#RemovalDate#:

Removal date of the Product

 

#ContractExpiry#:

Expiry date of the current Service Contract.

 

#ServiceContractName#:

The name (Status) of the current Service Contract.

 

#SWL#:

Safe Working Load as shown in the LOLER dialogue.

 

#ManufactureDate#:

Manufactured Date as shown in the LOLER dialogue.

 

#LastExamination#:

Last Visit Date as shown in the LOLER dialogue.

 

#NextExamination#:

Next Visit Date as shown in the LOLER dialogue.

 

#JobNumber#:

Job Ticket 'J' number.

 

#JobOrder#:

If a job order has been selected within a Job Ticket Booked Day.

 

#CalledInBy#:

'Call By' field shown on the Job Ticket page.

 

#CalledInByNumber#:

'Caller No' field shown on the Job Ticket page.

 

#BookedDate#:

Date the current Job Ticket is Booked.

 

#BookedTime#:

Time the current Job Ticket is Booked.

 

#BookedDateTime#:

Bot the date and time the current Job Ticket is Booked.

 

#BookedTimeEnd#:

The time the current Job Ticket end date is set to.

 

#ConsultantName#:

Managing Agent Name.

 

#ConsultantAddress#:

Managing Agent Address.

 

#ConsultantContact#:

Managing Agent Contact name.

 

#ConsultantTel#:

Managing Agent telephone number.

 

#ConsultantContactTel#:

Managing Agent Contact telephone number.

 

#JobDetails#:

The main details of the job (Job Details panel).

 

#JobReport#:

The Completion Report of the job (not the rep report. These are separate).

 

#CustomerSign#:

The signature of the customer while using the Mobile App.

 

#CustomerSignDate#:

The date and time that the customer signed when using the App (not editable).

 

#JobRepName#:

The name of the First Rep that has been selected on the Job Ticket Booking.

 

#SignedByRep#:

The name of the Rep that signed using the App.

 

#SignedByCustomer#:

The name of the customer that signed using the App (can be changed on the app to reflect the actual person signing if not the person named within the address)

 

#RepSign#:

The signature of the rep who signed the Job Ticket on the Mobile App.

 

#RepSignDate#:

The date and time the rep signed the Job Ticket on the App.

 

#AcceptRejectDate#:

The date the Accept (or Reject) button was pressed on the Mobile App.

 

#AcceptRejectTime#:

The time the Accept (or Reject) button was pressed on the Mobile App.

 

#TravelStartDate#:

The date the 'En-Route' button was pressed on the Mobile App.

 

#TravelStartTime#:

The time the 'En-Route' button was pressed on the Mobile App.

 

#TotalTravelTime#:

The total amount of time lapsed between pressing En-Route and subsequently pressing 'On Site' (using the App)

 

#TotalSiteTime#:

The total amount of time lapsed between pressing 'On Site' and 'Leave Site', in the absence of pressing 'Leave Site' the time the rep signed will be used. (using the App)

 

#TotalTravelSiteTime#:

The total amount of time lapsed between pressing En-Route and subsequently pressing 'Leave Site', in the absence of pressing 'Leave Site' the time the rep signed will be used. (using the App). This is useful for determining the total time on a particular job from when the rep started to travel to the site up until completing the job.

 

#DayDetails#:

The 'Additional Notes' section as shown on the popup Booking Form' Dialogue.

 

#RepReport#:

Details as recorded by the rep as their 'Rep Report. This field is not often used as the possibility of Typo's is high. instead, copy and paste the rep report into the 'Completion Report' rectifying any Typo's or grammar where required and use the Tag #JobReport# within your Job Ticket design.

 

#PartsUsed#:

The typed in 'Parts Used' report as entered on the Mobile App.

 

#FurtherWork#:

The typed in 'Further Works' Used report as entered on the Mobile App.

 

#PartsReport#:

'Parts' field on the booking Form Completion Reports Dialogue.

 

#LabourReport#:

'Labour' field on the booking Form Completion Reports Dialogue.

 

#TimeReport#:

'Time' field on the booking Form Completion Reports Dialogue.

 

#TravelReport#:

'Travel' field on the booking Form Completion Reports Dialogue.

 

#JobTicketText1#:

Text field 1 of the Job Ticket Custom Fields section.

 

#JobTicketText2#:

Text field 2 of the Job Ticket Custom Fields section.

 

#JobTicketText3#:

Text field 3 of the Job Ticket Custom Fields section.

 

#JobTicketText4#:

Text field 4 of the Job Ticket Custom Fields section.

 

#JobTicketText5#:

Text field 4 of the Job Ticket Custom Fields section.

 

#JobTicketToggle1#:

Toggle field 1 of the Job Ticket Custom Fields section.

 

#JobTicketToggle2#:

Toggle field 2 of the Job Ticket Custom Fields section.

 

#JobTicketToggle3#:

Toggle field 3 of the Job Ticket Custom Fields section.

 

#JobTicketToggle4#:

Toggle field 4 of the Job Ticket Custom Fields section.

 

#JobTicketToggle5#:

Toggle field 5 of the Job Ticket Custom Fields section.

 

#DocumentRevision#:

Document Revision number as shown at the top of the Document Designer panel of each Job Ticket.

 

#ProductVariants#:

All of the Product Variant names as selected when a product has been defined detailing all of the items that make up that product (the Product specification)

 

#PartsPickerStr#:

A single line list of parts used while using the Parts Picker of the app (requires parts to be allocated using the Assets Section).

 

#PartsPickerTbl#:

A table showing the parts used while using the Parts Picker of the app (requires parts to be allocated using the Assets Section).

 

#CheckListA#:

Check List A table (may have been renamed but the same HashTag must be used in order to identify it to the system.).

 

#CheckListB#:

Check List B table (may have been renamed but the same HashTag must be used in order to identify it to the system.).

 

#CheckListC#:

Check List C table (may have been renamed but the same HashTag must be used in order to identify it to the system.).

 

#CheckListD#:

Check List D table (may have been renamed but the same HashTag must be used in order to identify it to the system.).

 

#QuestionsE#:

Questions List E table (may have been renamed but the same HashTag must be used in order to identify it to the system.).

 

#QuestionsF#:

Questions List F table (may have been renamed but the same HashTag must be used in order to identify it to the system.).

 

#AllCheckLists#:

All of the Check Lists and questions lists inserted on to the Job Ticket design placed underneath each other. (unused tables / lists will be omitted).

 

#CheckListASM#:

Check List A table (may have been renamed but the same HashTag must be used in order to identify it to the system.). This tag will include the 'Service Month' detail if the option has been used.

 

#CheckListBSM#:

Check List B table (may have been renamed but the same HashTag must be used in order to identify it to the system.). This tag will include the 'Service Month' detail if the option has been used.

 

#CheckListCSM#:

Check List C table (may have been renamed but the same HashTag must be used in order to identify it to the system.). This tag will include the 'Service Month' detail if the option has been used.

 

#CheckListDSM#:

Check List D table (may have been renamed but the same HashTag must be used in order to identify it to the system.). This tag will include the 'Service Month' detail if the option has been used.

 

#QuestionsESM#:

Questions List E table (may have been renamed but the same HashTag must be used in order to identify it to the system.). This tag will include the 'Service Month' detail if the option has been used.

 

#QuestionsFSM#:

Questions List F table (may have been renamed but the same HashTag must be used in order to identify it to the system.). This tag will include the 'Service Month' detail if the option has been used.

 

#AllCheckListsSM#:

All of the Check Lists and questions lists inserted on to the Job Ticket design placed underneath each other. (unused tables / lists will be omitted).

 

#TicketImages#:

Pictures taken on site.

 

#NewPageTicketImages#:

Pictures taken on site but will be automatically placed on a new page. (Position this tag as the very last item on your design.

 

#VatExemptionCondition#:

VAT exemption status client condition as recorded on the Mobile App.

 

#TicketCreatedDate#:

Date the Job Ticket was originally created.

 

#JobPrice#:

Job Price as shown in the RH column of a Job Ticket.

 

#TimePrice#:

Time Price as shown in the RH column of a Job Ticket.

 

#TravelPrice#:

Travel Price as shown in the RH column of a Job Ticket.

 

#PartsPrice#:

Parts Price as shown in the RH column of a Job Ticket.

 

#LabourPrice#:

Labour Price as shown in the RH column of a Job Ticket.

 

#TotalPrice#:

Total Price as shown in the RH column of a Job Ticket.

 

#LeadSource#:

Lead Source name as shown on the Sales Prospect Dialogue.

 

#LeadOwner#:

Lead Owner name as shown on the Sales Prospect Dialogue.

 

#SalesDescription#:

Sales Description (Description panel) as shown on the Sales Prospect Dialogue.

 

#ProspectOther#:

'Other' name as shown on the Sales Prospect Dialogue.

 

#ProspectDrop1#:

Custom Fields Drop Down List 1 as shown on the Sales Prospect Dialogue.

 

#ProspectDrop2#:

Custom Fields Drop Down List 2 as shown on the Sales Prospect Dialogue.

 

#ProspectDrop3#:

Custom Fields Drop Down List 3 as shown on the Sales Prospect Dialogue.

 

#ProspectDrop4#:

Custom Fields Drop Down List 4 as shown on the Sales Prospect Dialogue.

 

#ProspectDrop5#:

Custom Fields Drop Down List 5 as shown on the Sales Prospect Dialogue.

 

#ProspectText1#:

Custom Fields Text Field 1 as shown on the Sales Prospect Dialogue.

 

#ProspectText2#:

Custom Fields Text Field 2 as shown on the Sales Prospect Dialogue.

 

#ProspectText3#:

Custom Fields Text Field 3 as shown on the Sales Prospect Dialogue.

 

#ProspectText4#:

Custom Fields Text Field 4 as shown on the Sales Prospect Dialogue.

 

#ProspectText5#:

Custom Fields Text Field 5 as shown on the Sales Prospect Dialogue.

 

#ProspectToggle1#:

Custom Fields Toggle 1 as shown on the Sales Prospect Dialogue.

 

#ProspectToggle2#:

Custom Fields Toggle 2 as shown on the Sales Prospect Dialogue.

 

#ProspectToggle3#:

Custom Fields Toggle 3 as shown on the Sales Prospect Dialogue.

 

#ProspectToggle4#:

Custom Fields Toggle 4 as shown on the Sales Prospect Dialogue.

 

#ProspectToggle5#:

Custom Fields Toggle 5 as shown on the Sales Prospect Dialogue.

 

See Also:

AutoVu Solutions Logo

If you would like to know more about AutoVu and what we can do to help your business, why not check out our Frequently Asked Questions page, or Contact Us any time to discuss your specific requirements.

Professional cloud based software