Last updated October 12, 2026

Section 3.9: Wrapping a Project and Wrap Reports

A production is finished when somebody writes down what happened. ABRAM does that part for you: a project can be wrapped, and wrapping it produces a report.

Open it from the project's three-dot menu with Wrap report. It is there before you wrap too, marked Running totals, so you can see cost or revisions drifting while there is still time to act.


1. What a Wrap Report Covers

The report is built from what the project already recorded, so nothing has to be re-entered at the end. It answers four questions:

  • What was delivered. The deliverables that reached their final state, the ones that did not, and how many were approved on the first pass.
  • Whether it finished on time. The planned wrap date against the actual one, and how many milestones were hit on schedule.
  • What it cost against what was budgeted. Actual cost, which is approved timecards plus expenses, set next to the budget the project started with, so you can state the gap as a percentage.
  • Who worked on it. Everyone crewed on the project, in which role, with their approved hours and labour cost.

Every one of those comes from records the project already holds, so the report is only as complete as the project was. Deliverables that were never marked complete, hours never approved and expenses never entered will be absent from it.

People who manage the project see the full report. Crew see their own hours, deliverables, first-pass approvals and skill credit, with no money.


2. Wrapping a Project

Wrapping is a deliberate step you take once the work is genuinely done. Before you wrap, it is worth checking:

  1. Deliverables are marked with their final status. See Section 3.8.
  2. Timesheets for the project are submitted and approved. The report counts approved timecards only, and timecard approval is a Studio plan feature. See Section 5.5.
  3. Expenses are entered against the budget, so the cost comparison is honest.
  4. Milestones are closed out. See Section 3.2.

To wrap the project, set its status to Completed in the project header. ABRAM seals the report with the wrap date. If you move the project out of Completed again, it is no longer wrapped.


3. What the Report Feeds

The wrap report is the last piece of evidence a project contributes to your organization's picture of who is good at what.

Skill records are weighted by how the work turned out, so a person's strengths are built from finished projects. What somebody typed into their profile on day one carries less weight than work ABRAM watched them deliver. Three things feed that picture:

  • Deliverables a person completed.
  • Hours logged against their tasks.
  • The wrap report filed when the project closed.

When a project has too few resolved deliverables or measurable figures to judge it fairly, skill credit is left unweighted, and the Skill credit card says so.

For each skill, the result appears on that person's Growth view of their Skills page as the hours logged against it, and a strength of Beginner, Intermediate, Advanced or Expert drawn from completed work. It is private to the person it describes. See Section 1.2 for how it sits alongside the skills a person enters themselves.

The practical consequence: the more projects your organization wraps, the more accurate crew matching becomes on the next one. See Section 4.2.


4. Reading the Cost Comparison

The cost-against-budget section is the part most worth reading twice. A wrap report on a project that came in over is the most reliable input you have when scoping the next job of the same shape. A run of wrap reports across similar productions will tell you where your estimates are consistently short.


5. Step-by-Step

  1. Open the project you are closing out.
  2. Confirm deliverables, timesheets, expenses and milestones are up to date.
  3. Set the project status to Completed.
  4. Open Wrap report from the three-dot menu and read it: Schedule, Budget, Scope, Skill credit and Crew.
  5. If records changed after the wrap, click Recompute to rebuild the report from current data.
  6. Check the Crew and Skill credit sections. Skill credit is what future matching will draw on.

Wrap Report Specification

Trigger

A project wraps when its status is set to Completed; the report is sealed with that date and unsealed if the status moves back. The report is reachable before wrap from the project's menu as running totals, and can be recomputed after sealing. People who manage the project see the full report. Crew see their own hours, deliverables, first-pass approvals and skill credit, with no money.

Report Contents

SectionSource
DeliveredDeliverable records and their final statuses, including first-pass approval
On timePlanned wrap date against the actual wrap date, and milestones hit on schedule
Cost against budgetApproved timecards and recorded expenses set against the budget the project started with
Who worked on itCrew on the project, their roles, approved hours and labour cost

Only approved timecards count toward hours and cost. Timecard approval is a Studio plan feature.

Downstream Effect

Skill records are weighted by project outcome. Three evidence sources feed a person's competency picture: completed deliverables, hours logged against tasks, and the wrap report at project close. Self-entered profile proficiency carries less weight than recorded completed work.

Competency Output

Per skill: hours logged, and a strength value from the set Beginner, Intermediate, Advanced, Expert, shown on the person's Growth view of the Skills page. It is visible only to the person it describes.