A common problem that we come across with most authorities utilising the govService platform is a lack of standardisation of naming conventions, reusable forms, integrations and more.
Low-code platforms such as govService do not offer much in the way of standardisation out of the box: you need to get creative in the way that you want your team to use the platform and which areas are best to standardise.
One of the packages we offer is an end-to-end implementation of standards using the JIRA Confluence cloud software package. The software is free for up to 10 users and is the perfect way to start out with documentation and standardisation of the platform.
Some key areas you should be looking to standardise are:
- Token naming (such as using camel case across all tokens)
- Input fields for repeated use, utilising govService’s inbuilt subform packages (such as address entry and customer detail entry)
- Documentation (using a standard documentation format that stores key information about a process, development status, changelog and more)
- Guides (such as a publishing checklist or go live checklist)
- Styling guidelines (such as placement of headers and information alerts)
- Integrations (for repeatable back office integrations such as address lookups)
We’ve found that using a consistent approach using the above areas of standardisation help to achieve a quicker implementation of the platform and make it easier for new team members to work on pre-existing and new processes.