Test KanGate on one active project and one workflow that matters. In 90 days, your team will see what holds work up, what resolves it, and whether the results justify a wider deployment.
For contractors testing day-to-day delivery and owners, EPCs, operators, or enterprise teams evaluating oversight. Start with one organization; agree the scope, participants, outputs, and price before kickoff.
90-DAY PILOTMISSION 90
CURRENT OBJECTIVEDoes KanGate earn its place?Real records. Visible findings.
DAYS 1–10Scope agreed
DAY 30Workflow configured
DAY 60Evidence under test
DAY 90Deploy / Refine / Stop
The working plan
Five phases. A decision at each step.
Select a phase to see the work and its outputs. Your team provides project records and qualified reviewers; KanGate configures the workflow and tests it against the agreed criteria.
PHASE 01 · DEFINE
Agree the scope before configuration.
Choose the project, workflow, reviewers, and records. Agree what success will look like and record the starting condition.
Pilot Workflow Charter
Project and package boundary
Authority Matrix
Baseline and acceptance criteria
BOUNDARY CONTROLMISSION / 01
CONTROL QUESTIONWhat will this pilot prove?
ProjectWorkflowReviewersEvidenceOutputsCriteria
Representative worked example
Six open conditions. What changes when one closes?
Step through a sample hydro package. Each accepted record resolves a specific condition. Contractors see the closure path; enterprise reviewers can inspect why the package is eligible for review.
Illustrative sequence, not a customer result. Acceptances are simulated; these controls do not approve work.
HYDRO-PKG-022REPRESENTATIVE MODEL
PACKAGE STATEBLOCKED6 OPEN RELEASE BLOCKERS
Repair NDEMISSING
NDE identity mappingUNRESOLVED
MTR linkageMISSING
Calibration evidenceUNACCEPTED
Final redlineABSENT
Qualification reviewPENDING
Select “Next accepted record” to inspect the first change.
Verified evidenceVerified eligibilityHuman authorization still required
Six blockers remain open.
Operating discipline
What each team brings to the pilot.
Before kickoff, name the people supplying records, resolving questions, and reviewing findings. Formal approvals stay with the designated project authorities.
01
KanGate
Configures and tests the selected workflow, supports the working group, produces the agreed outputs, and reports the findings.
Workflow and evidence model
Identity and relationship configuration
Blocker and readiness logic
Support, outputs, and reporting
02
Your organization
Supplies project records, current requirements, and qualified reviewers, whether the pilot is led by a contractor or an enterprise team.
Evidence and authoritative sources
Technical and contractual requirements
Timely answers and dispositions
Formal acceptance or rejection
03
Together
Agree the working boundary, review cadence, success criteria, exception handling, and final acceptance.
Boundary and success criteria
Authority checkpoints
Exception handling
Deploy / Refine / Stop decision
Day-90 delivery framework
Six controlled packages. Sixteen defined components.
06 delivery packages16 defined components
These six packages belong to one pilot. The agreement names the evidence classes, output formats, and acceptance criteria. Open a package to inspect its components.
PACKAGE 01 · 2 COMPONENTSPilot Definition PackageAgrees the scope and decision rights.
01
Pilot Workflow CharterRecords the workflow, scope, evidence classes, assumptions, exclusions, objectives, and acceptance criteria.
02
Authority MatrixNames reviewers, decision rights, and release authorities.
PACKAGE 02 · 4 COMPONENTSConfigured KanGate ModelSets up the selected workflow.
03
Configured Evidence ModelDefines required evidence and the conditions for each status.
04
Canonical Identity ModelMatches records to the project objects in scope.
05
Relationship ModelLinks evidence, requirements, project objects, and release decisions.
06
Configured Evidence IntakeHandles the evidence classes named in the agreement.
PACKAGE 03 · 3 COMPONENTSValidation and Control OperationChecks records and exposes open conditions.
07
Preflight and Validation ResultsRecords the checks applied and their results.
08
Blocker LedgerLists missing, conflicting, rejected, deferred, and unresolved conditions.
09
Verified-State and Readiness ViewShows current status, open conditions, and release eligibility.
PACKAGE 04 · 3 COMPONENTSProof and Output PackageConnects source evidence to agreed outputs.
10
Evidence Lineage and Proof ManifestTraces findings to their sources and produces the agreed manifest.
11
Agreed Generated Register or Register SetProduces the register or bounded register set named in the agreement.
12
Representative Controlled DeliverableProduces the agreed pilot output defined before configuration.
PACKAGE 05 · 2 COMPONENTSMeasurement PackageCompares the starting and finishing conditions.
13
Baseline AssessmentRecords the workflow and evidence condition at the start.
14
Closeout AssessmentRecords the same workflow at closeout.
PACKAGE 06 · 2 COMPONENTSFinal Pilot Decision PackageRecords the findings and next-step recommendation.
15
Final Outcome ReportReports scope, configuration, operation, findings, limitations, and results.
16
Deploy / Refine / Stop RecommendationExplains the recommendation and its evidence.
How success is evaluated
Measure what changes. Keep the gaps visible.
Compare the same workflow at the start and finish. Missing records, conflicting evidence, and unsupported status claims are findings to examine—not reasons to hide the result.
Source records and review responsibilities traceable
Agreed components demonstrated or delivered
Baseline compared with closeout; recommendation delivered
Scope boundaries
A defined commitment. Clear limits.
Included in the controlled pilot
One project. One selected workflow.
One participating organization—contractor, owner, EPC, operator, or enterprise program—one active project, one primary workflow or release gate, and an agreed evidence set and user group. The six packages cover configuration, testing, outputs, assessment, and the final recommendation.
The signed pilot agreement governs scope, commercial terms, formats, evidence classes, acceptance criteria, and deliverable acceptance.
Not included unless separately agreed
Production-scale expansion.
Organization-wide rollout, unlimited projects or integrations, open-ended customization or reporting, wholesale historical cleanup or turnover, professional approvals or certifications, 24/7 support, and deployment beyond the pilot environment.
Commercial structure
Scope first. Commercial terms second.
PILOT PRICINGEstablished after pilot-fit review.Scope and price agreed before kickoff.
Price depends on the records to process, rules to configure, connections to establish, and support and outputs required. The fit review establishes those needs before a proposal is issued.
Autodesk AECO Technology Partner Program member
01Operating boundary
Project, workflow, users, and control question
The selected project, participating users, workflow, and decision the pilot must support.
02Evidence profile
Classes, volume, formats, and condition
The types, volume, formats, and condition of project records determine intake and checking effort.
03Control complexity
Rules, identities, relationships, and authority
The checks, record matching, relationships, and review responsibilities needed for this workflow.
04Delivery effort
Connections, support, registers, and outputs
Agreed connections, review cadence, user support, registers, and final output formats.
Autodesk AECO Technology Partner Program member.png)