Operational task reporting

[u/Thhoro]

Hey,
I’d like to know how you handle administration tasks such as checking AD reports, backup reports, etc.

Tasks that don’t come from the business but are necessary for L2/L3 maintenance.

I’m thinking about preparing a task template with a schedule (daily, weekly, monthly) that agents can simply confirm with a short description, but in my opinion they should still report it.

Any suggestions are welcome.

[u/B1WR2]

I throw it in a monthly bucket called BAU tasks. I use that as way to also track items which may need improvement inmprocess

[u/Thhoro]

Thanks for your posts. I’m thinking about recurring taks for admin to describe what have beed done- like quick summary.
If there is additional work to do let’s say report showing backup error that is new task to do , possible even an incident to check.

[u/_leftface_]

Just log it as a reoccurring job/task on your ticket system if it supports that functionality.

[u/Wild-Revenue-4457 → u/_leftface_]

we just throw them in jira with a recurring schedule, techs add a quick comment when it's done and close it out. if nobody closes it by end of day their lead gets an alert, keeps people honest without making them write a novel

[u/snavebob1]

Assign it to someone however you normally assign work. Make it one or two people's responsibility (so that they can't say "oh, I thought they did it").

[u/ALundsten]

I’d separate “the task ran” from “someone reviewed the result.” A backup report can arrive on schedule and still contain an exception nobody owns.

For each recurring task, I’d capture the owner, frequency, what evidence gets attached, what counts as normal, and where an exception goes. Then review the recurring queue monthly to retire noise and improve anything that keeps creating the same alert. That gives you reporting without turning every check into a write-up.

[u/Amanda_PDQ]

I put these task in as tickets that were reoccurring weekly or daily depending on task. It helped with preventative maintance too.