A practical planning checklist

Is this workflow ready to automate?

Choose one task you repeat, spot what could get in the way, and decide what the first project should deliver.

No signup. Tick items as you review them. Selections stay only on this page and are not saved or sent. Use your browser's print dialog to keep a copy.

1. Choose a specific process

I can describe the recurring task in one sentence.
There is one person who owns the process and can approve the result.
I know how often the task runs and who uses the result.
I know how much time the task takes, or where errors or delays happen.

Example: “Every Friday, the operations lead prepares a client delivery summary from the shared project tracker.”

2. Understand the inputs and exceptions

We know where the data comes from, can access it and know who owns it.
The main fields use consistent names and formats, and everyone knows what they mean.
I can identify missing, duplicate, late, or invalid records.
I know which decisions still require a person.

Bring a made-up sample or one with confidential details removed to the first discussion. Do not email passwords or other access credentials, or confidential data.

3. Check the practical constraints

We can check the tools, plans and access we need before building.
The right person can approve access, connections, and any necessary changes.
The data owner can confirm how information may be used and shared.
Someone can maintain the workflow and respond when a run fails.

Your organization still needs to approve the work. Find out who must approve it early.

4. Define the finish line

We have agreed on the result or report we want.
We can compare the result with a known sample and check unusual cases.
The person who owns the process can run it before the project ends.
The proposal will say which changes, instructions and support are included, and what is not.

Agree on something you can check: the totals match, the right person receives a request, or the owner can run the next cycle using the guide.

Choose the next step

The process and inputs are clear: agree on a small build and how to check it.
You know the problem but the process is unclear: begin with a workflow review.
Access, ownership, or data quality is still unclear: resolve those questions before agreeing to build.

This is a planning aid, not a compliance assessment or a guarantee of suitability or savings.

Describe one process

Process to improve:

Process owner:

Current tools and source:

Frequency and current effort:

Desired output:

How we will check it:

Known access or license limits:

Target timing and budget:

Want help planning a project from this?

Explore the workflow review Describe your process

Email Felipe about your workflow

A brief description is enough for a first conversation. Opens your email app; nothing is sent automatically.