Use one project boundary consistently
For many teams, one project per brand is the simplest structure. Larger brand portfolios may use one project per campaign or therapy division, but the boundary should be documented and applied consistently. Avoid mixing unrelated brands just because they were imported on the same day.
Project names should be short and recognizable in the field. Include a controlled version or campaign identifier only when it helps users distinguish the active project; do not create a row of files called “final,” “latest” and “new final.”
Create the same category pattern
Representatives work faster when every project follows a familiar structure. A practical pattern is Core Story, Evidence, Dosage and Use, Safety, Questions and Optional Material. Some products will need different sections, but the main navigation logic can remain recognizable.
Place the most-used categories first. Do not hide required safety information in an obscure folder. Category names should describe what the representative will find, not internal design-team shorthand.
Design a short core sequence
The core category should contain the minimum approved pages for a complete, relevant discussion. Optional study details and secondary product information belong outside that path so a short doctor call does not feel rushed.
Test the sequence with role-play. If representatives repeatedly jump backward or leave the core route to find a necessary page, improve the structure through the appropriate review process.
Manage updates and archives
- Identify the approved master and its effective date.
- Prepare the new project or pages in a controlled test copy.
- Verify content and offline operation on the target tablet.
- Publish or distribute the replacement through the permitted channel.
- Remove the withdrawn version from active use.
- Retain any required archive outside the field presentation list.
The active workspace should show only what a representative can use now.
Back up without creating confusion
Export and restore are useful for device changes and team continuity, but uncontrolled backup files can reintroduce old content. Include enough naming information to identify the project and date, and store backups only in approved locations.
After restoring, open the project, confirm categories and compare several pages with the source. A successful file transfer does not by itself prove content integrity.
Example structure
| Project | Suggested categories | Field purpose |
|---|---|---|
| Brand A — Active | Core, Study, Use, Safety, FAQ | Primary doctor story |
| Brand B — Active | Core, Comparison, Use, Safety | Alternative product route |
| Division Training | Process, Practice, Device Help | Non-promotional field training |
Easy E-Detailing supports multiple projects, categories, page reordering and project export/restore. Explore the project screens, learn how the workflow operates or read the company standardization guide.
Add a monthly workspace review
Once a month, or at the interval set by the organization, review the active project list with the content register. Confirm that each project has an owner, an approved source, a current version and representatives who still need access. Remove duplicate test projects and move historical material out of the active field view through the permitted process.
Ask users which names or categories cause hesitation. A naming system that makes sense to the content team may not be obvious during a short appointment. Improve labels consistently across projects without changing approved claims.
Finish by opening a sample of projects offline and checking a restored backup in a safe test environment. This turns organization from a one-time cleanup into an operating habit.