Batch Register
For the operations lead whose scheduler runs jobs nobody has read against the rules

Paste the scheduler export. Get every job against the clock a rule sets.

Paste your scheduled jobs and reports, the way your scheduler exports them. Get every job classified by what consumes it, the clock a rule puts on that consumer with the clause behind it, the gap between the job's schedule and that clock, the jobs with no owner and no fallback, the duplicates, and the list to take to the owners before the next audit asks how often the evidence is actually produced.

Build your own registerEight jobs free, no account. Runs in your browser; nothing leaves it until you choose to save.
An operations analyst at her desk with two monitoring screens, reading the day's figures
The answer to how often the evidence is actually produced, held per job and ready before anyone asks for it. It reads your lines against clause text published by the same house, at compliance.theartofservice.com, which no other register carries.
Specimen: an invented payments and lending company. Eight of its 36 jobs shown.
JobPeriodClockGap
card_env_log_review slow168h24h144 h168 h / 24 h
siem_log_review_export log daily730h24h706 h730 h / 24 h
prod_db_full_backup no restore24hno clockno clock
gdpr_breach_report_pack no drillno period72hno period72 h clock
quarterly_access_review_export slow8,760h4,380h4,380 h8,760 h / 4,380 h
vuln_scan_export scan4,380h2,190h2,190 h4,380 h / 2,190 h
customer_statement_feed1hno clockno clock
halden_widget_warmer unreg1hnot placednot placed
36 jobs, 35 classified5 slower30 clauses11 findings
Lit cell: read from the schedule or from a clause, the period hours converted from the schedule. Plain: computed, or nothing to read. Gap: the hours the period runs past the clock. The full register adds the class, the owner, the fallback, the question for each owner, the duplicates and the concentration.
One job per line: Job | Schedule | Source | Consumer | Owner | Fallback, or just Job, Schedule, or the job name alone. Tabs, pipes or commas; a header row is optional and its column names are recognised in any order; a cron expression is read in any column. A first line regimes: PCI DSS, CPS 234 | as at: 2026-09-22 ticks the rules and pins the date. A scheduler's CSV export pastes as it is.
Runs against the published dictionary of 47 classes; every clock cites its clause.
01

Paste the jobs you already schedule

The scheduler's export, the report calendar, the cron table or a line per job from memory: one job per line with its schedule, and where you have them the source, the consumer, the owner and the fallback, in any order the header names. Every job is matched against a published dictionary of 47 consumer classes in ten families; a job that matches nothing is marked unrecognised and never guessed.

02

Read the period, the clock and the gap

Per job: the class and its family, the period read from the schedule in hours and words, the shortest clock the ticked rules put on that consumer with the clause that states it, and the gap between the two. Where a text says periodically, regularly or a defined frequency, the row says so and carries no hours; the register never fills a blank the standard left open. Per register: jobs by family, by period band and by owner, and how many sit on a fixed clock.

03

Take the findings and the questions to the owners

Eleven findings in a fixed order: the unrecognised job, the schedule slower than its clock, the on-demand job where the clock is fixed, no owner, no fallback, the backup with no restore test beside it, the log review outside the daily read, the breach pack with no drill, the duplicate, the concentration on one owner or one source, and the scan slower than quarterly. Every classified job carries one question for its owner; the owner list groups them by the person they go to.

Why a register and not a control list

A control list says what should exist. A scheduler export says what actually runs and how often, and the two are different objects. When the auditor asks how often the card-environment logs are reviewed, the answer is not in the policy; it is the schedule of the job that produces the review. Read against the clause, that schedule is a finding: the log review job runs weekly against a daily clock. Batch Register reads that gap job by job from the export you already hold, in your browser, and never says a control is present or absent.

