Eagar (Post-production) — module user guide

# Eagar (Post-production) — User Guide

The post-house module of Togra: a self-contained business workspace for a post-production facility — room bookings, client quotes, invoices and a client portal — kept deliberately distinct from the producer-side film books.

1. What Eagar is for

Eagar serves a different customer from the rest of Togra. Where the other modules run a producer's slate, Eagar runs a post-production house — the suites, mix stages, review theatres and ADR booths a facility books out, the client quotes it bids, the invoices it raises and the read-only portal it gives its clients. It is opt-in only: a producer group with no explicit module whitelist doesn't see Eagar; it appears only when switched on, for post houses (or producers running post in-house).

Because it's a separate business, Eagar's money is deliberately its own — post-house client invoices are distinct from the producer-side invoices in Airgead/Cearta, and they don't post to the film book of record. (Eagar grew from a standalone product merged into Togra; this guide reflects the post-house core.)

2. How the module is laid out

The Eagar sub-nav: Bookings · Rooms · Bids · Invoices · Client portal.

3. The surfaces in detail

Bookings (bookings.php) — a week-view calendar of suite / mix-stage / review-theatre bookings, per room per day — the facility's diary. Rooms (rooms.php) — the room catalogue: edit suites, mix stages, review theatres and ADR booths (the resources you book out). Bids (eagar-bids.php) — post-house client quotes with sectioned line items, tax-credit rebate maths and a status workflow; feeds the bid PDF. Invoices (eagar-invoices.php) — post-house client invoices: drafts, line items, payment logging and a status workflow — distinct from Togra's producer-side invoices. Client portal (client.php) — a read-only project view for outside clients showing the bookings and invoices for the projects they're associated with.

4. Eagar and the rest of Togra

• Self-contained, opt-in. Eagar is a parallel business vertical, off by default and shown only when whitelisted. It doesn't sit in the producer's development → production → rights flow.
• Money kept separate by design. Eagar's client invoices and bids are the post house's billing, deliberately named and kept distinct from the producer-side AR (Airgead/Cearta) and the film book of record (Cuntasaíocht) — a post house's books are not a production's books.
• Shared shell. It reuses Togra's auth, projects and file infrastructure, so a facility that also produces can run both, but the post-house surfaces stay in their own module.

Audit note (2026-06-07): Eagar is correctly scoped as a self-contained, opt-in post-house module. Its one potential point of confusion — invoices — is already disambiguated in the code (eagar-invoices.php, explicitly distinct from the producer-side invoices.php). No surface needed to move.

5. How this makes post-house work easier

• The diary and the catalogue in one place. Bookings against a real room catalogue means the facility's capacity is visible and double-bookings are obvious.
• Quote to invoice in one workflow. Bids carry the rebate maths and a status workflow, then become invoices with payment logging — the post house's commercial pipeline end to end.
• Clients see only their own. The read-only client portal gives a facility's clients their bookings and invoices without exposing anyone else's — no email back-and-forth.
• It stays out of the way. Opt-in and self-contained, so a producer who doesn't run post never sees it, and a facility's books never tangle with a production's.

6. Worked example

A post job. Define the Rooms (suites, mix stage, ADR booth); when a client enquires, raise a Bid with sectioned line items and rebate maths; on acceptance, book the rooms in Bookings; convert the work to an Invoice and log payments; the client watches their bookings and invoices through the Client portal.

This guide reflects the Eagar module as shipped (the post-house core). It is opt-in and distinct from the producer-side modules.