[ ← home ]
Weekly report
The recurring report that never skips a week. Recurring reports are easy to automate — and easy to forget when someone is on holiday. A job builds the report at the same time every week, checks its own work, and shows you proof that it ran.
You say — once
~/work ❯ › "every Friday at 4, assemble the weekly KPI report from our exports"
▼
01 · Friday at 16:00
A job gathers the export files, builds the report, and saves it where your team expects to find it.
▼
02 · The output is checked
The job verifies its own result: the file exists, the numbers can be read, and the report covers the right week. If a check fails, the run is marked red and Altoquant tries to repair the cause.
▼
03 · The history is visible
The Jobs view shows a green block for every week that ran correctly — and a red one for any week that did not. A report can no longer go missing without anyone noticing.
What comes back — minutes to produce the report
15 ┤ ╭────╮
13 ┤──────────╯ ╰───╮
11 ┤ ╰─╮
10 ┤ ╰╮
8 ┤ ╰╮
6 ┤ ╰╮
5 ┤ ╰─╮
3 ┤ ╰─────────────────────
└────────────────────────────────────────────────
automated from week 5 — same report, 3 minutes, zero hands
What you get
- The same report, built the same way, every week
- A clear red signal when something went wrong — instead of a missing file
- The full output of every past run, kept and openable
[ jobs ] [ verification ] [ run history ]
Stay in touch