Getting Started

Implementation Overview

Ordus implementation follows a structured approach designed to minimize disruption while maximizing value from day one. Implementation timelines vary based on organizational size, operational complexity, documentation readiness, and integration requirements.

Typical implementation ranges from 4-16 weeks from contract signature to full operational deployment. Organizations with 30-100 staff and straightforward operations typically complete implementation in 6-8 weeks. Organizations with 150+ staff, multi-state operations, or complex integration requirements may require 10-16 weeks or longer depending on specific circumstances.

Implementation timeline depends heavily on:

• Organizational size and number of operational sites

• Service complexity and regulatory frameworks

• Current documentation state and completeness

• Integration requirements with existing systems

• Internal resource availability and change management capacity

• Customization needs specific to operational model

What You Need

Prerequisites

Organisational Readiness:

• Executive sponsorship and commitment

• Designated implementation contact person

• Access to current policy documentation

• Staff communication plan

• Change management strategy

Technical Requirements:

• Internet connectivity at all operational sites

• Staff access to mobile phones or computers

• Email addresses for all staff requiring Ordus access

• (Optional) Integration access to existing systems (rostering, incident management)

Documentation Inventory:

• Current policies and procedures (PDF, Word, or scanned documents)

• Site-specific protocols and operational guides

• Incident reporting procedures

• Emergency contact lists

• Organisational charts and role definitions

• Participant care plan templates (if applicable)

No Technical Infrastructure Required

Ordus operates via Ordus chat interface or WhatsApp. No servers to install. No hardware to purchase. No IT department required. Staff use existing mobile phones or computers.

Implementation Timeline

The following timeline represents a standard implementation for medium-sized organizations (50-100 staff, 3-5 sites). Your specific timeline will be determined during the discovery session based on organizational size, complexity, and requirements.

Timeline variations by organization profile:

• Medium organizations (30-100 staff): 6-8 weeks typical

• Large organizations (100-250 staff): 8-12 weeks typical

• Enterprise organizations (250+ staff): 10-16+ weeks depending on complexity

• Multi-state operations: Add 2-4 weeks for jurisdictional configuration

• Complex integrations: Add 2-6 weeks depending on systems and requirements

All timelines are estimates and subject to adjustment based on discovery findings and organizational factors.

Week 1-2: Foundation & Setup

Discovery Session (2 hours):

• Understand your operational model, service types, sites

• Map current pain points and priority use cases

• Define success metrics and implementation goals

• Identify key stakeholders and implementation team

Technical Setup:

• Ordus creates your organisation account

• Manager dashboard access provisioned

• WhatsApp Business API integration configured

• Staff registration process designed

Documentation Collection:

• You provide current policies via secure upload portal

• Ordus processes documents, creates knowledge base

• Initial policy relationships mapped

• Site-specific protocols configured

Week 3-4: Knowledge Base Development

Policy Processing:

• Complete document extraction and structuring

• Relationship mapping across all policies

• Metadata tagging (roles, sites, topics)

• Version control system configured

Testing & Validation:

• Manager access to dashboard for review

• Sample question testing with your team

• Policy accuracy verification

• Confidence scoring calibration

Customisation:

• Incident detection rules aligned to your terminology

• Severity classification thresholds set

• Manager routing logic configured

• Site-specific emergency contacts loaded

Week 5-6: Pilot Launch

Pilot Group Selection:

• Typically 5-15 staff across 1-2 sites

• Mix of roles: support workers, team leaders, manager

• Include relief/casual staff if possible

• Both experienced and newer staff

Staff Registration:

• Pilot group receives registration instructions via email

• 5-minute registration process per staff member

• WhatsApp verification completed

• Initial orientation message sent

Pilot Period (2 weeks):

• Staff ask questions naturally via Ordus chat interface or WhatsApp

• Manager monitors dashboard daily

• Incident detection tested with real scenarios

• Feedback collected from pilot participants

Pilot Review:

• Success metrics reviewed: question volume, response accuracy, staff adoption

• Policy gaps identified and addressed

• Incident routing validated

• Refinements made based on feedback

Week 7-8: Full Deployment

All-Staff Rollout:

• Remaining staff registered in phases (site-by-site or role-by-role)

• Communication campaign: email, team meetings, posters

• Manager availability for questions during first week

• Gradual increase in question volume

Training & Support:

• Optional staff training sessions (15-30 minutes per group)

• Manager dashboard training (1 hour)

• Documentation provided: quick start guides, FAQs

• Live support available during business hours

Go-Live Monitoring:

• Daily check-ins with implementation contact

• Real-time monitoring of question volume and response accuracy

• Incident detection validation

• Early issue resolution

Week 8+: Optimisation

Continuous Improvement:

• Weekly dashboard review with management

• Policy refinements based on question patterns

• Training gap alerts acted upon

• Incident pattern analysis for quality improvement

Feature Activation:

• Compliance monitoring enabled (if not activated from start)

• Advanced dashboard features unlocked

• Integration with existing systems (if planned)

• Additional site rollout (for staged implementations)

Implementation Approaches

Implementation approach is determined collaboratively during discovery based on organizational priorities, timeline constraints, and operational requirements. The following approaches represent common patterns but may be customized to your specific needs.

Standard Implementation (Most Common)

Timeline: 6-8 weeks (subject to organizational complexity)
Best for: Medium to large organisations (30-200 staff), single-state operations, straightforward service delivery

Sequence:

1. Foundation & Setup (Week 1-2)

2. Knowledge Base Development (Week 3-4)

3. Pilot Launch (Week 5-6)

4. Full Deployment (Week 7-8)

