Joblogic already knows which planned visits are on each PPM contract and which have been done. What it does not hand you by default is a grid that says, for every site and every month, how many visits fell due and how many were finished before that month closed. That grid is what a client asks for at the quarterly review, and what an Operations Director needs to spot one site quietly slipping while the rest of the estate looks fine. This page covers where the planned work sits in Joblogic, how to pull it out through the published API, and the counting rules that stop the numbers moving every time someone reruns them.
What Joblogic shows you, and the question it leaves open
Joblogic's own introduction to PPM in Joblogic Web describes the building blocks. A PPM contract has a start and end date. Visits are programmed against a site or asset with a due date and a frequency, and can be cloned, so one monthly visit becomes twelve scheduled ones. Progress is tracked on an "All PPM Contracts" overview, the scheduler can filter PPM work apart from reactive jobs, and Joblogic says you can report on PPM visit costs, contract invoices and site profitability.
The API mirrors this. Its PPM contract search returns, for each contract, TotalNumberOfVisits, NumberOfCompletedVisits and PercentageCompleted alongside SiteId, StartDate and EndDate (all from the Joblogic API reference). That is a contract-to-date measure. On a contract that runs April to March, a site that has done every visit so far will still show roughly half complete in October, because the visits for November to March are in the total. The reference does not spell out how PercentageCompleted is calculated, so check it on one of your own contracts, but either way it answers "how far through the year are we?" rather than "did we do last month's work?"
A monthly, site-by-site view needs the individual visit jobs.
Getting planned jobs out of Joblogic
Joblogic publishes its API documentation at apidocs.joblogic.com. The practical points for a reporting pipeline:
- Access is requested and approved. Joblogic's support article on API access describes an API Access app that handles the request and approval, with the client ID and secret sent in separate emails. The API reference adds that requests are only accepted from IP addresses Joblogic has whitelisted, and that you get a UAT tenant to build against first.
- Authentication is OAuth 2.0 client credentials against Joblogic's identity server, with the scope
JL.Apishown in the reference's example. - Rate limits. The reference says endpoints are limited to 100 requests per minute by default, that limits can vary by client, and that going over returns HTTP 429.
- Dates are UTC. All request and response date-times are UTC. A visit completed at 00:30 on 1 October British Summer Time is 23:30 on 30 September in UTC, so decide which calendar your month boundaries follow and convert once.
Three endpoints do most of the work:
| Endpoint | What it gives the report |
|---|---|
POST /api/v1/Job/getall |
Paged job search. Set IncludePPMJobs to true and IncludeReactiveJobs to false. Filter by SiteId, StartCompleteDate and EndCompleteDate. Returns JobNumber, SiteId, SiteName, DateComplete, JobStatusDescription and UpdatedAt. Page size is capped at 50. |
GET /api/v1/Job/GetById |
Full job record, including PPMContractId, TargetCompletionDate, DateComplete and Status. |
POST /api/v1/ppmcontract/getall |
One row per PPM contract: number, customer, site, dates and the visit counts above. IncludeCompleted and IncludeCancelled exist as filters, so set them if you want history. |
When a visit is added to a PPM contract through the API, the request takes a DueDate and the response returns a JobUniqueId, which is how you know each planned visit becomes a job. The reference does not say which field on the resulting job carries that due date. TargetCompletionDate is the obvious candidate, and it is what the example below assumes, but confirm it by adding one visit in your UAT tenant and reading the job back. There is also a Visit/GetAll endpoint that returns engineer visits for a job with StatusDescription, IsAborted, HasRevisit and a NoAccess field, which helps when you need to explain a miss rather than count it.
Joblogic may also offer in-app report exports. We have not relied on them here, because a scheduled pull through the API is what keeps a monthly grid consistent from one run to the next.
The data model
Fields
| Source | Object | Fields used |
|---|---|---|
| Joblogic | PPM contract | PPMContractNumber, CustomerName, SiteId, SiteName, StartDate, EndDate, IsCancelled, IsSuspended |
| Joblogic | Job (PPM visit) | JobNumber, SiteId, PPMContractId, TargetCompletionDate, DateComplete, Status |
| Joblogic | Visit | JobId, StatusDescription, IsAborted, NoAccess |
| Your own | Month calendar | Month start, month end, in the time zone you report in |
Joins
| From | To | Key | Watch for |
|---|---|---|---|
| Job | PPM contract | PPMContractId to the contract's unique ID |
Jobs with a null PPMContractId are reactive or were logged by hand |
| Job | Site | SiteId |
The contract search returns one site per contract; check any multi-site arrangements |
| Job | Month | Due month from TargetCompletionDate |
Convert from UTC before truncating to month |
| Visit | Job | JobId |
One job can have several visits; use the latest for the reason |
Formulas
| Measure | Formula |
|---|---|
| Planned in month | count of PPM jobs with due date in the month, excluding cancelled |
| Done on time | planned jobs with DateComplete on or before the last day of the due month |
| Done late | planned jobs with DateComplete after the month closed |
| Open | planned jobs with no DateComplete at the run date |
| On-time rate | done on time ÷ planned |
| Catch-up | jobs completed in the month whose due month is earlier; reported, never added to the rate |
| Portfolio rate | sum of done on time across sites ÷ sum of planned across sites |
The month a job belongs to is fixed by when it was due, never by when it was finished. That single rule is what lets September's figure stay the same when you rerun it in December.
Joblogic PPM jobs · run 5 November 2026
PPM completion by site · Fernhallow Engineering Services (fictional)
72 of 88 planned visits
done in October 2026.
Planned means a PPM visit job due in the month, not cancelled. Done means completed by the last day of that month. Catch-up work from earlier months is shown but never counted.
- Oct on-time rate
- 81.8%
- 72 of 88 planned
- Six-month rate
- 89.6%
- 448 of 500 planned
- Open PPM visits
- 20
- Due May–Oct, no completion
- Sites under 85%
- 4 of 8
- In Oct
Planned vs done on time, all sites
Planned Done on time
Site by month: done on time / planned
≥ 95% · < 85%
| Site | May | Jun | Jul | Aug | Sep | Oct | 6 months | Contract to date |
|---|---|---|---|---|---|---|---|---|
| Quarrington Road DepotCorlan Property Partners | 13/13 | 12/12 | 8/10 | 11/11 | 11/11 | 8/9 | 95.5% | 76/136 |
| Eastmere Health CentreCorlan Property Partners | 15/15 | 14/15 | 13/13 | 15/15 | 14/15 | 16/17 | 96.7% | 109/173 |
| Larkspur Yard OfficesCorlan Property Partners | 5/7 | 9/10 | 7/7 | 9/10 | 7/9 | 10/10 | 88.7% | 61/101 |
| Wyncote Leisure CentreBrennock Learning Trust | 18/18 | 17/18 | 17/20 | 16/20 | 13/16 | 12/19 | 83.8% | 122/216 |
| Sallowfield Primary SchoolBrennock Learning Trust | 5/6 | 5/6 | 6/6 | 6/6 | 9/9 | 7/9 | 90.5% | 49/85 |
| Thistlebank LibraryBrennock Learning Trust | 5/5 | 7/7 | 3/4 | 5/5 | 4/4 | 5/5 | 96.7% | 37/62 |
| Corrow Street Retail UnitCorlan Property Partners | 6/8 | 7/7 | 6/8 | 6/7 | 2/5 | 4/7 | 73.8% | 42/78 |
| Hindmarsh Court OfficesCorlan Property Partners | 10/11 | 14/14 | 10/10 | 8/10 | 8/9 | 10/12 | 90.9% | 77/138 |
| All sites | 92.8% | 95.5% | 89.7% | 90.5% | 87.2% | 81.8% | 89.6% |
Contract to date counts completed visits against every visit on the contract year, including ones not yet due, so it is not a monthly completion rate.
October 2026 reconciliation, all sites
- PPM visit jobs due in month90
- Less cancelled−2
- Planned88
- Done by month end72
- Done after month end4
- Still open12
- Catch-up from earlier months (not counted)7
- All PPM jobs completed in month79
Still open, oldest first
| Job | Site | Due | Days over |
|---|---|---|---|
| P52941 | Hindmarsh Court Offices | 26 May | 163 |
| P52847 | Corrow Street Retail Unit | 28 May | 161 |
| P52865 | Corrow Street Retail Unit | 10 Jul | 118 |
| P52542 | Wyncote Leisure Centre | 28 Aug | 69 |
| P52876 | Corrow Street Retail Unit | 17 Sep | 49 |
| P52565 | Wyncote Leisure Centre | 19 Sep | 47 |
| P52873 | Corrow Street Retail Unit | 19 Sep | 47 |
| P52267 | Eastmere Health Centre | 29 Sep | 37 |
| P52881 | Corrow Street Retail Unit | 8 Oct | 28 |
| P52879 | Corrow Street Retail Unit | 9 Oct | 27 |
| P52111 | Quarrington Road Depot | 11 Oct | 25 |
| P52733 | Sallowfield Primary School | 14 Oct | 22 |
Showing 12 of 20 open visits.
Worked example (illustrative, fictional)
Fernhallow Engineering Services is an invented contractor with eight sites on PPM contracts running 1 April 2026 to 31 March 2027. The run date is 5 November 2026. Wyncote Leisure Centre, one of the sites, had trouble getting into its plant room in October.
Step 1: due in October. Twenty PPM visit jobs at Wyncote have a target completion date in October. One was cancelled, so planned is 20 − 1 = 19.
Step 2: sort the 19. Twelve have a DateComplete on or before 31 October. Three were finished on 4 or 5 November, after the month closed. Four have no completion date. Check: 12 + 3 + 4 = 19.
Step 3: the rate. 12 ÷ 19 = 63.2%.
Step 4: what the naive count would say. Fifteen PPM jobs at Wyncote were completed during October: the 12 above plus three catch-up jobs (two due in August, one due in September). Dividing completions in the month by jobs due in the month gives 15 ÷ 19 = 78.9%, which flatters October with work that belonged to earlier months.
Step 5: what the contract figure says. The Wyncote contract has 216 visits for the year and 122 completed so far, so 122 ÷ 216 = 56.5%. That is lower than October's real rate, not because October was worse but because most of the year's visits are not yet due.
Step 6: roll up. Across all eight sites, 72 of 88 planned October visits were done on time: 72 ÷ 88 = 81.8%. Take Wyncote out and the other seven sites did 60 of 69, which is 87.0%. One site pulled the portfolio down by about five points, and the site-by-month grid makes that obvious where a single number would not. Over May to October, Wyncote did 93 of 111 on time (83.8%).
Averaging the eight site percentages for October instead of pooling the counts gives 83.1%, because a five-visit library counts as much as a nineteen-visit leisure centre. Pool the counts.
Where Joblogic PPM numbers go wrong
- Cancelled visits left in the denominator. Cancelled contracts are a filter on the contract search, but cancelled individual jobs can still come back from the job search. Filter on status explicitly.
- Statuses are your own. The API notes that a job's status must match an existing status in your account, which means names differ between Joblogic customers. Map them once in the warehouse, test the mapping and record which ones count as complete.
- Rerunning with completion-date filters.
StartCompleteDateandEndCompleteDateare handy for narrowing a pull, but filtering on them alone drops open jobs. Pull by site and keep the full job history, usingUpdatedAtto see what changed. - No access versus not done. Whether an evidenced no-access visit counts against you depends on the contract. The general rules for that, and for tolerance windows, are in the PPM compliance report template; this page only adds where those signals sit in Joblogic.
- Statutory and non-statutory work mixed together. If your Joblogic visits were set up from SFG20 schedules (SFG20 is developed by BESA and published by SFG20 Ltd), carry the schedule reference onto each job, for example as a job attribute, which the API can read and write. You can then split the grid so one missed statutory visit is not hidden among routine ones. Mapping tasks to SFG20 is a separate job, and this page reproduces none of its content.
If you run Uptick, Simpro or ServiceMax rather than Joblogic, the counting logic is the same but the objects differ: see the Uptick, Simpro and ServiceMax pages.
Running it every month with IVP.ai
The IVP.ai Data Layer pulls Joblogic's PPM contracts and visit jobs on a schedule, within the access and rate limits Joblogic sets, and stores every job with its history so a closed month's figure does not change on a rerun. The due-month rule, the cancelled filter and the status mapping become tested definitions rather than steps someone remembers. The grid above then runs as a report or agent on the first working day of each month, and Deskless by IVP.ai can send each contract manager the open visits for their sites. By default it flags and drafts; it does not reschedule work unless you set it up to.
Because the same warehouse can hold your CRM and finance data, the PPM view can sit next to contract value and invoicing. A national fire safety and security company used IVP.ai to bring HubSpot, Uptick and its finance spreadsheets into one governed view and now saves 10+ hours a week on reporting (case study). More on the platform and on field service reporting.
To see this on your own Joblogic data, start a free 48-hour pilot. We connect up to three sources, clean the data and have one report or agent running on your real data within 48 hours of read-only access. You then have 14 days of access to decide whether to choose a plan or walk away.