The admin page is used to design and add the newly feature to the checkboard. Here we can define the “Workflow”. Here find the key fields available on this page:
    - Client Details
    - Client Group Details (based on language wise)
    - Available Roles
    - Available Users
    - Available Milestones

Any query related with the title can be raised via checkboard and the consolidated status/tracking/query about the title can be viewed and handled in one go within this system. Email configuration feature is part of this system for easy communication between the groups of project team (Publisher / Newgen team).
This system supports the publisher for easy allocation of files to multiple members (irrespective of any region / location).

This system is functioning without any FTP requirement. Source files and all the status of the required files can be sent within the system and until the project is getting distributed. The below listed files are used for File Transfer process
    - Input PDF
    - Output ePub file
    - JS file (For Navigation Synchronation)
    - Supporting screenshot files (Cover, TOC, Start Reading Location)

QA process is used to audit the output file against the input source file. The dynamic synchronization happens in the navigation element using the support of JS file.
The checkboard has an additional feature to recheck the Cover, TOC & SRL page exactly. The approved title moved to next stage “Ready for Distribution”.
In case of corrections noted, QA person add the error detail in the “Annotation” field and revert the title to the production team.(Standard corrections list is available for each move)
Features:
    - One click side by side view of input and output files
    - Dynamic checklist against section (front-matter, back-matter, etc.) and format
    - (EPUB, EPDF) specific
    - Automatic push to stores upon approval
Revises
We can able to view all the correction titles and correction details in the “Correction” stage. On receipt of the correction, we will amend the corrections and upload the revised file to the checkboard. Here, the output version one increased for every correction round. This update will support the end user to get the latest version output

If any new version of a file received, the old version file should be archived from checkboard on receipt of the client confirmation. There is a provision in the system to archive the file with reason.

1. Multiple users are accessing the system at a time
2. Starting from Login to final delivery of the product can be tracked in a single page.
3. Speedy Process
4. Less turnaround time
5. QA checking happens online view
6. Fully managed discussions between various users/teams
7. Configurable Workflows between various teams and functions
8. Document central to manage process related documents