which design pattern is good for implementing a workflow in one service without workflow engion?

I have a service that is inherited from one interface and have one method that process a request. my Hangfire call this method. in this method I have 4 steps that is in one transaction:

1- read a file and insert into a list 2- validate data and if a record is not success that set state to false 3- for successful records call another method that implement my business, if for any record business is finished state set true else set false 4- for success records create an access file and for others create bad file.

which design pattern is best practice.

is state good or not?