Collect startup information without confusing saved with approved.
Once a customer or supplier is ready to begin working with you, you may need more information than at first contact. ImbaHub can develop a bounded workflow that supports steps, saving and returning before a specific version goes to the designated reviewer.
- Draft
The participant continues working on information.
- Submitted
A specific version sits with the designated receiver.
- Reviewed
The owner has made the agreed decision.
Saving something is not approval from the organization.
A draft is saved but a required step is missing. Should the workflow say complete?
No. Confirm saving and show remaining steps; submission and review have their own states.
Define what the next work stage actually needs
Choose one onboarding type and a concrete receiving decision. A fictional collaboration might need contact roles, approved content sources and practical startup choices. Do not request passwords or sensitive information merely because a workflow can collect it.
Separate this from a first inquiry form and the handover of a finished website. Decide what is required now, what is optional and who reviews it. Submission does not automatically imply activation or acceptance of a contract.
Make steps and saving status understandable
Group questions by task and show the person's current position. A draft can be incomplete if the agreed model allows it. A saved indicator must not imply that all details are checked or that the receiver already has a final version.
Resuming needs bounded access and a defined storage model. A link opening private material is an access route, rather than an innocent navigation address. Lifespan, renewed verification and any login are decided for the actual solution.
| State | What it means | What it does not mean |
|---|---|---|
| Draft | Permitted information is saved under the model | Everything is complete or submitted |
| Ready to submit | Required steps meet current conditions | The receiver approved the content |
| Submitted version | A specific version enters the agreed review route | The relationship is automatically activated |
| More information needed | Reviewer identifies what is missing | An unexplained general error |
| Reviewed | The designated owner made the agreed decision | Every other business decision is complete |
Deliver the right version to an accountable owner
Submission should identify the version the receiver reviews. Later draft edits must not silently replace that evidence. Decide who may request additional information and how the user understands what needs correction.
A notification and an actual review record are separate outcomes. The test follows the marked version to the agreed receiving view. External business systems, document uploads and further automation are assessed separately where needed.
Deliver a testable first onboarding route
An initial scope can cover one participant type, a few steps and a named receiver. Test incomplete drafts, save failures, resuming, submission and requests for corrections. Keyboard, mobile and understandable field errors belong in the defined route.
The handover describes steps, access, saving rules, versions and ownership of outstanding work. Scope and pricing follow review; additional integrations and ongoing operations are specified separately. We do not present this as existing standard support in an Imba product.
Sources and further reading
Questions, answered
Is a saved draft the same as a submission?
No. Define and show the difference so the person knows when a specific version actually goes for review.
Can all suppliers use the same workflow?
Only when information, access and review decisions fit. Different onboarding types may need different conditions.