Tour planning
Build monthly tour plans with one or more cities per day, work/off days and planned doctor or medical-store visits. Managers can review accessible staff plans.
CRIDOS PHARMA / FIELD-FORCE MANAGEMENT
From tour planning and customer visits to team reviews and approvals. A shared workspace for the daily work of pharma teams.
START WITH THE DAILY WORKFLOW
Show the product through the tasks your team already knows. These screenshots come from the actual application.
Actual application screens rendered with fictional names and records for this demonstration.
CHOOSE YOUR DEMO PATH
Plan the day, find customer context, record work and review the result.
Connect the team’s planned work, recorded activity and decisions.
Maintain structure, access and the settings your team relies on.
THE COMPLETE CAPABILITY GUIDE
Daily field work comes first, followed by customer relationships, team review and company controls.
Build monthly tour plans with one or more cities per day, work/off days and planned doctor or medical-store visits. Managers can review accessible staff plans.
Add doctors and stores to today’s plan from the dashboard and see whether planned calls are completed, ongoing or aborted.
When enabled by management, working-city rules and city-change requests support controlled changes to the day’s tour plan. Planner cutoff settings support next-month planning.
Start and end field, drive, camp, meeting or office work. Record start/end coordinates, durations and activity information. Driving captures vehicle and odometer readings.
Select the target address, start a visit during a work session and record location. Complete or abort the visit; capture notes, participants and products discussed.
Configure visit-radius enforcement and distance. Office work uses the configured office radius. Recorded work-log points can be reviewed on a map.
Record non-visit work through sessions. Medical camps can reference a doctor; office sessions support individual task notes.
Review the timeline of sessions, visits, camps, meetings, office tasks and approved leave. Accessible staff views support manager review.
Maintain names, contact details, specialities, birthdays, approval state, staff assignments and medical-store associations.
Maintain store records, assigned staff, associated doctors and visit history, with approval where required.
Keep multiple addresses for supported records, with city/state references and coordinates for location-based visit rules.
Keep contextual remarks and past visits with the doctor or medical-store record. Review visit participants and products discussed.
Doctor lists and pickers follow assignments to the caller and accessible staff. Broader visibility requires explicit permission.
Use authorized record approval, permission-controlled deletion and two-level deletion requests with reasons and decision history.
Review visit coverage by city, current open visits, pending approval categories, doctor birthdays, today’s plan and upcoming tour plans.
Review visit statuses and doctor coverage over selected periods. Staff monthly summaries bring together visits, tracked work, drive distance and leave.
Review vehicle distance/time and leave trends with available date and staff filters.
Download supported master lists, tour plans and reports as XLSX files. Billing invoices can be downloaded as PDFs.
Create self or permitted staff requests, review through first/final approval, reject with reasons, cancel where permitted, and configure auto-cancellation.
In-app notifications, browser push where supported and enabled, and email on supported workflow events. Company email notifications are configurable.
Authorized users can view staff tracker coordinates. These are recorded locations, rather than continuous live GPS tracking.
Manage users, one role per user, permissions, manager–staff relationships and reporting exclusions.
Maintain headquarters, products and units, specialities and vehicles. Use the available geographic catalogue for addresses and tour plans.
Configure visit rules, concurrent visits, office radius, planner cutoff, leave auto-cancellation, half-day leave and notification preferences where permitted.
Company-specific app identity and workspace routing, tenant-scoped records and role-based access keep each customer’s operations separate.
Profile/password changes, password recovery, email verification, active-session controls, appearance preferences and a local device PIN lock.
View manually managed invoice and payment history, transfer instructions and invoice PDFs. Platform management handles contracts, invoicing and payment recording.
Daily, travel and other allowances, kilometres and receipt photos. Monthly submissions support configured one- or two-stage approvals, rejection, resubmission, review conversations and exports.
Standalone doctor or medical-store orders with products, quantities and units. Daily/team views, customer order history and item-level XLSX export. Corrections are creator-only on the same day.
No matching capabilities. Try another term.
WHAT TO EXPECT
Available todayResponsive web application with company workspaces, field operations, reporting and administration.
Optional by companyExpenses and Orders require platform enablement and user permissions. Orders record demand; they do not manage fulfilment or approval.
Location captured at eventsCoordinates support visit rules, work-session records and work-log maps. Continuous live tracking is not part of this scope.
Commercial discussionPricing and rollout terms are agreed with Cridos. Current billing is manually managed; native mobile apps are future work.
COMMON QUESTIONS
Yes. The current product is a responsive web application with mobile-focused screens. A native mobile application is not currently included.
Visibility depends on permissions, staff hierarchy, doctor assignments and headquarters context. Access can be broader where explicit permissions allow it.
Device coordinates are recorded when starting a visit. When visit-radius enforcement is enabled, the server rejects a start outside the configured distance from the selected address. The setting is configurable by company.
Both are optional modules controlled by platform management. Their interfaces and APIs require company enablement and the appropriate permissions.
The implementation supports company branding and workspace routing, while each company’s operational records and access are scoped to its workspace.
LET’S TALK ABOUT YOUR TEAM
Walk through the product with your team structure, field workflows and operating requirements in mind.
Book a product demo