Clear stages
Each case has a state, an owner and a next step.
All projects
WORKFLOWS / APPROVALS / AUTOMATION
Rewinit FLOW
Less retyping. Smoother operations.
We are building a tool for moving cases through successive stages of work. FLOW is intended to connect forms, tasks, decisions and notifications in a process the whole team can understand.
Delivery preparation
A plan that leads to deployment.Delivery preparation
As of 28 October 2026Scope defined. Next step: delivery.
We have prepared the project identity, first-version scope and acceptance criteria. The next stage is to build and verify the described journey with a partner. Timing will be agreed for the selected deployment.
- Prepared
- Scope and identity
- 01 / Next stage
- One form, three process stages, requester and operator roles, and decision history.
- 02 / Planned stage
- Partner pilot
Who are we building this for?
Service, administration and operations teams coordinating work through email and spreadsheets.
Where do we begin?
A case is waiting for a decision, but nobody knows who owns the next step. The first FLOW deployment will cover one process from submission to closure.
What will the first version include?
Process automation / Rewinit FLOW
Decisions in context
Approval, rejection and requests for more information will be recorded in the case history.
Supervised automation
Notifications and stage transitions with a way to pause a case for manual review.
Explore the planned journey.
Choose successive steps to see how the project’s first application is intended to work.
Interactive delivery plan
Rewinit FLOW / 01
Receive a case
Example scenario
Request TEST-28 includes a description and required fields.
Planned outcome
A form creates the case and assigns an owner.
An example scenario using prepared data. This presentation illustrates the planned process; it does not operate external systems.
A plan that leads to deployment.
Each stage follows verification of the previous outcome. The pilot scope will be agreed with a partner.
Prepared
Scope and identity
Project mark, visual direction, audience, first-deployment scope and acceptance criteria.
- 01
Next stage
First version
One form, three process stages, requester and operator roles, and decision history.
Acceptance criterionA case completes the full path; rejection and information requests work, and users only see cases they are authorised to access.
- 02
Planned stage
Partner pilot
Walk through real process variants with a partner’s team and check exceptions and cover arrangements.
- 03
Planned stage
Preparation for availability
Publish the agreed process, operating instructions and ownership of subsequent changes.
Development journal
Rewinit FLOW / DEVELOPMENT
First-deployment scope and identity prepared.
We have prepared the project mark and visual identity and defined its audience, first scenario, milestones and acceptance criteria. The delivery plan describes the next outcome to verify.
Project identity
A distinct mark and colour within the shared Rewinit system. The identity accompanies the project from planning to first-deployment materials.
Download SVG logoRewinit FLOW / PARTNERS
Build the first deployment with us.
We are seeking a partner to adapt the scope to a specific process and evaluate the outcome in a pilot.
Discuss FLOWA useful starting point
- One recurring process
- Roles and decision conditions
- Example cases and exceptions