QCI Accreditation & Certification Platform
Turning an RFP into a clear digital experience.
After studying the government RFP and understanding the accreditation workflow, I designed a 20-screen UX/UI Proof of Concept to demonstrate how organisations could navigate the accreditation and certification journey digitally.
- Role
- UX/UI Designer
- Project type
- Government RFP / Proof of Concept
- Platform
- Web application
- Deliverable
- 20-screen POC
- Purpose
- Technical evaluation
- Status
- Proposal / POC
Where the project started
Request for Proposal
High-level requirement themes only
The starting point was the government RFP.
I reviewed the requirements, scope, process expectations and functional needs described in the RFP to understand what the proposed solution needed to demonstrate.
From requirements to experience
The challenge was to move beyond simply interpreting requirements and demonstrate how those requirements could translate into a practical digital experience.
Organisation
Create and manage an organisation profile.
Application
Apply for an applicable accreditation/certification scheme.
Documentation
Provide business certificates and supporting documents.
Assessment
Plan and manage the assessment stage.
The opportunity
“How might we transform a complex accreditation process described in the RFP into a simple, guided digital journey?”
01
Make it clear
Help users understand where they are in the process.
02
Make it manageable
Break complex tasks into smaller steps.
03
Make it demonstrable
Create a realistic POC that clearly communicates the proposed solution during technical evaluation.
Mapping the accreditation journey
I converted the requirements from the RFP into an end-to-end user journey so that the POC could demonstrate how an organisation would move through the process.
- Create profile
- Add business information
- Upload documents
- Select scheme
- Apply
- Plan assessment
- Select slot
- Assessment
- Certification
My approach
01
Read
Review the RFP and understand the requirements.
02
Structure
Translate requirements into user journeys and information architecture.
03
Design
Create the key screens and interactions needed to demonstrate the proposed experience.
04
Prototype
Connect the screens into a 20-screen POC for technical evaluation.
Three challenges I focused on
Challenge 01
“How do we simplify a complex multi-step process?”
Challenge 02
“How do we make document and application requirements easy to understand?”
Challenge 03
“How do we demonstrate the complete proposed solution within a limited POC?”
From challenge to UX solution
Challenge 01 · Complex process
UX solution — Created a guided, stage-based journey.
Result — The process becomes easier to understand and navigate.
Challenge 02 · Document-heavy workflow
UX solution — Structured document submission using:
- ·Clear document categories
- ·Required indicators
- ·Upload states
- ·Validation
- ·Review before submission
Result — Users understand what information they need before completing the application.
Challenge 03 · Demonstrating the solution
UX solution — Designed a connected 20-screen POC instead of isolated UI screens.
Result — The evaluation team could understand the proposed product journey through a tangible experience.
From RFP to prototype
I translated the requirements into a 20-screen POC that demonstrated the proposed end-to-end experience.
01
Organisation setup
- Registration
- Organisation Profile
- Business Information
- Certificates
- Documents
02
Application
- Dashboard
- Scheme Selection
- Scheme Details
- Requirements
- Application
- Document Submission
- Review
- Submission
03
Assessment
- Assessment Planning
- Available Slots
- Slot Selection
- Confirmation
04
Certification
- Application Status
- Assessment Status
- Certification Status
Key screen story
Screen 01
Organisation Profile
Why — Establishes the organisation identity before beginning the accreditation journey.
Screen 02
Scheme Selection
Why — Helps the organisation identify the relevant accreditation/certification path.
Screen 03
Document Submission
Why — Creates a structured way to provide required business information and documentation.
Screen 04
Assessment Planning
Why — Moves assessment scheduling into the digital journey.
Screen 05
Application Status
Why — Provides visibility into progress and next steps.
One connected experience
Rather than designing individual screens, I focused on creating one connected journey.
Designed to demonstrate capability
The purpose of the POC was not to launch a production product. It was to demonstrate our understanding of the RFP and show how we could translate the requirements into a realistic digital solution.
RFP understanding
Demonstrated understanding of the business and process requirements.
UX thinking
Converted requirements into a structured user journey.
Product thinking
Showed how the workflow could work as a connected digital experience.
Visual execution
Presented the proposed solution through a polished 20-screen POC.
A POC built for a competitive evaluation
14
Competing companies
2
Companies progressed
20
Screens in our POC
The POC was part of our technical proposal for the government selection process. It helped us communicate our understanding of the RFP and demonstrate our proposed UX approach through a tangible product experience. The POC contributed to a strong technical proposal that progressed to the next stage of evaluation.
My contribution
I translated the RFP requirements into a structured UX journey and designed the 20-screen POC to communicate the proposed solution during the technical evaluation.
- RFP understanding
- Requirement mapping
- User journey
- Information architecture
- UX flow
- Wireframes
- UI design
- 20-screen POC
- Prototyping
- Proposal presentation support
Beyond visual design
01
Requirement-driven
The design was based on understanding the RFP rather than designing a generic accreditation product.
02
End-to-end
The POC demonstrated the complete journey from organisation setup through certification.
03
Easy to communicate
The visual prototype made the proposed solution easier for stakeholders and evaluators to understand.
Outcome
The RFP requirements were translated into a tangible digital experience.
A complete 20-screen accreditation journey was demonstrated through the POC.
The POC strengthened the technical proposal and helped communicate our UX and product capabilities during evaluation.
What I learned
An RFP is not just a list of requirements — it is an opportunity to understand the problem behind the requirements.
A strong POC should demonstrate thinking, not just visual execution.
When the product is complex, showing the complete journey can communicate value faster than explaining individual features.
From RFP to experience.
I transformed a complex government requirement into a clear, connected and visually demonstrable UX solution.
14
Competing companies
2
Progressed to the next stage