Internal teams
The same record for ICE's own decisions, commitments and handoffs.
Who acted, under whose authority, on which version, what was decided or promised, who took responsibility, what happened, and what changed later. One foundation, a profile for each kind of work.
Take the two-minute sales tourAutomatic capture, exception review
Set up once per workflowSource mappings, roles, policy references and the population are configured when a workflow is accepted. After that, versions, authority and later events bind themselves.
No second formStaff keep working in their own tools. Evidence opens from a small panel or a link in the workflow they already use.
Only what needs a personPeople come back for an approval the business already requires, a material exception or a review request. Nothing else.
Forty proposed workflows
These come from what ICE said it wants covered, including sales. They are proposals to check with each owner, not a list of ICE's systems or reporting lines.
Loading...
To add a team or process: give it a stable ID, then declare its actor, authority, input and version, the decision or commitment, the owner who receives it, the acknowledgement, the effect and later changes, plus who may see it and the test that proves it. No new primitive is needed for each department.