Reconstructed professional artifact

Role-Based Deliverable Workflow Guide

A public-safe reconstruction showing how a complex deliverable process can be organized around the user’s next action, required inputs, authority, and handoff condition.

5 stagesPrepare through publish

4 rolesContributor reviewer approver document control

Role-basedActions organized around responsibility

SyntheticNo employer or client records

Representative workflowPublic reconstruction

Stage	Primary role	Required action	Control / check	Exit condition
1. Prepare	Contributor	Assemble required files, confirm naming, and enter required metadata.	Completeness, naming, revision, source record, and required-field checks.	Package is complete enough to route.
2. Submit	Contributor + Document Control	Submit the package through the approved intake path.	Receipt logged; role and destination confirmed; access blockers recorded.	Package is accepted into the review workflow.
3. Review	Reviewer	Review against requirements and record comments or disposition.	Reviewer assignment, revision history, comment resolution, and traceability.	Review outcome is complete and ready for approval.
4. Approve	Approver	Approve, reject, or return the reviewed package.	Authority verified; unresolved issues visible; final disposition recorded.	Approved content is authorized for publication.
5. Publish	Document Control	Publish the approved record and preserve history.	Final status, metadata, source preservation, superseded version, and audit history.	Approved record is available from the controlled location.

How the guide is designed

Organize by role and action rather than software menus.
State what information is required before the user starts.
Separate review authority from approval and publication authority.
Show the exact condition that starts the next stage.
Treat permissions and identity failures as workflow blockers with an owner and next action.

Download responsibility matrix Download permissions register Return to case study