We've used the RFP to highlight the project scope and have outlined this below.
Key Objective
The primary objective behind Content creation is to have world class product support content based on user personas. The content needs to be developed in English.
Key Deliverables
Content Creation in English for Phoenix Rise - School Management System
Key Expectations
| 1 |
Product support help guide content based on user personas. The content needs to be developed in English for Phoenix Rise consisting of 7 broad categories. |
| 2 |
Interactive user manual/help webpage that is elegant in design and responsive, supporting gifs and videos, other than content and images. Content should be structured well using the various instructional design principles and theories. |
| 3 |
Multiple reviews (minimum 2) within the company to ensure the quality is maintained across the deliverable |
| 4 |
Vendor should be able to complete the work as per mentioned timelines |
| 5 |
Utilize style manuals (e.g. Microsoft Style Manual) to ensure consistency in writing and formatting. The sentences should be clear, concise and to the point. |
Content Required
Supporting Notes:
Content for each question/feature will:
-
Have short explanation of the feature itself
-
Have Clear explanation on navigation in a bread crumb model
-
Have Detailed explanation of navigation from the home dashboard
-
Have explanation on what details/data/knowledge required as inputs for the feature
-
Have explanation of the workflow related to that feature (like what happens next)
-
Have explanation details on involved stake holders /user types with respect to that feature
-
Have explanation on role wise functionality
-
Have explanation on notifications to be received / sent
-
Have links to related sections or features
-
Have definitions for any domain specific or technical abbreviations used on screen
-
Have media and annotations (like screenshots, video capture of screens)
-
Need not have field wise explanation though desirable