Build a baseline you can compare the next request against.

Record what the client actually agreed.

Start with the agreement rather than rebuilding it from memory. Record its reference, date and revision. Describe the scope in terms you can compare with a later request.

• Deliverables: pages, templates, components, collections or other outputs.
• Acceptance criteria: what makes the agreed work complete.
• Revision rounds: what a round includes and its agreed limit.
• Exclusions: features, services and content not included.
• Dependencies: required inputs, access, decisions and approvals.

Separate fees, costs and unknowns.

Record the fee, currency and tax basis. Use net revenue consistently when reviewing contribution margin.

• Actual delivery cost: costs already incurred.
• Remaining forecast cost: estimated cost to finish the agreed work.
• Loaded hourly cost: your delivery cost basis for extra hours.
• Target contribution margin: a planning target, not a promise of net profit.

Do not count the same cost in actual and remaining amounts. If a forecast is incomplete, keep that uncertainty visible. A tidy margin is unreliable when its inputs are missing.

The additional-work pricing guide shows the difference between cost, net fee, tax and the client total.

Make dates and dependencies visible.

Record delivery dates and milestones with the conditions on which they depend. Clarify whether additional delivery days mean business or calendar days.

A request can add work, move a dependency or change the delivery sequence. Describe that effect rather than turning hours into days automatically.

• Which client inputs are outstanding?
• Who reviews or approves each milestone?
• How does a late input affect the schedule?
• Which dates are agreed and which are provisional?

Use the schedule-change process in the agreement. A revised estimate should not appear as an already-approved date.

Keep approval attached to the right revision.

Identify who can approve scope and later changes. Keep the approval date and written evidence or reference with the revision it relates to.

Compare a change with the approved baseline and prepare a new decision. Preserve enough history to explain the original understanding and what changed.

An agreed change, an invoice and a payment are different events. A manually recorded payment does not confirm receipt through your bank or accounting system.

Review the baseline before using it.

• Correct client, project and agreement reference.
• Specific deliverables, revision limits and exclusions.
• Visible dependencies and acceptance criteria.
• Clear fee, currency and tax basis.
• Complete, separate actual and remaining forecast costs.
• Consistent revenue and cost basis for the target margin.
• Agreed dates and a clear day basis.
• An authorized approver and approval evidence.

Then use the scope-change response process to assess the next request. If a key detail is unresolved, resolve it or label it before committing to a fee.

Keep a recovery copy.

Margvant keeps project records locally in the browser with a 50 MiB workspace safety limit. Clearing browser data or losing access to the browser can remove local records; browser storage is not a cloud backup.

Export a recovery copy and protect its password. Backup archives are encrypted, which does not mean the active browser workspace is encrypted as a whole. The planned Agency license covers five independently activated browsers/devices, each with its own workspace. It does not provide shared records or synchronization.

Read the privacy overview and license information for the current boundaries. The public demo lets you explore the process before purchase availability is enabled.