Raidlog.com

This feature/change is not released yet. Will be available June 1st. 2024

Effective management of Change Requests is crucial for addressing modifications in project scopes, timelines, or resources efficiently. This guide details each field within the Change Request module of RAIDLOG, helping you to understand and utilize them fully.

Each field in a Change Request is designed to capture specific information necessary for evaluating and processing the change. Here's what each field represents:

- Field Type: Short text
- Purpose: Provides a concise title or name for the Change Request.

- Field Type: Long form text
- Purpose: Offers a detailed explanation of what the change involves and why it is proposed.

- Field Type: Reference to user
- Purpose: Identifies the user responsible for managing and overseeing the Change Request.

- Field Type: Picklist
- Purpose: Indicates the current status of the Change Request (e.g., Pending, Approved, Rejected, Implemented).

- Field Type: Array
- Purpose: Allows for labeling or categorizing the Change Request for easier filtering and organization.

- Field Type: Short text
- Purpose: A unique identifier assigned to each Change Request for tracking purposes.

- Field Type: Date
- Purpose: The deadline by which the Change Request needs to be resolved or implemented.

- Field Type: Date
- Purpose: The date on which the Change Request was initially submitted.

- Field Type: Long form text
- Purpose: Explains the rationale behind the necessity for the change.

- Field Type: Financial field
- Purpose: Quantifies the financial impact of the Change Request.

- Field Type: Shortform text
- Purpose: Provides a brief description of how the budget will be affected.

- Field Type: Shortform text
- Purpose: Lists the project deliverables that will be impacted by the change.

- Field Type: Duration (Number+Hours, days, weeks)
- Purpose: Estimates the additional time required to implement the change.

- Field Type: Shortform text
- Purpose: Describes the effect of the change on project resources.

- Field Type: Duration (number + Days, Weeks, Months, Years)
- Purpose: Details the impact of the change on the project schedule.

- Field Type: Shortform text
- Purpose: Provides a summary of how the schedule will be affected.

- Field Type: Long form text
- Purpose: Elaborates on how the project scope will be altered by the change.

- Field Type: Link to related RAID items
- Purpose: Connects the Change Request to other relevant items or documents within RAIDLOG.

1. Name
 - Field Type: Short text
 - Purpose: Provides a concise title or name for the Change Request.
2. Description
 - Field Type: Long form text
 - Purpose: Offers a detailed explanation of what the change involves and why it is proposed.
3. Owner
 - Field Type: Reference to user
 - Purpose: Identifies the user responsible for managing and overseeing the Change Request.
4. State
 - Field Type: Picklist
 - Purpose: Indicates the current status of the Change Request (e.g., Pending, Approved, Rejected, Implemented).
5. Tag(s)
 - Field Type: Array
 - Purpose: Allows for labeling or categorizing the Change Request for easier filtering and organization.
6. Change Request #
 - Field Type: Short text
 - Purpose: A unique identifier assigned to each Change Request for tracking purposes.
7. Due Date
 - Field Type: Date
 - Purpose: The deadline by which the Change Request needs to be resolved or implemented.
8. Request Date
 - Field Type: Date
 - Purpose: The date on which the Change Request was initially submitted.
9. Reason for Change
 - Field Type: Long form text
 - Purpose: Explains the rationale behind the necessity for the change.
10. Budget Impact (cost)
 - Field Type: Financial field
 - Purpose: Quantifies the financial impact of the Change Request.
11. Budget Impact Description
 - Field Type: Shortform text
 - Purpose: Provides a brief description of how the budget will be affected.
12. Deliverables Impacted
 - Field Type: Shortform text
 - Purpose: Lists the project deliverables that will be impacted by the change.
13. Effort Impact (Duration)
 - Field Type: Duration (Number+Hours, days, weeks)
 - Purpose: Estimates the additional time required to implement the change.
14. Resource impact
 - Field Type: Shortform text
 - Purpose: Describes the effect of the change on project resources.
15. Schedule Impact (duration)
 - Field Type: Duration (number + Days, Weeks, Months, Years)
 - Purpose: Details the impact of the change on the project schedule.
16. Schedule Impact Description
 - Field Type: Shortform text
 - Purpose: Provides a summary of how the schedule will be affected.
17. Scope impact Description
 - Field Type: Long form text
 - Purpose: Elaborates on how the project scope will be altered by the change.
18. Related Items
 - Field Type: Link to related RAID items
 - Purpose: Connects the Change Request to other relevant items or documents within RAIDLOG.

Complete and Accurate Data: Ensure all fields are filled out comprehensively and accurately to provide a clear picture of the Change Request.

Consistency: Use standard conventions for names and descriptions to maintain consistency across all Change Requests.

Training: Regularly train team members on the importance and usage of each field to ensure everyone understands how to use the system effectively.

- Complete and Accurate Data: Ensure all fields are filled out comprehensively and accurately to provide a clear picture of the Change Request.
- Consistency: Use standard conventions for names and descriptions to maintain consistency across all Change Requests.
- Training: Regularly train team members on the importance and usage of each field to ensure everyone understands how to use the system effectively.

Fields Overview