Data requirements
A smaller, documented input makes the service safer and easier to audit.
The normal starting point is normalized project, task, and dependency CSVs. Nothing operational should be sent through the public website.
Accepted profile
Fields the working schema is designed around.
- project token
- task token
- owner role
- state
- period band
- dependency token
- blocker code
- evidence state
The field list is a planning profile, not a request to email data. The exact schema and secure exchange are agreed in writing after fit review.
Explicit exclusions
Data and authority we do not need.
No autonomous commitments to customers, unrestricted inbox access, forced portal migration, or claim that reminders alone change behavior.
Credentials, unrestricted system access, and unrequested free text are never part of the published plan.
Data lifecycle
Five visible handling stages.
- 01
Agree
Write down the permitted fields, purpose, owner, transfer, retention, and deletion rule.
- 02
Prepare
The buyer exports and normalizes only the agreed minimum input.
- 03
Validate
Schema failures and unknown values are rejected without inference.
- 04
Deliver
Portable outputs carry definitions, exceptions, and confirmation states.
- 05
Delete
Working data follows the written retention rule; the buyer keeps the final pack.
Field glossary
Shared definitions prevent expensive rework.
- Dependency
- A buyer-declared prerequisite between two tasks.
- Blocker code
- A closed-enum reason supplied by the buyer.
- Readiness
- A structural view of completed prerequisites, not a promise of go-live.
- Handoff
- A state change between buyer-defined owner roles.
- Evidence state
- Whether the buyer reports the required completion proof as present.
- Project token
- A random identifier with no customer name or reversible mapping.
A useful first conversation
Check the data boundary before discussing a plan.
Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.