Skip to main content

Modify a grant or security

C
Written by Collier Kirkland

After a security has been added to the cap table, you may need to change it, whether to correct a data entry mistake or to formally amend the terms of the grant. Pulley's modification workflow lets you make those changes directly, without a support request, while automatically building the audit trail your legal team and auditors need to see.

Every post-issuance change is classified, logged, and optionally communicated to the stakeholder. Nothing changes silently.

This feature is available for a subset of Pulley accounts. If you don't see the Modify option in the Actions dropdown on an accepted security, this feature has not yet been enabled for your account yet.


Before you begin

A few things to have ready before you start:

  • The security must be added to the cap table.

  • Know whether your change is a clerical error or a true modification. The system requires you to classify each changed field before saving:

    • A clerical error is a data entry mistake, correcting a wrong number, fixing a name, updating an erroneous date.

    • A modification is an intentional amendment to the terms of the security. This distinction feeds directly into stock-based compensation (SBC) accounting accuracy.

  • Decide in advance whether you need to regenerate documents. If the change affects terms that are reflected in the signed agreement, you'll want to regenerate. This resets existing signatures and prompts the stakeholder to re-sign on the updated document. If the change is minor and doesn't affect the document content, you may be able to skip regeneration.

⚠️ If you do not regenerate documents during the modification workflow, you will be unable to do so later.


Modify a single security

  1. Go to Cap Table in the left navigation and locate the security you need to update

  2. Click into the security record

  3. Open the Actions dropdown and select Modify

    Why does this say "Modify"? The word choice is intentional. Selecting Modify signals that you're entering a structured, recorded amendment workflow, not making a casual field update. Any change made here is classified and logged automatically.

  4. Update the fields you need to change. Most fields on securities (including quantity) are now editable through this workflow

  5. When you're done making changes, click Update to proceed to the summary modal

  6. Review the Summary of Changes modal carefully. It shows every field you changed, showcasing each old value and its respective new value side by side. Nothing has been saved yet at this point

  7. For each changed field, select a reason:

    • Clerical error: a data entry mistake; no change to actual equity terms

    • Modification: an intentional amendment to the terms of the security

  8. Optionally, add a Note to the stakeholder. If you're notifying the stakeholder, they will see this note

  9. Choose your document and notification options (see below)

  10. Click Save to confirm

⚠️ The "Do not notify the stakeholder" checkbox is checked by default. Before saving, confirm whether you want the stakeholder notified of this change. If you're making a true modification or regenerating documents, you'll almost certainly want to uncheck this box before proceeding.


Document regeneration and stakeholder notification

Before saving, you may see up to two optional checkboxes. The document regeneration checkbox does not appear for every modification. It surfaces only when the change involves fields that affect document content. For example, updating the number of shares on a security will trigger it; correcting a stakeholder's name in a metadata field may not. If you don't see it, Pulley has determined the change doesn't require a new document version.

  1. Generate new stakeholder documents using the current template bundle: When checked, Pulley regenerates the agreement using the current template, creates an immutable new document version, and resets existing signatures. The stakeholder will be prompted to re-sign the updated document in their tasks.

    • When to check this: whenever the checkbox appears and the change reflects a true modification to equity terms or if an updated or new template was assigned and require signatures. It's strongly recommended you don't skip it in those cases.

    • When you might skip it: if the change is a minor clerical fix and you've confirmed the document content doesn't need to reflect the correction.

  2. Do not notify the stakeholder of these changes: This checkbox opts out of stakeholder notification. It is checked by default, meaning notification is suppressed unless you actively uncheck it. Unchecking this box requires you to acknowledge that you understand and accept responsibility for not notifying the stakeholder, including any compliance implications.

    • When to check this (suppress notification): for minor clerical corrections with no bearing on the stakeholder's equity terms, where a notification email would cause unnecessary confusion. For example, fixing a typo or formatting error in a field that doesn't appear in any signed document.

    • When to uncheck (send notification): any time the change could affect how the stakeholder understands their equity, particularly for true modifications to terms like exercise price, share count, or vesting schedule. Pulley will send the stakeholder an email indicating that a modification has taken place. If documents were regenerated, the email links directly to the re-signing task.

