OK, you have what the Navy calls a "chop chain" or "approvals list."
For each paper report, you need a record in your DB, which implies a table to track reports by some sort of sequence number or other UNIQUE identifier.
For each RECORD in that implied table, you need a record of each stage of approvals, but you will have multiple approvals for a single document so you might want to have a separate "approvals" table that is a child of the document table.
Then when you have a form to be approved by the next person in sequence, you need a table that identifies the next person, which implies a separate list of approval officers and their approval order, and you would track the stage of approvals with each document.
Now, the SIMPLE way to keep that straight is if you have a domain-oriented in-house network you can use the Environ function to get the USERNAME of the person logged in and use that as part of the signature process - rather than asking someone who they are. Because of course they could lie, and you want to properly track stuff and prevent improper erasure of other stuff. (Note the highly technical jargon here...)
The last part of this is that if you don't want users to be able to erase "stuff" then they can't be allowed to see "stuff." So you need to have a form that ALWAYS stands between your users and the underlying data tables. I.e. they can never be allowed to see the navigation pane of the database; nor can they ever be allowed to see the menu bar or ribbon, depending on version number of Access that you are using.
This will give you a direction to think about. I'm not giving you details because you have to decide whether you even want to go this way.