From contract intake to a continuously accurate man-day ledger, this guide covers agreement types, automatic recalculation, lifecycle, and the scope guard that keeps every engagement inside its contracted pool.
This guide walks you through creating a framework agreement for a consulting firm in PMAP and keeping its man-day budget true as work proceeds. You will see how the framework and project_based contract models account for man-days differently, how RecalcUsedManDays updates used_man_days whenever linked projects change, and how the remaining_man_days value and days-remaining countdown stay current without manual bookkeeping.
It is written for delivery leads, procurement owners, and program managers who govern external pentest capacity. By the end you can create an agreement with the right contract model, link projects to it, read the utilization gauge with confidence, manage the agreement through its lifecycle, and export the ledger for procurement review.
Inside this guide
- See where the agreement sits in PMAP and how the ledger is assembled before you touch a record.
- Choose between the framework and project_based contract types for the engagement in front of you.
- Create the agreement, set its man-day pool, and link pentest projects to it.
- Let RecalcUsedManDays keep used_man_days in sync as projects are created, updated, or deleted.
- Read the utilization gauge, the remaining_man_days value, and the days-remaining countdown.
- Lean on the scope guard so no project pushes the agreement past its contracted budget.
- Export the agreement ledger so procurement has a clean, auditable record.
Before you start
- A PMAP account with framework_agreement read permission, plus create, update, or delete where you will change records.
- At least one active consulting firm in the cross-tenant directory, since the firm picker shows only is_active firms.
- The target company inside your auth scope, because creation requires the company_id to be within the caller’s scope.
- The contracted man-day pool or one-off engagement scope you are recording, taken from the signed contract.
- Familiarity with how your pentest projects carry estimated_days and actual_days, since those drive the recalculation.
