Workflows Directory

Workflow templates for energy, engineering firms or law firms

Results

80 workflow templates, showing 49 to 72

  • Prebill exception review

    Before the billing attorney opens a prebill, the billing coordinator has every awkward entry marked: rates that differ from the firm's rate table, possible duplicates, entries outside the client's billing guidelines, unclear narratives and expenses without support, each sent to the person who acts next.

    Starts it
    Billing coordinator
    Brings
    export, notes, document
    Gets
    5 outputs
  • Privilege log entry check

    Before a draft privilege log goes to review counsel, the paralegal gets an entry-by-entry check against counsel’s approved format and role map, and a list of logged documents’ attachments with no entry. It checks metadata only: review counsel makes every privilege call and writes or approves every description.

    Starts it
    Paralegal
    Brings
    export, notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Project experience sheet

    For one finished project and one proposal, turn the firm's approved project records into a one-page experience sheet: the firm's role, the scope it performed, partners' work kept apart, and the record behind each line. Names, images and permissions still to confirm are listed for sign-off.

    Starts it
    Proposal lead
    Brings
    export, notes, pasted text
    Gets
    6 outputs
  • Project handover readiness check

    When a finished deliverable is ready for the team that will run it, the project manager brings one checklist against that team's own requirements: acceptance evidence, instructions, access, training, support owners and open items. The receiving owner accepts or names the conditions still to meet.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    6 outputs
  • Project intake and capacity review

    When a new initiative is proposed, the portfolio owner sees it scored on the business's own criteria beside the projects already committed, the delivery days it would use month by month, and what it would crowd out or push later. The owner accepts, defers or rejects it.

    Starts it
    Portfolio owner
    Brings
    export, notes, document
    Gets
    6 outputs
  • Project lessons review

    When a phase or a project ends, the project manager gets one blameless review: whether it achieved what it was for, how scope, schedule and budget moved and why, whether the success measures were the right ones, and practice changes for the team to choose, each with an owner and a follow-up date.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    8 outputs
  • Project scope baseline

    A project manager turns an approved brief into a draft scope baseline: the deliverables, what is excluded, the acceptance criteria for each deliverable, the constraints and the open questions for the sponsor. Nothing implied counts as scope until the sponsor says so.

    Starts it
    Project manager
    Brings
    export, notes, document
    Gets
    7 outputs
  • Project status report

    The lead of an internal project gets a status report the sponsor can read in two minutes: each workstream red, amber or green with the reason, what moved, who must clear each blocker, the decisions needed and the dates at risk. No milestone is called done without evidence, and the lead confirms every status.

    Starts it
    Project lead
    Brings
    export, notes, pasted text
    Gets
    7 outputs
  • Punch list consolidation

    The site manager gets the punch list for the next closeout walk as one list grouped by location and trade, with repeated entries merged, photographs attached and a proposed follow-up date for each open item. Nothing is assigned, closed or accepted.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    7 outputs
  • Receivables exception review

    The controller gets every short payment, unmatched or ambiguous receipt, possible duplicate and disputed invoice on one list, each with its evidence and a proposed next step, before anything is applied on a guess.

    Starts it
    Billing coordinator
    Brings
    export, notes, document
    Gets
    3 outputs
  • Reference check question plan

    After the interviews, the recruiter gets short reference calls aimed only at what the panel still could not establish, put to the referees the candidate named and agreed to, with a note sheet for each call that keeps the referee's own words. It gives no view on the candidate.

    Starts it
    Recruiter
    Brings
    export, notes, document
    Gets
    6 outputs
  • Referral source follow-up

    The day after a partner meets someone who sends the firm work, they have a follow-up draft and a list of every promise made at the table, by both sides. The draft uses only approved materials and nothing said in confidence; the partner checks it, chooses the next step and sends it.

    Starts it
    Partner
    Brings
    export, notes
    Gets
    5 outputs
  • Research plan for counsel

    Before an associate or paralegal starts on a partner's research question, they hold a one-to-two-page plan: the question split into sub-questions, the stated facts against each, the firm's own notes to read first, where to search and with what terms, and the gaps. Leads, not authorities: nothing is named from memory.

    Starts it
    Associate
    Brings
    export, notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Reviewer comments into one resolution list

    The owner of a document that came back from several reviewers gets one checklist: every proposed edit and comment, grouped by section, with clashes between reviewers set side by side. Every item stays open until the owner decides it, and the document itself is never touched.

    Starts it
    Document owner
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs
  • RFI review package

    The project engineer gets one packet for each request for information: the register entry, the question word for word, the drawing revisions and specification extracts it touches, earlier responses, and a numbered list of what is unresolved. No answer is proposed.

    Starts it
    Project engineer
    Brings
    export, notes, pasted text
    Gets
    8 outputs
  • RFQ clarification list

    A buyer sending drawings and specifications out for quotation gets one list of missing details, conflicting revisions and ambiguous tolerances, and a record of each supplier's answers. The buyer approves every message; the engineer settles every technical question.

    Starts it
    Buyer
    Brings
    export, notes, pasted text
    Gets
    6 outputs
  • Sales call preparation brief

    Your salesperson, partner or account manager walks into every meeting with a brief they can read in five minutes: who will be there, what has been said and promised so far, what is still open, and a plan for the call. Every line traces to your own notes or a public page, and anything inferred is labelled.

    Starts it
    Salesperson
    Brings
    notes, pasted text
    Gets
    7 outputs
  • Sales proposal preparation

    Your account executive answers an RFP in minutes, not weeks, with a proposal draft where every claim traces to approved company information and every gap is already a question for the right person.

    Starts it
    Account executive
    Brings
    document
    Gets
    4 outputs
  • Schedule recovery options

    When a committed milestone slips, the project manager brings the sponsor two to four ways back: what each changes, the dates it gives every later milestone and dependency, and the assumptions it rests on. The sponsor chooses; delivery leads confirm the dates.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    5 outputs
  • Scope change impact review

    When new work turns up in a project plan, the project manager gets one review: every deliverable compared with the agreed baseline, each addition marked approved or not, its estimated effect on effort, cost and the end date, and the decision the sponsor has to make. The sponsor accepts or declines each one.

    Starts it
    Project manager
    Brings
    export, notes, document, pasted text
    Gets
    6 outputs
  • Service visit work packet

    Before a planned visit to a turbine, inverter or terminal asset, the maintenance supervisor gets one packet built from the logs and approved scope supplied: reported symptoms, previous visits, open parts requests and access questions. It judges no condition and sends nothing.

    Starts it
    Maintenance supervisor
    Brings
    export, notes
    Gets
    7 outputs
  • Shared folder filing plan

    The office coordinator gets a plan for tidying a shared folder: a proposed folder structure, every file's move with its owner named, and the duplicates and access questions to settle first. Owners approve their own moves; nothing is moved, renamed or deleted.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    6 outputs
  • Site observation follow-up

    After a site visit, the visiting engineer and the project manager get one observation report: each field note beside its location, source photograph, drawing revision and any earlier register entry, a proposed follow-up owner, and the questions still open. It assesses no condition.

    Starts it
    Visiting engineer
    Brings
    export, notes
    Gets
    5 outputs
  • SOP exception capture

    Turn what your most experienced person does with the awkward cases into an exception register for one procedure. Once the owner approves it, every colleague handles those cases the way your best person does.

    Starts it
    Operations lead
    Brings
    notes, document
    Gets
    2 outputs