Purpose and applicability
Can the joy and love dimensions form a reflective-reflective Affective Commitment construct, and how do organizational prestige and identification predict it?
No completed-result prerequisite is required for the first run.
Do not use it merely because it is available
Use Higher-order models only when its estimand, data roles and assumptions answer the stated research question. Choose a related estimator or diagnostic when the intended outcome is not among the documented outputs below.
Study preparation
- Teaching data
- organizational-identification-model-comparison.csv
- Observations
- 305
- Study type
- Deterministic synthetic teaching study
- Calculate route
- Calculate → PLS-SEM Algorithm after authoring the higher-order construct
Open the data dictionary and variable-role reference
Model
Organizational Prestige (org_pre1–org_pre8), Organizational Identification (org_ident1–org_ident6), Affective Commitment (Joy) (ac_joy1–ac_joy4), and Affective Commitment (Love) (ac_love1–ac_love3); the last two form the reflective-reflective Affective Commitment higher-order construct
Organizational Prestige → Organizational Identification; Organizational Prestige → Affective Commitment; Organizational Identification → Affective Commitment
Exact workflow
Download organizational-identification-model-comparison.csv and the prepared organizational-identification-higher-order.qpls project. Keep both files in a writable study folder.
Start QuickPLS, choose Open Project, and open the prepared project. Its saved model is already arranged and fitted.
Open Data and confirm that the study contains 305 observations. Return to the model or calculation workspace.
Confirm the saved model specification: Organizational Prestige (org_pre1–org_pre8), Organizational Identification (org_ident1–org_ident6), Affective Commitment (Joy) (ac_joy1–ac_joy4), and Affective Commitment (Love) (ac_love1–ac_love3); the last two form the reflective-reflective Affective Commitment higher-order construct. Structural specification: Organizational Prestige → Organizational Identification; Organizational Prestige → Affective Commitment; Organizational Identification → Affective Commitment.
Confirm that construct labels, indicators, and arrows are readable. The supplied project is saved after Arrange and Fit; do not rearrange it before the tutorial run.
Choose Calculate, then use Calculate → PLS-SEM Algorithm after authoring the higher-order construct.
Review the essential settings listed below. Open Advanced settings only when the design requires a non-default option.
Resolve actionable blockers, review applicability warnings, and leave Open Results when finished selected.
Choose Start calculation. Wait for Completed, then confirm that Results opens for this method.
Inspect the named outputs below in order. Use Save Report, table Copy, or Export as required, then save and reopen the project to confirm the result remains available.
Essential and advanced settings
- Confirm the reflective-reflective disjoint two-stage HOC definition
- Run the PLS-SEM Algorithm point estimate; use the inference setting only when bootstrap inference is required
Keep other advanced controls at their documented defaults unless the study design requires a justified change. Record every non-default value in the research log.
Results to inspect
- Stage-one and stage-two receipts
- Higher-order weights/loadings
- Structural paths
- Bootstrap inference when requested
Interpretation guidance
For Higher-order models, interpret the listed outputs together with the prerequisite result, the selected settings, model assumptions and data quality. The supplied values are instructional; they are not validation against an external paper or another software package.
Reporting guidance
Report the QuickPLS version, Higher-order models route, sample size, model or variable roles, preprocessing, essential settings, non-default advanced settings, and the named primary outputs. Retain the project, data checksum and exported table used in the manuscript.
Common mistakes and recovery
- Running the method before completing its prerequisite calculation.
- Changing the data, model or variable roles after the prerequisite result was saved.
- Treating an unavailable or not-applicable value as zero.
- Reporting an estimate without its method-appropriate uncertainty or diagnostic context.
Screen-by-screen evidence
Images shown here are mapped to this tutorial’s required installed-application evidence. Missing captures are labelled explicitly and are not replaced with generic screenshots.