No Workflow or Rejection Process

[bryan_mingJVKR8]

Forms currently do not have a proper workflow.
- No approve / reject buttons
- No clear rejection status or resubmission flow
- No way to skip steps or sections when they are not required
- No conditional logic based on responses
When a form is rejected, there is no clear action for the user. Site teams end up managing approvals and rework through email or messaging apps instead of inside ACC.

[buildintel]

Hi @bryan_mingJVKR8 

Sounds like you are in a typical friction "transformation period" in our idustry
I'll give some ideas per point.

- No approve / reject buttons -> Approval is the Closed Status on forms once the final user clicks on Submit. You are also welcome to add mandatory signatures at the end or per step.
Rejection can happen a few ways -> Deleting the previous party's signature and sending back to them, raising an issue and sending back to them. Closed forms can also be shared with commercial team for payments release.

- No clear rejection status or resubmission flow -> the reason for this is to give your teams flexibility to manage each case as needed. You can also add a Due Date. If you create a Planned VS Actual on Due Dates that gives you plenty power who is delaying and by how long.

- No way to skip steps or sections when they are not required -> it is not necessary to make all sections on forms mandatory. you can create optional sections that can be skipped without problem

- No conditional logic based on responses -> be careful, ACC cannot manage the form workflow for the site team. I would recommend splitting ownership amongst the project team so each member can monitor responses in good time

-When a form is rejected, there is no clear action for the user -> This sounds like bad communication from the person who rejected. He needs to either comment or raise an issue and log exactly what the problem is, and what their expectations are for rectification.

-Site teams end up managing approvals and rework through email or messaging apps instead of inside ACC -> this behavior happens when the project team doesnt know how to use ACC and when project leadership doesnt have expectations for ACC to be used. Emails and messaging apps are a good way to create more misunderstandings going forward. I'd highly recomment persistence to use ACC correctly otherwise no point making the investment on ACC

Happy to help if you have more points to discuss
Kind regards
BI