Automation
Small scripts and flows that take repeat work out of inboxes, spreadsheets, and memory.
IT ops, small tools, runbooks, automation
I turn messy IT work into tools people actually use.
I am Brent. I like finding the repetitive, fragile, "why are we still doing it this way" parts of IT work and turning them into simple automations, checklists, scripts, and workflows that save time without making the job harder to understand.
The kind of work I like
Useful little systems for work that happens over and over.
AI-Assisted Review
Practical helpers for summaries, triage, documentation cleanup, QA, and exception notes.
Runbooks
Checklists and procedures that make the next handoff clearer than the last one.
Projects
Things I have built, tested, or want to keep improving.
These are the kinds of operational problems I like working on: practical, a little messy, and much better once the repeatable parts are captured.
Automation project
Ticket Triage Summary
Problem: Repetitive ticket updates made it hard to see what needed attention.
What I built: A status digest that groups tickets by age, owner, blocker, and next action.
Why it helped: The queue became easier to scan, and stale work was harder to miss.
Tools/concepts: API pulls, structured summaries, checklist rules, AI-assisted wording.
Time saved: 3-5 hrs/week
Impact: clearer queue ownership
What I learned: A useful automation does not need to replace judgment. It should make judgment faster.
Runbook project
Runbook Checklist Flow
Problem: Important recurring procedures lived in memory and scattered notes.
What I built: A guided checklist that captures evidence, timestamps, outcomes, and exceptions.
Why it helped: The procedure became easier to repeat, review, and hand off.
Tools/concepts: Forms, validation, audit trail, exception handling, handoff notes.
Time saved: 20-40 min/run
Impact: fewer missed steps
What I learned: Documentation becomes more valuable when it is part of the work, not after the work.
Data cleanup project
Report Cleanup Automation
Problem: Recurring reports required manual cleanup before anyone could trust the numbers.
What I built: A repeatable cleanup flow with validation checks and a short exception report.
Why it helped: The report became faster to prepare and easier to trust.
Tools/concepts: Spreadsheet automation, parsing, validation rules, exception queues.
Time saved: 2-4 hrs/report
Impact: faster decisions
What I learned: The best reports are not prettier. They are more reliable with less human cleanup.
Savings calculator
A quick way to size up repetitive work.
I built this to turn "it only takes a few minutes" into a rough monthly number. It is not a promise, just a useful gut check.
Resources
Public repos for the things I keep reaching for.
As I clean these up, this section will point to reusable material on GitHub: templates, scripts, forms, and notes that are useful beyond one project.
Checklists & Runbooks
Reusable procedures, operator checklists, handoff notes, and templates for recurring IT work.
GitHub repo placeholder Runbooks · templates · operational notesScripts & Utilities
Small automations, cleanup helpers, reporting utilities, and scripts I have built or adapted for repeat work.
GitHub repo placeholder Scripts · automation · cleanup helpersForms & Documents
Intake forms, tracking documents, review templates, and other lightweight workflow materials.
GitHub repo placeholder Forms · documents · workflow templatesAbout Brent
I care about the work behind the work.
I like the quiet parts of IT that make everything else run better: clean handoffs, repeatable steps, fewer mystery spreadsheets, and tools that remove just enough friction to matter. This site is where I collect the projects, docs, and experiments I am building around that kind of work.
Where to find me
Follow along as I build and share more of this work.
I post updates, project notes, and useful things I am learning as I clean up scripts, runbooks, and workflow ideas.