The dictionary and the clock table are ours and published in full: every consumer class it recognises, in ten families, and what each rule sets on a consumer, with the hours only where the published text states them. The requirement text behind every clock is stated in our own words from the published standards, published at compliance.theartofservice.com, the same publisher as this register, and ships with this page as a static file. The register reads your own lines and states the clock; it does not rule on the obligation.

Batch Register: the questions buyers ask

What is Batch Register?

Batch Register reads your scheduler export and puts every scheduled job against the clock a rule sets. For each job it returns the consumer class, the clock with the clause behind it, and the gap between the job's schedule and that clock.

What do I paste into Batch Register?

One job per line, with the schedule and, where you have them, the source, consumer, owner and fallback. Tabs, pipes or commas all work, a header row is optional and its column names are recognised in any order, and a cron expression is read in any column.

How many jobs can I run for free?

Eight jobs are free and no account is needed. Everything runs in your browser and nothing leaves it until you choose to save, and a scheduler's CSV export pastes as it is.

How does it know how often the evidence is actually produced?

It reads the period from the schedule and states it in hours and words. Where the ticked rule puts a clock on that consumer, it shows the clock with the clause that states it and the gap between the two.

What if a rule says periodically rather than giving a number?

Where the text says periodically, regularly or a defined frequency, the row says so and carries no hours. The register never fills a blank the standard left open.

Which regimes can it read jobs against?

PCI DSS v4.0, ISO/IEC 27001:2022 with the 27002:2022 guidance beside it, DORA, NIS2, the GDPR, APRA CPS 234, ISO 22301:2019, NIST SP 800-53 Rev 5 and the HIPAA Security Rule. You tick the ones that reach you, and a first line such as `regimes: PCI DSS, CPS 234 | as at: 2026-09-22` ticks the rules and pins the date.

What happens with a job it does not recognise?

A job that matches nothing against the published dictionary of 47 consumer classes in ten families is marked unrecognised and never guessed. The unrecognised job is the first of the findings.

What findings does it raise?

Eleven findings in a fixed order: the unrecognised job, the schedule slower than its clock, the on-demand job where the clock is fixed, no owner, no fallback, the backup with no restore test beside it, the log review outside the daily read, the breach pack with no drill, the duplicate, the concentration on one owner or one source, and the scan slower than quarterly.

Does it tell me whether a control is present or absent?

No. Batch Register reads the gap job by job from the export you already hold, in your browser, and never says a control is present or absent. It states the clock in our words, cited to its clause, and does not rule on the obligation.

What can I take to the job owners?

Every classified job carries one question for its owner, and the owner list groups those questions by the person they go to. The register also shows the jobs with no owner and no fallback, and the duplicates.

Where does the clause text behind each clock come from?

We read the published text of PCI DSS v4.0, ISO/IEC 27001:2022 and 27002:2022, DORA, the NIS2 Directive, the GDPR, APRA CPS 234, ISO 22301:2019, NIST SP 800-53 Rev 5 and the HIPAA Security Rule, read clause by clause from the published text. The requirement text is published at compliance.theartofservice.com by the same publisher.

Is a schedule the same thing as a control?

No. A control list says what should exist, while a scheduler export says what actually runs and how often, and the two are different objects. When the auditor asks how often the card-environment logs are reviewed, the answer is the schedule of the job, read against the clause.

What this does, and what a spreadsheet, an auditor or an AI assistant does better

A spreadsheet is better for holding the scheduler export and for the formulas and notes your operations team already maintains, and it needs no dictionary of consumer classes. An auditor, consultant or lawyer is better on whether a control exists and whether a clock has been met, which this register never decides, and on how the rule applies to your estate. A general AI assistant is better for drafting the owner questions into an email or a report, or explaining a clause in prose. What this does that they do not is read the period from each pasted job's schedule, put the shortest clock the ticked rules set beside it with the clause that states it, and show the gap, the jobs with no owner or fallback and the duplicates, without filling a blank where a standard says only periodically; it never says a control is present or absent.

Primary source: PCI DSS