Queue division order changes for approval
When an owner sends a division order change, WebRun reads the signed request in DocuSign, compares the new decimals against the current ownership in Petrofly, and queues a clear before-and-after summary in Slack for a person to approve before any decimal interest in the owner record is changed.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I intake and approve division order changes automatically?
When an owner sends a division order change, WebRun reads the signed request in DocuSign and compares the new decimals against the current ownership in Petrofly, confirming the property still totals 1.0. It queues a before-and-after summary in Slack for a person to approve, so no owner record is changed until someone signs off on it.
- Every ownership change is checked to still total 1.0 before any edit
- A person approves each change, so decimals never move unreviewed
- The approver sees the signed source and a clear before-and-after together
Built for oil and gas operators · revenue accountants · land and division order teams · upstream producers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
petrofly.comin a real browser with your saved login - no setup, no API keys. -
1
DocuSign - read the change request
WebRun opens the signed division order change in DocuSign to read the new decimals. - Open the completed division order change envelope in DocuSign
- Read the owner, the property, and the new decimal interests being requested
- Note the reason for the change: a sale, an inheritance, a correction, or a name change
Done when The requested owner, property, and new decimals have been read from DocuSign.
-
2
Petrofly - compare to current ownership
WebRun opens Petrofly to compare the requested decimals against current ownership. - Open Petrofly and pull the current owner and decimal interests for the property
- Compare the requested decimals against what is on file and check the property still totals 1.0
- Flag any conflict, gap, or overlap the change would create, but make no edit yet
Done when The requested change has been compared to Petrofly and any conflict identified, with no record changed.
-
3
Slack - queue the change for approval
WebRun queues the division order change in Slack for a person to approve. - Post a before-and-after summary of the change to the approvals channel
- Show the current decimals, the requested decimals, and whether the property still totals 1.0
- Leave the change queued for a person to approve. Never edit the owner record on its own
Done when A before-and-after change summary is queued in Slack for a person to approve.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change an owner's decimal interest on its own?
No. WebRun reads the request and prepares a before-and-after summary, then queues it in Slack for a person to approve. No decimal interest in Petrofly is changed until someone approves the change.
How does it check the change is valid?
It compares the requested decimals against the current ownership in Petrofly and confirms the property still totals 1.0. Any conflict, gap, or overlap the change would create is flagged in the summary.
What paperwork does it read?
It reads the signed division order change envelope in DocuSign, including the owner, property, new decimals, and the reason for the change, so the approver sees the source alongside the before-and-after.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.