If you regenerate documents, the stakeholder will need to re-sign regardless of whether you suppress the notification email. The re-signing task will appear in their Pulley task queue. Leaving notification on gives them context before they encounter the task, suppressing it means they'll see the re-signing task without explanation.


Swap a template bundle

If a security was issued with the wrong template, if your company has updated its equity agreement templates since the grant was issued, or if a security was originally recorded without a template and now requires one, you can assign or swap the template bundle directly from the modification workflow.

This includes securities that were recorded without generating documents. For example, grants where signatures were captured outside of Pulley. Assigning a template through the Modify workflow will trigger document generation and allow you to capture signatures in Pulley for the first time.

  1. Open the security record and select Modify from the Actions dropdown

  2. In the edit form, locate the Documents section

  3. Click Swap next to the template bundle

  4. Select Swap with an existing bundle and choose the correct template from the list

  5. (Optional) In the Documents section, mark any existing documents attached to the grant or security as Archived if they are outdated or no longer valid.

  6. Proceed through the summary modal, select your reason, and save.

When swapping a template bundle, always check the box to generate new stakeholder documents. Swapping the template without regenerating documents means the new template won't be reflected in any signed agreement. The stakeholder will need to re-sign the newly generated document.

Note on template edits vs. template swaps: Swapping a template on a specific grant or security only affects that specific entry. If you edit the template itself (via Company → Templates), that change applies to only to new documents generated going forward. It does not retroactively update existing signed documents.


Modify multiple securities at once

For corrections that span many securities at once, such as a batch of grants imported with incorrect vesting start dates, you can run the same modification workflow in bulk spreadsheet mode.

  1. Go to Cap Table in the left navigation and select the security type (for example, Options)

  2. Click the Actions button and select Modify to open spreadsheet mode

  3. Make your changes across the relevant rows directly in the spreadsheet

  4. Click Save when done

  5. The summary of changes modal appears, listing every changed row individually with old and new values

  6. Apply a shared reason across all changes. This populates the reason field for every modified row at once. You can also add a note

  7. Choose your document and notification options and save

The same compliance workflow applies in bulk mode. Every change is classified, every change is logged, and the full amendment trail is maintained across all modified securities.

Bulk mode is particularly useful for correcting data migration errors or batch imports. If you've onboarded with a large number of securities that share a common error, this approach lets you resolve them all in a single action rather than security by security.


After you save

Once a modification is saved:

  • The changes are applied immediately to the security record

  • Every change is logged in the security's activity feed with the timestamp, the fields changed, the reason, and any notes

  • If you regenerated documents, the new document version appears in the Active tab of the security's document section section when editing the grant. Prior versions need to be moved to the Archive tab and will remain on record. When viewing the grant without entering the edit state, archived documents appear inline alongside active documents with an Archived label rather than in a separate tab.

  • If you notified the stakeholder, they receive an email alerting them to the modification. The email directs them to a page where they can review the specific changes and complete re-signing if required

  • If re-signing is required, a task appears in the stakeholder's Pulley task queue


Troubleshooting

I don't see Modify in the Actions dropdown

The modification workflow is only available for securities and grants that have been added to the cap table. If the security or grant is still in draft status, use the standard edit flow. If Modify still doesn't appear, this feature may not yet be enabled for your account.

The stakeholder says they didn't receive a notification email

Confirm whether the Do not notify the stakeholder box was checked before saving. If it was checked, no email was sent,but the changes are still recorded and the re-signing task (if applicable) will appear in their task queue.

The stakeholder's signatures were reset and they're confused

This is expected behavior when documents are regenerated. Pulley creates a new document version with the updated terms, which requires a fresh signature. The original signed document is preserved in the Archive tab and is not lost.


What's next

Did this answer your question?