Note: Timeline may extend based on documentation completeness, integration requirements, or organizational change management needs.

Rapid Implementation

Timeline: 3-4 weeks (subject to feasibility assessment)
Best for: Urgent operational needs, high manager capacity pressure, imminent Commission assessments

Sequence:

1. Compressed discovery and setup (Week 1)

2. Accelerated policy processing with priority documents first (Week 2)

3. Brief pilot with manager group only (Week 3)

4. Immediate full deployment (Week 4)

Trade-offs: Less pilot testing, more refinement post-launch, higher implementation contact time commitment, increased organizational change burden

Feasibility depends on: Documentation readiness, internal resource availability, organizational change capacity

Staged Implementation

Timeline: 10-16 weeks (may extend based on organizational scope)
Best for: Large multi-site organisations (150+ staff), multi-state operations, complex service delivery across multiple frameworks

Sequence:

1. Foundation & Setup (Week 1-2)

2. Knowledge Base Development (Week 3-5)

3. Pilot Launch Site 1 (Week 6-7)

4. Deployment Sites 2-3 (Week 8-10)

5. Deployment Sites 4-6 (Week 11-13)

6. Final sites and optimisation (Week 14-16)

Benefits: Lower organisational change burden, regional customisation, learnings from early sites applied to later sites

Timeline may extend for: Enterprise organizations with 15+ sites, multi-jurisdictional operations requiring state-specific configuration, complex integration requirements

Staff Registration Process

How Staff Register (5 Minutes)

1. Receive registration email from your organisation containing unique registration link

2. Click link → Opens Ordus registration page

3. Enter details: Full name, role, primary site, mobile number

4. Verify WhatsApp: Receive verification code via WhatsApp, enter code

5. Confirm registration: Receive welcome message with quick start guide

Complete. Staff can immediately ask Ordus questions via WhatsApp.

Manager Dashboard Access

Managers receive separate dashboard login credentials:

1. Email invitation with dashboard URL and temporary password

2. Initial login and password reset

3. Dashboard orientation (self-guided or scheduled training)

4. Access to all dashboard features: question analytics, incident overview, compliance monitoring

Common Implementation Questions

How much time does implementation require from our team?

Time requirements vary based on organizational size and complexity. The following estimates represent typical medium-sized organizations:

Your implementation contact: 3-5 hours per week during foundation and knowledge base development, 1-2 hours per week during deployment and optimisation.

Managers: 1 hour for dashboard training, 30 minutes daily during pilot, 15 minutes daily during full deployment (reviewing dashboard).

Staff: 5 minutes for registration, 15-30 minutes optional training session.

Enterprise organizations and complex implementations may require additional internal resource allocation. Specific time commitments will be outlined during discovery.

What if our policies aren't documented?

Ordus can work with partial documentation and build knowledge base iteratively. Start with critical policies (incident reporting, medication administration, emergency procedures). Add remaining documentation progressively.

Alternatively, Ordus can extract operational knowledge from manager interviews and create initial policy documentation as part of implementation.

Documentation development services available at additional cost for organizations requiring comprehensive policy creation.

Can we integrate Ordus with our existing systems?

Yes. Common integrations include:

• Rostering systems: Staff site assignments, shift schedules

• Incident management platforms: Automatic incident report creation

• Care management systems: Participant care plan access

• HRIS: Staff roles and permissions

Integration requirements and feasibility assessed during discovery session.

Integration complexity varies significantly based on existing system architecture, API availability, and data structure. Custom integration projects priced separately based on technical requirements and estimated development effort.

What happens to our data if we stop using Ordus?

Complete data export provided in standard formats (CSV, PDF). Includes:

• All policies and documentation

• Complete interaction history

• Incident reports

• Compliance audit trail

• Dashboard analytics

Data retained for 90 days post-cancellation for export, then permanently deleted.

Data export format and completeness guaranteed per contract terms. Organizations with custom data structures or integration requirements should discuss export specifications during contract negotiation.

How do we measure success?

Key metrics tracked from day one:

• Manager time savings: Reduction in questions interrupting managers

• Response accuracy: Confidence scores on policy answers

• Incident response time: Detection to manager notification

• Staff adoption: Percentage of staff asking questions

• Training gap detection: Proactive training delivered before incidents

• Compliance readiness: Audit trail completeness

Dashboard provides real-time visibility into all metrics.

Success metrics should be defined collaboratively during discovery based on organizational priorities and baseline operational data. ROI measurement framework provided as part of implementation for organizations requiring board-level reporting.

Getting Help

During Implementation

Your Implementation Manager:

• Assigned from contract signature through go-live

• Weekly check-in calls during active implementation

• Email and phone support during business hours (AEST)

• Available for on-site visits if required (additional cost for regional/interstate)

Technical Support:

• Live chat support via dashboard during business hours

• Email support with 4-hour response time

• Phone support for urgent technical issues

Post-Implementation

Ongoing Support:

• Help documentation available 24/7 via dashboard

• Email support for operational questions

• Monthly check-in calls (first 3 months)

• Quarterly business reviews

Account Management:

• Dedicated account manager assigned

• Proactive feature updates and optimisation recommendations

• Access to product roadmap and beta features

• Annual strategic planning session

Next Steps

Ready to implement Ordus?

1. Contact our team to schedule discovery session

2. Review implementation timeline and select approach

3. Sign contract and begin foundation setup

4. Complete implementation and activate your organisation's brain

Questions before starting?

• Review Use Cases for real-world implementation examples

• Read Security & Compliance for data protection details

• Check FAQs for common pre-implementation questions

• Contact us to discuss your specific requirements