Your fields, your approvals,
no developer.
Onplana lets the people who run the work add the fields they report on, automate the follow-ups they chase by hand and take requests through a form, with an approval step wherever a person should decide.
Where the process leaks
From side spreadsheets and reminders to rules on the project
Without it
Requests arrive by email and chat, and someone retypes each one into the plan.
The fields your organization reports on live in a spreadsheet beside the project.
A reminder to chase an overdue task depends on someone remembering to send it.
An approval is a reply in a thread nobody can find at audit time.
With Onplana
A request form at its own link turns each submission into a task in the right project.
Your fields sit on the project, the task and the proposal, as columns you can filter.
A workflow notices the overdue task, waits a day and emails the people on it.
An approval step pauses the run until the people you named decide, and records who did.
What you get
Fields, rules and forms on the same projects
The fields describe the work, the workflows act on it, and the forms bring new work in, all on the tasks your Gantt and boards already show.
Fields in your own words
Add the fields your organization tracks to projects, tasks and proposals: text, numbers, currency, dates, dropdowns, checkboxes, ratings and more, each with the options you set.
Fields for one project
A project's managers add the fields only their work needs, without an admin, and a field that earns its place is promoted to the whole organization with its values kept.
Columns you can filter and export
Task fields are columns in the Grid view, grouped as organization or project fields. Filter on them, and the Excel export keeps each one as its type: numbers as numbers, dates as dates.
Workflows that read as a sentence
When something happens to a task, a project, a timesheet or a proposal, check a condition, wait, update the work, post a comment or send an email, per project or across the organization.
Approval steps with an inbox
Pause a workflow until the people you name sign off, first decision or everyone, and decide from an Approval Inbox with the run's timeline beside the request.
Describe it, then check it
Write what should happen in a sentence and the AI fills in the builder. Nothing is saved or turned on until you read the steps and save them yourself.
Request forms with no sign-in
Publish a form at its own link, behind a password if you want one. Each submission becomes a task in the project you pick and can start a workflow.
Signed webhooks to your systems
Send task and project events to your own endpoint, signed with HMAC-SHA256 so it can tell the call came from Onplana, with every delivery kept to check.
Built in, not bolted on
Onplana has twelve custom field types on projects, tasks and proposals, and a workflow can start from a task, a project, a list, a timesheet, a proposal or a new member, on the Professional plan and up. Each change a workflow makes to a task is marked with its name in the task's history.
From request to project
A front door for new work
Intake forms collect requests from people with no Onplana account, on the Professional plan and up. Where a request needs a decision before it becomes a project, the governance pipeline takes it from there.
A form lives at its own link, optionally behind an access password, and names your organization so visitors know whose form it is.
Each submission is kept with its answers and becomes a task in the project you chose, with the answers in its description.
The people and teams you list are notified, and the submission can start a workflow that tags, assigns or asks for approval.
On the Enterprise plan and up, a submission becomes a governance proposal in one click and goes through your review gates.
What it costs, and what it does not do
Custom fields, workflows, the Approval Inbox and intake forms are on the Professional plan and up. Signed webhooks are on the Business plan and up.
Fields hold values; they do not compute them, so a total or a score across fields is a report, not a field. A form asks the same questions of everyone who opens it. And custom fields are not part of a saved project template, which keeps the task outline and its timing.
Free, no account
Not ready to change the process yet?
Score how your PMO runs today, or start from a project plan template.
Questions about fields, workflows and forms
Which plan do I need?
Custom fields, workflows with approval steps and public intake forms are all on the Professional plan and up. Signed webhooks are on the Business plan and up, and turning an intake submission into a governance proposal is on the Enterprise plan and up.
Do I need a developer to set any of this up?
No. Fields are added from settings, workflows are built in a builder that reads as a sentence, and forms are built field by field. By default an organization's owners, admins and portfolio managers manage them, and a project's own managers can add fields for their project. A webhook is the one place a developer helps, because something has to receive it.
What kinds of fields can I add?
Twelve types: Text, Long text, Number, Date, Dropdown, Multi-select, Checkbox, URL, Email, Phone, Currency, Rating. A field belongs to projects, tasks or proposals, and dropdown and multi-select fields take the list of options you set, which keeps the values clean enough to filter and report on.
Our plans come from Microsoft Project with custom columns. What happens to them?
They arrive as fields on the imported project rather than on every project in the organization, so one import never fills everyone's Grid with its columns. Promote the ones worth keeping to organization-wide later; the values already entered stay attached.
Can the AI build a workflow for me?
It can draft one. Describe what should happen in a sentence and it fills in the builder: the trigger, a name and the steps. It never saves the workflow or turns it on. You read the steps, fix anything it flagged, and save; a new workflow starts paused.
How do I tell a change a workflow made from one a person made?
The task's History tab marks it with the workflow's name, under the person whose action set the workflow off. Anyone who can open the task can see it, and so can an agent reading the task's history.
Put the process where the work is.
Start free, then add your fields, your first workflow and a request form when your team moves up a plan.
Start free