Can you please say more about what this means? Do you mean something like a receipt? Could the print form field type address this need? You can try it out in beta and we expect it will be released next week. It's not quite the same as a dedicated receipt or form printing button but it can be used as a way to output a summary formatted to your liking.
Our current primary focus is on supporting workflows with 2-way data sharing needs in a really generic way. That means we're not specifically targeting the kind of approval workflow you describe so there isn't a specialized UI around it.
You can do use entities for server-based approval workflows but you'll have to design forms that support each workflow step. For example, you could have one form that data collectors use that create new entities that they first encounter. Then a second form can list all entities for supervisors to review and then show a list of statuses like "approved", "needs corrections", "talk to supervisor", "rejected", etc. and maybe a text field for questions. That form can update entities when submitted. It could update both a status column and the label (e.g. prepend 
when approved). A third form can be used to show a list of supervisor-processed entities with possible actions to take.
The forms I described would look quite similar to the community reporting forms from the Entities tutorial that we recently published but the statuses would have different meaning.
This requires more form design work than a built-in review workflow and may also require more training. The tradeoff is that it's completely flexible and can be adapted to your specific needs.
If you were thinking more about an offline, on-device review workflow, see this guide for ideas.