Workflow reviews for site and office admin
One job record, written down four times.
I trace one recurring admin process from the first site note to the final office record. You get a written plan showing where information is being copied, lost or chased, what to change now, which tools to keep and whether anything needs to be built.
15 minutes. One workflow. No preparation, no obligation.
| Where it was written | Job ref | Unit | Photos |
|---|---|---|---|
| 1 / Site notebook08:40, on the jobWhat actually happened | TS-1184 | Unit 3B | 2 |
| 2 / Message to office08:52, from the van | TS-1184 | −Not included | 2 |
| 3 / Tracker spreadsheet14:10, re-keyed in office | TS-1148Two digits swapped | Unit 3B | 0Still on a phone |
| 4 / Handover packWeek 14, sent to client | TS-1184 | Unit 3B | 0Nobody can find them |
You already know which workflow it is.
It is the one that produces the same phone call every week. Usually the information exists. It is just somewhere the next person cannot use it.
- Site photographs nobody can match to a job
- Weekly reports rebuilt by hand in the office
- Service dockets keyed in two or three times
- Certificates and safety files that take an afternoon to find
- Snags and close-out details scattered across five threads
- A process only one person actually knows
Current workflow focus
Handover packs should not become a final-week search.
Delaney Works is testing whether clearer ownership, status and approval can make O&M and handover document control easier for M&E and building-services contractors.
The review looks at the route, not the software.
A workflow is the path one piece of information takes: a docket from the van to the invoice, a snag from the walk-round to sign-off. The review follows one of them end to end and comes back in writing.
What gets traced
- Where the record starts, and who writes it
- Every point it is copied or keyed again
- Where the job reference or context drops off
- Who checks it, and who needs the final output
- What has to be retained, and for how long
What you receive
- The main failure points, in plain language
- What can be improved in the current process
- Which existing tools are worth keeping
- The smallest useful next step
- A clear boundary for any possible build
A written route from today’s process to a simpler one, with the handoffs and next action made clear.
Three clear decisions, made in order.
- 1Free
A 15-minute call
Describe one workflow that annoys you, in your own words. Nothing to prepare. By the end you will know whether it is worth looking at properly.
- 2From €1,000
The workflow review
A fixed-scope review ending in a written recommendation you can read, share, and use. The final price is agreed before work begins.
- 3Optional
Implement the recommendation
If a build is justified, it is scoped and agreed separately after you have the recommendation.
Who you deal with
Emmet Delaney
Software engineer with approximately 10 years of professional software engineering experience, based in Limerick and working with businesses across Ireland.
The person on the introductory call is the person who runs the review and builds anything you later agree to. No account manager in between, and no reason to recommend a bigger system than the problem deserves.
Remote across Ireland. Site visits where seeing the process matters.
Take a practical resource.
Download a blank form or read the short guidance before you book. Everything is open, with no sign-up required.
Bring one workflow to a 15-minute call.
The one that gets written twice, or chased every Friday. Describe it as you see it.
Book a 15-minute callOr email [email protected]