Configure Quality Settings
Time: ~10 minutes Level: Intermediate Applies to: Pro · Enterprise
What You Will Learn
By the end of this tutorial, you will be able to:
- Adjust individual check thresholds to match your project standards
- Configure weightage by WBS or activity code
- Set up Primavera attribute mappings
- Save and apply custom quality configurations
Prerequisites
- A Kazinex account on the Pro or Enterprise tier
- A schedule loaded with a quality score already calculated (see Achieve a 90+ Quality Score)
Step 1 — Open Quality Settings
Access the settings panel from the Quality tab.
- Open the Quality tab.
- Click the gear icon in the Quality toolbar.
- The Quality Settings panel opens.
What you should see: A settings panel with sections for Thresholds, Weightage Configuration, and Primavera Attributes.
Step 2 — Review Default Thresholds
Understand the starting values before making changes.
- Scroll through the Thresholds section.
- Note the default values for key checks:
- High Duration: 44 working days
- High Float: 44 working days
- Negative Float threshold: 0 days
- Zero Duration awareness: enabled
- Each threshold has a description explaining what it controls.
What you should see: A list of threshold fields with numeric inputs and descriptions. Default values follow industry best practice based on DCMA 14-Point Assessment guidelines.
Step 3 — Adjust a Threshold
Change a threshold to match your project requirements.
- Find the High Duration threshold.
- Change the value from 44 days to 60 days.
- Find the High Float threshold.
- Change it from 44 days to 50 days.
- These changes mean activities up to 60 days are acceptable and float up to 50 days does not trigger a warning.
What you should see: The input fields accept your new values. A preview or note may indicate how many activities would be affected by the change.
Step 4 — Configure Weightage by WBS
Assign different scoring weights to different parts of the WBS.
- Open the Weightage Configuration section.
- Select WBS as the grouping method.
- A list of WBS Level 2 (or Level 3) nodes appears.
- Assign a higher weight to critical sections (for example, "Commissioning" gets 30% weight).
- Assign lower weights to less critical sections (for example, "Temporary Works" gets 5% weight).
- Ensure all weights sum to 100%.
What you should see: A table of WBS nodes with weight percentage inputs. The quality engine will score each WBS section separately and combine them using these weights.
Step 5 — Configure Weightage by Activity Code (Alternative)
Use activity codes instead of WBS for weightage.
- In the Weightage Configuration section, switch to Activity Code grouping.
- Select an activity code type (for example, "Phase").
- Assign weights to each code value: "Design" 20%, "Construction" 60%, "Commissioning" 20%.
- This approach scores each phase independently.
What you should see: A dropdown for the code type and weight fields for each code value. Choose either WBS or Activity Code — not both simultaneously.
Step 6 — Set Up Primavera Attribute Mappings
Configure how Kazinex interprets Primavera-specific attributes.
- Open the Primavera Attributes section.
- Map calendar types — choose which Primavera calendar format your schedule uses.
- Map percent complete types — tell the engine which percent complete field to prioritise.
- Map duration types — specify how durations are calculated in your P6 project.
What you should see: Dropdown fields for each Primavera attribute mapping. These settings help the quality engine correctly interpret P6-specific data.
Step 7 — Save Your Configuration
Persist your custom settings.
- Review all changes in the settings panel.
- Click Save at the bottom of the panel.
- The quality engine recalculates the score using your new configuration.
What you should see: A brief loading indicator while the score recalculates. The Quality dashboard updates to reflect the new thresholds and weightage.
Step 8 — Verify the Updated Scores
Confirm that your settings are applied correctly.
- Close the Settings panel and return to the Quality dashboard.
- Check the overall score — it may differ from before depending on your threshold changes.
- Expand individual categories to verify that checks use your new thresholds.
- If using WBS or activity code weightage, note that the category scores may be weighted differently now.
What you should see: Quality scores that reflect your custom configuration. WBS sections with higher weights have a proportionally larger impact on the overall score.
What's Next?
- Analyse Resource Loading — examine resource allocation across your schedule
- Master the AI Copilot — use natural language to query quality results
- Quality Settings Reference — full documentation on all settings
Troubleshooting
| Issue | Solution |
|---|---|
| Save button is greyed out | Ensure your weights sum to 100%. The save button disables when validation fails. |
| Score did not change after saving | Your threshold changes may not affect the current schedule. Only checks with activities near the threshold boundary will shift. |
| Weightage section is empty | Ensure your schedule has a WBS structure or activity codes assigned. Weightage requires grouping data to work with. |
| Primavera attributes not available | These settings only apply to schedules imported from P6. Other formats may not have these attributes. |